Agile Software Development With SCRUM

Agile Software Development with SCRUM

www.scrumguides.com

10 January 2009

Today’s Agenda

Opening: program overview, knowing each other

Understanding Agile and SCRUM

SCRUM simulation

Extra SCRUM topics

Concepts of Agile Planning

We will be having 10-minute breaks each 60-90 minutes.
Agile Software Development with
2 SCRUM ©SCRUMguides

About myself

Alexey Krivitsky
Software developer, Agile coach

Certified ScrumMaster
Certified Scrum Practitioner
http://www.linkedin.com/in/alexeykrivitsky
email: alexey@scrumguides.com
skype: alexeykrv
icq: 436-471-64
gsm: +380 50 358 92 12

Currently building up a training center
www.scrumguides.com


Our presence

Ukrainian Agile community
www.agileukraine.org

Join our Google discussion group

Ukrainian SCRUM portal
www.scrum.com.ua


Today’s Agenda



SCRUM simulation

Extra SCRUM topics



Exercise “Continuum”


Project successes/failures

Have you been on a successful project?

Have you been on an unsuccessful project?


Agile might help you, let’s see…



The two approaches, two cultures

Predictive approach
Sees projects as predictive processes which results can be
foreseen (predicted) with acceptable probability after
reasonable planning and study efforts spent.

Adaptive approach
Questions predictability of projects due to their built-in
complexity. It puts stress on steering based on observations.


The predictive approach
Release

Design spec

Requirements spec

Order

C
D
Actual
need
P
P

R

The adaptive approach

When in the project we 100% know if we
on/off the track in terms of the time, scope,
costs…?
Vision

C

Actual need


The two approaches to project management

Predictive approach
Heavy-weight;
–
Process-oriented;
–
Plan-driven;
–
“Waterfall”.
–

Adaptive approach
Light-weight;
–
People-oriented;
–
Value-driven;
–
“Agile”.
–


Order and Chaos


The two approaches on the time scale

Which advantages/disadvantages of
the approaches you see? Agile Software Development with

Agile and SCRUM

SCRUM – one of the Agile approaches.

It is a project framework, or a set of
recommendations by following which you can
increase the chance of successful ending of
your projects.


Agile Manifesto

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Main aspects of Agile


The main aspects of Agile

Team Work

Prioritization

Short cycles

Learn and Adapt


The main aspects of Agile: Team work

What is a team?

How to make good team?


Team work (cont.)

Exercise “an airplane factory”.


Team work (cont.)

What is a team?

Are you in a good team?

How to become a greater team?

How to evaluate and motivate people’s work
in a team?


Is here such a thing as “team work”?
Release

Design spec

Requirements spec

Order

C
D
Actual
need
P
P

R

A SCRUM team is

A cross-functional group of people
(5-9 members) responsible for managing
itself to develop the product.



Team Work

Prioritization

Short cycles

Learn and Adapt


Prioritization and Traditional approaches

An alternative tool to backlogs are
requirement specifications.


“Gimme all requirements, or ….”


As a result …

As a result all requirements are the
“top priority”.

Which is basically the same as not having
the priorities at all.


And as a result …


What does it mean to us?

As a consequence: we can cut costs and
duration of our projects in 2/3!

Does it mean we (the teams) will earn less
money?


What about your projects?

Think about your current (recent) projects.

List 5-10 features that could have been
avoided or simplified by keeping the product
as good as it was.

What would be your % of rarely/never used
features?


Prioritize (cont.)

YAGNI - “You ain’t gonna need it”.
A strategy of postponing decisions until the last
possible moment.

Product backlog
Just-in-time requirements management tool.


The “menu” (Agile) approach

Product backlog is the project’s menu.

“Servants” help to make better decisions.


What saves our projects?

“The features that we manage to de-scope are
the savers of our projects” © Kent Beck



Team Work

Prioritization

Short cycles

Learn and Adapt


The main aspects of Agile: Short Cycles

The shorter the cycle the more efficient the process

We have more time to “play” with the product that
1.
we are developing;

The sooner we can catch a defect the easier it is to
2.
fix it;

The shorter the cycle (the smaller a batch of work)
3.
the less need we have in creating intermediate
artifacts.

Short Cycles (cont.)

“Fail fast” (с) Ken Schwaber


Iterative and Incremental approach

How do you eat an elephant?
-
One bite at a time!
-


Shorter Cycles = Faster Feedback

Daily meetings
1.
Code Reviews
2.
Release to end-users
3.
Iteration reviews
4.
Continuous integration
5.
Feedback from (onsite) clients
6.
Unit-testing
7.
(Automated) acceptance testing
8.
Pair programming
9.


Shorter Cycles = Faster Feedback (ordered)

Pair programming (immediate feedback)
Unit-testing (5-10 minutes)
Continuous integration (hourly)
Feedback from (onsite) clients (daily)
Daily meetings (daily)
Code Reviews (some days)
(Automated) acceptance testing (some days)
Iteration reviews (each second week)
Release to end-users (some weeks-months)



Team Work

Prioritization

Short cycles

Learn and Adapt


Exercise “Ball Points”


The main aspects of Agile: Learn and Adapt

As we work we learn lots of new things about
the product being developed, technologies
being used, our clients, ourselves.

By incorporating this information into daily
work we can become better day by day.


Visibility tools

In order to evolve the way we work we need to
keep everything visible to ourselves and our
clients

