1

AgileBill Krebs

Agile Coach - Allscripts

linkedin.com/in/BillKrebs

twitter.com/AgileBill4d

Build the Right Thing

2

That’s not what I wanted!projectcartoon.com

3

AgileBill Krebs

IBM Developer & Lead ’83-09

Founded a consulting practice

Served a non profit university

Agile Coach at Allscripts

Agile since 2001 Certs: MIS/cs, CSM, CSP, MBTI, Innovation

Games Taught Agile Scrum and Lean to over 1,000 worldwide Certification in Virtual Worlds from the

University of Washington June 2010 through their one year program.

Specialist in 2d or 3d web base training and collaboration

bill.krebs@allscripts.comAgileBill4d

bit.ly/amagile

4

Sound Familiar?

Customers

want it

yesterday

We spend more time fixing bugs than adding new features!

They changed

their mind!It wasn’t what

they expected

We planned, but were surprised

5

Our Goals

Time to Market Quality

Flexibility

Customer Sat

Risk Reduction

6

Aspects of Agile

Leverage ChangeScrum

OptimizeLean

Build the Right ThingUser Stories, Innovation Games

Bake in QualityAgile tech

7

Process, Specs, Plans?

8

Strategy

› Create with Innovation Games

› Know your audience

› Specify with User Stories

Hohmann

Cohn

Kessler & Sweitzer

9

Know your Stakeholders

End Users

Partners

Insiders (your team)

Principals ($$$)

PIPE

10

Personas

Steve – Wears multiple hats, dog at home

Nell – New hire, high tech

Mary – Masters Student – single mom

Joe – the Plumber: domain expert, computer illiterate

11

Breaking Writer’s Block

› 3 of the 12+ Innovation Games from Enthiosys

− Remember the Future (Invent)

− Product Box (Invent)

− By a Feature (Prioritize)

12

Remember the Future

› Purpose: defines success

› Picture a year from when your customers started using your product. Ask “What will your product have done to make customers happy”?

Write down your answers to form key directions for your product.

Open Ended, Strategic More at enthiosys.com

13

Product Box

› Purpose: Identify the product’s best features

› Picture a box of cereal. Design a similar informative package for your product. What features would you list? Think both of colorful slogans for the front, and tech specks for the side of the box

Open Ended, Mid level strategic More at enthiosys.com

14

Buy a Feature

› Purpose: Prioritize Features

› Create a list of features and provide a price. Customers buy features with play money. Price some high enough so that customer must negotiate and pool their money to buy them.

› Observe the discussion and which features are purchased.

Mid level technique More at enthiosys.com

15

A User Story

As an online shopper, I can ship to a friend

Ron Jefferies 3 ‘C’s

Card

Talk with Bob, my

stakeholder

We know we’re done when:[x] Can retrieve friend’s address[ ] Can specify ship date and carrier[ ] Can track order

Conversation

Confirmation

16

RGB - Card details

Role Goal (Benefit)

As a studentI can view the course materials online after

class

So I can review any points I missed

As a teacherI can get feedback from

students

So I know if I should speed up, slow down,

or repeat

17

Conversation

Spoke with ____ on ____

Spoke with ____ on ____

18

Confirmation

No More, No Less

[ ] ______________

[ ] ______________

[ ] ______________

19

Examples

As an teacher,

I want to be able to setup a learning management system

So students can study outside of class

Priority 5. Estimate 8 points

[x] Students can register

[ ] Students can chat on a message board

[ ] Teachers can collect exercises

[ ] Teachers can organize learning modules

Front

Back

What’s missing?

Hint: 3 Cs

20

Reinforce your learning

Question Answer

What are some of the three parts of a user story?

What are the 3 parts of the ‘card’?(hint – think colors)

A story is a _____ to future conversation

What do we do with stories?(hint – think planning)

Why don’t we give much space to write?

21

Answers!

Question Answer

What are some of the three parts of a user story?

CardConversationConfirmation

What are the 3 parts of the ‘card’?(hint – think colors)

Role, Goal, Benefit

A story is a _____ to future conversation

What do we do with stories?(hint – think planning)

Prioritize, size

Why don’t we give much space to write?To make you break them down into small storiesSo you focus on the acceptance test

22

Bad Stories

› They are co-dependant› They aren’t valuable to users

(a geeky internal task)

› You can’t estimate them› They don’t tell you what to test› They haven’t been split yet if necessary

You know your story still needs work if…

23

Exercise

› Write a User Story

› Include the 3 Cs and RGB

› Review some

24

User Story Template› What makes a good user story?....................

Independent

Negotiable

Valuable

‘Estimatable’

Sized appropriately

Testable

25

User Story

− ½ a page− Role, Goal (optional benefit) − Ticket to conversation with

stakeholder− Conversation leads to writing

acceptance test as part of story

− Can annotate with priority and estimate

Use Case

− 2 pages or more− Emphasizes ‘actors’ – who

interacts with this scenario?− Gives sequential steps− Can highlight alternate path

Alternatives

26

Relationship to Agile Project Management

27

Scrum via Mike Cohn

28

Roles

› Product Owner− Knows the business− Prioritizes requirements based on business value

› Scrum Master− Serves the team, not the other way around− Knows the process, and make it flow

› The Team

› The Stakeholders− Give feedback on the demos

29

The Product Backlog

Continuous Flow of new

Reqs

ProductBacklog

Sorted byProduct Owner

Estimated byTeam

Sprint Backlog

30

Estimating

› COCOMO II?

› Or Wide band delphi− 1, 2, 3, 5, 8, 13, 20, 40, 100, ?

High Low discussion

Not Just Numbers

31

Release Plan: an ordered pile of stories

In

Stretch

Out

Conservative Velocity * number of iterations

At our best velocity

Not in this release.

Good to know now.

Hot

32

Release Plan: an ordered pile of stories

In

Stretch

Out

Conservative Velocity * number of iterations

At our best velocity

Not in this release.

Good to know now.

Hot

ContinuousPrioritization

of new stories

33

15 Minute Scrum Meeting

1. List 2 things you finished yesterday

2. List 2 things you’ll finish today

3. What blockers stand in your way?

34

A day in the life of an Agile team

Morning

Scrum meeting (everyone)

Task 1

Task 2

Task 3

Task 4Task 5

AfternoonTask 6

Task 7Task 8

Task 9 Task 10

Evening Full Build

35

A Two Week Sprint

‘Mon’ Tue Wed Thu Fri

Plan Daily Daily Daily Daily

Daily Daily Daily DailyDemo

Retro

36

A Release

Mar Apr May June

Sprint 5 Sprint 1 Sprint 3 Sprint 5

Release

PlanningSprint 6

Sprint 2 Sprint 4 Sprint 6

Glance at product visionto help in release planning

37

38

Shodan Retrospective

Actions, not a score card

Outer range shows high useNote diverse opinions in team

39

When do we know our true velocity?

40

A_____A_

A_____

1 3 5 __, __, __, 40 100

As a ______ I can _______ so that _______

C___C______C_____

Done

____ Minutes

I …

I …

My _____ Are …

P_______I_______P_______E__ ____

‘M’ T W T F

____. . . .

. . . .________

by AgileBill Krebs. @AgileBill4dhttp://bit.ly/amagile

Fist of _____

Agile in one page reference card(Quiz until you fill it out)

41

bit.ly/amagile

bill.krebs@allscripts.com

linkedin.com/in/BillKrebs

Skype: AgileBill4d

twitter.com/AgileBill4d

More