ScrumGuides training: Agile Software Development With Scrum

Agile Software Development with SCRUM

www.scrumguides.com

13 February 2009

Today’s Agenda

Opening: program overview, knowing each other

Understanding Agile and SCRUM

SCRUM simulation

Extra SCRUM topics

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 cone of uncertainty
SCRUM decreases the chaos by fixing the scope


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.

Principles of Agile Manifesto

Please see www.agilemanifesto.org for the
twelve principles


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?


Team work (cont.)

Exercise “an airplane factory”.


Push vs. Pull systems

SCRUM
is a pull system


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


Today’s Agenda


Understanding Agile and SCRUM till 16:00

Coffee break 16:00 – 16:30

SCRUM simulation 16:30 – 17:30

Extra SCRUM topics 17:30 – 18:00



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.

The “Flip Coins project


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


The Sprint Burndown Chart


The Task Board - an information radiator



Team Work

Prioritization

Short cycles

Learn and Adapt


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

Opening: program overview, knowing each
other


SCRUM simulation

Extra SCRUM topics


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


Join our community!

Ukrainian Agile community
www.agileukraine.org

Join our Google discussion group

Ukrainian SCRUM portal
www.scrum.com.ua


ScrumGuides training: Agile Software Development With Scrum

More Related Content

ScrumGuides training: Agile Software Development With Scrum