Successfully Working with Scrum in Teams

The 3 Scrum Roles

👔 Product Owner

Responsibility: Maximizing product value

✅ Manages and prioritizes the Product Backlog
✅ Defines user stories and acceptance criteria
✅ Decides on feature scope
✅ Stakeholder communication
❌ Does NOT estimate stories (the team does)

🎯 Scrum Master

Responsibility: Servant leader, removes blockers

✅ Facilitates Scrum ceremonies (Planning, Daily, Retro)
✅ Coaches team in agile methods
✅ Removes impediments (blockers)
✅ Protects team from disruptions
❌ Is NOT a project manager or boss

💻 Development Team (3-9 people)

Responsibility: Delivers working increments

✅ Cross-functional (all skills in team)
✅ Self-organized (decides "how" themselves)
✅ Estimates user stories (Scrum Poker)
✅ Commits to sprint goals
✅ Developers, testers, designers work together

The 5 Scrum Ceremonies

📋

Sprint Planning (4h for 2-week sprint)

Goal: Planning the upcoming sprint

Part 1: What?

• Define sprint goal
• Select stories from backlog
• Scrum Poker for estimates

Part 2: How?

• Break stories into tasks
• Technical discussion
• Capacity check

☀️

Daily Standup (15 min, every day)

Goal: Synchronization, identify blockers

Each team member answers:

1️⃣ What did I accomplish yesterday?
2️⃣ What am I planning today?
3️⃣ Are there any blockers?

⚠️ No detailed discussions – "parking lot" for later!

🎬

Sprint Review (2h for 2-week sprint)

Goal: Demonstration of finished features

✅ Team shows completed user stories
✅ Stakeholders provide feedback
✅ Backlog is adjusted if needed
❌ No PowerPoint – live demo!

🔄

Sprint Retrospective (1.5h for 2-week sprint)

Goal: Continuous improvement

😊 What went well?

Celebrate successes

😞 What went poorly?

Identify problems

💡 What to improve?

Derive action items

🔍

Backlog Refinement (10% of sprint time)

Goal: Prepare upcoming stories

✅ Detail stories
✅ Clarify acceptance criteria
✅ Rough estimates
✅ Identify dependencies

Best Practices for Successful Scrum Teams

✅ Definition of Done (DoD)

Clear checklist when a story is "done":

• Code written & reviewed
• Tests (unit, integration) passed
• Documented
• Deployed & verified

✅ Sprint Length: 2 Weeks

Optimal for balance between flexibility and planning stability. 1 week = too hectic, 4 weeks = too sluggish.

✅ Velocity Tracking

Measure completed story points per sprint. After 3-4 sprints velocity stabilizes → better planning.

✅ Team Colocation (when possible)

Remote is ok, but dedicated team rooms increase productivity by ~15%. For remote: video-first culture + good tools.

✅ No Scope Changes During Sprint

Once committed = protected. New requirements go into next sprint. Exception: critical bugs.

✅ Pair Programming & Code Reviews

Increases code quality, knowledge sharing and reduces bugs by ~60%.

Avoid Common Anti-Patterns

❌ Scrum as Waterfall with Sprints

Sprint 1 = Design, Sprint 2 = Development, Sprint 3 = Testing → This is NOT Scrum! Each sprint must deliver a finished increment.

❌ Product Owner Missing from Planning

Without PO, questions can't be clarified → wrong implementation. PO presence is mandatory!

❌ Daily Standups as Status Reports

The daily is for TEAM synchronization, not reporting to the manager.

❌ Retrospective Without Action Items

"Nice chat, but nothing changes" → useless. Every retro must produce concrete improvements with owner and deadline.

Start with Scrum Now!

Use Scrum Poker for your next sprint planning.

Start Scrum Poker