Scrum Summary

Frequently combined with Extreme Programming(XP) workflow since Scrum didn't provide a defined workflow

Principles

• Make plans around fixed-duration iterations (typically 4 weeks)
• Break work down into small customer-value features that can be delivered within one iteration
• Don't interrupt the team in the middle of an iteration
• Deliver functional improvements to customers at the end of every iteration

Role	Artifacts	Ceremonies
Product owner	Burn-down chart	Daily scrum
Scrum master	Sprint backlog	Sprint planning
Team	Product backlog	End meetings (retrospective - demo)

Pros

1. Simple, lightweight.
2. Good improvement over structure phased process.
3. Good starting point when no consistent or poorly defined workflow are defined.

Cons

1. Unnecessary inventory (inventory waste): time boxed planning usually provides a much bigger backlog than what is strictly necessary to pick the next work item. 
2. Expensive estimation effort: Instead of estimating the average size of backlog items, effort are spent on estimating each particular item thus generating waste.
3. Product Owner role trivializes the problems of product planning, product design, and requirement analysis.