Scrum is a process that is based on agile (Agile Methodology) methodologies. It is built as a process that functionally makes agile actionable. It does this through a series of artifacts, ceremonies amd team structure:
Artifacts
- User Stories (User stories guide project goals): The unit of work that needs to be done. It's written with a specific format so as to make the work focus on the user rather than the engineering solution.
- Backlog: A list of all the user stories - prioritized and pruned by the Product Owner regularly.
- Sprints: A set period of time for a complete deliverable to be completed within. Usually 2 to 4 weeks long.
Ceremonies
- Daily Scrum (Standup): As short daily meeting (15 min. max) where the team syncs up. The focus is on the progress of the stories, not the team member.
- Sprint Planning: An all hands meeting where the top of the backlog is pulled into the sprint.
- Sprint Review: At the end of the sprint, an all hands meeting where the client gives feedback on the previous sprint's delivered work.
- Sprint Retrospective: An all hands meeting where the team discusses what worked and what didn't in the previous sprint. It's a vulnerable time to WOOP (WOOP Process) and make real change.
Team
- Product Owner: The person that is in charge of the direction of the product. They interface with customers, analyze markets, maintain the backlog and work closely with the Scrum Master to gauge the project's scope, budget and timeline.
- Scrum Master: The scrum master is in charge of the axctual process of work being created. They are the team's resource for fixing problems, both internal and external. They own the ceremonies, but don't necessarily run them individually.
- Development Team: The rest of the team. Engineers, designers, QA, etc.
Citations
#DPM #toolong