Implementing Scrum at Portfolio and Program level
The decision to implement Scrum at these levels could take some time, as there are two possible approaches:-
- create the new Scrum roles and integrate them into the current programme and portfolio architecture, OR
- redesign the programme and portfolio management organisational structure, replacing the existing managers or converting their roles into their Scrum equivalents.
What is recommended is that the new Scrum roles do not replace the traditional Program and Portfolio Manager roles, but work in conjunction with the established managers. The program and portfolio processes are essentially those of monitoring and measuring performance across projects, which can still be managed by the Portfolio and Program Managers, assisted by the Project Office. The Product Owners can manage the quality of the products and the Scrum Masters can deal with resourcing and Scrum compliance concerns.
Experienced Scrum Masters and Product Owners could fill these new roles and transfer the knowledge and skills to the PMO and the other roleplayers in the programme and portfolio space. The Scrum Master will have the responsibility of convening planning meetings and other meetings necessary at this level to fulfil the requirements of Scrum. The Product Owner will establish the Program or Portfolio Product Backlog and train all those concerned in prioritizing and refining the Backlog, as well as building the contents. This obviously is a project on its own, and includes implementing the recommended processes to support the new approach.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: