Scrum Management

Basics of the Framework

court-smith

TechSpectrum#2620

Waterfall

▪ Traditional / Legacy

▪ Predictive

▪ Not Flexible

▪ Long Durations

▪ Used in Fast Food Chains and Construction

Agile

▪ New (2000)

▪ Adaptive

▪ Flexible

▪ Short Durations

▪ Used in Software, Science, Games,

Government.

Agile Manifesto

1 Individuals and Interactions over Processes and Tools

2 Working Software over Comprehensive Documentation

3 Customer Collaboration over Contract Negotiation

4 Responding to Change over Following a Plan

Agile Framework (Scrum)

• Roles

• Events

• Artifacts

Scrum Roles

1 Product Owner

Responsible for the vision, prioritization, marketing,

stakeholder management.

2 Scrum Master

The expert who helps make sure the project is following

scrum practices. They are not a manager. Helps to facilitate

meetings.

3 Development Team

Responsible for executing the work, working together, and

self directed. Typically 5-9 People who are cross functional.

4 Stakeholder

Anyone who has any outside effect on the product

(customer, users, shareholders, company owner, investors)

Scrum Artifacts

1 Product Backlog 2 Sprint Backlog 3 Product Increment

Scrum Events (Ceremonies)

1 Sprint Planning

Inspect the Product Backlog, create a Definition of “Done”

Adapt the Sprint Goal and Sprint Backlog

2 Daily Scrum

Inspect the progress towards Sprint Goal.

Adapt the Sprint Backlog and Daily Plan.

3 Sprint Review

Inspect the Product Increment, Product Backlog, and Market

conditions.

Adapt the Product Backlog

4 Sprint Retrospective

Inspect the Team and Collaboration, Technology, and

Definition of Done.

Adapt to have Actionable Improvements

Product Backlog Refinement

▪ Break down larger requirements as you

come closer to the sprint.

▪ Do not plan longer than 4 sprints.

▪ Work with your Development Team on

breaking down requirements.

Sprints

▪ Scrum projects make progress in a series of “sprints”

▪ Typical duration is 2–4 weeks or a calendar month at most

▪ A constant duration leads to a better rhythm

▪ Product is designed, coded, and tested during the sprint

▪ Plan sprint durations around how long you can commit to keeping change out of the sprint

Resources

Agile Estimating and Planning by Mike Cohn

Agile Product Management: Creating Products that Customers Love by Roman Pichler

Agile Project Management with Scrum by Ken Schwaber

Agile Software Development Ecosystems by Jim Highsmith

Essential Scrum: A Practical Guide to the Most Popular Agile Process by Kenneth Rubin

Scrum and XP from the Trenches by Henrik Kniberg

Succeeding with Agile: Software Development using Scrum by Mike Cohn

The Scrum Guide at www.ScrumGuides.org

User Stories Applied for Agile Software Development by Mike Cohn