Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Grooming - Where requirements meet the reality

No description
by

ISDC ISDC

on 16 June 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Grooming - Where requirements meet the reality

What is NOT grooming?
What is grooming?
Activities
Clarification
Understanding
Debate
Negotiation
Ovidiu Dolha
Requirements Engineer @ISDC
Continuous
improvement
activist
Client - team
mediator
Developer
CGI enthusiast
Skywatcher
Hanger outer
Cook?
Professionally
Personally
Discovering requirements
Planning
Q&A
session
Analysis
and
design
Dimensions & color
distribution
Bodies to be delivered
Material codes
Where requirements
meet the reality

Grooming
A set of activities initiated by the Product Owner and Scrum Master with the objective to make improvements to the Product Backlog in order to have just sufficient detail about the user stories so that the planning meeting can be productive. During the grooming phase, requirements are debatable, negotiable, and changeable.
Definition attempt
(Pre-grooming)
Preparation
Functional
Focus
Presentation
Constructive interaction
Technical
discussions
Actual meeting
highlight color each part
User story
Acceptance criteria
As a <role>,
I want to <function>
so that <goal>
Description
Expectations
Clear
Complete
Tailored
Precise
Team member
Product Owner
Stakeholder
Unofficial
References
Preliminary
estimations
Functional
solutions
Risks and
dependencies
Commitment &
common ownership
(of the product)
Continuous Improvement
ISDC Defined Agile Model (IDAM)
Plan
Act
Check
Do
Interviews
Open sessions
Discovering practices
Adding experience
of senior agilists
Delivering artifacts
Sharing & validating
IDAM core team
Do's and dont's
Knowledge
transfer sessions
Detailed wiki
Many more...
Open sessions
(workshops)
IDAM new members
=> Raw data
Actually working
Regular workshops
Individual tasks
Research & trials
Consolidating
Quality assurance
Model in prezi
Discuss
and change

JUST
GOOD
ENOGH
Settle on acceptance criteria (just good enough)
Ask me things now!
(Alternatively, you could also ask me later)
(Or just don't ask me anything. That is also acceptable)
CONCLUSION
Prepare for grooming
(using the info you have)

Understand what it means
It can make a BIG difference!
Grooming
Discourse
Meeting
...
...
...
Pre-groom to obtain
initial requirements

Bit Messy
+ Grooming

= Less messy
Weird
+ Grooming
= Even weirder
(but totally different)
Fuzzy
+ Grooming

= Clear & Neat
Share and improve your practices
Describes the functionality
Does not contain expectations
or parameters
What I will do
What others will do
What the system will do
Simple
To the point
No ambiguities
Contract structure
No conflicting info
Important cases covered
Exceptions mentioned
Constraints mentioned
to the team
to the client
and
Constraints and performance
(non-functional requirements)
Mockups
Documents
Other stories
External links
Specific (e.g. page numbers)
Up-to-date
(computer generated imagery)
(3D stuff)
Participants
Time
Grooming
Sprint
Planning
Estimations
Sprint Review
(& Demo)
Retrospective
2012 Q2
2012 Q3
2012 Q4
2013 Q1
IDAM KTS':
80
60
40
20
[27]
[35]
[52]
[42]
[64]
(details, language)
parameters
Full transcript