Scrum for Product Owners

The Agile/Scrum is a project management methodology that is in sharp contrast to traditional project management.  That is because it starts with a different set of underlying precepts.

The Agile/Scrum methodology is a structured project management methodology.  It follows a prescribed process that includes Sprints and Scrums.

Within the Agile/Scrum project management methodology there are a set of meetings that are used to plan and manage the process.  Rather than analytical tools, this methodology relies heavily on the use of specific targeted meetings.

Story Cards, also known as Product Backlog Items (PBIs) are the technique used for documenting project scope, quality requirements, estimates and priority of the deliverables in an Agile/Scrum project.

The product backlog is the prioritized list of project deliverables.

The Scrum Team performs the project work conducted during a Sprint on an Agile/Scrum project.

The Scrum Master is the individual who is responsible for facilitating the Agile/Scrum Sprint process.

Sprint Controls are the project management tools that are used by the Scrum Master and Scrum Team to assess performance.

A clear goal or vision is essential to project success.  That is as true with Agile/Scrum as with traditional projects.

Preparing the Product Backlog is the first step in the Agile/Scrum Sprint methodology. It includes creating and prioritizing all the Story Cards.

To do the work of the Sprint, a Scrum Team must be assigned.

The Sprint is initiated with a Sprint Planning Session that organizes the work, estimates the effort, and initializes the Scrum Board and Burn Down Chart.

Sprint execution is the actual work of the Scrum team during the Sprint to accomplish the tasks needed to complete each Story in the Sprint Backlog.

The Sprint Demonstration is the formal meeting where the Scrum Team demonstrates to the Product Owner the performance of each deliverable that was created during the Sprint.

The Backlog Refinement is the update of the Product Backlog based upon what has been completed and what has been learned in a recently completed Sprint.

The Sprint Retrospective is a lessons learned meeting with a focus of identifying opportunities to improve the performance and management of the next Sprint. 

Project requirements management in an Agile/Scrum project is conducted using Story Cards and Backlogs.  The list of requirements is variable and is not finalized until the end of the project.

Stakeholder Engagement is the effort by the Product Owner to communicate with all affected stakeholders in order to identify potential requirements and provide project status.

The Product Owner writes the story cards, which document the requested scope of an Agile/Scrum project.

The Product Owner must regularly prioritize the Story Cards that make up the Product Backlog and at the beginning of a Sprint he or she must prioritize the Story Cards selected for the Sprint Backlog.

Release planning allows the Product Owner to manage the rollout of capability in order to obtain feedback and assess progress.

During a Sprint, the Scrum Team meets daily at a Scrum Meeting to provide status on progress.

Roadblocks are impediments that prevent the Scrum Team from completing Stories and tasks. The Scrum Master is charged with removing or creating a workaround for the Roadblocks.

Sprint Demonstration Planning ensures that the Sprint Demo meeting appropriately reflects the work accomplished by the Scrum Team.

Agile/Scrum is an organizational approach to project management and requires buy-in from senior management to be effective.

Organizational alignment is the activity needed to ensure the systems and processes within the organization support the Agile/Scrum methodology and do not undermine it.

Agile/Scrum projects are often used to implement both product line strategy and operational strategy.  They can be used with customer projects – but there are challenges with that approach.

Senior management also has the role of selecting projects that are suitable for the Agile/Scrum methodology.

When implementing Agile/Scrum, there are several process and project challenges that most organizations encounter and must be addressed.

There are common reasons for why an Agile/Scrum implementation initiative will fail.  Awareness of these failure points reduces the likelihood that an organization will fall prey to one of these.