How to Fix Your Release Process1. How to Fix Your
Release Process
Driving Successful Product Delivery
5. 5© Perforce Software Inc. All Rights Reserved.
The definition of what you need to create is
unclear, incomplete, or wrong.
The #1 Reason for Bad Releases
6. 6© Perforce Software Inc. All Rights Reserved.
What Causes Bad Releases?
1 2 3 4 5
Insufficient User
Involvement
Creeping
Requirements
(Scope Creep)
Unclear
Requirements
Gold Plating
Minimal
Specifications
7. 7© Perforce Software Inc. All Rights Reserved.
Where Releases Go Wrong
1 2 3
Office documents for
managing key artifacts
Artifacts managed in a
variety of applications
No traceability,
resulting in a loss of
knowledge
Office Documents Dedicated Applications Knowledge Gaps
8. 8© Perforce Software Inc. All Rights Reserved.
How To Fix Your Release Process
1 2 3 4
Automation
reduces lag
Collaboration
improves efficiency
and quality
Visibility is
knowledge
Traceability is the
supporting glue
AutomationCollaboration Visibility Traceability
10. 10© Perforce Software Inc. All Rights Reserved.
This is the heart of your engineering efforts.
You need a platform for engineering excellence!
Let’s Build It!
11. 11© Perforce Software Inc. All Rights Reserved.
Create Requirements
The devil is in the details:
• Know what you need to create!
• Use detailed specifications / requirements
• Manage risk, FMEA, RPN
• Build a traceability matrix
Create
Epics
Stories
Requirements
Specifications
FMEA
Traceability
12. 12© Perforce Software Inc. All Rights Reserved.
Execute on Requirements
Team execution:
• Manage tasks, estimations
• Do code reviews to ensure quality commits
• Version everything and track back to work items
• Collaborate (Slack, comments, online reviews)
• Track changes, bugs
Execute
Tasks
Code Review
Source Control
Digital Assets
CAD Drawings
Collaboration
Changes
13. 13© Perforce Software Inc. All Rights Reserved.
How to Create the Right Requirements
1 2 3 4
Automation
reduces lag,
catches bugs earlier.
Set your team up
for success.
One solution to track
and trace.
Quality code.
==
Less rework.
Collaboration
improves efficiency
and quality.
Continuous
Integrations
Right
Priorities
Code Review Collaboration
14. 14© Perforce Software Inc. All Rights Reserved.
You Need End-to-End Traceability
Requirements Test Cases Test Runs Issues Source Code
17. 17© Perforce Software Inc. All Rights Reserved.
• Working in silos.
• Testing as an afterthought.
• Quality is not part of how you work.
• Lack of automation.
• Bad test cases come from bad
requirements.
What Causes Poor Quality?
18. 18© Perforce Software Inc. All Rights Reserved.
How To Avoid Quality Issues
• Requirements need tests cases —
and vice-versa
• More efficient creation of test cases
• Changes to requirements can invalidate tests
cases
• Traceability is built in from the start
19. 19© Perforce Software Inc. All Rights Reserved.
• Instant analysis for better decisions
• Impact analysis
• Upstream and
downstream
Impact Analysis
• Suspect dependencies —
now about an issue before
it becomes an issue.
• Gap analysis
• Compliance
Information Is Power
Requirement
Test Case Test Run
Issue
20. 20© Perforce Software Inc. All Rights Reserved.
How to Improve Quality
Manual Test Cases
One solution for
all test cases.
One solution
for test results.
Single view of all
testing activity.
Automated Test Cases
23. 23© Perforce Software Inc. All Rights Reserved.
Release Retrospective
Measure / Report
Burndown
Burnup
Velocity
Trace Matrix
Risk Analysis
Trend
Validation
• What worked well for us?
• What did not work well for us?
• What actions can we take to improve
our process going forward?