Scrum for Team Members

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 Sprint Retrospective is a lessons learned meeting with a focus of identifying opportunities to improve the performance and management of the next Sprint. 

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