Change in Portfolios & Programs
Change in portfolios and programs is inevitable and must be properly managed. The impact of changes is frequently wide spread and involves a variety of stakeholders in an organization. The request for modifications begin with the change request, the primary instrument used for initiating, gaining approval and recording actions. The change request form needs to be completed by the stakeholder proposing the adjustment(s).
The program or portfolio manager makes sure that the approved change process is implemented so that there are no adverse impacts on constraints and/or scope. Prior to changes being approved, the project teams collaborate to analyze the impact of the recommended amendment. Lastly, the sponsor provides the final feedback with regards to the enactment of accepted change requests. Changes that have been approved should never adversely impact the delivery of value or expected benefits for an organization.
The main objective at the program level is the focus on business objectives. The goal is to ensure that the organization meets its objectives: benefits realization, project interdependencies and structured change. At the portfolio level, the focus is on enterprise value. Goals at this level are strategic objectives, economic costs and corporate risk. Finally, at the project level, which is more familiar to most, is aligned toward defining business capabilities within the constraints of time, cost and resources.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios