Skip to content

Agile Project Plan Template

December 14, 2012

A agile project is still a project and information that covers a E2E project is still required. How this information is created and communicated will also depend on the framework used (e.g. Scrum) as well as the overall software development cycle and gates in place (I am following Jim Highsmith SDLC [Envision, Speculate, Explore & Adapt, Close out] and I have tried to summarize it here: the big picture )

Although in draft version, I am trying to see how a project plan can be easily created and how key information can be communicated. One could spend hours writing such templates as so much information can be added. The goal of this document is to cover areas the team will need to take care; not to do the work for them. An example is “As a team, have you considered non-functional requirements?”

In the spirit of agile and common sense, creating the project charter should be a team effort including stakeholders (based on Liftoff Launching Agile Teams Projects) and adding some (excel) tools  such as Risks Management and Milestone Slip Chart. I have also added the idea of aligning the design with user stories and testing (see also: )

I will keep building over the Xmas period.

Here is a second draft including some excel tools: agile-project-plan-template-v1-2

This document includes Excel Milestone Slip chart tool,  Excel Risk and Issues management tool and Word Meeting Minutes tool (add actions, collect them in a table, set dates for you etc and I am quite happy to explain how they work.

(I have included reference to Lift-off and added a Scrum checklist).

  1. In the link that you have that says “Jeff Sutherland Proposed model” It looks like that is your own model did I miss something?

    As to the model that is linked, it looks a lot like so called “waterfall” — especially at the front. I think that is fine, however, and I’m glad to see the agile movement finally coming around for the need for planning up front. It still lacks prototyping however.


    • Thanks – I have updated my post so I refer to my other post.

      “waterfall”: yes it does look like but it isn’t. First the PO needs to build the business case (Envision) then he/she needs to get a team and explain the product and the team to do their sprint 0 i.e. work out what the stories are (Speculation). Then they can crack on with “sprinting”. The idea is to keep these first 2 natural phases short and based on interactions and individuals to get the team ready to sprint. “Natural” because that happens anyway even if this is not always formal and sometimes too short (rushed). One example of good up-front planning is used of “user story mapping”: I have found very useful to keep the end in mind (in production, tested including non-functional requirements).

      A long topic though 🙂

      Thanks again for your comments1 Much appreciated!

  2. Great article and I like the template. I’ve created something simple – but not specifically for agile. Perhaps your readers may be looking for similar… the microsoft excel project planning template I created incorporates a visual project Gantt. This is freely available for download at no charge at

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: