2. 2
FUG2016
• Global organization vs. teams
• Handling of non-functional requirements
• Coexistence of waterfall and agile
approaches/projects
• End2End Visibility – integration into SDLC
• Maintain functionality overview/documentation
• Change management in agile projects
Challenges for Agile on Enterprise Level
3. 3
FUG2016
Customer Quote
“Every project needs to follow either
our corporate Waterfall or Agile
process and all requirements we are
gathering must be available in a
single source of truth.”
SDLC Owner
Major TV Broadcasting & Media Company
6. 6
FUG2016
Bi-Modal with Serena Dimensions RM
Traditional Data Model Agile Data Model
Co-existence in one common RM Data Model
Business Reqs
Product Reqs
Component Reqs
Epic
Feature
Story
Epic
Feature
Story
Business Reqs
Product Reqs
Component Reqs
7. 7
FUG2016
Serena Dimensions RM supports:
Business Reqs
Product Reqs
Component Reqs
Epic
Feature
Story
Epic
Feature
Story
Business Reqs
Product Reqs
Non-Functional
Pure Waterfall Agile
Hybrid
9. 9
FUG2016
• Free definable artifact
types with their attributes
• Access rights on attribute
level
• Link relations definition
• Link constraints
• Lifecycle Workflow
Serena Dimensions RM’s flexible Class Definition
Implement the desired Agile/Hybrid approach (or start with blueprint)
10. 10
FUG2016
• Product breakdown in Releases
and Sprints
• Epic breakdown in Features and
Stories
• SAFe:
– Epics span Releases
– Features fit in Release
– Story fit in Sprint
RM Agile also supports SAFe
Product /
Project
Release
Sprint
Epic
Feature
Story
12. 12
FUG2016
• Agile artefacts and agile views
• Agile artefacts based on RM classes
• Backlogs and Story Boards
• Product/Release/Sprint breakdown
• Calculations and visualizations on priority, effort, progress
• Burndown reports on Release and Sprint level
• Support of hybrid approaches
• Requirements and agile artefacts
• Traceability throughout all artefact types
• Non-functional requirements
• Re-use of backlog and story boards for traditional artefacts
• Integration into development
• Story to be provided to (agile) development tool
• Feedback on development progress back to RM boards
Agile Capabilities in Dimensions RM
Product
Backlog
Product
Storyboard
Sprint
Backlog
Sprint
Storyboard
13. 13
FUG2016
Activities:
• Define features, stories or other
artefacts for one product
• Prioritize
• Define acceptance criteria
• Assign items to one or more
product releases
RM Product Backlog
16. 16
FUG2016
Activities:
• Move stories through lifecycle
stages
• Re-assign stories
• Can also be used for requirements
analysis sprints
Integration:
• Integration with development
management (like Dimensions CM)
• Feedback of story progress from
development
RM Sprint Storyboard