Robust ThemeDec 09, 2019 2020-04-08 7:40
An Agile/Scrum Glossary
By Chris Daily
Welcome to our Agile Glossary. As with anything on the internet, there is a lot of misinformation about agile and the meanings of the terms. That makes it difficult to identify what is true and what isn't true. People invent their versions of terms based on a bad experience, have misinterpreted, or are just making stuff up. Access to a glossary of agile terms is important because it provides a common understanding and a shared vocabulary among team members, stakeholders, and other stakeholders involved in the development process. This is especially important in Agile methodologies, focusing on collaboration, communication, and flexibility.
A glossary of agile terms helps to ensure that everyone is on the same page and that there is no confusion or misunderstanding about the meaning and usage of specific terms. It provides a reference point for team members, stakeholders, and other stakeholders to refer to when they have questions or need clarification on a particular term or concept.
Having a glossary of agile terms also helps to ensure that everyone is using the same terminology and that there is consistency in the way words are used. This is particularly important when working with remote teams or when working with stakeholders who may have different backgrounds or levels of experience with Agile methodologies.
Additionally, having a glossary of agile terms can benefit new team members or stakeholders who may be unfamiliar with Agile methodologies. It can serve as a helpful resource for them to learn about the different concepts, practices, and terminology used in Agile development.
Over the years, folks with the organization that I am helping has been one of the biggest issues influencing the adoption of Agile and scrum. Agile is confusing enough without creating additional confusion around what terms mean.
In summary, having access to a glossary of agile terms is important because it helps to ensure that everyone is on the same page, that there is no confusion or misunderstanding about the meaning and usage of specific terms, and that everyone is using the same terminology. It can benefit new team members or stakeholders unfamiliar with Agile methodologies.
We hope you enjoy it. Let us know if there are additional terms you would like to use.
A budgeting approach that emphasizes flexibility and adaptability and allows for changes in scope and requirements. Agile budgeting is used in conjunction with incremental delivery.
Agile Burn-up Chart
A chart representing the total amount of work completed in a sprint over time.
Agile Change Management
The process of managing and implementing changes in an Agile environment. Agile change management emphasizes flexibility, collaboration, and customer satisfaction.
The process of helping individuals, teams, and organizations adopt and improve Agile practices. Agile coaches work with teams to help them understand and implement Agile principles and practices.
Contracts that are flexible and focus on deliverables rather than specific tasks. Agile contracts are used to support incremental delivery and allow for changes in scope and requirements.
A work environment characterized by flexibility, collaboration, and customer satisfaction. Agile culture emphasizes self-organizing teams, open communication, and continuous improvement.
The process of delivering software incrementally, in small chunks, focusing on working software over comprehensive documentation. Agile delivery is characterized by flexibility, collaboration, and customer satisfaction.
Agile Delivery Model
A model for delivering software incrementally, in small chunks, focusing on working software over comprehensive documentation. Agile delivery models include Scrum, Kanban, and Extreme Programming.
A software development approach that emphasizes flexibility, collaboration, and customer satisfaction. Agile development comprises iterative and incremental delivery, self-organizing teams, and a focus on working software over comprehensive documentation.
Agile estimation determines the effort required to complete a specific task or project within an Agile framework. Agile estimation techniques are designed to be flexible and adaptable, allowing teams to adjust their estimates as new information becomes available. Common techniques used in Agile estimation include Planning Poker, Story Points, and T-Shirt Sizing. Agile estimation is typically done by the development team, with input from stakeholders and other team members. It is intended to provide a rough estimate of the effort required to complete a task or project rather than a precise one.
Agile Extreme Programming
A software development methodology that emphasizes rapid feedback and adaptation and values working software over comprehensive documentation in an Agile project.
Agile games are interactive activities, exercises, or tools that teach or reinforce Agile principles, practices, and values. They are used to help teams understand and apply Agile concepts in a fun and engaging way. These games can be used in various Agile ceremonies, such as sprint planning, retrospectives, daily stand-ups, and training sessions or workshops.
Some examples of Agile games include:
Planning Poker: A game that estimates the effort required to complete a task or feature. It is usually used during sprint planning or backlog grooming.
Scrum Poker: A game that helps teams to prioritize and make decisions by allowing team members to vote on different options by placing dots next to their preferred choices.
Speedboat: A game used to help teams understand the importance of working together and of dependencies between different tasks or features.
Lean Coffee: A game that is used to facilitate open, collaborative conversations and to identify areas for improvement.
Timeline: A game that is used to help teams understand the importance of delivering value early and often and of adapting to change.
Ball Point Game: A game that reinforces the value of lean, iterative work, team-building, and identifying areas for improvement.
Agile games can be an effective way to increase engagement and participation, encourage collaboration and communication, and foster a culture of continuous improvement. They can also be a valuable tool for teaching Agile methodologies, practices, and values to new team members or organizations that are new to Agile.
Managing and coordinating work across multiple teams, typically in a large and complex project. Agile governance includes specific practices and roles for managing and coordinating work across multiple teams.
Agile Kanban Board
A visual board used to track work progress in an Agile project using the Kanban method.
The process of leading and managing Agile and scrum teams emphasizes flexibility, collaboration, and customer satisfaction. Agile leaders work with agile and scrum teams to understand and implement agile principles and practices and to continuously improve their performance.
Agile Lean Software Development
A software development methodology that emphasizes speed, efficiency, and waste reduction in an Agile project.
A set of guiding values and principles for Agile software development, emphasizing individuals and interactions, working software, and customer collaboration.
Agile Manifesto Values
The four values that guide the Agile methodology:
Individuals and interactions over processes and tools;
Working software over comprehensive documentation;
Customer collaboration over contract negotiation;
Responding to change over following a plan.
Agile Manifesto Principles
The twelve principles that guide the Agile methodology:
Customer satisfaction by early and continuous delivery of valuable software
Welcome changing requirements, even late in development
Working software is delivered frequently
Business people and developers must work together
Customers, developers, and testers must work together
Continuous attention to technical excellence
Agile processes promote sustainable development
The sponsors, developers, and users should be able to maintain a constant pace indefinitely
Continuous attention to sound design
Simplicity is essential
The best architectures, requirements, and designs emerge from self-organizing teams
Regularly the team reflects on how to become more effective, and adjusts accordingly.
Want to learn more about Agile? Check out our Agile Fundamentals course and jumpstart your career!
Agile Maturity Model
A framework for evaluating and improving an organization's level of Agile adoption and effectiveness. Agile maturity models typically include levels such as "initial," "managed," "defined," and "optimizing."
Agile is a methodology based on iterative and incremental development, it allows teams to deliver a product incrementally, and with short cycles called sprints which allow them to adapt to changes and incorporate feedback from stakeholders, it also promotes teamwork, flexibility, and collaboration. Agile methodologies are widely used in software development, product management, and project management, but they can also be applied to other fields, such as marketing, finance, and HR.
Agile methodologies are popular because they provide a framework that helps teams to focus on delivering value, improving communication, and increasing efficiency. Additionally, many tools and practices can be used to implement Agile methodologies, such as stand-up meetings, retrospectives, and burndown charts.
Here are some of the most popular methodologies and frameworks:
Extreme Programming (XP)
Dynamic Systems Development Method (DSDM)
Feature-Driven Development (FDD)
Agile Unified Process (AUP)
Test-Driven Development (TDD)
Behavior Driven Development (BDD)
Agile Modeling (AM)
Agile Data Methodology
Agile Project Management (APM)
Agile Systems Engineering (ASE)
Agile Processes in Software Engineering and Extreme Programming (XP)
Agile Management Framework (AMF)
Agile Pair Programming
A software development technique where two developers work together at one workstation in an Agile project.
Agile Performance Management
The process of managing and improving an Agile team's performance. Agile performance management emphasizes flexibility, collaboration, and customer satisfaction.
Agile Performance Metrics
Metrics that are used to measure and improve an Agile team's performance, such as velocity, burn-down chart, and definition of done.
Agile planning is the process of creating a plan for a project or product development in an Agile framework. Agile planning typically involves breaking down the project into smaller, manageable chunks called "iterations" or "sprints", and determining the tasks and activities that need to be completed in each iteration. The planning process is collaborative and involves the entire development team, as well as stakeholders and customers, to ensure that all necessary tasks and activities are identified and prioritized. The goal of Agile planning is to create a flexible and adaptive plan that can change as new information becomes available or priorities shift. Agile planning also involves regular reviews and retrospectives to evaluate progress and adjust the plan as needed.
Agile Planning Poker
A consensus-based technique used to estimate the relative effort of tasks in an Agile project.
Agile Portfolio Management
The process of managing and coordinating multiple Agile projects and programs. Agile portfolio management emphasizes flexibility, collaboration, and customer satisfaction.
Specific techniques and tools used in Agile development, such as Scrum, Kanban, user stories, and retrospective meetings.
Agile Process Improvement
The process of continuously improving an Agile team's performance and practices. Agile process improvement typically includes retrospectives and is characterized by flexibility, collaboration, and customer satisfaction.
The process of acquiring goods and services in an Agile environment. Agile procurement emphasizes flexibility, collaboration, and customer satisfaction.
Agile Program Management
The process of managing and coordinating multiple Agile projects and programs. Agile program management emphasizes flexibility, collaboration, and customer satisfaction.
Agile Project Delivery
The process of delivering a project using Agile principles and practices, emphasizing flexibility, collaboration, and customer satisfaction.
Agile Project Management
A project management approach that emphasizes flexibility, collaboration, and customer satisfaction. Agile project management is typically used in software development and is characterized by iterative and incremental delivery, self-organizing teams, and a focus on working software over comprehensive documentation.
Agile Project Planning
A project planning approach that emphasizes flexibility, collaboration, and customer satisfaction. Agile project planning is typically done in small chunks and is characterized by iterative and incremental delivery.
Agile Release Train
An Agile Release Train (ART) is a group of Agile teams that work together to deliver capabilities or product increments on a regular schedule, usually every few months. The ART is a key concept in the Scaled Agile Framework (SAFe) which is a widely used methodology for scaling Agile development.
An ART is a collection of teams that work together to deliver a set of capabilities or product increments on a regular schedule, usually every few months. The ART is a key concept in the Scaled Agile Framework (SAFe) which is a widely used methodology for scaling Agile development.
The ART is led by a Release Train Engineer (RTE), who is responsible for ensuring that the ART is aligned with the overall organizational goals and that the ART is delivering value to the customer. The ART comprises multiple Agile teams, each responsible for providing a specific set of capabilities or product increments.
The ART is a self-organizing entity that is responsible for its planning, execution, and delivery. The ART operates on a fixed calendar, with regular releases called Program Increments (PI) that align with the ART's calendar. Each PI is typically 8-12 weeks long, and it's the ART's responsibility to deliver the agreed-upon capabilities or product increments within that timeframe.
The ART operates in a network of ARTs, which together make up the larger Agile Release Train, this allows for better coordination and collaboration between teams and better alignment with the overall organizational goals.
In summary, Agile Release Train is a group of Agile teams that work together to deliver a set of capabilities or product increments on a regular schedule, usually every few months. It helps to align teams and ensure that the work is aligned with the overall organizational goals and that the ART delivers value to the customer. It's a key concept in the Scaled Agile Framework (SAFe), and it allows for better coordination and collaboration between teams.Agile Refactoring
The process of restructuring existing code to improve its quality and maintainability without changing its external behavior in an Agile project.
Agile Resource Management
The process of managing and allocating resources in an Agile environment. Agile resource management emphasizes flexibility, collaboration, and customer satisfaction.
A meeting at the end of a sprint where the team reflects on what went well and what can be improved in an Agile project.
Agile requirements refer to the process of defining and managing the requirements for a project or product in an Agile development environment. In Agile, requirements are typically gathered and managed through a process called user stories, which are short, informal descriptions of a feature or function from the perspective of an end user. These stories are prioritized and refined by the development team, stakeholders, and customers throughout the development process, with the goal of delivering a product that meets the needs of the end user. Agile requirements are also expected to be flexible and adaptable, allowing teams to adjust and change as new information is discovered or new priorities arise.
Identifying, analyzing, and mitigating risks in an Agile environment. Agile risk management emphasizes flexibility, collaboration, and customer satisfaction.
A time-boxed period, usually two to four weeks, during which specific work is completed in an Agile project.
Agile Story Points
A measure of complexity and effort used to estimate the size of a user story in an Agile project.
Agile Test-Driven Development
A software development technique where tests are written before any code is written in an Agile project.
A software testing approach that emphasizes collaboration, flexibility, increased quality, and customer satisfaction. Agile testing is typically done parallel with development and is characterized by incremental delivery and a focus on working software over comprehensive documentation.
A technique for managing time and setting deadlines by allocating a fixed amount of time for a particular task or project in an Agile project.
The process of adopting Agile principles and practices in an organization. Agile transformation typically involves changes in culture, processes, and governance.
Backlog, aka Product Backlog
A prioritized list of work of features, enhancements, and defects to be completed for a project or product.
Big Room Planning
A planning session where all members of the development teams and stakeholders come together in one room to plan the next iteration or release of a product. This helps to ensure that everyone is on the same page and that any dependencies or risks are identified and addressed. Due to COVID 19, many organizations have adapted to virtual big-room planning approaches to accommodate remote development team members.
A chart that shows the remaining work in a sprint over time.
Specific, measurable, attainable, relevant, and time-bound objectives that an organization sets to achieve its strategic goals and improve performance.
A set of features, functionalities, or services that a product or system provides to its users or customers.
A software development practice where code changes are automatically deployed to production.
A software development practice where code is frequently integrated and tested automatically.
A methodology that focuses on continually identifying, analyzing, and improving processes, products, and services to increase efficiency, effectiveness, and customer satisfaction. This is a fundamental principle of Agile and Lean methodologies, and it helps organizations to stay competitive, adapt to changes, and deliver value. Check out our post on the continuous improvement model here:.
Cross-functional team that is responsible for delivering the product or service in an Agile development process. The Development Team is a key component of the Scrum framework, and it is composed of individuals with different skills and expertise who work together to turn the product backlog into an increment of potentially releasable functionality.
The Development Team is self-organizing and is responsible for delivering the product increment that they commit to during the Sprint Planning. The Development Team is responsible for the development and the quality of the product, and they are the ones who are responsible for the technical design, coding, testing, and integration of the product.
The Development Team is composed of a variety of roles, including:
Developers: who are responsible for writing code and implementing the product backlog items.
Testers: who are responsible for testing the product and ensuring it meets the acceptance criteria.
Designers: who are responsible for creating visual designs and user interfaces.
Database Administrators: who are responsible for managing the databases.
Operations: who are responsible for maintaining the systems and the infrastructure.
The Development Team is a self-organizing entity that works together to deliver a product increment that meets the Definition of Done (DoD) and meet the requirements of the stakeholders. They are also responsible for continuously improving their development process and increase their productivity. They work closely with the Product Owner and the Scrum Master to ensure the product backlog is complete and well-formed, and they collaborate with the other teams in the ART to ensure that the product increments are delivered on time, within budget, and with the right quality.
Daily Scrum, aka Daily Standup
Daily Scrum, also known as Daily Standup, is a short, daily meeting held at the same time and place, usually in the morning, where the team syncs up on progress and plans for the day. The meeting is typically time-boxed to 15 minutes or less, and the entire Development Team attends it.
During the Daily Scrum, team members answer the following three questions:
What did I do yesterday to help the Development Team meet the Sprint Goal?
What will I do today to help the Development Team meet the Sprint Goal?
Are there any obstacles impeding the Development Team's progress?
The Daily Scrum is a time for the whole team to communicate, coordinate, and align their efforts. It helps the team to identify any issues or obstacles early on and to make adjustments to the plan as needed. The Daily Scrum also allows the team to stay focused on the sprint goal and to make sure that they are making progress toward it.
During the Daily Scrum, the Definition of Done is the criteria for completing a work. The Definition of Done provides transparency and a common understanding that help the team to coordinate and work efficiently on achieving the sprint goal, delivering value, and ensuring high quality.
Definition of Done
A shared understanding of what constitutes a completed piece of work.
Relationships or connections between different tasks, features, or components of a project or product that affect their delivery or success.
A simple and effective method of prioritizing and making decisions by allowing team members to vote on different options by placing dots next to their preferred choices.
A philosophy that emphasizes the importance of observation and experience in acquiring knowledge. In Scrum and Agile, empiricism is applied through the inspection and adaptation of the product and process during development; this allows making decisions based on facts rather than assumptions, which is one of the fundamental principles of Agile methodologies.
A large user story that is broken down into smaller stories.
A software development methodology that emphasizes rapid feedback and adaptation and values working software over comprehensive documentation.
A visual representation of the tasks, activities, and timelines involved in a project; is typically used to track progress and identify any dependencies or risks.
A software development approach where a product is delivered in small, usable chunks. Kanban A method for managing work across teams, characterized by visualizing work, limiting work in progress, and managing flow.
A method for managing work across teams, characterized by visualizing work, limiting work in progress, and managing flow.
Lean Agile is a methodology combining Lean and Agile principles to create a flexible and efficient approach to product development.
Lean is a philosophy that emphasizes the elimination of waste and the maximization of value through continuous improvement. It is a way of thinking that focuses on delivering maximum value to customers while minimizing waste and inefficiencies.
Conversely, Agile is a project management methodology that emphasizes flexibility, collaboration, and continuous delivery of value. It is designed to enable teams to quickly respond to changes and deliver working software in short iterations.
When combined, Lean and Agile create a methodology that focuses on delivering value to customers as quickly as possible while minimizing waste and inefficiencies. The approach is based on continuous improvement, collaboration, and customer focus. Lean Agile encourages teams to iterate quickly and make data-driven decisions to optimize their processes and improve their product.
Lean Portfolio Management
Managing a portfolio of projects or products using Lean principles, such as minimizing waste and maximizing value.
Lean Software Development
A software development methodology that emphasizes speed, efficiency, and waste reduction.
Objectives and Key Results (OKR)
Organizations use a goal-setting framework to define and track their objectives and measure their progress. It is a popular system that helps align individual and team goals with the organization's broader objectives. OKRs are typically set for a defined period, such as a quarter or a year. For more information, check out our blog post here.
A software development technique where two developers work together at one workstation.
An individual responsible for leading a product or service's development, launch, and management. They play a crucial role in the product's and the organization's success. They are responsible for defining the product vision, creating the product roadmap, and ensuring that the product aligns with the overall goals and strategies of the organization.
Some of the specific responsibilities of a Product Manager may include:
Conducting market research to identify customer needs and pain points.
Defining the product vision and creating a product roadmap that aligns with the organization's goals and strategies.
Creating a product backlog that prioritizes the features and functionalities that will be developed.
Collaborating with cross-functional teams, such as engineering, design, and marketing, to ensure that the product is delivered on time and to the desired quality.
Defining the product's go-to-market strategy and working with the sales team to ensure the product is successfully launched.
Monitoring and analyzing product performance and customer feedback to identify opportunities for improvement.
Communicating with stakeholders, including customers, investors, and senior leadership, to ensure that the product aligns with their needs and expectations.
Product Managers must have a good understanding of the product development process, the target market and customers, and the competitive landscape. They also need to have strong leadership and communication skills, the ability to think strategically, and the ability to make data-driven decisions.
It's important to note that Product Manager's role can vary depending on the organization, type of product, and industry. Additionally, the role may overlap with other roles such as product owner in Agile methodology or project manager in some cases.
Product Owner, aka PO
The individual responsible for the product backlog and for representing the interests of the stakeholders. Refactoring The process of restructuring existing code to improve its quality and maintainability without changing its external behavior.
Product Owner Synch, aka PO Synch
A meeting where multiple product owners come together to discuss and share information about their products. This helps to ensure that the products align with the overall goals and strategies of the organization and that any dependencies or risks are identified and addressed.
An individual who is responsible for leading a project from start to finish. They are responsible for defining the project objectives, creating a project plan, and ensuring that the project is completed on time, within budget, and to the stakeholders' satisfaction.
Project Managers are responsible for the following:
Defining the project scope, goals, and objectives
Developing a project plan, including timelines, budgets, and resource requirements
Identifying and managing project risks
Coordinating and communicating with the project team, stakeholders, and other interested parties
Managing project deliverables and ensuring that they meet the quality standards
Tracking project progress and reporting on it to stakeholders
Making decisions and solving problems that arise during the project
Managing the change control process
Closing the project and conducting a post-project review.
Project Managers need to have a good understanding of project management methodologies, such as Waterfall, Agile, and Prince2, and be able to lead and motivate the project team to achieve the project objectives. They also need to be able to communicate effectively, manage conflicts, and make decisions under pressure.
A document that outlines the goals, objectives, tasks, activities, and timelines involved in a project.
The belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. It is considered a key component of high-performing teams, and it fosters an environment where team members feel comfortable sharing ideas, asking questions, and taking risks.
Teams that are geographically dispersed communicate and collaborate remotely, usually through technology. A team is considered a remote team if one team member is in another physical location.
A meeting where the team reflects on what went well and what can be improved.
Potential issues or challenges that could impact the delivery or success of a project or product.
Scaled Agile Framework (SAFe)
A framework for managing and completing large and complex projects, typically used in software development. SAFe is an extension of Agile methodology and includes specific practices and roles for managing and coordinating work across multiple teams.
Scrum, aka Scrum Process Framework
A framework for managing and completing complex projects, typically used in software development. It is an iterative and incremental approach to project management.
A facilitator for the Scrum team and responsible to the development team to remove barriers and ensure Scrum is understood and enacted.
Scrum Master Sync
A meeting where multiple Scrum Masters come together to discuss and share information about their respective teams and projects. This helps to ensure that the development teams work effectively and efficiently and that any issues or challenges are identified and addressed.Scrum of Scrum
A meeting where representatives from multiple Scrum teams come together to discuss and share information about their respective projects. This helps to ensure that the projects align with the overall goals and strategies of the organization and that any dependencies or risks are identified and addressed.
A cross-functional team that works together to develop, launch, and manage a product or service using the Scrum framework. The scrum team typically includes a Scrum Master, Product Owner, and Development Team.
Scrum Team Member
An individual who is part of a cross-functional team that works together to develop, launch, and manage a product or service using the Scrum framework. The Scrum Team comprises three roles: the Product Owner, the Scrum Master, and the Development Team.
Scrum Team Members are responsible for the following:
Collaborating with other team members to deliver a product increment at the end of each sprint
Participating in all Scrum ceremonies (e.g., Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective)
Communicating and working closely with the Product Owner to ensure that the product backlog is understood and that the Development Team is working on the essential items
Communicating and working closely with the Scrum Master to ensure that the team follows Scrum practices and that any obstacles or issues are identified and addressed.
Continuously improve their skills and knowledge and actively contribute to the team's performance.
The values that guide the Scrum methodology:
Courage: The willingness to take on difficult challenges and to speak up when there are problems or concerns. Scrum team members must be courageous to propose new ideas, question assumptions, and take calculated risks.
Focus: The ability to concentrate on the tasks at hand and to stay aligned with the goals and objectives of the project. Scrum team members must have the focus to prioritize their work and to stay on track, even when faced with distractions or obstacles.
Commitment: The dedication to delivering high-quality work and meeting the project's goals and objectives. Scrum team members must be committed to the project and the team and continuously improve their skills and knowledge.
Respect: The regard for the opinions, perspectives, and contributions of others. Scrum team members must respect the team's diversity, be open to feedback, and be willing to collaborate and compromise.
Openness: The willingness to be transparent, to share information, and to be open to new ideas and perspectives. Scrum team members must be open to learning and change, and continuously improve the process and the product.
By following these values, the Scrum team will be able to work together effectively, overcome obstacles, and deliver valuable products that meet the needs of the customer. These values also help to create a positive, collaborative, and high-performing team culture.
Teams that are empowered to make decisions and manage their work.
A time-boxed period, usually two to four weeks, during which specific work is completed.
A list of tasks and deliverables the Development Team commits to completing during a sprint (a time-boxed period of 1-4 weeks). The Sprint Backlog is created and managed by the Development Team based on the items in the product backlog selected for the sprint.
The goal or objectives for a sprint. Sprint Planning A meeting at the start of a sprint to plan the work for the upcoming sprint.
Sprint Planning is a meeting held at the beginning of each sprint in Scrum methodology. The purpose of sprint planning is to plan and prepare for the upcoming sprint. The entire Scrum team, including the Product Owner, Development Team, and Scrum Master, attend the meeting.
During the sprint planning, the team should focus on the following:
Reviewing the product backlog: The team should check and select the product backlog items they will work on during the sprint. The Product Owner should be present to provide context, speak to the value of each item, and answer any questions the team may have. Continuous improvement ideas identified in the last sprint retrospective from the previous sprint cycle should be included in the review.
Defining the sprint goal: The team should define a clear goal for the sprint that aligns with the overall goals and objectives of the product.
Planning the work: The Development Team should plan the work that needs to be done to achieve the sprint goal. The team should also identify any dependencies or risks that could impact the sprint.
Estimating the work: The Development Team should estimate the effort required to complete the work and make sure that the work is doable within the sprint timebox.
Creating a sprint backlog: Once the work is planned and estimated, the Development Team should create a sprint backlog, which is a list of the items that will be worked on during the sprint.
Sprint Planning is an essential part of Scrum; it sets the direction for the sprint and ensures that the team is aligned and committed to achieving the sprint goal. It also helps the team to identify any challenges early on and adjust their plan accordingly.
Sprint Retrospective, aka Scrum Retrospective
Sprint Retrospectives are held at the end of each sprint. The purpose of the sprint retrospective meeting is to allow the team to reflect on what went well and what can be improved during the sprint. The aim is to identify areas for improvement and make changes that will lead to better performance in the next sprint. This sprint retrospective meeting allows the entire team to come together, share their perspectives, and discuss what worked and didn't.
During the sprint retrospective, the team should focus on the following:
Reviewing the progress of the sprint: The team should review the progress of the sprint and assess whether the sprint goals and objectives were met.
Identifying what went well: The team should identify what worked well during the sprint and what contributed to the team's success.
Identifying what can be improved: The team should identify what did not work well during the sprint and what can be improved. The team should also suggest changes that can be made to improve performance and provide learning opportunities.
Prioritizing improvements: The team should prioritize the improvements that need to be made and create an action plan to implement them. Improvements may be added to the product backlog by the product owner.
Sprint retrospective meetings can become stale over time. Many teams use their sprint retrospective meetings as a team-building opportunity. Gamification, aka Agile Games, is often used to encourage collaboration and interaction during the sprint retrospective meeting.
For sprint retrospectives to be compelling, trust and psychological safety are required. Team members must feel comfortable speaking up and sharing their thoughts, ideas, and concerns without fear of judgment or retribution. They should also be open to feedback and willing to listen to others. With trust and psychological safety, the team can have honest, open, and constructive conversations, leading to continuous improvement, better performance, and, ultimately, a better product. To foster psychological safety, attendance at the sprint retrospective should be limited to only those who perform the work.
A meeting at the end of a sprint to review the completed work and gather feedback. Task Board A physical or virtual board used to track work and progress during a sprint.
A physical or virtual board used to track work and progress during a sprint.
A software development technique where tests are written before any code is written.
A technique for managing time and setting deadlines by allocating a fixed amount of time for a particular task or project.
The belief in the reliability, truth, ability, or strength of someone or something. Trust is a fundamental component of effective teamwork, and it enables team members to rely on each other, communicate openly and honestly, and collaborate effectively.
User Story (User Stories)
Short, simple descriptions of a feature or functionality from an end user's perspective.
User Story Mapping
A technique created by Jeff Patton that is used in Agile development methodologies to organize and prioritize the requirements for a product or service. It involves creating a visual map that shows how user stories (short, simple descriptions of a feature or functionality from the user's perspective) relate to each other. The technique is used to help ensure that the product or service meets the user's needs and is developed logically and coherently.
The process of user story mapping typically involves the following steps:
Identify the user or customers of the product or service, and understand their needs and goals.
Create user stories that describe the features or functionality that the user needs.
Group the user stories into larger themes or categories, such as "account management" or "order processing."
Arrange the user stories into a visual map, with the most important or critical user stories at the top and less important user stories at the bottom.
Prioritize the user stories based on their importance and dependencies.
Refine and refine the map as new information becomes available or as the product development process progresses.
The user story map is a valuable tool for ensuring that the product development process is user-centered and that the product or service meets the user's needs. It helps the team to understand the big picture and to ensure that the product is developed logically and coherently. It also helps the team to identify and prioritize the most critical features and functionality and to ensure that the product is delivered incrementally, with the most important features delivered first.
User story mapping is a simple but powerful technique that can help teams to deliver better products and services. It's a collaborative process that requires active participation from the team and stakeholders, it helps to align everyone around the same goal, and it leads to a shared understanding of what's being built and why.
A measure of the work a team can complete in a sprint.
A linear and sequential approach to software development where each phase of the project, such as requirements gathering, design, and testing, is completed before moving on to the next phase.