Project Management

Please login or join to subscribe to this thread

Project charter & project management plan for Agile projects

linkedin twitter facebook   Agile   Business Case  
avatar
Suma Rao Senior PM - Portfolio and Project Management | Puma North America Newton, Ma, United States
Hello everyone, I am trying to find suitable templates for project charter and project management plan that are best suited for Agile Projects. I looked within PMI templates (and online) and could not find anything that fit the mold. Any help/sample from the experienced/practicing agile gurus would be greatly appreciated! 
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Suma -

No reason that you couldn't use an existing (lightweight) charter template for a project following an adaptive approach. Another option might be a Product Vision Board such as the one which Roman Pichler shared.

A PM plan is a bit more challenging as the information which we find in a typical PM plan might be distributed across multiple information repositories and radiators when a team is following an adaptive approach. It still makes sense for them to document their "ways of working" somewhere, but where and how that is done would be a team decision unless there were organization standards dictating this.

Kiron
...
1 reply by Suma Rao
Jun 13, 2024 10:15 AM
Suma Rao
...
Makes sense, thanks!
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
I know I will not answer your question but here comes the best recommendation I can give you based in my experience, not more than that. The first step to fail is to call <something> project. I am saying that in the terms of choose the right things for your initiative. Remember you have to select the approach (agile in this post), the process to support the approach (waterfall, incremental, iterative, iterative-incremental, etc), the method to support the process (Scrum, DSDM, etc) which in this case could be optional. If you select a method most of the deliverables will belong to the method. So, my recommendation, is taking a look to business analysis related documentation. And critical to understand is if you are using the concept of product based initiative to lead the agile process.
avatar
Keith Novak Tukwila, Wa, United States
Agile project management is a very generic term. If that is your search criteria, you're not likely to find much useful.

A better strategy might be researching the type of project since what works best differs by industry, or looking for templates of subsections of your plan like breaking down a problem into iterations or how to document a user story.
avatar
Jim Morgan Durham, NC, United States
Hi Suma--I agree with the advice that you can use a standard project charter. The only difference is that, ideally, iterative/incremental ("agile") projects do not have predicted dates and the budget is only for the first increment, if that.

Also ideally, there is no project plan in the traditional sense. You only need a list of requirements, often called a "product backlog." This includes not only end-user requirements, but also technical requirements needed to complete the user requirements, and what I call "business requirements," meaning deliverables other parts of the business need to support the product or service. No dates are required, but some plans will identify which requirements must be in the first released version--as few as possible, hence the term, "minimally viable product."
avatar
Suma Rao Senior PM - Portfolio and Project Management | Puma North America Newton, Ma, United States
Jun 07, 2024 3:20 PM
Replying to Kiron Bondale
...
Suma -

No reason that you couldn't use an existing (lightweight) charter template for a project following an adaptive approach. Another option might be a Product Vision Board such as the one which Roman Pichler shared.

A PM plan is a bit more challenging as the information which we find in a typical PM plan might be distributed across multiple information repositories and radiators when a team is following an adaptive approach. It still makes sense for them to document their "ways of working" somewhere, but where and how that is done would be a team decision unless there were organization standards dictating this.

Kiron
Makes sense, thanks!
avatar
Navaid Ur Rehman Additional Director / Project Management Expert /Writer /Trainer| Confidential (Pakistan) Karachi, Sd, Pakistan
Dear Suma,
I understand the challenge of finding Agile-specific templates for project charters and management plans. Traditional templates often don't align well with Agile practices. Most of the time we make following documents under initiation process
Project Charter
Project Stakeholder Register
so you use same template for agile project management methodology but in planning phase you may need to customize the template as required for agile methodology.

Look for project management plan templates that emphasize the Agile principles, such as iterative development, flexibility, and customer collaboration. They should include sections for the product backlog, sprint planning, roles and responsibilities, and release plans.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If nominated I will not run, if elected I will not serve"

- General William T. Sherman

ADVERTISEMENT

Sponsors