Лист за преговор: Mastering Scrum Framework

Agile & Scrum Revision Sheet

1. 📌 Essentials

• Agile methodology emphasizes flexibility collaboration, and iterative development.
• Scrum is a framework within Agile focusing on roles, artifacts, and events.
• Key roles: Product Owner, Scrum Master, Development Team.
• Main artifacts: Product Backlog, Sprint Backlog, Burndown Chart.
• Critical events: Daily Scrum, Sprint Planning, Sprint Review, Retrospective.
• Prioritizes individuals/interactions over tools/processes.
• Sprint duration typically 2-4 weeks.
• The Scrum Master acts as a facilitator, not a manager.
• The Product Owner manages the product vision and backlog.
• The Development Team creates the product increment.

2. 🧩 Key Structures & Components

• Product Backlog — prioritized list of features/functions.
• Sprint Backlog — subset of Product Backlog for current sprint.
• Burndown Chart — visual progress indicator of remaining work.
• Daily Scrum — 15-minute stand-up for synchronization.
• Sprint Planning — sets sprint goal and selects backlog items.
• Sprint Review — inspects the increment and gathers feedback.
• Sprint Retrospective — team reflection to improve processes.
• Roles:
  • Product Owner — defines and prioritizes product features.
  • Scrum Master — facilitates Scrum adherence.
  • Development Team — executes work to build the product.

3. 🔬 Functions, Mechanisms & Relationships

• Product Owner prioritizes backlog items based on value.
• Sprint Planning pulls high-priority items into Sprint Backlog.
• Development Team works on Sprint Backlog tasks during the sprint.
• Daily Scrum ensures team synchronization and identifies obstacles.
• Burndown Chart tracks remaining work, updating daily.
• Sprint Review gathers stakeholder feedback on the increment.
• Retrospective identifies improvements for future sprints.
• Roles collaborate to ensure transparency, inspection, and adaptation.
• Flow:

  Product Backlog
       ↓ (prioritized)
  Sprint Planning
       ↓
  Sprint Backlog
       ↓ (work)
  Daily Scrum → Progress updates
       ↓
  Sprint Review → Feedback
       ↓
  Retrospective → Process improvements
  

4. 📊 Comparative Table

Item	Key Features	Notes
Product Backlog	Prioritized list of features	Managed by Product Owner
Sprint Backlog	Tasks selected for current sprint	Derived from Product Backlog
Burndown Chart	Visual progress of remaining work	Updated daily during sprint
Daily Scrum	15-minute stand-up for team synchronization	Focus on obstacles and coordination
Sprint Duration	Usually 2-4 weeks	Fixed length for consistency
Roles	Product Owner, Scrum Master, Development Team	Clear responsibilities

5. 🗂️ Hierarchical Diagram (ASCII)

Agile & Scrum
 ├─ Principles
 │   ├─ Individuals over tools
 │   └─ Adaptation over fixed plans
 ├─ Roles
 │   ├─ Product Owner: defines vision
 │   ├─ Scrum Master: facilitates process
 │   └─ Development Team: builds product
 ├─ Artifacts
 │   ├─ Product Backlog: prioritized features
 │   ├─ Sprint Backlog: current tasks
 │   └─ Burndown Chart: progress tracker
 └─ Events
     ├─ Daily Scrum: 15 min
     ├─ Sprint Planning
     ├─ Sprint Review
     └─ Retrospective

6. ⚠️ High-Yield Pitfalls & Confusions

• Confusing Scrum Master with a project manager; Scrum Master is a facilitator.
• Overlooking the iterative nature; each sprint produces a potentially shippable product.
• Misunderstanding the role of the Product Owner as a decision-maker, not a manager.
• Assuming the Sprint Backlog is static; it evolves during the sprint.
• Confusing the purpose of the Retrospective with Sprint Review.
• Believing the Daily Scrum is a problem-solving meeting; it's for synchronization.
• Ignoring the importance of the Burndown Chart as a progress tool.
• Thinking Scrum prescribes detailed documentation; it values working software.

7. ✅ Final Exam Checklist

• Understand Agile principles: individuals/interactions, adaptation.
• Know Scrum roles: Product Owner, Scrum Master, Development Team.
• Describe artifacts: Product Backlog, Sprint Backlog, Burndown Chart.
• Explain Scrum events: Daily Scrum, Sprint Planning, Review, Retrospective.
• Recognize the typical sprint duration (2-4 weeks).
• Clarify the Scrum Master’s facilitative role.
• Identify the Product Owner’s responsibilities.
• Describe how backlog items are prioritized and selected.
• Understand how progress is tracked via Burndown Chart.
• Know the purpose of each Scrum event.
• Comprehend the iterative cycle of planning, executing, reviewing, and improving.
• Emphasize transparency, inspection, and adaptation.
• Recognize that the goal is delivering potentially shippable product increments each sprint.
• Be aware of common pitfalls and misconceptions.
• Recall the core values: commitment, focus, openness, respect, courage.

---