What Should an Agile Project Charter Contain?
What makes a “good enough” project charter? Agile projects have a strong emphasis on people over process and verbal rather than paper communication. In contrast, many formalised methodologies require heavyweight project chartering/initiation documents that have to be completed in order to gain funding and approval to proceed with work.
Given this potential conflict, what should an Agile project charter contain – how much documentation is “just enough” to answer the key questions and what format should this information be presented in?
A number of commentators have attempted to address these questions:
Michael Lant in a blog post titled “How to make your project not suck” states that many projects begin without a clear statement of what success looks like. He states “ No industry, and no organization large or small, be it government, not for profits, start-ups or large multi-nationals seems to be immune to this gaffe., To be clear, not all projects suffer from it, but it is remarkably common.”
The clear definition he’s talking about is a well crafted Project Charter –
Larger projects seem to be better at this – perhaps because they tend to have more project management resources. Smaller projects, however, tend to overlook project charters, and if they do create a charter, it is rarely (if ever) referenced. In particular, and for a variety of reasons, smaller projects often take shortcuts, and a project charter is often one of the first things to go.
He provides some advice on preparing a project charter:
Separate out all of the legal mumbo jumbo and other extraneous information that is commonly found in a charter. These things are certainly important to the success of the project, but not usually to the people executing, so put those things it into a separate document. Now create a project charter that is no more than one page long, whose purpose is solely to provide a clear and concise definition of what success looks like for that project.
The project charter is the most important document you will create in a project and it is essential that all stakeholders participate in its creation. It balances intentions, aligns stakeholders and provides and agreed upon definition of what success looks like. Although the charter is only one page long, it can be a challenging piece of work to craft an effective document. It should take at a minimum a couple hours to create, and even for a small project, it could take an entire day. Its content must be arrived at by consensus amongst the stakeholders. This is all time well spent, and can save potentially endless days or weeks of revisions to realign the project.
A useful project charter contains three key elements:
1. Vision: The vision defines the “Why” of the project. This is the higher purpose, or the reason for the project’s existence.
2. Mission: This is the “What” of the project and it states what will be done in the project to achieve its higher purpose.
3. Success Criteria: The success criteria are management tests that describe effects outside of the solution itself.
In his post he goes on to provide an example of a charter, and advice on using the charter to set the direction of the project and keep it on track.
Martin Proulx provides a worked example of an Agile project charter on the Analytical Mind blog.
Another tool that is often used as part of the project charter is the Success Sliders. Debbie Schatz wrote an article describing this tool in the Mortgage Banking magazine – it is available on the CCPace website
The Sliders are set to indicate the relative importance of various “dimensions” of the project, and provide guidance when potentially conflicting decisions come about. Rob Thomsett describes the tool in detail in his book Radical Project Management.
Ryan Martens discusses the value of the one page A3 report. The A3 (named for the size of the sheet of paper, approx the same as two foolscap pages side by side) is a technique used in Toyota to distil the essence of a problem down to what can fit onto a single sheet of paper. He quotes John Shook’s article in MIT Sloan Management Review
1. “Establish the business context and importance of a specific problem or issue
2. Describe the current conditions of the problem
3. Identify the desired outcome
4. Analyze the situation to establish causality
5. Propose countermeasures
6. Prescribe an action plan for getting it done
7. Map out the follow-up process”
Allan Kelly provides a template for an A3 report
While the A3 report described by Shook doesn’t contain all of the elements of a project charter, the technique provides a simple tool concentrate the whole team’s focus a clear statement of what the problem is to be solved and what the solution needs to deliver.
What constitutes a good Agile Project Charter in your environment, are you able to share examples with the InfoQ community?
get 'er done
I think as a team you document as feels naturally necessary depending on your conditions. Are you working on a contract that requires a user manual? If so, write one. Do you plan on adding several people to the team over the course of a year? If so, perhaps starting a wiki with "how to get started developing" is a good thing to iterate on.
Either way, I'd focus more on being productive and get things rolling naturally and not worry so much about having a well defined process, just be agile and roll with the punches ;)
Re: get 'er done
There is a whole aspect of project governance that goes against the grain of the pure agilista, but never-the-less must be handled.
There are many benefits to using agile techniques and practices, even in 'hostile environments'. Project charters and like practices are just more stakeholder requirements.
Re: get 'er done
As to adding more people to your project incrementally I just wrote about that: agilepainrelief.com/notesfromatooluser/2010/06/...
Agile Pain Relief Consulting
Re: get 'er done
I don't see this as an 'agile' type of thing at all, this is just good common sense.
Re: get 'er done
I wrote one of the original articles to which Shane refers. I have found that a lightweight project charter is extremely helpful even for the smallest projects. Case in point: I am a member of technology networking group called Silicon Halton. We have about 150 members and we have several goals as an organization - one of which is to promote growth of the tech industry in our region. On Tuesday seven of us met to strategize how we are going to write our business plan. All seven of us are very experienced IT and project management people - on average at least 20 years of experience. At least two of the people are serious PMBOK practitioners. We've all written business plans, and we’ve all done a lot of project management. If any group should know what to do and how to do it, it should be this group – especially for a business plan that will likely be a mere 15-20 pages.
The group notion at the beginning of the exercise was to get'er done. Instead, we stopped and wrote a project charter for the project of writing the business plan. This may sound silly, especially give that the resulting project charter was five bullet pints and it took us three hours to write. In part, it took three hours because no one was familiar with creating a project charter like this and needed to learn how to do it. More importantly, however, the process for the most part took so long because while trying to create the charter we discovered some very different ideas as to what we were trying to accomplish. Seven bright, committed, experienced people and seven ideas of what success looked like. At the end of the exercise, we were all in agreement and knew what we were supposed to be accomplishing. In spite of initial resistance and a large degree of impatience on the part of some of the team members to “get'er done”, all were thankful that we didn't just start working on it. We now all agree on what success looks like and how to measure it. The few hours we spent up front likely saved us days of in-flight debate and rework down the line.
After decades of witnessing countless software projects struggle and sometimes fail because of simple misalignments that are easily resolved with a few hours of work up front, I don’t start any project now without a one page project charter. Since doing this, my success rate has improved dramatically.
Be careful that this does not accidentally restrict the project
For me, one of the key benefits of an agile approach is that there is an explicit understanding that _anything_ might change during the project. Typically this understanding leads to planning only short stories, sprints or iterations, and leaving decisions about further work until the first bits have been done.
An example from my experience. Despite the fact that some people made a fuss about an imagined final product, The _real_ goal of the first iteration was to produce something compelling enough to show unconvinced board members that the project was worth continued internal funding. To a large degree the _detail_ of what was produced was unimportant. Once approval was gained, the overall goals of the project changed again, this time to producing a technology demo for integration with a potential partner. And so on.
Even by the end of the second iteration showing the early versions to the stakeholders had already changed the product vision a long way from the initial plans which had been talked about so much.
At each stage, the outcome of the work for the iteration affected (often profoundly and largely unpredictably) the goals for the next piece of work. Attempting to set down any kind of charter with a longer expected lifetime than a single iteration would have been both a waste of time and a (potentially dangerous) distraction.
For me, "embrace change" is king. Don't attempt to guess, or worse enforce, the future.
Re: Be careful that this does not accidentally restrict the project
Agile Pain Relief Consulting
Nice! I've translated into french your article :
Jim Driscoll Dec 08, 2013