Scrum Guide Glossary: Key Terms & Definitions
Hey guys! Ever feel lost in the Scrum world with all its jargon? Don't worry, you're not alone! The Scrum Guide is packed with specific terms, and understanding them is crucial for effectively using Scrum. This glossary breaks down the key terms you'll find in the Scrum Guide, making them easy to understand and implement. Let's dive in and demystify the Scrum lingo!
Agile
Agile, at its core, is more than just a methodology; it's a mindset. It's all about embracing change, collaborating closely, and delivering value incrementally. Think of it as the opposite of rigid, waterfall approaches where everything is planned upfront and changes are a nightmare. Agile methodologies, like Scrum, are designed to be flexible and responsive to evolving requirements. The Agile Manifesto, a foundational document in the agile world, outlines the core values and principles that underpin this mindset. These values emphasize individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
In essence, adopting an agile approach means prioritizing adaptability and continuous improvement. Teams that embrace agile principles are better equipped to handle uncertainty, deliver value faster, and create products that truly meet the needs of their users. It's about fostering a culture of collaboration, transparency, and empowerment, where everyone is focused on delivering the best possible outcome. So, when you hear the term "agile," think flexibility, collaboration, and a relentless pursuit of value.
Artifacts
In the Scrum framework, artifacts represent the tangible or visible pieces of work that provide transparency and opportunities for inspection and adaptation. The three primary Scrum artifacts are the Product Backlog, the Sprint Backlog, and the Increment. Each artifact contains a commitment to ensure it provides information that fosters progress toward the objective. For the Product Backlog, it’s the Product Goal; for the Sprint Backlog, it’s the Sprint Goal; for the Increment, it’s the Definition of Done. These commitments reinforce empiricism and the Scrum values for the Scrum Team and their stakeholders.
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. The Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.
These artifacts are crucial for maintaining a clear understanding of the project's progress and direction. They provide a shared reference point for the Scrum Team and stakeholders, enabling effective communication and collaboration. By regularly inspecting and adapting these artifacts, the team can ensure that they are continuously delivering value and meeting the evolving needs of the product.
Burn-down Chart
A burn-down chart is a visual tool used to track the progress of work within a Sprint. It displays the amount of work remaining (typically in story points or hours) against the time left in the Sprint. The chart typically shows a downward trend, indicating that the team is completing work and moving closer to achieving the Sprint Goal. However, it's not actually part of the Scrum Guide anymore. While burn-down charts can be helpful for visualizing progress, they are not a mandatory component of Scrum. Teams can choose to use other tools or techniques to track their progress, as long as they are able to effectively monitor their work and make adjustments as needed.
The key benefit of a burn-down chart is its simplicity. It provides a quick and easy way to see whether the team is on track to complete the Sprint Backlog items within the Sprint timeframe. If the line on the chart is trending above the ideal line, it may indicate that the team is falling behind and needs to take corrective action. Conversely, if the line is trending below the ideal line, it may indicate that the team is ahead of schedule and can consider taking on additional work. While not explicitly mentioned in the Scrum Guide, the principles of transparency and inspection that burn-down charts promote align well with the Scrum framework.
Daily Scrum
The Daily Scrum is a short, 15-minute event for the Developers of the Scrum Team. It's held every day of the Sprint, and it's a crucial opportunity for the Developers to synchronize their activities and create a plan for the next 24 hours. The Daily Scrum is not a status report meeting for the Scrum Master or Product Owner; it's a meeting for the Developers, by the Developers. The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
During the Daily Scrum, Developers often discuss what they accomplished yesterday, what they plan to do today, and any impediments they are facing. This helps the team identify potential roadblocks and make adjustments to their plan as needed. By having this daily synchronization, the Developers can ensure that they are all on the same page and working towards the Sprint Goal in a coordinated manner. The Daily Scrum promotes self-management, collaboration, and transparency within the Development Team, making it an essential component of the Scrum framework.
Definition of Done
The Definition of Done (DoD) is a formal description of the state of the increment when it meets the quality measures required for the product. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. The Definition of Done is crucial for ensuring that the Increment is of high quality and meets the needs of the users. It helps to prevent misunderstandings and ensures that everyone is on the same page regarding what constitutes a completed piece of work.
A well-defined Definition of Done typically includes items such as code being reviewed, tests passing, documentation being updated, and the feature being integrated with the rest of the system. The Definition of Done may evolve over time as the team learns more about the product and the needs of the users. However, it should always be clearly defined and consistently applied across all Product Backlog items. By adhering to a strict Definition of Done, the team can ensure that they are delivering high-quality Increments that provide real value to the users.
Developers
The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. Developers are accountable for: Creating the plan for the Sprint, the Sprint Backlog; Instilling quality by adhering to a Definition of Done; Adapting their plan each day toward the Sprint Goal; Holding each other accountable as professionals. The term "Developers" encompasses all the individuals who are responsible for designing, building, testing, and delivering the product. This could include programmers, testers, designers, writers, and anyone else who contributes to the creation of the Increment.
The Developers are a self-organizing team, meaning they have the autonomy to decide how best to accomplish their work. They are not micromanaged by the Scrum Master or Product Owner, but rather are empowered to make their own decisions and take ownership of their work. The Developers are also responsible for continuously improving their skills and knowledge. They should be constantly learning new technologies, techniques, and best practices in order to deliver the best possible product. By fostering a culture of self-management, continuous improvement, and collaboration, the Scrum framework enables the Developers to be highly effective and deliver value to the users.
Empiricism
Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation. Empiricism is the foundation of the Scrum framework. It's the idea that we learn by doing and that we should make decisions based on what we observe and experience. In Scrum, this means that we break down complex projects into smaller, manageable pieces, and we continuously inspect and adapt our approach based on the feedback we receive.
Transparency, inspection, and adaptation are the three pillars of empiricism in Scrum. Transparency means that everyone involved in the project has a clear understanding of the work being done, the progress being made, and any challenges that are being faced. Inspection means that we regularly examine the Scrum artifacts and processes to identify areas for improvement. Adaptation means that we make changes to our approach based on what we have learned through inspection. By embracing empiricism, Scrum teams can continuously improve their performance and deliver value to the users more effectively. This iterative and adaptive approach allows for flexibility and responsiveness to change, making Scrum a powerful framework for managing complex projects.
Increment
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. To provide value, the Increment must be usable. Each Sprint, the Scrum Team delivers an Increment of the product. This Increment must be in a usable condition and meet the Definition of Done. The Increment represents the sum of all the Product Backlog items completed during a Sprint, integrated with all previous Increments. It's a tangible result of the team's efforts and should be potentially shippable, meaning it could be released to users if the Product Owner chooses to do so.
The Increment is crucial for providing feedback and validation. Stakeholders can review the Increment during the Sprint Review and provide feedback to the Scrum Team. This feedback can then be used to inform future Sprints and ensure that the product is evolving in the right direction. The Increment also provides a sense of progress and accomplishment for the Scrum Team. By delivering a usable Increment each Sprint, the team can see the tangible results of their work and feel motivated to continue improving the product. The focus on delivering a working Increment each Sprint is a key differentiator of Scrum and helps to ensure that the product is continuously evolving and delivering value to the users.
Product Backlog
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. It's a living document that reflects the evolving understanding of the product and its users. The Product Backlog is not a fixed list of requirements, but rather a flexible and adaptable plan that can be adjusted as needed.
The Product Backlog contains all the features, enhancements, bug fixes, and other changes that may be made to the product. These items are typically expressed as user stories, which describe the desired functionality from the perspective of the end-user. The Product Owner is responsible for managing the Product Backlog, ensuring that it is prioritized and that the items at the top of the backlog are the most valuable and important. The Product Backlog is a crucial tool for ensuring that the Scrum Team is always working on the most important things and that the product is evolving in the right direction.
Product Goal
A Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. The Product Goal provides focus for the Scrum Team. It is a concise statement that describes the desired outcome for the product and serves as a guiding star for all the work that is done on the product. The Product Goal is not a specific feature or set of features, but rather a broader vision of what the product should become.
The Product Goal should be ambitious but achievable. It should inspire the Scrum Team and motivate them to work towards a common purpose. The Product Goal also provides a framework for making decisions about what to include in the Product Backlog. Items that contribute to the Product Goal should be prioritized over items that do not. The Product Goal is a crucial tool for ensuring that the Scrum Team is aligned and focused on delivering value to the users.
Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing the Product Backlog, ensuring that it is prioritized and that the items at the top of the backlog are the most valuable and important. The Product Owner is the voice of the customer and represents the needs and desires of the users. They work closely with the Scrum Team to ensure that the product is meeting the needs of the users and delivering value to the business.
The Product Owner is also responsible for making decisions about the product roadmap and release planning. They work with stakeholders to gather feedback and insights, which they then use to inform their decisions about the direction of the product. The Product Owner is a key member of the Scrum Team and plays a crucial role in ensuring that the product is successful. They are empowered to make decisions about the product and are accountable for the results. The Product Owner is a leader, a communicator, and a decision-maker, all rolled into one.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is a servant-leader for the Scrum Team. They help the team to self-organize, collaborate, and continuously improve. The Scrum Master also helps to remove impediments that are blocking the team from making progress. They work with the organization to create an environment that is conducive to Scrum and to promote the adoption of agile principles.
The Scrum Master is not a project manager or a team lead. They are a facilitator and a coach. They help the team to work together effectively and to deliver value to the users. The Scrum Master is a key member of the Scrum Team and plays a crucial role in ensuring that Scrum is implemented effectively. They are a champion for the Scrum framework and help to promote its adoption throughout the organization.
Scrum Team
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. Scrum Teams are cross-functional, meaning that they have all the skills necessary to deliver a working Increment of the product. Scrum Teams are also self-organizing, meaning that they have the autonomy to decide how best to accomplish their work.
The Scrum Team is a small, tightly knit group of individuals who are focused on delivering value to the users. They work together collaboratively and communicate openly. The Scrum Team is empowered to make decisions about the product and the process. They are accountable for the results. The Scrum Team is the engine that drives the Scrum framework.
Sprint
A Sprint is a short, time-boxed period when a Scrum Team works to complete a set amount of work. Sprints are the heartbeat of Scrum, and the length of the Sprint is typically one to four weeks. At the end of each Sprint, the Scrum Team delivers an Increment of the product. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every Sprint. They are designed to create a regular cadence for delivering value and for gathering feedback from stakeholders.
During the Sprint, the Scrum Team focuses on completing the items in the Sprint Backlog. The Sprint Backlog is a plan for delivering the Sprint Goal and is created by the Developers. The Scrum Team works together collaboratively to complete the work in the Sprint Backlog and deliver a working Increment of the product. The Sprint is a crucial element of the Scrum framework and helps to ensure that the product is continuously evolving and delivering value to the users.
Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. The Sprint Backlog is created during Sprint Planning and is continuously updated throughout the Sprint as the Developers learn more about the work.
The Sprint Backlog is a crucial tool for the Developers. It provides them with a clear understanding of what they need to accomplish during the Sprint and how they plan to do it. The Sprint Backlog also helps the Developers to track their progress and to identify any impediments that are blocking them from making progress. The Sprint Backlog is a living document that is constantly evolving and adapting to the changing needs of the Sprint.
Sprint Goal
The Sprint Goal is a single objective for the Sprint. The Sprint Goal is a commitment by the Developers, providing focus and coherence. It encourages the Scrum Team to work together rather than on separate initiatives. The Sprint Goal is created during Sprint Planning and is a concise statement that describes what the Scrum Team hopes to achieve during the Sprint.
The Sprint Goal should be aligned with the Product Goal and should provide a clear sense of purpose for the Scrum Team. The Sprint Goal helps the Scrum Team to focus their efforts and to make decisions about what is most important to accomplish during the Sprint. The Sprint Goal also provides a framework for the Daily Scrum, helping the Developers to coordinate their work and to identify any impediments that are blocking them from achieving the Sprint Goal.
Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. The resulting plan is created by the collaborative work of the entire Scrum Team. Sprint Planning addresses the topics of: Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done? It's a collaborative event where the entire Scrum Team comes together to plan the work for the upcoming Sprint.
During Sprint Planning, the team discusses the Product Backlog items that are most important to deliver and selects a Sprint Goal that aligns with the overall Product Goal. The team then breaks down the selected Product Backlog items into smaller tasks and estimates the effort required to complete each task. The result of Sprint Planning is a Sprint Backlog that provides a clear plan for the work that will be done during the Sprint. Sprint Planning is a crucial event in the Scrum framework and helps to ensure that the team is aligned and focused on delivering value during the Sprint.
Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and gathers feedback. The Sprint Review provides an opportunity for stakeholders to see the Increment that has been created during the Sprint and to provide feedback on the product. During the Sprint Review, the Scrum Team also discusses any challenges that they faced during the Sprint and any lessons that they learned.
The Sprint Review is a collaborative event where the Scrum Team and stakeholders come together to inspect the product and to plan for the future. The Sprint Review is not a demo or a status report. It is an opportunity for stakeholders to provide valuable feedback that can be used to improve the product and to ensure that it is meeting their needs.
Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Sprint Retrospective is an opportunity for the Scrum Team to reflect on their performance during the Sprint and to identify areas for improvement.
During the Sprint Retrospective, the Scrum Team discusses what went well, what could have been better, and what actions they can take to improve their performance in the future. The Sprint Retrospective is a collaborative event where the Scrum Team comes together to learn from their experiences and to plan for continuous improvement. The Sprint Retrospective is a crucial event in the Scrum framework and helps to ensure that the team is continuously improving and delivering value to the users.
Stakeholders
Stakeholders are those with an interest in the project. Stakeholders are external to the Scrum Team. Stakeholders are the individuals or groups who have an interest in the outcome of the project. They may include customers, users, business owners, executives, and other interested parties. Stakeholders provide valuable input and feedback to the Scrum Team, helping to ensure that the product meets their needs and delivers value to the business.
Stakeholders participate in the Sprint Review, where they have the opportunity to see the Increment that has been created during the Sprint and to provide feedback on the product. Stakeholders also provide input to the Product Owner, helping to shape the Product Backlog and to ensure that the product is aligned with their needs. Stakeholders are a crucial part of the Scrum framework and play a vital role in ensuring that the product is successful.
Okay, guys, that's a wrap on the Scrum Guide glossary! Hopefully, this breakdown has made those terms a little less intimidating and a lot more understandable. Now you can confidently navigate the Scrum world and contribute to your team's success. Keep learning, keep practicing, and remember to embrace the agile mindset! Good luck!