Certified Scrum Professional (CSP) Exam Study Flashcard

Empirical Process Control is the Scrum principle that decision-making is based on observation, experience, and experimentation rather than on detailed upfront planning. This approach promotes adaptation and responsiveness to change.

Sprint Review Feedback is input from stakeholders and team members about the Increment and the Scrum process. It helps the team make necessary adjustments to the Product Backlog, improve future Sprints, and better meet stakeholder needs.

The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team. This includes managing the Product Backlog, prioritizing items, and ensuring that the team understands the requirements.

Scrum Values—Commitment, Courage, Focus, Openness, and Respect—guide the behavior and decision-making within a Scrum Team. These values foster a collaborative and productive environment and contribute to the team's overall effectiveness.

Time-boxing refers to setting fixed durations for Scrum events such as Sprints, Sprint Planning, Daily Stand-ups, and Sprint Retrospectives. This ensures that these events are efficient and help maintain focus and momentum.

Scrum Teams ensure quality through adherence to the Definition of Done, regular code reviews, testing, and continuous integration. Additionally, the team’s commitment to Scrum values and practices helps maintain high-quality standards.

Scrum addresses complex problem-solving through iterative development, continuous feedback, and adaptability. By breaking work into manageable increments and inspecting progress regularly, teams can respond to emerging challenges effectively.

Scrum addresses risk management through regular inspections and adaptations. By reviewing progress and adapting the Product Backlog, teams can identify and mitigate risks early. Sprint reviews and retrospectives also help manage risks.

Scrum addresses stakeholder engagement through regular Sprint Reviews, where stakeholders can provide feedback and interact with the team. This continuous engagement helps align the product with stakeholder needs and expectations.

In Scrum, Value is defined by the benefits and usefulness delivered to stakeholders through the product. It encompasses meeting customer needs, achieving business objectives, and providing incremental improvements to the product.

A successful Sprint is defined by achieving the Sprint Goal, delivering a potentially shippable Increment that meets the Definition of Done, and ensuring that the team has effectively collaborated and addressed any challenges encountered.

Scrum ensures alignment with business objectives through regular reviews, continuous stakeholder engagement, and by prioritizing work based on business value. The Product Backlog is refined to reflect changing business needs and priorities.

Scrum ensures focus on delivering value through regular prioritization of the Product Backlog, setting clear Sprint Goals, and delivering incremental improvements that are reviewed and adjusted based on stakeholder feedback.

Scrum facilitates stakeholder feedback through regular Sprint Reviews, where stakeholders can review the Increment, provide input, and suggest changes. This continuous feedback loop helps ensure the product aligns with stakeholder needs.

Scrum handles cross-team dependencies by fostering communication and collaboration between teams. Scrum Masters coordinate with other teams to resolve dependencies and ensure that they do not impede the progress of the teams involved.

Scrum handles external dependencies by identifying them early, communicating with external parties, and managing dependencies through effective planning and coordination. Scrum Masters and Product Owners work to mitigate impacts on the team’s work.

Scrum integrates with other Agile methodologies by adopting best practices and principles that align with Agile values, such as iterative development and continuous improvement. It can be combined with methodologies like Kanban or XP to address specific needs.

Scrum supports continuous improvement through iterative Sprints, regular inspections during Sprint Reviews, and team reflections during Sprint Retrospectives. These practices help teams learn from experience and refine their processes.

In Scrum, incomplete work at the end of a Sprint is either added back to the Product Backlog or carried over into the next Sprint, based on the team’s review and prioritization. The team assesses and adjusts their approach in subsequent Sprints.

The Sprint Backlog is a list of tasks and requirements identified by the Scrum Team to achieve the Sprint Goal. It helps the team plan and manage their work during the Sprint, and it is updated as tasks are completed or adjusted.

Value Stream Mapping helps identify and visualize the flow of work through a process, including areas of waste and inefficiencies. In Scrum, it can be used to understand and improve how value is delivered to the customer.

A Scrum Team is self-organizing when it independently decides how to best accomplish its work. Team members take ownership of their tasks, collaborate, and manage their work without being directed by outside authorities.

Technical Debt refers to the implied cost of additional rework caused by choosing an easy solution instead of a better, more comprehensive one. It can accumulate over time and affect the quality and maintainability of the product.

Cross-functional teams bring together members with various skills needed to complete the product work. This promotes collaboration, reduces dependencies on external resources, and increases the team’s ability to deliver a potentially shippable product.

A good Product Backlog item is clear, actionable, and valuable. It should be specific enough to be understood and estimated by the team, have acceptance criteria, and be prioritized based on its value to the customer and business.

The three pillars of Scrum are Transparency, Inspection, and Adaptation. These pillars support the Scrum framework and ensure effective communication, continuous improvement, and responsive changes to emerging needs.

Scrum Master Servant Leadership implies that the Scrum Master serves the team by facilitating Scrum events, removing impediments, coaching team members, and supporting the Product Owner, rather than directing or controlling the team.

Backlog Refinement, also known as Backlog Grooming, involves reviewing and updating the Product Backlog items to ensure they are well-defined, prioritized, and ready for future Sprints. It is important for maintaining a clear and actionable backlog.

Release Planning involves defining a plan for delivering a product or a set of features to stakeholders. It includes determining the scope, schedule, and milestones, aligning with the Product Roadmap and the goals of the organization.

