Your browser doesn't support the features required by impress.js, so you are presented with a simplified version of this presentation.

For the best experience please use the latest Chrome or Safari browser. Firefox 10 (to be released soon) will also handle it.

Agile software development with scrum

Delivery is focused on user needs
Role centric development
Iteration based, iterations are called sprints and last maximum 20 days
Objectives oriented

Some impressions.

Requirements are defined as a set of user stories or features and describe the vision of the product and what to do to get the ^product done. Must be small enough to get delivered in days.

Priorities identifies what to do first to achieve business driven goals. Pareto says that 80% of the business is done with 20% of the effort, so requirements must be ordered by a business driver.

The product backlog

ordered list of user stories
updated iteration over iteration
describe the product roadmap through velocity
continuously updated
each iteration delivers a potentially shippable increment of software

The product owner

is the responsible for the product
resolves daily the impediments

The team is heterogeneous and self-organize. It has a specific identity and it is responsible for the delivery and the Project Management through the Scrum tools.

The Scrum master is the process officer that thicks the time and helps the product owner to resolve the impediments.

The Sprint planning meeting is the Big Bang of a Sprint (iteration) where the Product Owner, Team and Scrum Master sits to describe the sprint objectives and to extract all the task that has to be done to accomplish the Sprint Objective.
The outcome is the Sprint Backlog

The Sprint backlog is owned by the team and enlist the task to be done to get the sprint. Each task has an estimation in term of remaining hours. And every day it drives the Sprint and the team workload that discuss it during the Daily Scrum

The Daily Scrum

, is a 15 mins standup meeting where the team and the Product Owner meet and report what has been done the day before, what is going on and which are the impediments in getting the objectives. Team updates the Sprint Backlog with the remaining hours and update the Burndown chart

The Burndown chart is the visualization of how the sprint is going and it shows how many hours are missing in order to get the product done.

At the end of the sprint, the Sprint Review meeting is the momentum where the team shows the delivery with a demo and they run a retrospective to learn something from the past

The resulting Product is potentially shippable and can follow all the necessary steps to get to production.

And the team is continuously learning a lesson in order to improve step by step.

Use a spacebar or arrow keys to navigate