What is Scrum?
Scrum is a framework that allows you to tackle complex problems by breaking them down into manageable chunks. Scrum can help you and your team address new and complex problems while delivering new products faster. Scrum is a framework for developing complex solutions that help people, organizations, and teams generate value by solving problems.
Ken Schwaber and Jeff Sutherland are the original creators of Scrum. They’ve written The Scrum Guide to explain Scrum. This guide contains the definition of the scrum. This definition contains Scrum’s responsibilities, events, patterns, and rules that bind to them.
In short, Scrum requires a Scrum Master to market an environment where:
- A Product Owner orders the work for a Multiplex problem into a Product Backlog.
- The Scrum Team turns a variety of the work into an Increment useful during a Sprint.
- The Scrum Team and its stakeholders review the results and adjust the subsequent spirits.
The Scrum Framework
Scrum is simple. It’s a way for agile teams to work together more effectively while maximizing productivity. Scrum is not a methodology. Scrum is a framework that you can apply to different fields. Scrum is based on Empiricism, which is the scientific method. Scrum is a product development framework that uses short cycles, accountability, self-organization, and feedback to improve productivity. The graphic schema below represents these actions, as Ken Schwaber and Jeff Sutherland describe in their book Software in 30 Days, which prevents us from planning through the provision of software.
The Scrum Values
Scrum team values are important to get Scrum projects right. When you apply these principles to running your team, it will help the project succeed and everyone will be happy. There are five core Scrum values that are listed below:
- Commitment: A scrum team is made up of people, and there needs to be a commitment to progress and a desire to meet goals. In Scrum, you are responsible for your actions and the work that you do.
- Focus: If you focus on the goals, you can avoid wasting time and deliver on time. This Scrum value reduces risks and delivers high-value products.
- Courage: A Scrum project must be flexible to adapt to changing conditions, and you need bravery and courage to accept a new idea.
- Openness: It is important to be open about your work, progress, what you learned and the issues you are facing. Be open to sharing plans and ideas. Be open to asking for help. Be open to making changes.
- Respect: As a team member, you should be respectful of your colleagues, their decisions, and their experience. As a member of a team, you should show respect by listening to your colleagues and engaging constructively with them.
The Scrum Team
A Scrum Team is a small unit of people who work together to achieve the Scrum goals. The Scrum team includes a Scrum Master, a Product Owner, and Development Team. Within the Scrum team, there are no sub-teams or rankings. It is a coordination unit of professionals focused on one goal at a time, the product goal.
The Scrum Team needs a person who owns the Product Backlog. This Product Owner is responsible for maximizing the value of the product for both the consumer and the business.
- The product owner is responsible for directing the team and communicating with stakeholders
- The product owner writes user stories
- The Product Owner prioritizes the items in the Product Backlog and is responsible for the value of the work the Development Team performs.
- The product owner works with the scrum team for any problems that come up during an iteration
Scrum Master ensures that following the Scrum framework the team is put into practice by coaching Scrum principles and concepts, often facilitating key sessions, and encouraging the team to grow and improve. The responsibilities of Scrum Master include.
- With key stakeholder input, helping the team determine the definition of the product.
- To provide high-quality features for this product, under Scrum principles, team coaching.
- To help the Scrum team avoid or overcome obstacles to its development, whether it is internal or external to the team.
- Promote self-organization and cross-functionality in the team.
- Facilitate team events to ensure regular progress.
A development team is a group of people that work together to create software. The Scrum development team is made up of individuals with a wide range of experiences and skills. The size of the development team is between 3-9 team members.
- The development team in Scrum is Cross-functional.
- The development team in Scrum is Self-Organized.
- Improve how they work together as a team and make sure that high-quality results are created through close, collaborative work with other professionals.
- Responsible for the definition of Done in the sprint.
- Create and manage the Sprint Backlog.
The Scrum Events
Suggested events are used in Scrum to create consistency and reduce the need for scheduled meetings in Scrum. All events are timely. Once the sprint starts, its duration is fixed and it cannot be shortened or lengthened. The rest of the events can be eliminated whenever the goal of the program is achieved, making sure that proper time is spent without wasting time in the process. The events of Scrum are:
- Sprint: Sprint is a time-based iteration in the Scrum framework. Each Sprint takes place over a fixed period of time, i.e a week, two weeks, one month, etc where an Iteration can be split into multiple Sprints, as decided by the Scrum Team and the project stakeholders.
- Sprint Planning: Sprint Planning is one of the most important meetings in a Scrum project, being the first item on Sprint´s schedule. It goes through an overall view of next Sprint´s initiatives (or tasks, as they are usually referred to in Scrum) that need to be done to keep the project on track toward the final goal. This meeting should be kept short and focus on one iteration to come. Only Product Backlog Items (PBI) that can be completed within an iteration should be selected. The sprint backlog is maintained by adding tasks here.
- Daily Scrum: The Daily Scrum is a 15-min meeting that is held every day in Scrum. The key success factor here is that it’s a time-bound meeting with strict guidelines, so the team members can easily spend the exact amount of time needed for this activity. Daily scrum provides a short status report from every member, so it’s an excellent chance for leadership to keep track of where everyone’s at and whether they need help with anything.
- Sprint Review: Sprint Review meeting is conducted at the end of a Sprint. It is commonly held after each Sprint, though in some organizations it happens every other Sprint and at the end of an iteration. At the Sprint Review meeting, representatives from each team talk about what they’ve delivered and the progress made. The meeting also helps to redirect the work of developers not yet working on their final tasks.
- Sprint Retrospective: Sprint Retrospective meeting is a time-boxed meeting. The main goal of this meeting is to look for process improvement or looking after the business value. The meeting collects feedback within a time-boxed framework that encourages everybody to be focused, active, and honest in their participation.
Scrum samples represent work or value to provide transparency and opportunities for inspection and adaptation. The patterns described by Scrum are specifically designed to maximize the transparency of key information so that everyone has an equal understanding of the pattern. Samples of scrum are:
- Product backlog: A product backlog is a list of features, requirements, enhancements, or bug fixes (defects) that are ready to be worked on. In Scrum it is defined as the list of Product Backlog Items (PBI), being prioritized and groomed at the beginning of a sprint. It is basically a list of features that haven’t been prioritized for development by the Product Owner or team. These are often referred to as “user stories” in Scrum terminology.
- Sprint backlog: The sprint backlog is the list of planned work items for a sprint. This list is owned and managed by the development team. The list is created during the Sprint Planning meeting. The development team wants to ensure that all necessary tasks for completing work items in the product backlog are included as part of this list.
- Increment: Each incremental change (or increment) is a concrete stepping stone toward the purpose of the product. A useful increment is one that is completely functional and can be used by customers.
To learn more about the Scrum Framework
There are over 100 books on Scrum within the market today, tens of thousands of papers, articles, and presentations, but it all starts with the Scrum Guide. The Scrum Guide was written and maintained by the creators of Scrum, Ken Schwaber, and Jeff Sutherland, With over 500,000 members of our Scrum community, you can ask a question on the forum and expect immediate feedback that will help you. Our community of Professional Scrum Trainers (PSTs) specialize in their field and always write blogs that provide insights from their experiences working directly on scrum teams. Articles, white papers, videos, webinars, and other materials are often released by the community and are available in the resources section of the website and read other ways to learn about Scrum.
To learn more about the Scrum framework, to identify which of these terms are needed, to determine which Scrum elements are needed, and to understand how these elements are connected Recommend that you refer to the Scrum Guide. For more information on specific terms for software development teams that use Scrum and agile software development techniques, see the Professional Scrum Developer Dictionary.