Should agile projects have a project charter?

Agile Change Management Governance Information Technology

Mirko Blüming Senior Project Manager| Statkraft Germany GmbH Düsseldorf, Nrw, Germany

The project charter fixes project's objectives, deliveries, time, quality, etc. Changes are subject to formal change process. If a project charter is changed a lot, best practice is to stop the project. This sounds contradictory to agile principles where change is welcome. Therefore, not writing a charter is the natural consequence, isn't it? I think not - however the charter should focus more on processes and responsibilities rather than deliveries. What do you think?

Posted: Dec 1, 2018 1:39 PM

Sort By:

< 1 2 3 >

Alexandre Costa Scrum Master| Integer Consulting - Pictet technologies Loures, Portugal

Normally all projects have a business case and a project charter , the level of detail is the one that change according to the approach. Independent of waterfall or agile the investment must be justified and high lines of the project should be chartered in a document. Most times when the project team is recent is necessary to do a team charter to establish work principles, but that part should be made mainly by the team.

...

1 reply by Stéphane Parent

Aug 28, 2019 2:22 PM

Stéphane Parent

...

Agreed, Alexandre. I've had one-page charters for predictive-based projects.

Posted: Aug 28, 2019 2:18 PM (Updated by author: Aug 28, 2019 2:18 PM)

Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada

Aug 28, 2019 2:18 PM

Replying to Alexandre Costa

...

Agreed, Alexandre. I've had one-page charters for predictive-based projects.

Posted: Aug 28, 2019 2:22 PM

< 1 2 3 >

Please login or join to reply

Should agile projects have a project charter?

Sponsors

Newsletters