Scrum Framework Deep Dive

Scrum Overview

Scrum Theory

3 pillars:
1. Transparency: Mọi thứ visible
2. Inspection: Thường xuyên kiểm tra
3. Adaptation: Điều chỉnh khi cần

5 values:
1. Commitment: Cam kết với goal
2. Focus: Tập trung vào sprint goal
3. Openness: Cởi mở về challenges
4. Respect: Tôn trọng nhau
5. Courage: Can đảm làm đúng

3 Roles

Product Owner (PO)

Trách nhiệm:
- Define product vision
- Manage Product Backlog
- Prioritize items
- Accept/reject work
- Talk to stakeholders
- Maximize value

KHÔNG:
- Manage team (không phải manager)
- Estimate work
- Assign tasks
- Implement solutions
- Attend daily

Skills:
- Business acumen
- Communication
- Decision making
- Negotiation

Scrum Master (SM)

Trách nhiệm:
- Facilitate Scrum events
- Coach team on Scrum
- Remove obstacles
- Protect team
- Facilitate improvements
- Teach stakeholders

Servant Leadership:
- Phục vụ team
- Không command
- Tạo điều kiện
- Mentor

KHÔNG:
- Project manager
- Team lead
- Decision maker

Development Team

Đặc điểm:
- Self-organizing
- Cross-functional
- Size: 3-9 người
- Full-time dedicated
- No titles (theo Scrum)
- Collective accountability

Skills (ví dụ):
- Developers
- Testers
- Designers
- DevOps
- Data

Trách nhiệm:
- Estimate
- Plan Sprint
- Deliver increment
- Self-manage
- Raise impediments

5 Events

1. Sprint (Iteration)

Duration: 2-4 tuần (thường 2)
Fixed length
Never extend

Bao gồm:
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective

Sprint Goal:
- 1 objective
- Shared by team
- Guide the work
- Không đổi mid-sprint

2. Sprint Planning

Khi: Đầu sprint
Duration: 2-4 giờ (2 tuần sprint)

3 topics:
1. WHY - Sprint Goal (value)
2. WHAT - Items selected (backlog)
3. HOW - Plan to deliver

Participants:
- PO (chủ trì)
- SM (facilitate)
- Dev team (toàn bộ)

Outputs:
- Sprint Goal
- Sprint Backlog
- Delivery plan

3. Daily Scrum

Khi: Mỗi ngày
Duration: 15 phút (time-boxed)
Format: Standup

3 questions (traditional):
1. Đã làm gì hôm qua?
2. Sẽ làm gì hôm nay?
3. Có obstacles?

Modern approach:
- Focus on Sprint Goal progress
- Update board
- Re-plan if needed

Best practices:
- Same time, same place
- On time, end on time
- Focused discussion
- Offline after (parking lot)

4. Sprint Review

Khi: Cuối sprint
Duration: 1-2 giờ
Participants: Team + stakeholders

Agenda:
1. Sprint overview
2. Demo increment
3. Feedback
4. Backlog updates
5. Next steps

Purpose:
- Inspect increment
- Adapt backlog
- Transparent
- Collaborative

Không phải:
- Status meeting
- Complaint session

5. Sprint Retrospective

Khi: Cuối sprint, sau Review
Duration: 1.5 giờ
Participants: SM + Dev team (không stakeholders)

Formats:
1. Start-Stop-Continue
2. Mad-Sad-Glad
3. 4Ls (Liked, Learned, Lacked, Longed for)
4. Sailboat
5. Timeline
6. Starfish

Outputs:
- Action items (2-3)
- Owners assigned
- Follow up in next retro

Purpose:
- Inspect process
- Improve
- Team building
- Open communication

3 Artifacts

Product Backlog

Owned by: PO
Content: All desired features, changes
Order: Priority (value)

Structure:
- Epic → Feature → User Story → Task

Item format (User Story):
"As a [role], I want [feature], so that [benefit]"

Example:
"As a customer, I want to search products, 
so that I can find what I need quickly"

Attributes:
- ID
- Title
- Description
- Acceptance Criteria
- Priority
- Estimate
- Dependencies

Sprint Backlog

Owned by: Dev Team
Content: Sprint Goal + selected items + plan

Format:
- Sprint Goal statement
- Selected Product Backlog items
- Task breakdown
- Estimates (hours/days)
- Assignment

Updated daily
Tự thay đổi trong sprint

Increment

Định nghĩa: Tổng hợp các backlog items hoàn thành trong sprint
Điều kiện: Đáp ứng Definition of Done
Đặc điểm: Có thể sử dụng được (usable)
Quan trọng: Working software > documentation

Ví dụ Increment:
- Feature A: Completed + tested + deployed to staging
- Feature B: Completed + tested
- → Increment = A + B

Definition of Done (DoD)

Ví dụ DoD cho team software

☐ Code complete
☐ Code reviewed (peer)
☐ Unit tests written and passing
☐ Integration tests passing
☐ Acceptance criteria met
☐ No critical bugs
☐ Documentation updated
☐ Deployed to staging
☐ PO accepted

DoD tốt vs xấu

TỐT:
- Rõ ràng, đo lường được
- Team thống nhất
- Rigorous enough
- Không thay đổi giữa các sprint
- Include quality standards

XẤU:
- Vague ("Done means done")
- Too weak (chỉ "code complete")
- Too strong (không thể achieve)
- Thay đổi liên tục
- Không có testing/quality

Scrum Anti-Patterns

Common Anti-Patterns

1. Scrum Master as Project Manager
2. Daily Scrum = status report to SM
3. PO không available
4. Sprint Goal không có
5. Mid-sprint changes
6. Skipping Retro
7. Retro không có action
8. Velocity as KPI
9. Micro-management
10. No stakeholder involvement

Scrum vs Kanban

                Scrum                Kanban
Iterations      Fixed (2-4 weeks)    Continuous
Changes         No mid-sprint        Anytime
Roles           Defined (PO/SM/Dev)  Optional
Metrics         Velocity             Lead time
Ceremonies      Mandatory            Optional
WIP Limits      Sprint-based         Explicit limits
Best for        New products         Support, ops

Scaling Scrum

Multiple Teams, One Product

Options:
1. Scrum of Scrums
   - Daily sync between teams
   - Representative from each

2. SAFe
   - Full framework
   - PI Planning
   - Release Train Engineer

3. LeSS
   - Same PO, one backlog
   - Multiple teams
   - Sprint Planning Part 1 + 2

4. Nexus
   - Scrum.org
   - 3-9 teams
   - Nexus Integration Team

Bài tập thực hành

Hãy thiết kế Scrum setup cho một team!