Scrum is one of the most popular Agile frameworks. Most of this is due to its ability to provide clear guidance and rules for teams that use it. However, remembering all of these rules is not easy. And sometimes you just need a quick reminder to get back on track. So grab this Scrum cheat sheet and stay sure of what you are doing!
In the Scrum cheat sheet, you will find all of the most important terms and practices explained in a simple and efficient manner. Making it easy to check something and get back to work immediately.
Scrum has been the most popular Agile framework for quite some time now and this is not going to change any time soon. The framework is easy to understand and covers various business management aspects, making it easy to pick up and keep up. Compared to Kanban that provides only vague guidance for its practitioners, Scrum rules are very extensive and restrictive. However, this is just what most new Agile practitioners are after and they pick Scrum in order to have a good start with Agile.
If you want to learn more about the framework read – What is Scrum? Here are the most important Scrum terms and practices and below you will find the Scrum cheat sheet.
Scrum projects are organized in short iterations (Sprints), during which the team plans, executes, and reviews work. After each Sprint the team adds incremental value to the end goal. This does not have to be a new product release, just an added value to the product.
Scrum tasks can be of varying sizes, however, no task should exceed the duration of the Sprint. If you have tasks that come close to the Sprint duration, split them up into several smaller ones.
Team members self-assign tasks by choosing them from the Sprint backlog. This is usually done before the Sprint begins, but the assignments can change during the iteration.
New tasks in an iteration
Once a Sprint has started no new tasks can be added to the Sprint backlog. Any new issues are added to the backlog for the next Sprint.
Product Owner – represents client interests and orders the work for a complex problem into a Product Backlog. Core responsibility – communication.
Scrum Team – a cross-functional team of professionals that self-organize to turn a selection of the work into an Increment of value during a Sprint. Core responsibility – delivering value.
Scrum Master – facilitates the Scrum application and helps ease the organizational transition. Core responsibility – Scrum application.
Scrum iterations are called sprints. They are planned and executed one at a time and usually last 1-4 weeks. Sprint duration is decided before the Sprint begins and cannot be changed before a new Sprint begins.
Scrum teams use Story points or hours to estimate the task size. This is done during the Sprint planning with the entire Scrum team.
Scrum events are curated in a way that implements three empirical Scrum pillars – transparency, inspection, and adaptation.
Sprint – 1-4 week iteration during which the Scrum Team delivers an incremental added value to the end product or goal. This can be a new product version or simply a needed improvement.
Sprint Planning – an 8-hour session where the Product Owner and the Scrum Team decide what the team should accomplish in the next Sprint. This includes setting the Sprint goal and choosing user stories that help achieve it.
Daily Scrum – a 15-minute meeting where each of the team members presents what they have done yesterday, what they have planned for today and how does it help achieve the end goal.
Sprint Review – a 4-hour meeting for the Scrum Team, Product Owner, and the stakeholders to discuss what was done during the Sprint, gather feedback and adjust the course of action.
Sprint Retrospective – a 3-hour discussion between the Scrum Team and the Scrum Master on how the process could be improved and made more effective in the next Sprint. It is a good practice to take at least one of the discussed solutions and implement it in the next Sprint.
Scrum task board
The Scrum task board is usually combined out of 4 sections – Product Backlog where the Product Owner places user stories, Sprint Backlog where Scrum Team plans tasks, Doing for tracking the tasks in progress, and Done for completed tasks.
Scrum limits the amount of work the team does in one iteration by having a clear set duration of the Sprint. The team cannot commit to more work that fits within one Sprint.
Scrum uses the Product Backlog to prioritize the most important user stories. The Scrum Team picks the most important items during Sprint Planning and works on them during the next Sprint.
This is the first column on the Scrum task board. It holds all the prioritized epics and user stories and represents a project plan. Curated by the Product Owner.
This is the second column on the board that holds all the tasks planned for the current Sprint. It represents a Sprint plan and is curated by the Scrum Team.
This is a short description of a client requirement. Usually written in a form similar to this: As a … I want …, so that … .Used to gather user requirements and feedback.
A large user story that cannot be delivered as defined in one iteration. Usually divided into smaller user stories before the Scrum Team commits to it.
A measuring unit used to estimate task duration. One story point could mean anything and it is up to the team to define it – in hours, money, or size of tasks.
A Scrum chart displaying how the number of incomplete tasks decreases over time. Can be used to identify issues when the number of tasks stops decreasing all of a sudden.
Using Teamhood for Scrum project management
Teamhood is a visual project management tool optimized for Agile project management. Thus, it is a great tool to visualize and track your Scrum projects. Simply choose a Scrum template and you will get a workspace ready for your project. In this predesigned workspace, you will find:
1 – Product Roadmap. To easily plan out where you plan to take the product in the next year. The roadmap is divided into quarters, making it easy to note down important steps in the product development and draw dependencies to see what should come first.
2 – Product Backlog. To identify how the Roadmap will be implemented and prepare tasks for the Sprint Backlog. The Product Backlog in Teamhood is divided into three sections – Features/User Stories, Bugs, and Tasks. Thus allowing you to categorize items according to their type. Additionally, each item can be assigned different statuses to see what is ready to be pulled in the Sprint Backlog. The predefined statuses are – New items, For grooming, Priority 2, and Priority 1, you can also always add or delete any status in this view.
3 – Sprint Backlog and task board. Once the tasks are ready for the Sprint, they can be moved to the Sprint board in Teamhood. They should be added first to the Sprint Backlog column, evaluated and then the team can start working. All the sub-items are tracked in the secondary process steps for more clarity. The board is also divided into several rows, making it easy to see past Sprints and plan the ones ahead.
4 – Releases and Retrospectives views. The last two boards in Teamhood Scrum workspace are dedicated to tracking releases and reflecting on the process. The release board helps you track what features or improvements have been made during each Sprint. While the Retrospective board helps review the process, identify what should be improved and commit to actions for the next Sprint.
Teamhood is equipped with various project management tools and features that make Scrum project management easy. Try it out now for comprehensive task details, actionable Agile metrics, easy task estimation, scope limits, and task assignments. Complete with automated time tracking and Portfolio view, Teamhood is a Scrum project management powerhouse.
Scrum board examples
Scrum is a great choice for teams that want to move fast and react to the changing environment. Planning, completing, and reviewing the work in short iterations allows to quickly test out new ideas and deliver a final result that is done in accordance with the customer feedback. Scrum was created for small collocated teams but has since proven to be a great candidate for scaling. Great for Agile beginners it may very well be your intro into Agile and with this Scrum master cheat sheet you are sure to do great!
Scrum – Frequently asked questions
Are Agile and Scrum the same?
No. Scrum is one of many Agile applications. The Agile manifesto defines 4 values and 12 principles for projects to follow. And frameworks such as Scrum, Kanban, XP, and others are more focused on how to implement these values and principles in the day-to-day activities of a project.
Is Scrum only fit for development projects?
No. Scrum was first created and adapted for software development teams, but now it is used in a variety of fields. Sales, Marketing, Accounting, Engineering, Manufacturing, and other teams can successfully adopt and benefit from Scrum.
Is Scrum the best Agile framework?
Scrum is definitely the most popular out of the Agile applications. However, no one can say it is the best. Seeing which of the frameworks will be the best for your team will depend on a variety of factors, such as the team size, project type, previous Agile experience and personal process preferences.
Is the Scrum Master same as the Project Manager?
No. The role of the Scrum Master is to help the Scrum team to adopt and use Scrum practices. They are the Scrum experts in that project and responsible for ensuring the team succeeds with the framework itself.
Is Product Owner the same as the Project Manager?
No. The role of the the Product Owner is more similar to the Product Manager. They have to communicate with the project stakeholders and prioritize the Product Backlog to make sure the team is working on what is the most important at that moment. The Scum team is a self-organizing unit, that needs little supervision.