Getting Ready To Produce

What's Needed Before Iteration1

Questions

and

Discussions

are

Welcome

Who Are You?

- introduce yourself as if you

were your product -

DevJam Jams

DevJam Agility

Creating Community and Common Vision

Form Communities (Chartering)

Compose a Product (Personas – Story Maps – Design)

Create an Eco-System (Iteration 0 – Common Workspace)

Iterative Delivery and Tuning

Staying Connected (Daily Standup – Common Workspace)

Tracking Progress (Task Wall - Burnchart - Velocity)

Technical Agility (Continuous Integration – Test Driven)

Delivering Value (Acceptance Test - Story Sign Off)

Tuning and Improving

Validating Progress (Review / Product Presentation)

Reflect and Improve (Retrospective)

Prioritizing and Planning

Product Releases (Releases - Priorities - Estimates)

Iterative Delivery (Iterations – Stories/Tasks - Estimates)

Preproduction

( getting ready to produce )

______________________

Creating Community and Common Vision

Form Communities (Chartering)

Composing a Product (Personas – Story Maps)

Create an Eco-System (Iteration 0 – Common Workspace)

1) Why are you building? ( charter )

2) Who is buying (in)? ( personas )

3) What do they do? ( story maps )

4) Which (to build) first? ( planning )

5) When is there value? ( story tests )

Preproduction Tools

Chartering( why are you building? )

Chartering (a project story)

Meet as a community to discuss:

Elevator Pitch

Goals - Success Measures

Community Mapping

Values - Working Agreements

Strengths - Challenges

Cadence

Telling a Project Story ( charter )

Elevator Pitch

What are you building and why?

( keep it short and memorable )

Measurable Goals

Project Charter: <name removed > / Time Frame: start of Q3 and end of Q4

Elevator Pitch: Less papers means less manual mistakes; build a new system with a

sustainable process

Goals

Prove proposed technology - Move away from paper process

Usable system to pilot - Validate the ability to have dynamic business rules

Adapt to business and regulatory environment - Show value of iterative development

Build confidence and buy in with business users - Fine tuning estimates (validate sizing)

Have fun and learn (new knowledge)

Value to Company

Build efficiencies in field using technology - Shorter processing time with fewer errors

Straight through efficiencies - Increase service level agreements with customer

Increase business feedback

Success Measures

There is continuous feedback from business community

Plans are reviewed and updated based on iteration outcome

Community is improving on delivering on commitments and learning from each delivery

Status of request on-line are viewable

Business rules can change to manage work load

- the blur is intentional -

What Does Success Looks Like?

Create a short elevator pitch

Include 2 goals w/ success measures

_______________________________

Find someone to pair with and

share your project story

- did you fail? -

- when is failure good? -

Personas ( who is buying / buying in? )

Personas Are More Than Actors

Personas represent people & clarify product value

Our Product - Point of Sale App

Create a Point of Sale application

10 local stores

Application runs only on registers

Registers are new, running Tomcat & MySQL

Another system provides item price & description

Pragmatic POS Personas

Emergent Personas

Informative Personas

Creating Your Personas

Choose a name ( sticky name – alliteration helps )

-------------------------------------------------------------------------------------

Add an image ( a conversation starter )

-------------------------------------------------------------------------------------

Add a description Value from product

( who is this person? ) ( what is our sell? )

- time at job - financial benefit?

- knowledge of domain - increased productivity?

- FT / PT - fewer steps?

- incentives - more fun?

- level of engagement - easier to use?

Story Maps( what is the user experience? )

Persona Driven Authoring

Anatomy of a User Story

The What Story

– User goals and tasks

The Completion Measures Tests

– User satisfaction / product value

The How Tasks

– Design and coding work

The Estimates Effort

– Consensus of effort to complete tasks

Someone doing (or getting) something of value

Let’s Jam!

( fearless story jams )

Creating Story Maps

Name high level activities for persona

( “what do you do at work?” )

scenarios - business processes

Walk a day in the life for each activity

( “what are the tasks?” )

user stories (user tasks) - sub processes

Back up and re-tell the experience

( “are there any variations?” )

Mile wide - inch deep

Let’s Map the Point of Sale

Maps Guide Discussions

A Clever Variation

What are your story maps?

Back up and find variations & dead ends

Activity

Activity

Task Task Task

Task Task

Task

Task

Task

Task

Task Task Task Task

Task Task

Task

Task

Task

- what is still missing? -

- what are the next steps? -

Variations and Value

Mapping Variations

Other Invesments(backlog items )

Start up costs

Environments Work ( nuke and pave )

Architectural Spikes – Technical Debt

Infrastructure Work – Non Story Work

Visual design

Prototypes (paper and other) - Graphics

Which tasks are first?

Activity

Activity

Task Task Task

Task Task

Task

Task

Task

Task

Task Task Task Task

Task Task

Task

Task

Task

What are your priorities?

When is value delivered?

Activity

Activity

Task Task Task

Task Task

Task

Task

Task

Task

Task Task Task Task

Task Task

Task

Task

Task

What are the story tests?

Questions

________________________________________

Coaching and Developing Agility

david.hussman@devjam.com

www.devjam.com

© 2010 DevJam - All rights reserved.