Like all of the agile processes, Scrum is an iterative and incremental approach
to software development. Although the terms iterative and incremental each have a
unique meaning, they are often used together. Let’s briefly tease them apart so we
can better understand their meanings.
Chapter Contents
- Deliver Working Software Each Sprint
- Defining Potentially Shippable
- Identifying Potentially Shippable Guidelines
- Deliver Something Valuable Each Sprint
- Prepare in this Sprint for the Next
- Billiard Ball Sprints
- Only Pull into a Sprint What Can Be Completed
- Work Together Throughout the Sprint
- Avoid Activity-Specific Sprints
- Replace Finish-to-Start Relationships with Finish-to-Finish Ones
- Overlapping User Experience Design
- Think Holistically, Work Incrementally
- Architecture and Database Design
- Keep Timeboxes Regular and Strict
- Never Extend a Sprint
- Don’t Change the Goal
- Break the Habit of Redirecting a Team
- Get Feedback, Learn, and Adapt
- Additional Reading