Product Operations Program ManagerBarcelona, Cataluña, Spain
Dear peers,
I am looking for recommendations for defining a template that includes the right information to be delivered to the Portfolio board. In short, it must contain information about the closing Project Phase and the request of next Phase.
If the template itself is not available, I am interested in learning which information should, in your view, be included in such a document.
I thank you in advance for your reactions. Saving Changes...
Sounds like you are looking for a Project Phase Closeout Report - I'm pretty sure there must be some examples in the templates section of this community.
The type of info I'd expect to see include:
- What business value did we deliver (vs. what were we expected to deliver)?
- How did we perform cost & schedule-wise relative to plan?
- What did we learn?
- What resources & funding do we need for the next phase, what key milestones will we achieve, and when
- What risks do we want to highlight with regards to the next phase
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I will write something obvious but I have to do that: information (format and content) will highly depends on your stakeholder analysis process where you will know your audience. In our case we have a simple stage gate process defined to help portfolio people to take decisions about programs and projects (kill, continue, hold). The information we publish is focused on that. In our case is mainly based on "value management" process we defined where we take into consideration for each program/project strategical/finance/quality data. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
The 'right information' is defined by the intended audience which can be garnered through stakeholder analysis. Whatever the chosen details and layout, focus on providing the information in an At-a-Glance format - one-pager.
Kiron presented a nice list from which to begin. Saving Changes...
You can refer to PMBOK to have an idea for the information you need to communicate at the end of each phase or project. However, you need to consider the organization and/or project specific needs as well. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
You always forward a slice of all your project information. For example, you could send your top three risks, top three issues, top three milestones, ... Saving Changes...
There might (or should be) pre-identified reporting requirements for the project, or standard reporting processes brought down from on-high (ie. the PMO) that will dictate what is and isn't included in such a report. The fall back is always the sponsor or customer who are pretty clear about what information they or the executive would want to see and/or hear. Saving Changes...
Community Champion
