Scrum and XP Practices: Cross Reference
December 12, 2007
I've had several people tell me how useful the Scrum/XP cross-reference in our book is, so I thought I'd share it with you, too.
To create this chart, I referred to Ken Schwaber & Mike Beedle's Agile Software Development with Scrum and both editions of Kent Beck's Extreme Programming Explained. Practices that are similar are cross-referenced, but that doesn't mean they're identical. Refer back to the source material to understand how cross-referenced practices differ.
If a row lists n/a for a particular method, that means that there is no corresponding practice defined in that method. Implied means that a similar approach is included or assumed, but it's not described in detail.
If you have corrections, please let me know, with references when possible. I intend this to be a living document.
Art of Agile | 2nd Edition XP | 1st Edition XP | Scrum |
---|---|---|---|
Thinking | |||
Pair Programming | Pair Programming | Pair Programming | n/a |
Energized Work | Energized Work | 40-Hour Week | implied |
Informative Workspace | Informative Workspace | implied | implied |
Root-Cause Analysis | Root-Cause Analysis | implied | implied |
Retrospectives | implied | implied | implied |
Collaborating | |||
Trust | implied | implied | implied |
(in Trust) | Team Continuity | n/a | implied |
Sit Together | Sit Together | implied | Open Working Environment |
The XP Team | Whole Team | On-Site Customer | Scrum Team |
Real Customer Involvement | Real Customer Involvement | implied | implied |
Ubiquitous Language | implied | implied | n/a |
Stand-Up Meetings | implied | implied | Daily Scrum |
Coding Standards | implied | Coding Standards | n/a |
Iteration Demo | implied | implied | Sprint Review |
Reporting | implied | implied | implied |
Releasing | |||
"Done Done" | implied | implied | implied |
No Bugs | implied | implied | n/a |
Version Control | implied | implied | n/a |
(in Version Control) | Single Code Base | implied | n/a |
Ten-Minute Build | Ten-Minute Build | implied | n/a |
Continuous Integration | Continuous Integration | Continuous Integration | n/a |
Collective Code Ownership | Shared Code | Collective Ownership | n/a |
Documentation | implied | implied | implied |
Planning | |||
Vision | n/a | n/a | implied |
Release Planning | Quarterly Cycle | Small Releases | Product Backlog |
(in Release Planning) | Incremental Deployment | implied | implied |
(in Release Planning) | Daily Deployment | implied | n/a |
The Planning Game | implied | The Planning Game | implied |
Risk Management | n/a | n/a | n/a |
Iteration Planning | Weekly Cycle | implied | Sprints |
Slack | Slack | implied | implied |
Stories | Stories | implied | Backlog Items |
Estimating | implied | implied | Estimating |
Developing | |||
Incremental Requirements | implied | implied | implied |
Customer Tests | implied | Testing | n/a |
Test-Driven Development | Test-First Programming | Testing | n/a |
Refactoring | implied | Refactoring | n/a |
Simple Design | Incremental Design | Simple Design | n/a |
Incremental Design & Architecture | Incremental Design | Simple Design | n/a |
Spike Solutions | implied | implied | n/a |
Performance Optimization | implied | implied | n/a |
Exploratory Testing | n/a | n/a | n/a |
Other | |||
n/a | Shrinking Teams | n/a | n/a |
n/a | Negotiated Scope Contract | implied | n/a |
n/a | Pay-Per-Use | n/a | n/a |
implied | implied | implied | Scrum Master |
implied | implied | implied | Product Owner |
n/a | n/a | n/a | Abnormal Sprint Termination |
n/a | n/a | n/a | Sprint Goal |