In the case of an organizational dimension, it was found that a cooperative
corporate culture and a collaborative organizational environment are the most influencing factors of Agile success (Chow and Cao, 2008; Hameed, Latif and Kholief, 2016). 1. Do you think that Agile has been universally accepted and followed within your organization? (a) If yes, can you please justify your answer with some supporting statements? (b) If not, where do you think that the acceptance is lacking? 2. Can you please explain how does the management and executive level people influence the success of your Agile projects? 3. Other than normal day-to-day development work, do you recognize that Agile has impacted any other organizational activities such as team distribution and internal reward system? 4. Has Agile brought any changes into the corporate culture of your organization? (a) If yes, can you please point out such changes? (b) If not, do you think that the current corporate culture is supporting agile? How? 5. What are all the future changes you expect to be brought into this dimension to sustain agility within your organization?
People dimension of Agile adoption
Next, I would like to move on to people dimension of Agile adoption. Within this aspect, literature identifies customer involvement and team capability as the main success factors regarding Agile (Darwish and Rizk, 2015; Hameed, Latif and Kholief, 2016). Moreover, Agile values customer collaboration over contract negotiation (Value 3). 1. How is the customer involvement is ensured throughout the Agile software development lifecycle within your organization? 2. How does your organization help to keep up the bonding between team and customers? 3. What are all the future practices to be implemented within your organization in order to improve and maintain the customer relationship?
Process dimension of Agile adoption
Understanding organizational and people aspects, I want to switch over to the process dimension of Agile adoption. Previous studies have identified that it is imperative to have a good project management process and project definition process for attaining success with Agile projects (Darwish and Rizk, 2015; Hameed, Latif and Kholief, 2016). Although agile encourages to welcome changes (principle 2), ill-defined project requirements would definitely impair the success of any project (Chow and Cao, 2008). 1. Can you please elaborate agile project requirements elicitation practices that are being followed (along with roles involved) within your organization? 2. How do you manage with the changes being introduced during the development process? 3. What are the future practices to be implemented in order to improve project scoping and requirements definition processes within your organization?