AgilePalooza - Atlanta 2010
AgilePalooza was in Atlanta on February 26, 2010 and it was a great event. It confirmed a lot of concepts I have been trying to push at work lately and was comforting to know the Agile community supports what myself and a co-worker have been working on. Here are the top 5 important Agile principles, as I see them.
1. “Make sure everyone understands what they are doing and not just focusing on tasks.” To be Agile it is important that each individual understands the goals and direction of the company and how each individual’s responsibilities fit into the company’s goals and direction. When a Software Development company focuses on project to project and the projects are very different it is very challenging to adhere to and enforce processes because things are always changing. However; in Agile, if everyone has a clear understanding of what goals they are working towards it makes their contributions much more meaningful and helps boost morale. It gives purpose to the work.
2. “Agility with discipline.” This is a phrase that was brought up often during AgilePalooza. You cannot call yourself Agile unless you have enough discipline to stick with the processes as defined by Agile. Some software companies claim to be Agile but really do not understand what Agile is and do not follow all of the Agile methodologies. Just because you have a daily “stand-up” meeting does not mean that you are Agile.
3. “Predictive results come from predictive input.” During AgilePalooza it was reiterated over and over that a continuous, well-groomed, product backlog is essential. To be able to have predictive velocity you must have consistent and constant input, the backlog. You need a product owner who can keep the backlog full.
4. ”Need to avoid the seagulls.” If you are familiar with Agile you understand what chickens and pigs are. If not, read this article http://en.wikipedia.org/wiki/Scrum_(development). Seagulls are the people who fly in and poop on things and then fly away. You need to manage seagulls so that they do not mess up the rhythm and velocity of the team. The Agile team needs to remain focused.
5. ”Remove impediments.” You must have someone who can remove impediments or else you will not be able to run an Agile team. This can be a Scrum Master or another manager or even a Project Manager. Regardless of who it is, someone has to have the authority to remove impediments from the team’s view.
If AgilePalooza is coming to a city near you I would strongly recommend attending. It is a very small fee and you will walk away with many ideas of how to improve your processes even if you already practice Agile.