Welcome to Gossamer, this is where we SCRUM!This is where we get together to work as a team. Guidelines include:
- Courage—especially when it comes to solving hard problems
- Commitment to the shared team goals
- Respect for your team members
- Openness about work and any challenges that might come up
When you're ready you may sign in at the top right of the screen! See you inside.
What is SCRUM?¶
Scrum is a framework for managing software development. Scrum is designed for teams of approximately 10 individuals, and generally relies on two-week development cycles, called "sprints", as well as short daily stand-up meetings. Approaches to scale Scrum to larger organizations include Large-Scale Scrum and Scrum of Scrums.
Who does what in Scrum?¶
The Scrum framework is defined by three core roles: the Scrum Team, the Scrum Master, and the Product Owner.
The Scrum Team is exactly what it sounds like—the people working together to deliver products. Scrum Teams are given the freedom to organize themselves and manage their own work to maximize the team’s effectiveness and efficiency.
The Scrum Master is the team’s resident Scrum expert and facilitator, responsible for helping all team members follow Scrum’s theories, rules, and practices. They make sure the Scrum Team has whatever it needs to complete its work, like removing roadblocks that are holding up progress. (Don’t worry—if you’re new to Scrum, nobody’s going to ask you to be the Scrum Master right off the bat.)
The Product Owner is accountable for the work the team is supposed to complete, whether they do much of that work themselves or delegate it to other team members. The Product Owner is always a single person and not a committee; while they can take input from others when it comes to their decisions, final decisions ultimately come down to the Product Owner.
How is time organized?¶
The Scrum framework is marked by five Events (these include meetings and longer blocks of time). These are the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
A Sprint is a specified time period (usually ranging from one week to one month long) during which a Scrum team produces a product (like a big project, report, or something like an app). The work to be done during a Sprint is planned out during Sprint Planning, with help from the entire Scrum team. During this meeting, the team clearly defines deliverables for the Sprint and assigns the work necessary to achieve that goal.
The Daily Scrum (sometimes called a Stand-Up or Daily) is a 15-minute daily meeting where the Scrum Team has a chance to get on the same page and put together a strategy for the next 24 hours. Work from the previous day is analyzed, while work for the following day is plotted out.
The Sprint Review takes place after a Sprint ends. During Review, the Product Owner explains what planned work either was or was not completed during the Sprint. The Scrum Team then presents completed work and talks through what went well and how problems were solved.
The Sprint Retrospective also takes place after a Sprint. Retros include the entire Scrum team and provide a dedicated forum for the team to analyze their process during the previous Sprint and make adaptations as needed.
What the heck are “artifacts?”¶
Hefty title, simple concept. Artifacts are physical records that provide project details. Scrum Artifacts include the Product Backlog, Sprint Backlog, and Product Increments.
The Product Backlog is a complete, ordered list of all product requirements, and acts as the sole reference for any necessary product changes. The Product Owner oversees the Product Backlog, including how it’s made available to the team, its content, and how it’s ordered. The Product Owner and Scrum Team work together to review the Product Backlog and make adjustments when necessary, as product requirements change and evolve.
The Sprint Backlog is a list of all items from the Product Backlog to be worked on during a Sprint. This list is put together by prioritizing items from the Product Backlog until the team feels they’ve reached their capacity for the Sprint. Team members sign up for tasks in the Sprint Backlog based on skills and priorities, following the self-organizing Scrum framework.
A Product Increment is the sum of product work completed during a Sprint, combined with all work completed during previous Sprints. The goal of a Sprint is to produce a Done Product Increment. It’s up to the Scrum team to agree on what defines an Increment’s “Done” status, but all team members need to agree on and understand the definition.
Have a headache from all these terms? Don’t worry. The gist is this: Scrum is a framework for teams to get work done together. The jargon easily becomes second nature once you’re using it, and you can refer back to this cheat sheet whenever you get stuck.