“Agile” has been a buzzy word for software companies since the announcement of the agile manifesto in Utah, back 2001. Many stories have been revealed on the success of adopting agile, and the “we are agile” phrase seemed to be customer attractive.
In adopting agile, one should ask the following: How can I adopt agile? What aids in such adoption? And, what barriers will I face along the way?
In this article, Chris Carroll describes the principles to be followed when adopting agile: You can’t adopt faster than your teams and individuals are motivated to adopt; You can’t adopt faster than you can learn; Adopt incrementally with regular reflection and adjustment; Prioritize changes which add most value; and call in someone who has done it before.
It thus seems that taking such decision of adopting agile will not be a quick run, it is a decision that will need hard work and considerable time until you gain its benefits. Well, it is “Change” you are trying to introduce here after all.
Joanna, a senior consultant at Excellian, describes three organizational aspects that help in adopting agility:
This can be in the form of the support of developer and team-led innovations, the interest in new engineering techniques such as DevOps, and the use of maturity models (i.e; CMMI) that may aid in developing software that meets your business goals.
As Jacob Orshalick states, transparency is about three quantities: openness, communication, and accountability. Thus, just be honest and avoid any turnarounds.
People Aren’t Asking for the Right Information
This is a result of not being transparent. Being transparent will enable asking for the right information, and avoiding the wrong information.
As anything in life, change is faced with challenges. Adopting agile is about adopting a new mindset towards software development. Based on Vin D’Amico, those challenges may be due to the fact that unlearning an old style you were skilled in and used to could be an uncomfortable route.
This can be even emphasized when we know that the top three barriers for adopting agile are:
- Ability to change organizational culture
- General resistance to change
- Trying to fit elements into a non-agile framework
Would it then be wise, for just the sake of being agile, to jump in with both feets and turning the software engineers’ world upside down?
The Art of Agile Development book goes to the point when suggesting that only one question matters in this case (i.e; adopting agile): will agile development help us be more successful?