For project managers who are training in SCRUM agile, here is a scrum methodology diagram for reference:
Scrum Agile Methodology
- User stories (and tasks, features, etc.) are written and added to the product backlog. These can be written by the team, the project manager, project owner, or any other stakeholder.
- The Product Owner (or project manager) organizes the product backlog.
- During a sprint planning meeting, user stories are selected for design and development and implementation and prioritized into the sprint backlog by the product owner.
- The team works on the items in the sprint backlog with the Scrum Master helping to unblock team members.
- Every day the team meets for a daily scrum meeting where they discuss what they are working on and if they are blocked or stuck on anything.
- At the end of a sprint, there is a retrospective to see what went well and what needs to change.
- Then the cycle begins again with new user stories added, existing user stories selected for development and so on.
What is the Product Backlog?
The product backlog is the list of potential user stories that can be worked on. The list can contain tasks bugs and features as well.
It can be organized by priority, by estimated dollar value, by urgency, by number of customers who would be happy, or by some other criteria.
What is a User Story?
In contrast to traditional project management where work packages are worked on, in agile you have a user story. Each user story includes the user persona or actor. It also includes what they would like to be able to do in the system.
Examples of user stories
- As an author, I would like to write a book (for a word processor)
- As the system administrator, I would like to view all performance metrics of our active systems
- As an educator, I want to create a course outline
- As an teacher, when creating a course outline, I want to include PDF presentation files and images