Agile Requirements by Collaboration - GOTO Conference · Agile Requirements by Collaboration ......

1

Agile Requirements by Collaboration

Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010

Ellen Gottesdiener www.ebgconsulting.com

Agile Requirements by CollaborationCopyright © 2010 EBG Consulting, Inc.

[Aarhus, DK; 5 October 2010]

Facilitator, trainer, mentor, agile coach, conference advisorYears of varied project and product experienceCertified Professional Facilitator, Certified Scrum MasterExpert Reviewer, contributor to IIBA BABOK®

(Business Analysis Body of Knowledge)

Author: articles, books, blog

blog: www.ebgconsulting.com/blogtwitter.com/ellengotteNewsletter: Success with Requirements free - sign up at www.ebgconsulting.com

Founder & Principal Consultant, EBG Consulting

Ellen Gottesdiener

2



agile agile planningplanning

summarysummaryreleaserelease

workshopworkshopintrointro

iteration/iteration/WIPWIP

workshopworkshop

collaborative collaborative workshops workshops

roadmaproadmapworkshopworkshop

agileagileplanningplanning

3



rolling wave

planning

agileplanning

reqtsanalysis

4



progressiverequirements

elaboration

bouldersrocks

pebbles

5



product big-view

release pre-view

iteration/WIP now-view

Product BacklogProduct Roadmap

Product BacklogRelease Plan

Iteration/ WIP Backlog

PRODUCTBig-View

RELEASEPre-View

ITERATION/ WIPNow-View

Vision, ValueGoals, Objectives

PRO

DU

CT

6



collaborative collaborative workshopsworkshops

“…a structured meeting in which a carefully selected group of stakeholders work together to define, create, refine, and reach closure on deliverables….”

Reference: Gottesdiener, The Software Requirements Memory Jogger

7



collaborating community

business case

8



10-to-1 return on investment

risk of scope creep reducedfrom 80% to 10%

project failure & cancellation rates reducedby 50%

the 6 P’s

9



purpose

participants

10



principles

products

11



place

process

12



ActivitiesSequence

Venue Logistics

DeliverablesDecisionsPlans Next steps

GuidelinesWorking agreementsGround rules

PeopleRolesResponsibilities

GoalsNeedsMotivation

Whendo we do

what?

Whereis it

located?

Whatdo we create?

Howdo we

function

Whois involved?

Whydo we do

things?

ProcessPlaceProductsPrinciplesParticipantsPurpose

bigbig--view:view:roadmapping roadmapping

workshop workshop

13



purpose

define product’s vision and scope

identify features to deliver for entire product or portfolio

develop product backlog

14



participants

project sponsor

executive advisors: business/product mgmt

strategic product owner

subset of delivery team

15



[sample]products


Project Charter

Product Vision

PRODUCTBig-View

When? EventsMMF Dependency Graph

What?Relationship Map

Data DomainsGlossary

Why?Business Policy Groups

Regulations

Who? Stakeholders

How?

FeaturesMinimum Marketable Features

Process MapNonfunctional Requirements

16



vision

minimummarketable

features

17



“…a chunk of functionality that delivers a subset of the customer’s requirements, and that is capable of returning value to the customer when released as an independent entity.”

Source: Denne and Cleland-Huang Also see www.softwarebynumbers.org

nonfunctionalrequirements

18



product roadmap

workshop: once per product, revise outcomes periodically

time horizon: 1-3 years

19



prepre--view:view:release planningrelease planning

workshop workshop

purpose

20



identify what to deliver in release

elaborate and prune product backlog

estimate and prioritize backlog items

participants

21



strategic and tactical product owner

executive advisors: business/product management [as appropriate]

delivery team

[sample]products

22




RELEASEPre-View

State DiagramsDependency Graphs

MMF Context DiagramConceptual Data Model

Business Policies Regulations

User Roles, User Role MapPersonas

External Interfaces

Stories, Story MapQuality Attributes

Design & ImplementationConstraints

user story (canonical form)

As a <user role | persona>

I need to <action | behavior>

so that <business value>

23



delivery,developmentdependencies

pre-view: prune

the backlog

24



workshop: once per release, revise outcomes as needed

time horizon: 1-4 months

nownow--view:view:iteration planning iteration planning

workshop workshop

25



purpose

identify what to deliver in iteration or what requirements

to pull

elaborate and prune product backlog

estimate prioritized backlog items or determine cycle time based on acceptance criteria

26



participants

tactical product owner

delivery team

27



[sample]products

Iteration / WIP Backlog

ITERATION / WIPNow-View

User Story Context DiagramData Model, Data Dictionary

User Acceptance TestsBusiness Rules

Decision Tables, Trees

PrototypesExternal Interfaces

Ready Stories, ScenariosQuality Attributes

Design & Implementation Constraints

State Diagrams

28



tamped-down

requirements

doneness

29



asking questions

supplemental analysis models

30



data

rules

states

interfaces

user acceptance tests

now-view: prune

the backlog

31



work aheada.k.a.

“make ready”

workshops: 2+ times before iteration planning & multiple times throughout; as analysis queue opens

time horizon: 2-3 weeks

32



summarysummary

skills needed

33



facilitation

requirements modeling

agile (and other) methods

facilitation

34



reqtsmodeling

35



collaboration patternmulti-model

agile methods

36





Iteration / WIP Backlog

PRODUCTBig-View

RELEASEPre-View

ITERATION / WIPNow-View

Vision, ValueGoals, Objectives

Who?

Why?

How?

What?

PRO

DU

CT

When? EventsStates

Dependency Graphs

State DiagramsDependency Graphs

Relationship MapData Domains

GlossaryMMF Context DiagramConceptual Data Model

User Story Context DiagramData Model, Data Dictionary

Business Policy GroupsRegulations

Business Policies Regulations

User Acceptance TestsBusiness Rules

Decision Tables, Trees

StakeholdersUser Roles, User Role Map

PersonasExternal Interfaces

PrototypesExternal Interfaces

FeaturesMinimal Marketable Features

Process MapNonfunctional Requirements

Stories, Story MapQuality Attributes

Design & ImplementationConstraints

Ready Stories, ScenariosQuality Attributes

Design & Implementation Constraints

Project Charter

Product Vision

State Diagrams

successful workshops

37



sponsorship

clear scope and definition of value

business & technical participation

workshop planning & design

continual planning

adjust workshop formality

functional & nonfunctional requirements

skilled facilitation

retrospectives

done

38



collaboratingto agile beat

email

more agile

about EBG

[email protected]

www.ebgconsulting.com

Copyright © 2010 EBG Consulting, Inc.

ebgconsulting.com/agile.pdf

more workshops ebgconsulting.com/facres.phpebgconsulting.com/facassets.php

39



www.bettersoftware.com

Upcoming public offerings: LondonAgile Requirements: 6-7 DecemberCollaborating for Success 8-10 December

Agile Requirements by Collaboration - GOTO Conference · Agile Requirements by Collaboration ......

Documents

Transcript of Agile Requirements by Collaboration - GOTO Conference · Agile Requirements by Collaboration ......