How develop a Project Plan with Agile development methods?

How is it possible to develop a Project Plan, based on Project Management Best Practices, on a IT Development project following Agile methods? Is it possible to mix strong project management processes and Agile methods?

The Agile software development refers to a set of methodologies enabling cross-functional teams to collaborate to make requirements and solution evolve throughout a project. Based on this definition it is natural to expect impact on project plan. As requirements will evolve, how a Project Manager can build good estimation? How can he agree on a project scope? How to define deliveries?

As an adaptive and iterative methods, Agile enables small teams to plan tasks by tasks what will come up next. This gives really good short term planning overview. As it is based on strong daily communication within a team composed by developers and customer representative, the respond to change time is shorten. In theory, this will allow developers to build a complete customer orientated solution which should satisfy him. However it is necessary to discuss and set goals at the beginning of the project. The Agile concept also includes functioning principles we can find in Lean Six Sigma. These include error proofing, waste elimination, flow creation, add customer value and empowering workers. Using all concepts throughout project life will definitively increase customer satisfaction. Key principles need to be respected to reach your goals:

1. Active user involvement: working on day to day basis, they are consider as main contributors to the development team
2. Fix timescale for requirements evolution: even if the requirements shall evolve throughout the project, timescale shall be defined and followed
3. High-level requirement gathering session: this gives direction to the team
4. Small functionality development: develop small and increase direct benefits to customer. Releases should be based on incremental developement
5. Empower team to make decisions
6. Focus on small and more frequent deliveries
7. Test as soon as you can: testing shall be totally integrated to the project and release lifecycle
8. Approach shall be collaborative and supported by senior and top management

This does not answer your concern regarding Project Life Cycle adaptation and the way to build correct Project Plan integrating Agile development methods. Both methods are not incompatible. I would even say they can work very well together and each brings advantages. If you used to work with a Project Life Cycle based on Waterfall or gate approach model, it is true you will slightly have to modify it. Nevertheless it is possible to integrate Agile methods within these models with a bit of flexibility. As mention earlier in this article, Agile methods will bring to Project Manager detailed short term planning. However Project Management Best Practices will bring him long term planning, defined timescales (necessary to contain Agile flexibility) and proper project scoping. Main expected features should be part of the first project scope and even if they evolve throughout the project life, the key point is to get any change validated. By working with strong project life cycle, Project change process is key point to adapt to Agile Methods. How and Who validate/approve project scope/budget/timelines changes is the key of your adaptation.

To sum up Agile and strong Project Management methods can work together. Few advantages will be bring by Agile flexibility (short term planning, customer representative involvement...) and other by Project Management best practices (long term planning, scope definition, project change approval...). However it is necessary roles and responsibilities to be set up at the beginning. Change to Agile methods shall come to your organization with Top-Down approach and be supported by senior and top managers.

Thibaut