A Common Problem During Agile Adoption
Over the last decade or so, there has been widespread acceptance and adoption of agile development practices—particularly in the technology world. Agile development methodology provides avenues for increased collaboration among team members by means of frequent meetings with team members and stakeholders. It reduces waste by allowing for frequent course corrections and adjustments. Best of all, it allows for transparency on what is being done—and is delivered by encouraging regular demonstration sessions.
However, organizations that adopt agile methodologies often go through a period of frustration, learning and adaptation before becoming stable in the new paradigm. While this is entirely understandable and justified, organizations have been trying to reduce this learning curve and frustration. This article focuses on one common problem that is encountered during agile adoption—and how it can be remedied.
An enthusiastic start
The adoption of agile methodologies is usually preceded by training that is imparted to all team members on the basics of the framework and its ceremonies. Scrum masters are trained, and team names are chosen. A development team that was following the waterfall model transforms itself into small agile scrum teams, each with a different focus. Dependencies between teams are understood, and scrum of scrums are set up with team
Please log in or sign up below to read the rest of the article.