Sunday, June 10, 2018

Agile Teams in 2018

How can you create a team that is highly motivated, able to  prioritize on its own and deliver the most important user value in a constant pace indefinitely? 

The answer is - Practice AGILE.   

I have been part of so many successful Agile teams over the past decade,  learned and practiced many invaluable lessons throughout my career. Most recently I was part of an elaborative training with a highly effective team that practices these principles religiously.

These are the some of the most critical aspects to create a successful Agile team from my experience.

Unified Backlog
Keeping the single backlog of all activities is the number one priority. This includes business stories, tech items, even including all project mgmt, environment action items. These should be defined well so anyone in the team is able to work on it.

This reinforces the priority to the entire team. The transparency will enhance the trust in the process. The other aspect is to bring visibility to all non-business activities that need to take place to achieve an item in front of business folks.

Self-organizing teams
The team should be empowered to decide on the priority, methods and means to achieve the priority. As much as possible, external interferences should be reduced if could not be compeltely eliminated.

Team assessment
Anyone will obviously put forward his/her focus and efforts based on what is valued in the environment, on what basis performance is appreciated in the team. Unless we start valuing the collective achievements of the team, it will not translate into teams performance.

Individuals in the team should be able to trust each other. The common objectives should be repeatedly communicated to the team by the management. Instead of individual performance reviews, the peer reviews and overall team achievements should be considered for valuations.

This experience not only enhanced my trust in Agile but also gave me practical
handlers to follow Agile Manifesto Principles as much as possible even in a regulated bureaucratic environments.



No comments: