Agile Requirements Using RRC in CALM
-
Upload
sergio-orrego -
Category
Documents
-
view
223 -
download
0
Transcript of Agile Requirements Using RRC in CALM
-
8/3/2019 Agile Requirements Using RRC in CALM
1/26
IBM Software Group
2009 IBM Corporation
Implementing Agile Requirements usingIBM Rational Requirements Composer with C/ALM
Yan (Tina) Zhuo, IBM Rational
-
8/3/2019 Agile Requirements Using RRC in CALM
2/26
IBM Software Group | Rational software
2009 IBM Corporation
Topics
IBM Rational Requirements Composer AgileRequirements Project Template
Working with epics and themes
Analyzing requirements using attributes, tags and filters
Collaborating with stakeholders on requirements and
throughout application lifecycle
2
-
8/3/2019 Agile Requirements Using RRC in CALM
3/26
IBM Software Group | Rational software
2009 IBM Corporation
Agile requirements project template
The agile requirements project template includes a set offolders and a document template to elaborate a user story
Project Folder:
Stakeholder Needs
Features
GlossaryNon-functional Requirements
User Story Elaboration
Document Template: User Story Elaboration
Use the template to create a new Requirements Composerproject
Customize the template based on your project needs
3
-
8/3/2019 Agile Requirements Using RRC in CALM
4/26
IBM Software Group | Rational software
2009 IBM Corporation
Potentials artifacts for the Stakeholder Needs folder
4
Potential artifacts at theproduct and programlevel:
Business goals
Product visionProduct roadmap and
strategy
Business processes (as-is vs. to-be)
-
8/3/2019 Agile Requirements Using RRC in CALM
5/26
IBM Software Group | Rational software
2009 IBM Corporation
Potential artifacts for the Features folder
5
Potential artifacts:
Market analysis andrelease themes
Features and benefitsfor a product release
-
8/3/2019 Agile Requirements Using RRC in CALM
6/26
IBM Software Group | Rational software
2009 IBM Corporation
Potential artifacts for the Glossary folder
6
Potential artifacts:Glossary and Terms
-
8/3/2019 Agile Requirements Using RRC in CALM
7/26
IBM Software Group | Rational software
2009 IBM Corporation
Potential artifacts for the Non-functional Requirements folder
7
Potential artifacts:System-wide non-
functional
requirements
-
8/3/2019 Agile Requirements Using RRC in CALM
8/26
IBM Software Group | Rational software
2009 IBM Corporation
Potential artifacts for the User Story Elaborations folder
8
Potential artifacts:
Flow diagrams forscenarios
A scenario can involve
multiple user stories
Roles and personas
User story elaborationUI sketches
Storyboards
-
8/3/2019 Agile Requirements Using RRC in CALM
9/26
IBM Software Group | Rational software
2009 IBM Corporation 9
User story elaboration template
Elaborate a user story in a RRC document using a template
Attribute group for user story elaboration includes: Role, Business Value,Business Priority, Product Owner, Origin
-
8/3/2019 Agile Requirements Using RRC in CALM
10/26
IBM Software Group | Rational software
2009 IBM Corporation
User story elaboration - example
10
A user story may start as a shortstatement, explaining the intent ofthe user
It can be elaborated throughconversations and confirmation,leveraging techniques such asuser interface sketches, andstoryboarding
-
8/3/2019 Agile Requirements Using RRC in CALM
11/26
IBM Software Group | Rational software
2009 IBM Corporation
Topics
Requirements Composer Agile Requirements ProjectTemplate
Working with epics and themes
Analyzing requirements using attributes, tags and filters
Collaborating with stakeholders on requirements and
throughout application lifecycle
11
-
8/3/2019 Agile Requirements Using RRC in CALM
12/26
IBM Software Group | Rational software
2009 IBM Corporation
Strategy of describing and managing epicsProcess sketch or storyboard can visually describe an epic
Break down an epic into user stories to elaborate the details
Use a collection to manage a group of related user stories
12
-
8/3/2019 Agile Requirements Using RRC in CALM
13/26
IBM Software Group | Rational software
2009 IBM Corporation
Working with themes: use tags and filters
13
A story can beallocated to one ormultiple themes.
Allocate stories tothemes by applyingtags
Filter stories based onthemes
-
8/3/2019 Agile Requirements Using RRC in CALM
14/26
IBM Software Group | Rational software
2009 IBM Corporation
Topics
Requirements Composer Agile Requirements ProjectTemplate
Working with epics and themesAnalyzing requirements using attributes, tags and filters
Collaborating with stakeholders on requirements and
throughout application lifecycle
14
-
8/3/2019 Agile Requirements Using RRC in CALM
15/26
IBM Software Group | Rational software
2009 IBM Corporation
Analyzing elaborated stories using attributes, tags, and filters
Display all elaborated user stories with their attribute values
Filter and display elaborated story based on attribute valuesBy Business Priority
By Origin
By Product Owner
By Role
Organize elaborated stories by themes
Display elaborated stories in a collection
15
-
8/3/2019 Agile Requirements Using RRC in CALM
16/26
IBM Software Group | Rational software
2009 IBM Corporation
Topics
Requirements Composer Agile Requirements ProjectTemplate
Working with epics and themesAnalyzing requirements using attributes, tags and filters
Collaborating with stakeholders on requirements and
throughout application lifecycle
16
-
8/3/2019 Agile Requirements Using RRC in CALM
17/26
IBM Software Group | Rational software
2009 IBM Corporation
2009 C/ALM - A team collaborates across repositories
Bob Product Owner
Defines & linksrequirements to influencethe development plan
Scott, Deb, Marco Developers
Plan the iteration fromrequirements
Develop & deliverchanges
Tanuj Tester
Validate requirements
Submit defects
Test the iteration
Rational
Requirements
Composer
Rational
Quality
Manager
PlanRequirements
Find & Fix Defects
Requirements driventesting
Rational Team Concert
17
Align Plans
-
8/3/2019 Agile Requirements Using RRC in CALM
18/26
IBM Software Group | Rational software
2009 IBM Corporation
Collaborating on requirements through review and comment
18
Use the RequirementsComposer for different levels
of reviews:
Peer review
Stakeholder review
Customer review andapproval
-
8/3/2019 Agile Requirements Using RRC in CALM
19/26
IBM Software Group | Rational software
2009 IBM Corporation
C/ALM scenario:Creating a story work item using Card info
19
-
8/3/2019 Agile Requirements Using RRC in CALM
20/26
IBM Software Group | Rational software
2009 IBM Corporation
C/ALM scenario:Plan the detailed implementations in RTC
20
Create child work items in RTCto implement the story.
Parent story work item isassociated with a singleelaborated user story in RRC.
-
8/3/2019 Agile Requirements Using RRC in CALM
21/26
IBM Software Group | Rational software
2009 IBM Corporation
C/ALM scenario: creating test cases
21
Create one or more testcases from an elaborateduser story using one of the
following
1. Save Selection AsTest Case
2. Add a Validated Bylink
3. Link a Collection of
related user storieselaborated in RRC toa Test Plan in RQM
-
8/3/2019 Agile Requirements Using RRC in CALM
22/26
IBM Software Group | Rational software
2009 IBM Corporation
Linking a collection to a test plan in RQM
22
1. Do just-in-time story elaborations based on priority
2. Create collections of functionally related user stories3. Link the collection to a test plan in RQM
4. Continue to elaborate user stories when needed
-
8/3/2019 Agile Requirements Using RRC in CALM
23/26
IBM Software Group | Rational software
2009 IBM Corporation
Creating test cases from requirements collection
23
Create Test Cases from Requirements
-
8/3/2019 Agile Requirements Using RRC in CALM
24/26
IBM Software Group | Rational software
2009 IBM Corporation
Requirement and C/ALM
24
An elaborated user story is
implemented by a Story workitem, and validated by one ormultiple test cases.
-
8/3/2019 Agile Requirements Using RRC in CALM
25/26
IBM Software Group | Rational software
2009 IBM Corporation
Credits
Yan (Tina) Zhuo
Carolyn Pampino
Scott AmblerVishwanath Ramaswamy
Erich Gamma
Pratik ShahJohn Whitfield
Cherifa Mansoura
Daniel MoulNick Norris
Douglas Bush
25
-
8/3/2019 Agile Requirements Using RRC in CALM
26/26
IBM Software Group | Rational software
2009 IBM Corporation 26
Copyright IBM Corporation 2009. All rights reserved.
The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsiblefor any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties orrepresentations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materialsto IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials maychange at any time at IBMs sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.
IBM, the IBM logo, the on-demand business logo, Rational, the Rational logo, and other IBM Rational products and services are trademarks or registered trademarks of the International BusinessMachines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
Visit Jazz.net and IBM Rational
http://jazz.net
http://www.ibm.com/rational
Check out the brand new Rational events blog
Free trial downloads of IBM Rational tools
More Rational Web events
Take Action