Adherence to agile manifesto and agile principles is the essence of agile. Agile teams choose either a popular methodology (e.g., Scrum) or put together a methodology that follows agile principles and practices. In reality it takes several months for agile teams (either collocated or distributed) to mature and reach the other end of the spectrum.
Last month, I came across an interesting question from one of my friends in an agile conference. He asked, “How does a distributed agile team start on a project and make progress in delivering results?” I said, “It depends”, and paused for a while before discussing it at length.
The next day, I reflected on it again, recollected a series of incidents from some of my initial agile projects and created a visual on how my project matured over a period of time. Also, I thought about what I would do differently if I were to start all over again. Let me share those visuals and perspectives in two blog posts.
During the past decade, I have seen many agile projects transitioning through these levels as shown in this self-explanatory diagram. By and large, this schematic presents the past.
Looking back, my findings are,
Ideally, we must merge the first three levels and initiate agile projects swiftly so that the way we develop software is streamlined.
What do you think?