Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
This exchange of views is very interesting.
In projects where the development approach is adaptive, is there a "Project Charter"?
...
1 reply by Kiron Bondale
Jan 13, 2022 1:10 PM
Kiron Bondale
...
Definitely Luis!
It might not be called a Charter, but might be a Project or Product Canvas or something similar.
As the main purpose of a charter is to authorize the project's existence and to define its "North Star", it is valuable regardless of the delivery approach or life cycle approach but the format, structure and content will be context-dependent.
This exchange of views is very interesting.
In projects where the development approach is adaptive, is there a "Project Charter"?
Definitely Luis!
It might not be called a Charter, but might be a Project or Product Canvas or something similar.
As the main purpose of a charter is to authorize the project's existence and to define its "North Star", it is valuable regardless of the delivery approach or life cycle approach but the format, structure and content will be context-dependent.
Kiron
...
1 reply by Luis Branco
Jan 13, 2022 2:02 PM
Luis Branco
...
Dear Kiron
Thanks for answering my question
In adaptive approaches it will be the vision (statement) that is different from the project charter
Or am I mistaken?
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Jan 13, 2022 1:10 PM
Replying to Kiron Bondale
...
Definitely Luis!
It might not be called a Charter, but might be a Project or Product Canvas or something similar.
As the main purpose of a charter is to authorize the project's existence and to define its "North Star", it is valuable regardless of the delivery approach or life cycle approach but the format, structure and content will be context-dependent.
Kiron
Dear Kiron
Thanks for answering my question
In adaptive approaches it will be the vision (statement) that is different from the project charter
Or am I mistaken?
...
1 reply by Kiron Bondale
Jan 14, 2022 7:51 AM
Kiron Bondale
...
Luis -
The essence of the charter is unlikely to be different, but the level of detail and specific content might change depending on the delivery approach but also on a variety of other factors including organization standards, the scale of the project and so on.
Kiron
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Hi Luis,
regardless of vision, budget, timelines, or the understanding of the final product, the team is working on something they expect their employer to pay them for.
The charter is basically saying 'we will pay you for your work'. So yes, also an agile team needs a charter to work on something, be it a project or ongoing product development.
I agree that the charter rarely changes, even if the stakeholders who approved the project leave the organization. The project may diverge significantly from the original charter however.
Once the high level charter is approved, the details of a project become some type of in-work change package documentation under configuration control and governed by change boards. The details of that change package become the working parameters of the project, not the charter itself.
There is a significant change to scope or division of responsibility? That must be approved by the appropriate stakeholders as well so while the originating approval document for the project may change, the governance process for approved work simply moves to different forms of documentation intended for change management processes. Saving Changes...
Dear Kiron
Thanks for answering my question
In adaptive approaches it will be the vision (statement) that is different from the project charter
Or am I mistaken?
Luis -
The essence of the charter is unlikely to be different, but the level of detail and specific content might change depending on the delivery approach but also on a variety of other factors including organization standards, the scale of the project and so on.
Kiron Saving Changes...
Michael De LuigiPM Trainer| SGO Business SchoolJona, St. Gallen, Switzerland
Thank you all for this lively and inspiring discussion! I took that particular phrase out of the 'Agile Hybrid Project Pro Micro-Credential' training and I must admit that it doesn't sit well with me.
To me, a project charter is a living document. It represents the current outline of the project as approved by the authorised decision-makers. Over time, some features covered by the project charter might deviate from the original document signed at the outset and adapt over time - e.g. the deliverables, the budget, the timeline or - alas - even the project manager! I think that's a pretty normal process these days.
To me, an updated project charter is not only the constitution (even those evolve!) of a project that assures a common understanding throughout its (sometimes even tumultous) lifetime. It is also a high-level summary that is very useful to quickly familiarize people not (yet) involved in the project with the endeavour. This is particularly the case for project team members.
In my PM classes, I regularly ask participants who have already worked in projects whether they have been acquainted to the project charter in their projects, and the amount of people denying that is just mind-blowing ( 50%).
I think that's an important opportunity wasted for good communication and providing context, also for other stakeholders than only the project team. Or is there a reason that is beyond me why a project charter should be kept confidential?
In order to be an effective tool of communication, the project charter should be up to date. This is why would like to see the phrase "The project charter is the only document that never changes throughout the project." changed in PMI documents.
...
1 reply by Stéphane Parent
Jan 14, 2022 8:45 AM
Stéphane Parent
...
I guess the reason PMI states the charter never changes is because, like others have mentioned, changes to a charter usually means a new project.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Jan 14, 2022 8:02 AM
Replying to Michael De Luigi
...
Thank you all for this lively and inspiring discussion! I took that particular phrase out of the 'Agile Hybrid Project Pro Micro-Credential' training and I must admit that it doesn't sit well with me.
To me, a project charter is a living document. It represents the current outline of the project as approved by the authorised decision-makers. Over time, some features covered by the project charter might deviate from the original document signed at the outset and adapt over time - e.g. the deliverables, the budget, the timeline or - alas - even the project manager! I think that's a pretty normal process these days.
To me, an updated project charter is not only the constitution (even those evolve!) of a project that assures a common understanding throughout its (sometimes even tumultous) lifetime. It is also a high-level summary that is very useful to quickly familiarize people not (yet) involved in the project with the endeavour. This is particularly the case for project team members.
In my PM classes, I regularly ask participants who have already worked in projects whether they have been acquainted to the project charter in their projects, and the amount of people denying that is just mind-blowing ( 50%).
I think that's an important opportunity wasted for good communication and providing context, also for other stakeholders than only the project team. Or is there a reason that is beyond me why a project charter should be kept confidential?
In order to be an effective tool of communication, the project charter should be up to date. This is why would like to see the phrase "The project charter is the only document that never changes throughout the project." changed in PMI documents.
I guess the reason PMI states the charter never changes is because, like others have mentioned, changes to a charter usually means a new project. Saving Changes...
