After so many years working and implementing Agile practices in various organizations, I have found that Agile is still new for many. Everyone wants to adopt it, but still.. is not able to adopt it! There is one major piece that people miss and i.e. “The TEAM”. The team that will be responsible to implement it. The team that will make it either success or failure.
Before we decide on to implement Agile, we need to look at the team that we plan to implement it in. An agile team does not consist of just any random set of people. It is not a group of developers, testers, project manager who meet for 15 mins to perform daily standup rituals. It is not the team that plays poker to do product sizing and then do sprint planning. It is not a team that has individuals supporting multiple agile teams.
Let us understand what makes
An agile team should consist of members with cross functional skill sets that makes the team independent to deliver without waiting on external teams to certify it’s success or failure. These members are dedicatedly allocated to one team, and as a rule, work together to deliver the common goal without moving in and out of the teams.
The team should also understand the core principles of agile very clearly and it should be ready to go beyond rigid organizational boundaries. It should understand very clearly that the software delivered at the end of the sprint should be a working software, that works not at the unit level, but also at the integration level. Above all, it should feel empowered to be Agile.
Once one understand the team and forms an independent team to deliver, then comes the next steps – Team Activities beyond Agile standards. I will cover this in my next post.