Iterative Software Development usingtheSCRUM method · SCRUM is an iterative, incremental process...

transcript

Iterative Software Development

using the SCRUM method

Networked Embedded Systems

Armin Wasicek

Manifesto for Agile Software Development

� Individuals and interactions over processes and tools

� Working software over comprehensive documentation

� Customer collaboration over contract negotiation

� Responding to change over following a plan

http://agilemanifesto.org/

25.04.2012 Networked Embedded Systems 2

What is a Scrum?

Description

� SCRUM is an iterative, incremental process for

developing any product or managing any work.

� Scrum provides a small set of rules that create just

enough structure for teams to be able to focus their

innovation on solving what might otherwise be an

insurmountable challenge.

Characteristics

� Self-organizing teams

� Product progresses in a series of month-long “sprints”

� Requirements are captured as items in a list of “product

backlog”

� No specific engineering practices prescribed

� Uses generative rules to create an agile environment

for delivering projects

� One of the “agile processes”

A fable of chicken and pigs

A Pig and a Chicken are walking down the road.

The Chicken says, "Hey Pig, I was thinking we should open

a restaurant!". Pig replies, "Hm, maybe, what would we

call it?".

The Chicken responds, "How about 'ham-n-eggs'?".

The Pig thinks for a moment and says, "No thanks. I'd be

committed, but you'd only be involved!"

SCRUM roles

� Developement team

• Delivers functionalities

� Product Owner

• Manges product backlog

• Connects functionalities to

user and customer

• Focus on ROI

� ScrumMaster

• Organizes the scrum

• Controlling

CHICKEN:

� Management

• Provides resources

� Customer

• Determines functionalities

� User

• Rates usefulness/usability

For a successful project

you need both types!

� Pregame

− Planning

− System Architecture/High level Design

� Game

− Sprints (Concurrent Engineering)

− Develop (Analysis, Design, Develop)

− Wrap

− Review

− Adjust

� Postgame

− Closure

Scrum Methodology

SCRUM process flow

The Daily SCRUM

� Time boxed to fifteen minutes!

� The Team and the Scrum Master only.

� What have you accomplished since yesterday?

� Are your Sprint Backlog estimates accurate?

� What are you working on today?

� Is there anything blocking you?

Review

Product/Sprint Backlog

� Selected by team at outset of Sprint

� A Sprint is usually 30 days

� Changes during Sprint as information is discovered

� Okay to use other engineering practices (stories, micro-

iterations), but progress must be reported in the

backlog

� Time estimates must be updated daily

The Sprint Burndown Chart

The Product

� Delivers measurable value

� “Potentially Shippable”: the process can be halted after

every Sprint and there will be some value, some ROI

� Must be a product, no matter how incomplete

Process Comparison

Scrum Success Factor

Iterative Software Development usingtheSCRUM method · SCRUM is an iterative, incremental process...

Documents