A Burndown Chart is a graphical representation of work remaining versus time. It helps track progress towards completing the Sprint or project. It provides visibility into the team’s pace and whether they are on track to meet the Sprint Goal.

A Product Increment is a complete and usable version of the product developed during a Sprint. It includes all completed features and improvements, whereas a Feature is a specific functionality or capability within the Increment.

A Scrum Board is a visual tool used to track the progress of work within a Sprint. It typically includes columns for different stages of work, such as To Do, In Progress, and Done. It helps the team manage and visualize their workflow.

A Scrum of Scrums is a scaling technique used to coordinate work across multiple Scrum Teams. It involves representatives from each team meeting regularly to discuss progress, dependencies, and resolve inter-team issues.

The Product Backlog is a prioritized list of features, enhancements, bug fixes, and technical work that is needed for the product. It is maintained by the Product Owner and is continuously refined and adjusted as needed.

A Scrum Artifact is a work or value that is created and maintained during a Scrum project. The main Scrum Artifacts are the Product Backlog, Sprint Backlog, and Increment. They provide transparency and opportunities for inspection.

A Sprint Goal is a short, clear statement that describes the objective of the Sprint. It provides direction and purpose for the Scrum Team and helps in focusing on what is important for the Sprint.

An Increment is the sum of all completed Product Backlog items during a Sprint and all previous Sprints. It must be in a usable state and meet the Definition of Done, providing a potentially shippable product or feature.

Agile Coaching involves guiding teams and individuals to better understand and implement Agile practices, including Scrum. It focuses on fostering Agile mindsets, improving team collaboration, and enhancing overall performance.

Velocity is a measure of the amount of work a Scrum Team can complete in a Sprint, typically expressed in story points or work units. It helps in predicting future performance and planning, but should not be used as a performance metric.

The Definition of Done is a shared understanding among the Scrum Team of what it means for work to be complete. It includes criteria such as code being tested, documentation being updated, and the feature being potentially shippable.

A Feature is a high-level capability or function of the product, while a User Story is a more detailed description of a specific functionality from the user's perspective. User Stories often help define and break down Features into actionable tasks.

The Sprint Review is important for demonstrating the completed Increment, gathering stakeholder feedback, and adapting the Product Backlog. It provides transparency about progress and helps ensure that the product meets stakeholder expectations.

The Daily Scrum is important for synchronizing the team’s activities, identifying impediments, and planning work for the next 24 hours. It helps maintain team alignment and allows for quick adjustments to stay on track towards the Sprint Goal.

Sprint Goals provide a clear focus and objective for the Sprint, guiding the team’s work and decision-making. They help prioritize tasks, align the team on a common purpose, and measure the success of the Sprint.

Sprint Review Preparation involves ensuring that all necessary materials, such as the Increment and presentation materials, are ready for the review meeting. It helps ensure a smooth and productive review process, allowing for meaningful feedback.

The purpose of a Sprint Retrospective is to reflect on the past Sprint, identify what went well, what didn’t, and how processes can be improved. The goal is to continuously enhance team performance and Scrum practices.

The purpose of the Sprint Planning meeting is to define the work that will be completed in the upcoming Sprint, set the Sprint Goal, and plan how the Development Team will achieve it. It aligns the team on priorities and objectives.

The purpose of the Sprint Review is to inspect the Increment, gather feedback from stakeholders, and adapt the Product Backlog as needed. It allows the team to demonstrate the work completed and make necessary adjustments to future work.

Agile Metrics, such as velocity, burndown charts, and lead time, provide insights into team performance, progress, and efficiency. They help teams make data-driven decisions, improve processes, and manage expectations.

The Development Team is responsible for delivering a potentially shippable Increment of the product at the end of each Sprint. They self-organize to complete the work, ensuring high quality and meeting the Definition of Done.

The Scrum Master ensures team dynamics are healthy by facilitating open communication, resolving conflicts, and fostering a positive, collaborative environment. They help maintain focus on Scrum values and practices.

The Scrum Master facilitates conflict resolution by mediating disputes, encouraging open communication, and helping the team address issues constructively. They work to maintain a collaborative and respectful team environment.

The Scrum Master supports the Product Owner by helping them manage the Product Backlog, facilitating Scrum events, and ensuring that the Product Owner has the necessary information and support to prioritize effectively.

The Scrum Master supports the Development Team by facilitating Scrum events, removing impediments, fostering a collaborative environment, and ensuring that the team adheres to Scrum practices and principles.

The Scrum Framework embraces change through its iterative and incremental nature. By working in Sprints and regularly inspecting and adapting the product and processes, Scrum allows for flexibility and responsiveness to new information.

The Scrum Master facilitates the Sprint Planning meeting, ensuring that it is effective and that the team agrees on the Sprint Goal and the Backlog items to be included in the Sprint. They help the team understand the work required.

The Scrum Master helps identify and remove impediments that are obstructing the team’s progress. They work with the team and organizational stakeholders to address these issues and ensure the team can work efficiently.

The Scrum Master facilitates the Sprint Retrospective by ensuring it is conducted effectively, helping the team identify strengths and areas for improvement, and guiding the creation of actionable improvement plans.

A Product Roadmap outlines the high-level vision and strategic goals for the product. It helps align the team and stakeholders on long-term objectives, priorities, and planned releases, providing context for the Product Backlog.

A clear and concise Product Backlog ensures that all items are well-defined, prioritized, and understood by the team. This helps the team to deliver value efficiently, focus on the most important work, and avoid confusion and rework.