Tools that might help:
Sprint Burndown chart
Task boards
Wikis



Team Work

Prioritization

Short cycles

Learn and Adapt


Would SCRUM help in your case

Think about your current (recent) project.

List 3-5 main things that are (were)
preventing it from being more successful.

Can SCRUM help to avoid them?
Can SCRUM make them visible earlier?
How can SCRUM help you solve them?


Today’s Agenda



SCRUM simulation

Extra SCRUM topics



SCRUM in 59 minutes


Game structure

Planning
Choose a product and your PO
Help your PO to build up a PB
Help your PO to prioritize the PB items
Plan your first sprint

Sprinting
Day one - 7 min
Daily standup - 3 min
Day two - 7 min
Demonstration - 3 min (per a team)


Today’s Agenda



SCRUM simulation

Extra SCRUM topics


We will be having 10-minute breaks each 60-90 minutes.

SCRUM recap

Roles
The Team
–
ScrumMaster
–
Product Owner
–

Artifacts
Product Backlog
–
Sprint Backlog
–
Sprint/Release Burndown Chart
–

Meetings (ceremonies)
Sprint Planning
–
Daily Scrum (“Stand-Up”)
–
Sprint Review (Demo)
–
Retrospective
–


Today’s Agenda



SCRUM simulation

Summary of SCRUM concepts



Agile Planning

Requirements in SCRUM

Levels of Planning

Project Steering

Estimation Techniques

Requirements

What are the requirements to requirements?


What is important is …

That communications/negotiation happens
between the customer and the team.

User stories help deferring the details till later
They talk problems not solutions
They fit nicely as your Product Backlog items


User Story is…

User stories are simple, clear, brief
descriptions of functionality that will be
valuable to either a user or purchaser
of a product

Expressed in a form similar to:

As a <user> I can <do> so that <value>


Samples – Travel reservation system

As a vacation planner, I
As a user, I can reserve a
can see photos of the
hotel room.
hotels.

As a user, I can restrict
As a user, I can cancel a
searches so that I only see
reservation.
hotels with available rooms.

59

Details added in smaller substories

As a premium site member,
I can cancel a reservation
up to the last minute.

As a non-premium
As a user, I can member, I can cancel up to
cancel a 24 hours in advance.
reservation.
As a site visitor, I am
emailed a confirmation of
any cancelled reservation.

60

Details added as tests

High level tests are added to the story
Can be used to express additional details and expectations
–

As a user, I can cancel a reservation.

• Verify that a premium member can cancel the same day
without a fee.
• Verify that a non-premium member is charged 10% for a
same-day cancellation.
• Verify that an email confirmation is sent.
• Verify that the hotel is notified of any cancellation.
• Figure out what to do if the user’s card is expired.

61

From Mike Cohn’s “Agile Estimating and Planning”


Agile Planning


Levels of Planning

Project Steering

Estimation Techniques Agile Software Development with

The two levels of planning

Strategic level / Story level / product backlog
It is all about value. Hence the customers are at
–
better position to control this level.
It is the menu of a restaurant.
–

Tactical level / Task level / spring backlog
The tasks are defined in technical jargon. So the
–
teams control control this level.
It is the kitchen of a restaurant. Do you really want
–
to look inside? :)


From Mike Cohn’s “Planning Agile Projects”


Agile Planning


Levels of Planning

Project Steering

Estimation Techniques Agile Software Development with

There are four main parameters to planning


Visualizing the time-scope relationship

Release Burndown

2000
1800 1785
1620
1600
1400
Estimations

1200
1000
800
713
600
512
400
324
228
200 175
155
0
1 2 3 4 5 6 7 8
Sprints

The Performance metric

Velocity – speed at which the team converts
pieces of requirements into a working
product during a single sprint.

Light and powerful metric.


From Mike Cohn’s “Agile Estimating and Planning”


Agile Planning


Levels of Planning

Project Steering

Estimation Techniques

From Henrik Kniberg and Mike Cohn

A typical issue with estimations


Planning Poker. The Steps

Each estimator is given a deck of cards (1,2,3,5,8…)
A Product Owner reads a story
Estimators are for clarifications until everyone is ready to
estimate
Each estimator selects a card without showing it to the others
By command cards are got turned over
People with different estimates have discussions (limit with a
timer)
The round repeats until estimates converge


SCRUM and you

In your current (next) project which SCRUM
practices you think are the MUSTs?

Which you find hard to do?
Which you find impossible?
Which you find unnecessary?

Which can you start doing your next working
day?

Questions? Concerns? Any feedback?

Thank you!

My contacts

Alexey Krivitsky
Software developer, Agile coach

Certified ScrumMaster
Certified Scrum Practitioner
http://www.linkedin.com/in/alexeykrivitsky
email: alexey@scrumguides.com
skype: alexeykrv
icq: 436-471-64
gsm: +380 50 358 92 12

Currently building up a training center
www.scrumguides.com


Join our community!

Ukrainian Agile community
www.agileukraine.org

Join our Google discussion group

Ukrainian SCRUM portal
www.scrum.com.ua


Agile Software Development With SCRUM

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (20)

Similar a Agile Software Development With SCRUM

Similar a Agile Software Development With SCRUM (20)

Más de Alexey Krivitsky

Más de Alexey Krivitsky (20)

Último

Último (20)

Agile Software Development With SCRUM