Cheat Sheet covering key concepts for PSM I & PSPO I

Scrum Framework:
1. Scrum Roles:

Scrum Master:

 Leadership: Focus on facilitating and serving the needs of the Scrum Team.
 Coaching: Guiding the team and organization in adopting Scrum practices.
 Facilitation: Assisting in the planning and execution of Scrum events.

Product Owner:

 Product Backlog Management: Responsible for maintaining and prioritizing the Product
Backlog.
 Value-driven: Ensuring that the team works on high-priority items that bring maximum value.

Development Team:

 Cross-functional: Composed of individuals with diverse skills to deliver a complete Increment.

 Self-organizing: Capable of determining how to accomplish the work without external direction.
 Empowered: Given the authority to make decisions regarding the work they undertake.

2. Scrum Artifacts:

Product Backlog:

 Prioritization: Constantly ordering items based on value and need.

 Refinement: Regularly refining and clarifying items to make them ready for Sprint Planning.
 User Stories: Commonly used format for expressing product backlog items.

Sprint Backlog:

 Sprint Goal: The overarching objective for the Sprint that the team commits to achieving.
 Task Breakdown: Breaking down the user stories into smaller tasks for better planning and
tracking.

Increment:

 Definition of Done: A shared understanding of the criteria that must be met for work to be
considered complete.
 Potentially Shippable Product Increment: Ensures each increment is in a state to be potentially
released to users.

3. Scrum Events:

Sprint:

 Time-boxed Iteration: A fixed duration, usually 2-4 weeks.

 Goal-oriented: Focused on delivering a potentially releasable product increment.

Sprint Planning:

 What Can Be Done: Selecting items from the Product Backlog for the Sprint.
 How the Work Will Be Achieved: Planning the tasks required to complete the selected items.

Daily Scrum:

 15-minute Time-boxed Event: A brief, daily synchronization meeting.

Agile HUB @ T-Systems Iberia | Agile Challenge

  Daily Inspection and Adaptation: Team members discuss progress, plan for the day, and
address impediments.

Sprint Review:

 Presentation (not DEMO) of the Increment: The team showcases the completed work.
 Feedback and Collaboration: Stakeholders provide feedback, and the team collaborates on the
next steps.

Sprint Retrospective:

 Continuous Improvement: Reflecting on the Sprint and finding ways to improve.

 Inspection and Adaptation: Identifying and adapting processes that can be enhanced.

Scrum Values:
1. Commitment:

 Individual and Team Commitment: A commitment to achieving the Sprint Goal and delivering a
valuable increment.
 Definition of Done: A shared commitment to meeting the agreed-upon criteria for each backlog
item.

2. Courage:

 Openness: Honest communication and transparency within the team and with stakeholders.
 Respect: Valuing the perspectives and contributions of all team members.

3. Focus:

 Empiricism: Making decisions based on observation and experimentation.

 Transparency: Clear visibility into the work being done, progress, and potential impediments.

Scrum Principles:
1. Empiricism:

 Transparency: The state of being open and easily understood.

 Inspection: Regularly checking progress and adapting based on observed results.
 Adaptation: Making changes based on inspection results to improve.

2. Self-Organization:

 Cross-functional Teams: A group with all the necessary skills to deliver a complete product.
 Empowered Teams: Teams have the authority to make decisions and manage their own work.

3. Collaboration:

 Open Communication: Frequent and honest communication within the team and with
stakeholders.
 Shared Understanding: A common understanding of goals, priorities, and work among team
members.

Agile HUB @ T-Systems Iberia | Agile Challenge

Product Owner Responsibilities:
1. Visionary Leadership:

 Creating and communicating a clear product vision.

 Aligning the team with the overall business goals.

2. Value Maximization:

 Ensuring the team works on the most valuable features first.

 Constantly reassessing priorities based on changing business needs.

3. Stakeholder Management:

 Engaging with stakeholders to gather input and feedback.

 Balancing competing interests to maximize overall value.

4. Product Backlog Management:

 Maintaining a well-ordered and transparent product backlog.

 Regularly refining and updating the product backlog based on new information.

5. Release Planning:

 Collaborating with the team to plan releases and increments.

 Ensuring that each increment contributes to the overall product vision.

Scrum Metrics:
1. Velocity:

 Measure of Work Completed: The average amount of work a team can complete in a Sprint.
 Historical Performance Indicator: Used for capacity planning and predicting future Sprint
outcomes.

2. Burndown Charts:

 Visual Representation: Graphical representation of work remaining over time.

 Used in Planning and Review: Helps teams plan and track progress during the Sprint.

Stakeholder Engagement:
1. Communication:

 Open and transparent communication with stakeholders.

 Regularly updating stakeholders on progress and changes.

2. Feedback Management:

 Gathering and incorporating feedback from stakeholders.

 Balancing feedback with the overall product vision.

Agile HUB @ T-Systems Iberia | Agile Challenge

Additional Concepts:
1. Definition of Done (DoD):

 Criteria for Completeness: Agreed-upon standards that must be met for a product increment to
be considered done.
 Agreed Upon by the Team: A collaborative effort to ensure a shared understanding of
completeness.

2. Technical Debt:

 Cumulative Cost of Rework: The long-term cost of choosing expedient solutions over more
robust ones.
 Addressed in Sprints: Should be considered and addressed during Sprint Planning and Reviews.

3. Inspect and Adapt:

 Continuous Improvement: The core idea that teams should consistently evaluate their
processes and make improvements.
 Feedback Loops: Regular opportunities for reflection, learning, and adaptation.

4. Lean Thinking:

 Applying lean principles to minimize waste and maximize value.

 Continuously improving the product development process.

5. Economics of Product Development:

 Understanding the financial aspects of product development.

 Maximizing return on investment through effective product ownership.

6. Product Lifecycle Management:

 Managing the product throughout its lifecycle.

 Planning for product enhancements and adaptations.

Agile HUB @ T-Systems Iberia | Agile Challenge