Skip to content

Getting to Done

For someone else
Carlton Nettleton
For someone else

Too many Scrum Teams are focused on delivering more outputs rather than delivering better outcomes for customers and users. Focusing on outputs is an easy trap to fall into because outputs – user stories, features, velocity, etc. – are easy to measure, while outcomes, the positive benefits customers and end users receive from your product (or service), are hard to quantify. However, by focusing on outcomes, we can better adopt a perspective of that allows us to maximize the amount of work not done for the Scrum Team which enables us to deliver more, better and faster value to the business.

Here is the course outline:

1. Exercise - Escaping the Velocity Trap

2. Videos - Getting to Done

3. Apply Your Learning - Scrum Outside of Software

4. Conclusion - Software Craftsmanship

5. Challenge - Strong Definition of Done

To complete this challenge, you will need to be actively working with a Scrum or Agile team. If you are not currently part of a Scrum or Agile team, please contact your instructor to unlock a hidden quest.

6. Feedback - Getting to Done


The following certificates are awarded when the course is completed:

Course Completion Certificate
Back to top