Page 1
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
Page 2
2
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
agile agile planningplanning
summarysummaryreleaserelease
workshopworkshopintrointro
iteration/iteration/WIPWIP
workshopworkshop
collaborative collaborative workshops workshops
roadmaproadmapworkshopworkshop
agileagileplanningplanning
Page 3
3
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
rolling wave
planning
agileplanning
reqtsanalysis
Page 4
4
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
progressiverequirements
elaboration
bouldersrocks
pebbles
Page 5
5
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 6
6
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 7
7
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
collaborating community
business case
Page 8
8
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
10-to-1 return on investment
risk of scope creep reducedfrom 80% to 10%
project failure & cancellation rates reducedby 50%
the 6 P’s
Page 9
9
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
purpose
participants
Page 10
10
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
principles
products
Page 11
11
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
place
process
Page 12
12
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 13
13
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
purpose
define product’s vision and scope
identify features to deliver for entire product or portfolio
develop product backlog
Page 14
14
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
participants
project sponsor
executive advisors: business/product mgmt
strategic product owner
subset of delivery team
Page 15
15
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
[sample]products
Product BacklogProduct Roadmap
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
Page 16
16
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
vision
minimummarketable
features
Page 17
17
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
“…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
Page 18
18
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
product roadmap
workshop: once per product, revise outcomes periodically
time horizon: 1-3 years
Page 19
19
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
prepre--view:view:release planningrelease planning
workshop workshop
purpose
Page 20
20
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
identify what to deliver in release
elaborate and prune product backlog
estimate and prioritize backlog items
participants
Page 21
21
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
strategic and tactical product owner
executive advisors: business/product management [as appropriate]
delivery team
[sample]products
Page 22
22
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
Product BacklogRelease Plan
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>
Page 23
23
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
delivery,developmentdependencies
pre-view: prune
the backlog
Page 24
24
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
workshop: once per release, revise outcomes as needed
time horizon: 1-4 months
nownow--view:view:iteration planning iteration planning
workshop workshop
Page 25
25
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 26
26
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
participants
tactical product owner
delivery team
Page 27
27
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
[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
Page 28
28
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
tamped-down
requirements
doneness
Page 29
29
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
asking questions
supplemental analysis models
Page 30
30
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
data
rules
states
interfaces
user acceptance tests
now-view: prune
the backlog
Page 31
31
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
work aheada.k.a.
“make ready”
workshops: 2+ times before iteration planning & multiple times throughout; as analysis queue opens
time horizon: 2-3 weeks
Page 32
32
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
summarysummary
skills needed
Page 33
33
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
facilitation
requirements modeling
agile (and other) methods
facilitation
Page 34
34
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
reqtsmodeling
Page 35
35
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
collaboration patternmulti-model
agile methods
Page 36
36
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
Product BacklogProduct Roadmap
Product BacklogRelease Plan
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
Page 37
37
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 38
38
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
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
Page 39
39
Agile Requirements by Collaboration
Copyright © 2010 EBG Consulting, Inc. JAOO DK 2010, Aarhus, September 2010
www.bettersoftware.com
Upcoming public offerings: LondonAgile Requirements: 6-7 DecemberCollaborating for Success 8-10 December