Initiative, Release and Governance
Initiative/Release Life Cycle
When an Initiative (or Release) is created, it is initialized as a “Concept”. It could be added to a Portfolio where it can be prioritized against other Initiatives/Releases.
When the Concept is confirmed, it can become an official project: it is automatically done by passing one Governance Milestone, usually the first one but not mandatory.
An Initiative/Release can be marked as “confidential”: its view will be restricted to authorized persons. It can also be archived either because the Concept will never be implemented or the project is completed.
A Portfolio is a way to group Initiatives under the supervision of a Portfolio Manager so that synergies can be obtained.
An Portfolio type is used to categorize the Portfolio. The default types are listed below:
- Program: a group of Initiatives which aims at a common goal,
- Portfolio: a generic group of Initiatives.
See Portfolio page for a list of all the standard Portfolio's attributes.
Governance Life Cycle Process
The life cycle of each Initiative or Release is governed by a Life Cycle Process (selected initially during the creation).
A Life Cycle Process is a set of Milestones that support the company governance by providing validations/checkpoints.
Each Milestone has to follow a fully configurable process to be approved:
- It is first “submitted for approval” by the Initiative/Release Manager
- Then either the Request need to be reviewed and validated (mainly to ensure completeness and adherence to the Company's Governance process) Or it directly enter “Approval part”.
- If the Request was approved, either there is a list of Approvers who get notify that their Votes are required or not. If no approvers are defined, the Milestone status is set to the default status of the Milestone (most probably “Accepted”)
- The Approvers accept or reject the Milestone Approval
- And finally, a PMO Officer needs to confirm the decision so that the Milestone can effectively be accepted or rejected.