AgilePalooza was in Atlanta on February 26, 2010 and it was a great event. There were sessions covering various aspects of what an Agile team is and how to implement Agile practices. Here are the top 5 important Agile principles, as I see them, from AgilePalooza.
1. “Make sure everyone understands what they are doing and not just focusing on tasks.” It is important that each individual understands the goals and direction of the company as well as how each individual’s responsibilities align with the company’s goals and direction. Software Development companies which focus on project to project and the projects are very different have a hard time adhering to and enforcing processes as things are always changing. With Agile, if everyone has a clear understanding of what goals they are working towards their contributions become more meaningful and morale is boosted. It gives purpose to the work.
2. “Agility with discipline.” This phrase was brought up often during AgilePalooza. You cannot claim to be Agile unless you have enough discipline to enforce the processes as defined by Agile. Some software companies believe they are Agile but do not understand what Agile is and do not follow all of the Agile methodologies. Just having a daily “stand-up” meeting does not mean that you are Agile.
3. “Predictive results come from predictive input.” During AgilePalooza we were reminded over and over that a continuous, well-groomed, product backlog is crucial. To have predictive velocity you must have consistent and constant input into the backlog. You need a product owner who can keep the backlog full and active.
4. “Need to avoid the seagulls.” Those familiar with Agile understand what chickens and pigs are. If not, refer to http://en.wikipedia.org/wiki/Scrum_(development). Seagulls are those who fly in and poop on things and then fly away. You need to manage seagulls such that they do not mess up the team’s rhythm and velocity. The Agile team must remain focused.
5. “Remove impediments.” You must have someone who can and will remove impediments or else you will not be an Agile team. This can be done by a Scrum Master or another manager or even a Project Manager. Regardless of who it is, someone must have the authority to remove impediments from the team’s view.
When AgilePalooza comes to a city near you I would recommend attending. You will leave with many ideas of how to improve your processes even if you already practice Agile.
No related posts.
