Agile Requirements (Not an Oxymoron) - Boston...
60
Ellen Gottesdiener www.ebgconsulting.com © EBG Consulting, 2010 Agile Requirements (Not an Oxymoron) [Boston SPIN June 15, 2010]
Transcript of Agile Requirements (Not an Oxymoron) - Boston...
Ellen Gottesdiener www.ebgconsulting.com
©
EBG Consulting, 2010
Agile Requirements (Not an Oxymoron) [Boston SPINJune 15, 2010]
Facilitator, agile coach, trainer, mentor, conference advisorYears of varied project and product experienceCertified Professional Facilitator, Certified Scrum
Master
Expert Reviewer, contributor to IIBA BABOK®
(Business Analysis Body of Knowledge®)
Author: articles, books
eNewsletter: Success with Requirements free -
sign up at www.ebgconsulting.comTweets: twitter.com/ellengottBlog: ebgconsulting.com/blog
Founder & Principal Consultant, EBG Consulting
Ellen Gottesdiener
IntroIntro agile adaptationsagile adaptations
agile requirements agile requirements practicespractices
Q & AQ & A
summarysummary
oxymoron
“…a figure of speech that combinestwo normally
contradictory terms.”
visualthesaurus.com
good grief open secret
airline food seriously funny
jumbo shrimp vaguely aware
agilerequirements
requirements: basis for product development
software development
agile agile requirementsrequirements
practicespractices
agile agile requirements:requirements: planningplanning
value
fork over selected items
continual prioritization
bouldersrocks
pebbles
product big-view
release pre-view
iteration now-view
product roadmaprelease planning
Product BacklogProduct Roadmap
Product BacklogRelease Plan
Iteration BacklogIteration Plan
Project Charter
Product Vision
PRODUCTBig-View
RELEASEPre-View
ITERATIONNow-View
When? EventsMMF Dependency Graph
State Diagrams State Diagrams
What?Relationship Map
Data DomainsGlossary
MMF Context DiagramConceptual Data Model
User Story Context DiagramData Model, Data Dictionary
Why?Business Policy Groups
RegulationsBusiness Policies
Regulations
User Acceptance TestsBusiness Rules
Decision Tables, Trees
Who? Stakeholders PrototypesExternal Interfaces
How?Features
Minimum Marketable Features Process Map
Nonfunctional Requirements
StoriesStory Map
Quality AttributesDesign & Implementation
Constraints
Right Sized StoriesScenarios
Quality AttributesDesign & Implementation
Constraints
User Roles, User Role MapPersonas
External Interfaces
right size
work ahead
“ready” requirements
customer collaboration
agile agile requirements:requirements: developingdeveloping
concise, tamped-down
requirements
done
visualize
data
rules
states
interfaces
user acceptance tests
light touch
agile agile requirements:requirements: deliveringdelivering
sashimi slices
dependencies
developmentdelivery[vs. usage]
inspect and
adapt
unfolding story
agile agile requirements requirements
adaptationsadaptations
requirements development &
management
set the stage
product ownership
completenessinpurposeful
elicit
just…
in-timeenough
before
analyze
progressive elaboration
collaborating community
specify
smart documentation
validate
v & v collapse
requirements management
prune the backlog
summarysummary
planning
developing
delivering
agile requirements
flexible rigor
concise complex
small large
incompleteness finish
oxymoron
agile
requirements
Next public Agile Requirements: Cincinnati, September 20-21, 2010
more agile
about EBG
ebgconsulting.com/agile.pdf
www.ebgconsulting.com
©
EBG Consulting, 2010
