This document discusses managing requirements through the lifecycle of an agile project. It notes that while agile practices focus on short iterations and minimal upfront planning, enterprise projects still require requirements persistence for regulatory compliance, reuse, and institutional memory. The document advocates aligning requirements management tools with agile tools to capture stakeholder needs, maintain requirements traceability throughout iterations, and preserve requirements for auditing after a project's completion. This allows leveraging agile principles while addressing enterprise needs like compliance and long-term requirements maintenance.
Powerful Google developer tools for immediate impact! (2023-24 C)
Managing requirements through the lifecycle of an agile project
1. MANAGING REQUIREMENTS THROUGH THE
LIFECYCLE OF AN AGILE PROJECT
Click if you can’t see
the control panel
Type Questions
Here
The audio for the webinars is available through
the computer speakers
Presenter: Brad Matsugu
Product Marketing Manager
2. MANAGING REQUIREMENTS THROUGH THE LIFECYCLE OF AN AGILE
PROJECT
• Are you deploying complex, enterprise scaled IT projects within an Agile
environment? Are you struggling to leverage requirements management best
practices along with Agile principles? If so, this webinar is for you.
• During the webinar, we will address:
• Why you need to analyze the full business, not just development objectives
• How a strong alignment between Requirements Management and Agile tools can de-risk
and accelerate your IT project
• How to sustain your momentum and preserve the ‘why’ long after your project is completed
2
3. THE AGILE ‘GAP’
REQUIREMENTS REQUIREMENTS
Business Need
• Regulatory Compliance and Audit
• Institutional Memory – Requirements Persistence
• Standardization and Re-Use
• Business Case and Funding
• Release Planning
• Abstracting solution definition
• Change Impact and Costing
Agile Practice
• Focus forward
• Just enough detail
• Stories are transient - answers are in the code
• Limit work in progress
• Fast pace, maximize delivery, minimize ceremony
Gap
3
4. REQUIREMENTS MANAGEMENT IN ENTERPRISE AGILE
Business Analyst;
Blueprint; Persistent
Product Owner;
Agile ALM;Transient
Discovery & Scoping
Stakeholder
Input,
Business Case
Iteration n
Requirements
Operations
Regulatory
Compliance,
non-functionals,
Iteration 0
Initial
Requirements
&
Regulations
Demo
Product Backlog
Groom
Burn
Down
Demo
Plan/Create
Update,
Add,
Refine
Update,
Add,
Refine
Iteration Backlog
Update
Initial Product
Backlog
Update,
Add,
Refine
4
5. REQUIREMENTS MANAGEMENT IN ENTERPRISE AGILE
Business Analyst;
Blueprint; Persistent
Product Owner;
Agile ALM;Transient
Discovery & Scoping
Stakeholder
Input,
Business Case
Iteration n
Requirements
Operations
Regulatory
Compliance,
non-functionals,
Iteration 0
Initial
Requirements
&
Regulations
Demo
Product Backlog
Groom
Burn
Down
Demo
Plan/Create
Update,
Add,
Refine
Update,
Add,
Refine
Iteration Backlog
Update
Initial Product
Backlog
Update,
Add,
Refine
5
6. CONCEPT
• Analyze the business and gather stakeholder input
• Business
• Finance
• Legal
• PM
• Executive Sponsor
• Take advantage of Institutional memory
• Standardization and re-use across enterprise projects & portfolios
• Collaborate for cross departmental alignment
6
7. REQUIREMENTS MANAGEMENT IN ENTERPRISE AGILE
Business Analyst;
Blueprint; Persistent
Product Owner;
Agile ALM;Transient
Discovery & Scoping
Stakeholder
Input,
Business Case
Iteration n
Requirements
Operations
Regulatory
Compliance,
non-functionals,
Iteration 0
Initial
Requirements
&
Regulations
Demo
Product Backlog
Groom
Burn
Down
Demo
Plan/Create
Update,
Add,
Refine
Update,
Add,
Refine
Iteration Backlog
Update
Initial Product
Backlog
Update,
Add,
Refine
7
8. INCEPTION & CONSTRUCTION
• Cross departmental collaboration
• Collaborating with the customer
• Detailed traceability
• History
• Analytics
• Cohesion between RMS and Agile tools enhance the agile process
• Allows engagement from all users
• Supports distributed teams
8
9. REQUIREMENTS MANAGEMENT IN ENTERPRISE AGILE
Business Analyst;
Blueprint; Persistent
Product Owner;
Agile ALM;Transient
Discovery & Scoping
Stakeholder
Input,
Business Case
Iteration n
Requirements
Operations
Regulatory
Compliance,
non-functionals,
Iteration 0
Initial
Requirements
&
Regulations
Demo
Product Backlog
Groom
Burn
Down
Demo
Plan/Create
Update,
Add,
Refine
Update,
Add,
Refine
Iteration Backlog
Update
Initial Product
Backlog
Update,
Add,
Refine
9
10. OPERATIONS
• The ‘why’ needs to survive the project long after its completed
• Institutional memory – requirements persistence
• Regulatory and governance audits
10
11. REQUIREMENTS MANAGEMENT IN ENTERPRISE AGILE
Business Analyst;
Blueprint; Persistent
Product Owner;
Agile ALM;Transient
Discovery & Scoping
Stakeholder
Input,
Business Case
Iteration n
Requirements
Operations
Regulatory
Compliance,
non-functionals,
Iteration 0
Initial
Requirements
&
Regulations
Demo
Product Backlog
Groom
Burn
Down
Demo
Plan/Create
Update,
Add,
Refine
Update,
Add,
Refine
Iteration Backlog
Update
Initial Product
Backlog
Update,
Add,
Refine
11
12. FOR MORE INFORMATION
Our popular Business of IT series has a number of short,
insightful interviews with the most knowledgeable people on
the topic of driving improvements in project delivery.
Join the conversation..
http://www.blueprintsys.com/thebusinessofit/index.php
Contact: Brad Matsugu
Email: Brad.Matsugu@blueprintsys.com
Phone: +1 (647) 288-0700 x 831