Scrum Portfolio and Program Artefacts
In order to adhere to the principles of Agile, Scrum aligns the roles and activities at portfolio and program level with what happens within a Scrum at project level. In order to manage these oversight levels, two new artefacts, which are consolidations of the Product Backlogs, have been specified, the Program and the Portfolio Backlogs.
These two knowledge bases contain all the content of the subordinate Project Product Backlogs. The business rules for deciding if these user stories are “done” is the same; and there is a set of acceptance criteria that have to be met before a deliverable is accepted as complete.
Risk at Program and Portfolio Level
Program and portfolio management can be used as vehicles for risk management. The approach recommended is bottom-up, where individual scrum teams report on a risk identified during a Stand-up meeting or similar gathering, and this risk is passed up the reporting line
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: