Agile in a Nutshell - Portia Tung

Agile in a NutshellHow to deliver more value faster at less cost

By Portia Tung

Who am I?

Consultant.

Coach.

Storyteller.

Games Maker.

www.portiatung.org

...it’s an adventure!

Agile Principle #1:

Deliver value

Session Goal and Acceptance Criteria

Introduction to Agile Concepts

As a presenterI need to give an introduction to Agile conceptsSo that participants better understand how Agile can increase thevalue they deliver.

Acceptance Criteria:

[ ] We understand the core concepts of Agile.[ ] We’ve identified two or more ideas to try out Agile at work.[ ] We’ve had fun.

Agile Principle #2:

Respect for people

Pick a project

• Identify 3 challenges the project faces

•Share these with a friend

•Share these with the group

Pop Quiz Question #1

Time

CostScope

?


“Without a goal

it’s difficult to score”

?


“Show me the value!”

?

Agile Principle #3:

Eliminate waste

Agile Principle #1:

Deliver value

Value in a Waterfall Project Value in an Agile Project

Why adopt Agile?

1. Desperation: Competitors delivering higher quality deliverables faster

2. Frustration: Burden of legacy processes

3. Fear: Being left behind as Agile becomes the de facto way of working

4. Hope: Belief in a better way of doing things to reduce waste, deliver more

value and make work meaningful

5. Desire for Continuous Improvement:Go from Mediocrity to Good to Great

What is Agile?

What is Agile?

“Agile is now widely recognised as a

project delivery and general working

approach with a proven track record of

delivering more business value fasterthrough higher quality deliverables in comparison to traditional methodologies.”

Where does Agile come from?

Agile

ManifestoSnowbird, Utah

Feb. 2001

Your turn?3 March 2011

First man on the

moonJul. 1969

The Agile Manifesto

We are uncovering better ways of developing software bydoing it and helping others do it. Through this work we havecome to value:

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

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

www.agilemanifesto.org

eXtreme Programming (XP)

ScrumLean Software Development

Feature Driven DevelopmentAdaptive Systems Development

Dynamic Systems Development Method (DSDM)Crystal

Kanban

......

Different kinds of Agile

Think “Team”

Agile in Action

Agile Project Structure

Release1 – 12 weeks

Iteration1 – 4 weeks

Project1 – many weeks

Agile Requirement

User Story

Anatomy of a User Story

AS A <role>

I NEED <capability>

SO THAT <achieve some goal>

� Binary question format (Y/N)

� Statement

� Given-When-Then

BV Effort

<Title> Acceptance Criteria:





About User Stories

User Story Epic

About User Stories

User Story Epic Project

Backlog

Make stories even-sized

User Story Epic Project

Backlog

Project

Backlog

Multi-Level Stories

Release1 – 12 weeks

Iteration1 – 4 weeks

Project1 – many weeks

Iteration Level Story

Release Level Story

Project Level Story

Themes – Story Groupings

Project

Backlog

World Peace

Sustainable Philanthropy

Definition of Done

User Story

Acceptance Criteria

Acceptance Tests

Quality is not negotiable

The XP GameTeam ManifestoTeam Speed Networking

Kanban Board Building

Celebratory Team Lunch

Show & Tell

User Story Writing

Technical Design Walkthru

Collaboration in Action

Agile Heartbeat

Tuesday Tuesday Tuesday

• Show & Tell

• Iteration Retrospective

• Design

• Development

• Test

• Iteration Planning

• Release Planning

• Mid-Iteration Review

• Agile Estimating

• Pre-Planning

• Backlog Grooming

• User Story Writing

• Daily Standup

• Scrum of Scrums

Ongoing activities throughout an iteration

VELOCITY

A MEASURE OF WORK

Velocity Burndown Chart

# of Iteration

Level Stories

Iteration Days

Agile Principle #1:

Deliver value

Agile Values

Communication

Simplicity

Feedback

Courage

Respect

Team Manifesto

Agile Principle #4:

Continuous Learning

The Agile Challenge

Pros☺ Value-driven: Business Value + Agile Values

☺ Team-centric

☺Working a sustainable pace (9 – 5 everyday)

☺ Responsive to change through iterative planning and estimating

☺ Deliver high business value

☺ Deliver faster

☺ Fun!

GOOD

Very GOOD

BAD

VERY BAD

Iteration 0 Iteration 1 Iteration 2 Iteration 3

Cons� Must understand the Business Value you are delivering

� Must want to work with people

� Focused work makes Agile very tiring

� Must be able to embrace uncertainty by adapting to change

� Prioritise by Business Value first, then re-prioritise by constraints

� Define scope by Minimum Marketable Feature Set instead of by want

� Making work fun is hard work!

Agile Experience Retrospective

Agile Principle #5:

Continuous Improvement

In Summary

Agile Principle #1:

Deliver value

Agile Principle #2:

Respect for people

Agile Principle #3:

Eliminate waste

Agile Principle #4:

Continuous Learning

Agile Principle #5:

Continuous Improvement

Session Goal and Acceptance Criteria





The Gift of Feedback

Further Information

Resources

The Original XP Game by Pascal Van Cauwenberghe

and Vera Peetershttp://www.xp.be/xpgame.html

Scrum and XP in the Trenches by Henrik Kniberg

www.infoq.com

Fun and Games!http://www.agilecoach.net/

http://www.agilefairytales.com

ConferencesMini XP Day Benelux (1 April 2011)

http://www.xpday.net/

XP Days Benelux (1 – 2 December 2011)

http://www.xpday.net/

[email protected]

Blog: www.selfishprogramming.org