About Scrum

Scrum Process

Chartering (Strategy) The Product Owner explains in a few statements what the product is and why it is valuable. The team discusses success criteria and sets appropriate expectations.
Epics An epic level story is a single piece of work that is too large to be completed in a single iteration. It requires breakdown into smaller stories.
Themes A theme is a categorization element for use by the product owner. A theme is made up of a set of stories grouped around some functional area, persona or some other classification criteria.
Stories A story, also known as a user story or a product backlog item in Scrum, is the unit of business value from which task level work is derived.
Overview A release is a planning and delivery cycle that takes into consideration priorities, goals, dependencies, risks and other planning considerations in establishing milestones.
Planning Meeting The planning meeting is a session in which features are reviewed and prioritized, key dates and milestones are established, and the team determines which features will be delivered in the timeframe identified.
Prioritizing The list of stories must be rank-ordered sequentially so that the team understands the priority order in which to complete the work.
Estimation Accurate estimation in software development has proven challenging, to say the least. Instead of trying to answer the question "how long?" Teams answer the question "how big?"
Overview An iteration (or Sprint in Scrum) is a fixed-length timebox during which a development team completes a portion of their product backlog.
Planning Meeting The team holds a planning meeting at the beginning of each iteration to identify the stories that will be developed, and to break them down into tasks and acceptance criteria.
Tasks During the Iteration Planning meeting, stories are broken down into tasks. The tasks are all the work the team must complete to accept the story as done.
Defects There are times when defects or bugs are introduced during the development process. Open defects should be prioritized and planned into each iteration.
Acceptance Criteria Acceptance tests describe requirements in a testable format that the software must conform to.
Read Do Your User Stories Include Acceptance Criteria?
Daily Standup This meeting is an opportunity for teams to communicate what they've done, what they are committing to do next, and any issues that are causing them to be less effective.
Daily Standup This meeting is an opportunity for teams to communicate what they've done, what they are committing to do next, and any issues that are causing them to be less effective.
Read Do you do Daily Scrums (aka stand-up meetings)?
Iteration Review The goal of the review meeting is to demonstrate the features and functions completed during the iteration. The meeting gives project stakeholders the opportunity to see the actual progress being made.
Retrospective Retrospectives is a discussion where teams collaboratively examine and expose opportunities for improvement in terms of process and practices.
Burndown Charts Very simple, visible progress charts serve as helpful tools for communicating both to the team and to the rest of the organization.
Velocity Velocity is the measure of the throughput of an agile team per iteration. Since a user story represents value to the customer, velocity is the rate at which a team delivers value.
Cumulative Flow The Cumulative Flow diagram provides a graphic depiction of how stories are moving through various statuses on the way to being "Done".
Trends Frequent inspection and adaptation are indispensable elements of any successful agile development undertaking.

8 Steps to Scrum

8 Steps to Scrum
Figure: This Scrum image includes all the important steps from the initial meeting to the Review and Retro. Print this "SSW 8 Steps to Scrum pdf" and put it on your 'War Room' wall.

A Case Study

Watch the Case Study of how one of SSW Scrum teams did a website upgrade for the National Australia Day Council:

Book a Scrum Professional

Email or call Ulysses on +61 2 9953 3000 to get started!

Australia Wide

We have consultants available in all Australian capital cities including Sydney, Melbourne, Brisbane, Adelaide, Perth and Canberra.

We also offer 24 hours support by using Ben from Belgium and Danijel from Slovenia.

Get your project started

To find out if SSW can help your business, give us a call on +61 2 9953 3000 or contact us by email to get started!