The clear benefits of agile development is a better collaboration, incremental delivery, early error detection and the elimination of unnecessary work—have made it the default approach for many teams. Some developers have questioned whether requirements fall into the category of unnecessary work, and can be cut down or even completely eliminated. Meanwhile, teams developing complex products, systems and regulated IT continue to have requirements-driven legacy processes. So how does requirements management fit in an agile world? This session will take a look at requirements management and how it can bring significant value to agile development in regulated IT and complex product development projects, and sets out the characteristics of an effective requirements management approach in an agile environment.

1. AGILE DEVELOPMENT -
WHY REQUIREMENTS
MATTER
FARIZ SARACEVIC (IBM)
@FARIZSARACEVIC

2. CONFERENCE SPONSORS
GOLD
SILVER
BRONZE
MEDIA PARTNERS

3. AGENDA
• Why Requirements matter?
• Right-Sized Agile Requirements Management
• Understanding your requirements management needs
• Choices, choices…
• What’s Next?

4. WHY REQUIREMENTS MATTER?
If you ask for the wrong thing, you’ll get it…
If you don’t know what was asked for,
you’ll deliver the wrong thing…
This is not about
waterfall versus
agile…
You need to
understand what
problem you’re
trying to solve, get
feedback early
and often and
then adjust…

5. WHERE HUMAN SAFETY IS A FACTOR, EVEN SIMPLE
DEVICES AND SYSTEMS REQUIRE CAREFUL ENGINEERING
TO REDUCE RISK

6. THREE KEY CHALLENGES
• Products are becoming much more complex
• Products are becoming part of larger solutions / ecosystems
• Disrupt or be disrupted: innovating faster than competitors
More software
Hardware – Electronics – Software
More suppliers More teams More specialists
More subsystems
Learning fast Deciding fast Acting fast Delivering fast
From “predictable world” to “unpredictable world”
Safety and security … and new failure modes
Teams on-prem and on cloud
Teams on different cadences

7. REQUIREMENTS IN IBM DEVOPS
Customer /
Stakeholder
Product
Manager /
Product Owner
Dev Lead
Requirement
Feature
Dev Work
Item
Continuous
Customer Feedback
& Optimization
Collaborative
Development
Continuous Release
and Deployment
Continuous
Monitoring
Continuous
Business Planning
Continuous
Testing
Operate Develop/
Test
Deploy
Steer
DevOps
Continuous
Feedback
Requirements are the key artifact
representing feedback…
Requirements drive
articulation of application
features…
Development delivers
function for features…

8. Rational Team Concert (RTC)
DEVELOPMENT
Change Control
Board
(CCB)
Design and
develop software
(SCM)
Triage
Enhancements /
defects
Backlog
(Work items)
Customer /
Stakeholder
Product
owner /
manager
Dev Lead
Software Engineer
Analyze
Requirements
Specific work items can be put
into the product backlog and
delivered against directly

9. Rational DOORS Next Generation (RDNG)
REQUIREMENTS ANALYSIS
Change Control
Board
(CCB)
Triage
Requirements
Analysis
Enhancements /
defects
Backlog
(Work items)
System
Requirements
User Requirements
Customer /
Stakeholder
Product
owner /
manager
Dev Lead
Analyze
Requirements
Requirements Analysis transforms many
disparate inputs from different stakeholders
into specific Requirements for the development
team to work against.

10. Rational Team Concert (RTC)
Rational DOORS Next Generation (RDNG)
DEPLOYMENT
Change Control
Board
(CCB)
Design and
develop software
(SCM)
Triage
Requirements
Analysis
Enhancements /
defects
Backlog
(Work items)
System
Requirements
User Requirements
Customer /
Stakeholder
Product
owner /
manager
Dev Lead
Software Engineer
Analyze
Requirements
These two activities can be
executed in the same
organisation with Requirements
elaborating what business need
the development team is aiming
to solve.

11. REQUIREMENTS IN SCALED AGILE
FRAMEWORK (SAFE)
Scaled Agile Framework (SAFe) with the Power of DevOps
Requirements
articulated in
Portfolio Planning
and refined
through analysis
into Features and
Stories…

12. Rational DOORS Next Generation
CHOICES, CHOICES…
Rational Team Concert
How do you choose?

13. Small Agile Teams
UNDERSTANDING YOUR REQUIREMENTS
MANAGEMENT NEEDS
Regulated/Systems Enterprises
Need for regulatory
compliance and
auditing
Separation of roles
(Business Analysts,
Development)
Requirement
governance
Robust requirements
articulation needs
Unregulated, little or no
compliance or audit
requirements
Desire for single tool lightweight
requirements and change
management
Simple requirements articulation
needs
Rational DOORS
Next Generation
Rational
Team Concert

14. IBM RATIONAL TEAM CONCERT
REQUIREMENTS SIMPLICITY FOR SMALL AGILE TEAMS
RTC Quick Planner
• Easy to learn
• Fast work item creation
• Manage a backlog and sprints in a single
window using drag and drop
• Manage Parent/Child tasks and their rank
relationships
• IBM Design driven task based UI
Reporting
 Jazz Reporting Service
 Fast data collection
 Query builder
 New lean reports
Collaboration
 Activity streams to track events
 Automated work item reply
 Social flow for comments
 Manage & preview attachments
Kanban/Taskboard
• States and State-groups
• Customize card display
• Customize display of states
• Display small, medium, large
cards
Build & Deploy
• Post Build Deploy using UC
Deploy
• Gated control of builds for
deployment
Compliance for SCM
• Improved large team usage with
pessimistic locking
• Improved auditing for work item
link changes
• Ability to see who and when
code changes were delivered
Integration
Git
Jenkins

15. Better requirements… Less rework…
Better results!
IBM RATIONAL DOORS NEXT GENERATION
ENHANCE YOUR VALUE AND CAPABILITY BEYOND RTC FOR REQUIREMENTS
Search, filter
on attributes
Business
Objectives
Business
Processes
Use Cases
Storyboards &
Sketches
Reporting
Industry &
Domain Models
Impact &
Coverage
analysis
Rich text
Requirements
Traceability
between related
artifacts
Rational DOORS
Next Generation
Definition and Management
Lifecycle Traceability
Project Efficiency and Reuse
 Improves the developer’s ability to design
UI and software flow in the initial design
phase
 Better define and manage rich text use
cases, visual diagrams or processes
 Strengthens stakeholder’s traceability
across all lifecycle artifacts to find missing
requirements or use cases
 Easily discover the impact from requirement
or use case changes
 Reuse requirements for multiple projects to
lower development costs and capitalize on
best practice
 Enables the development experience
through a specification structures

17. www.agile.ba
THANK YOU!