There is considerable confusion about the various roles within an Agile development team these days. There are many titles available with little explanation of how they relate to Agile development. Amidst the confusion, here is a primer on the basics of Agile Development Roles.

Whatever your thoughts on using Agile, it does promote better communication. Collaboration is a central tenet for Agile, and communication is required for proper collaboration. Sadly, many organizations form information silos around their divisions and teams. This happens for many reasons, but it is a significant issue that should be addressed for any business that wants to stop wasteful development practices.

Over the years, I developed a series of training documents and videos for my teams that discuss Story Point estimation. They discuss how they are used and why they are essential. Since I did a previous post about Velocity, it is crucial to lay the groundwork for Story Points so that teams can estimate adequately.

Team velocity is a crucial tool for effective project management. Not only does it track team delivery, it also allows for the projection of delivery potential.

The edict is passed, and now your organization is going to be Agile. Congratulations! What does that mean? For most, this means implementing morning stand-ups, user stories, acceptance criteria, and story points. It doesn’t end there, though. The rest of your organization needs to adapt as well.