Let’s start with a birds-eye-view of understanding Scrum.
We’ll define the main phases of a Scrum project framework and explore each of these in detail later.
Watch Our Sample Video
In Scrum, we have a list of Product Requirements called the Product Backlog.
In Scrum, these are referred to as User Stories. These requirements are prioritized from top to bottom according to business value and they include everything you need to build – including new features, usability enhancements, bug fixes, and so on.
You develop these requirements into fully workable and tested code during time-boxed iterations.
In Scrum these iterations are called Sprints and they typically last from 1 to 4 weeks.
You’re going to pull together and work on the requirements you can complete in the time-frame of a single iteration. During that iteration, you define, code and test what you’ve built.
Then you’ll inspect how far you’ve come. Reorder the backlog as needed and pull together another set of requirements to work on in the next iteration.
At the end of each iteration, or Sprint, you end up with a working product that is potentially releasable.
By potentially releasable, we mean that it’s quality code that’s been tested and documented.
It works, and meets the team’s definition of DONE. It does NOT have to be a complete and marketable product all on its own.
For example, if you complete the code for “Print Preview”, but you haven’t already developed the Print feature, the preview feature isn’t very marketable by itself.
When the team has developed enough of the product so that it’s useful and valuable in the marketplace, then you’ll release it for customers to use.
If you want to learn more about Scrum and other Agile methodologies, you may be interested in our Agile Excellence for Product Managers and Product Owners Training and Certification. The course and certification is now available online, in-person, and as private customized training.