Becoming agile through mindfulness 2 Assignment

Becoming agile through mindfulness 2 - Assignment ExampleThere are two types of mindfulness organizational and individual. This classification is do to provide a clear distinction between the abilities of an organization or an individual. Individual mindfulness entails an individuals ability to regularly come up with new categories in the interpretation and perception of the universe. Organizational mindfulness, on the other hand, refers to the cognitive aspects used to solve problems on an organizational level (Butler and Gray, 2006). Organizational mindfulness entails the continuous refinement and scrutiny of existing expectations depending on the ever changing environment. Such refinement and scrutiny ensures that uncertainties are handled accordingly (Weick and Sutcliffe, 2001). The following are the percentages that confound up organizational mindfulness. Reluctance to Simplify Interactions this refers to the ability of an organization to recognize complex dish upes and si tuations and find ways to view the problem from different angles (Nagle, McAvoy & Sammon, 2011). An organization that employs this comp sensationnt is able to identify different ways of handling complex issues, and situations that occur during the software development process. This is because each(prenominal) the views and opinions of the participants of the software development team are highly valued (Nagle, McAvoy & Sammon, 2011). For an organization to employ this component during the development, one of the following factors has to be included in the development process 1. The participants should be free enough to stock their ideas and opinions in regard to the development process. One of the participants of the Cork workshop talks of the aspect of incorporating the customer in the development process. When explaining to her colleagues about how the customer makes changes to the development process, one of the other participants questions whether there was a way to avoid all t he changes imposed by the customer. He asked, So there was not stopping that?(2107). This participant was relate with the organizations over flexibility towards the customer. However, he was interested to learn whether the other participant felt the same. Being mindful of his colleague, he did not impose his opinion on her instead he gave her a chance to express herself. After being given the chance to speak, the female gives her view. She says No, actually its a very cocksure thing, thats to be welcomed because actually its put our project in front of the chief executive its put their clients role at heart the organization in a higher level of importance and is actually informing the organization better about what they do, so those changes are actually quite a nice (2108). 2. Analysis of customer requirements or any requirements should be prolonged. This goes a long way to ensure that all participants or stakeholders of a development process are fully aware of the current state of affairs. Discussions that are held during the course of the development process should be conducted in such a manner that all those who do not fully grasp the situation are able to do so by the end of the discussion. This involves clarifying issues to persons who may not deduce any technical jargon used. During the workshop held in Cork many