Enhancing Worker Digital Experience: A Hands-on Workshop for Partners
3 Reasons to Throwaway Requirements
1. Three Reasons to Throw Away your
Requirements Documents
Sponsored by
Link to watch webcast recording on-demand
2. Featured Presenters
Our knowledgeable speaker today is:
Andy Gurd
Senior Go-To-Market Manager
IBM Rational
Follow on Twitter: @andygurd
or find me on LinkedIn
3. The ROI of better Requirements Management
$500,000
69% net reduction in the cost of quality
$450,000 Return on investment within 6 months
$400,000 >75% improvement in productivity
$350,000
Rework
Testing
$300,000
$250,000 “In 6 months since deployment we’ve seen a 69%
net reduction in the cost of test preparation, testing,
$200,000
and rework by using IBM Rational DOORS and an
$150,000 improved requirements management process.
$100,000 Our team is testing and reworking comparable
functionality in one sixth the calendar time and
$50,000
one third the person hours. And we are able to
$0
better meet the needs of our stakeholders."
Before After Mia McCroskey, Senior Project Manager for Product Development at
Emerging Health, Montefiore IT
Link to full case study
4. Reason #1 - Collaboration
• Screenplay/script like
requirements
• Script / requirements needed to
determine impact of any changes
• Script / requirements form the hub
for co-ordinating successful
teamwork
Images courtesy of:
scottchan / www.freedigitalphotos.net
siraphat / www.freedigitalphotos.net
digitalart / www.freedigitalphotos.net
5. Requirements collaboration -
Documents/Spreadsheets
V1 V2
Requirements Analyst / User Reqts User Reqts
Systems Engineer
Comment on User Reqts Engineering
Engineering Team Manager
V1 V2
Technical Requirements Technical Requirements
6. Requirements collaboration –
Integrated RM Tool
Systems Engineer QA Manager “Everyone need to be following
“I need to be able to manage the the same process and creating
relationship between customer the same metrics and reports”
requirements and downstream design”
Engineers
“I need access to a
live central
repository and to
know that I am
looking at the latest
approved
requirements”
Project Manager Developers
“I need a process
that ensures
traceability between
my requirements
“I need to implement a process that enforces
and changes. I
traceability between all my project
need to know the
information and supply chain”
status of those
changes”
7. But I’m comfortable with docs and
spreadsheets, wont this be a difficult
transition?
• Familiar hierarchical structure of a document and rich text editing
• Columns like a spreadsheet for additional properties
• Management of individual requirements for tracking and reuse
8. In-Context Collaboration
Collaboration through
information discussions or
by formal review
Email notification available
for review updates
Dashboard widgets to show
review participation and
status
Notification to personal dashboard
Comments can be
used inside or outside
of a review
10. Reason #2 – Traceability
• Breadcrumb trail = weak
traceability
• Product & systems development
needs stronger traceability
• Need easy way to create manage
and traceability
• Traceability helps with
conformance to customer
requirements and compliance to
regulations
Image courtesy of Bill Longshaw /
www.freedigitalphotos.net
11. Traceability
Standards
Stakeholder
Requirements
Systems
Requirements Test Cases
Use Cases
Subsystem
Requirements
Test Cases
Related Blog Posts:
What is Traceability?
The uses and value of traceability
12. Traceability – Documents/Spreadsheets
Multiple documents to manage Need a way to identify requirements
If a requirement
changes, you need to
open multiple
documents to
determine impact and
update
15. Reason #3 – Agility
• Approaches to managing
change to requirements
Try to hold back the tide Go with the flow Take control
Images courtesy of
George Stojkovic / www.freedigitalphotos.net
Graeme Weatherston / www.freedigitalphotos.net
16. Supplementing the backlog with more
granular, contextual requirements
Prioritized Backlog
User Story 1
Roadmap/Strategy, User Story 2
Enhancement
Requests,
Problem Reports Epic 1
User Story 3
…..
Scenario
User Requirement A
Storyboard User Requirement B
Note User Requirement C
…..
Requirements and supporting information
17. Backlog and requirements
Prioritized User Stories
& Epics
Trace to
Requirements Modules ,
Requirements &
supporting artifacts
18. Summary
• Agility without control = chaos!
– Requirements need to persist
beyond an iteration
– Requirements and supporting
information add more granularity to
user stories and epics
– Link requirements and task
management for traceability
19. Summary
• Agility without control = chaos!
• Traceability provides rationale
and context
– Retrace to key design decisions and
customer requirements
– RM tool makes traceability a benefit
not an overhead
20. Summary
• Agility without control = chaos!
• Traceability provides rationale and
context
• Effective collaboration is essential
– Must have access to the right version
/ view of requirements for your role
– RM tool provides informal and formal
collaboration techniques
21. Summary
$500,000
• Agility without control = chaos!
$450,000
$400,000
$350,000
Rework • Traceability provides rationale and
Testing
$300,000 context
$250,000
$200,000
$150,000 • Effective collaboration is essential
$100,000
$50,000
$0 • Improving your Requirements
Before After
Management process supported
by an RM tool can deliver
significant quantitative and
qualitative benefits
22. Thank you for attending
Please visit our sponsor and any of the resources below:
• Video: Better requirements. Enhanced business agility. Fast ROI.
Featuring Emerging Health, Montefiore IT
• Requirements Management on ibm.com
• IBM Rational DOORS Next Generation on jazz.net
• IBM Requirements Management blog:
http://ibm.co/requirementsmanagementblog
• Follow on Twitter: @rationalrdm
• DOORS LinkedIn Group: linkd.in/WWSF6a