When we started to modernise our QA department, we realised there is a need for a function, that is making sure different handovers are running smoothly and mistakes once made won't be made again. This track will share our learnings of improving our products quality with release management.

2. 2
Release and Deployment Management aims to plan, schedule and control the movement
of releases to test and live environments. The primary goal of Release Management and
Deployment Management is to ensure that the integrity of the live environment is
protected and that the correct components are released
WHAT IS RELEASE MANAGEMENT?

3. 3
HOW DOES A RELEASE PROCESS WORK?
Idea
Produc+on
Product
Management
Development Design QA OperaJons

4. 4
RELEASE PIPELINE

5. 5
KIND OF LIKE THAT
PM DEV QA OPS
Produc+on
Idea

6. 6
IMPACT OF HANDOVERS

7. 7
à Bring different stakeholders closer
à Provide independent opionion
à ConJnuous improvement
WHAT TO DO?

8. 8
JOB SPEC.

9. 9
à Final gate before the release
à All stakeholders present
à Everyone’s consent to release is necessary
RELEASE MEETINGS

10. 10
à Define when to switch on a feature
à Who does what
ACTIVATION SCHEDULE

11. 11
à What is in the release
à Everything in the release is DONE DONE
CHANGELOG PROCESS

12. 12
à MiJgaJon plan for issues from live / going live
à All stakeholders present
POST RELEASE REVIEW

13. 13
à IdenJfy who you are affecJng
à Inform / manage the impact
STAKEHOLDER MANAGEMENT

14. 14
Schedule What happens and when during rollout?
RELEASE MEETING TEMPLATE
Resources & SynchronizaJon Are resources in place and available for all tasks before/
during/aYer rollout?
Sync on work Jme and communicaJon established?
Change-Log Is everybody on the same page about what has been
added/changed/updated with this release?
Are there any last minute changes?
RC and QA build.
Results and Verdicts QA TesJng Results and Verdict.
CM Feedback and Verdict.
Untested Content Is there any untested content and why?
Can this content be released or sJll be tested prior to
rollout?
What can only be verified aYer rollout? What will be
verified aYer rollout (discrepancies between test
environment and live environment)?
Any delays during sprint which might have knock-on effects
on test coverage or other stakeholders?

15. 15
App Submission Are there any pending work items prior to submission?
Are there any reoccurring or important tasks associated
with current submission?
Any known or unknown requirements not met?
InstallaJon and loading Jmes?
Required and supported OS versions/hardware?
RELEASE MEETING TEMPLATE
Known issues What are the known and outstanding issues and how do
they affect the planned release?
Are they acceptable to be released or can they be fixed and
tested before?
Stakeholders Who is affected by or affects this release (any
dependencies)?
Mobile (browser backend or feature flag affecJng the
app?)
Payment
Portal
MarkeJng & PR
AnalyJcs

16. 16
Risk & Damage Control What could go wrong with this release?
What can be done to prevent or miJgate it?
What happens when something goes wrong?
Latest Live-Issues: Live Bug details
RELEASE MEETING TEMPLATE
Sign off Anything not clear at this point? Go/No Go?

17. 17
à Minimised defects in the release
à Improved lead Jme for performing release acJvaJons
à Not making the same mistakes over and over again
CONCLUSION

18. 18
Q&A
Q&A
hap://www.linkedin.com/in/rainar
@rainary;

19. 19
Thank You!
Q&A
hap://www.linkedin.com/in/rainar
@rainary;