00 - IOT Tech Release Management Center

00-toc.md

Toc

Q_n_A.md

Approaches

• System driven?
• Test driven?

Managed

Use jira release management feature to manage your releases.

Suggestions

• Time a release, lets tear it apart, and see were the hotspots are, and make out a plan of attack?

Questions

Q. What is the function of the environment?

• How does the enviroment serve a need to to the release?
  Q. What serves the release, what inhibits the release?

https://en.wikipedia.org/wiki/Release_management
Q. What are our release goals?

• reliable applications faster and more frequently Q. What does a CD pipeline do?
• The movement of the application from a “build” through different environments to production as a “release” is part of the Continuous Delivery pipeline

Q. What is a release?

• It is a process
• What are the stages of the process?
  • Build
  • Deploy
• It is a version of sw
• Is essentially a snapshot of the artifact(s) and related metadata that will be deployed.
• A release is created from a single build.
  • A build is created by a build tool.
    • The build tool is executed from jenkins. Jira uses bamboo to build a version Q. What do we release?

Q. What does a release do?

• ships code from source to target?
  • How is this done?
    • Code is built by gradle, which is managed by jenkins, which is part of a Continous Integration Integration Process

Q. How many releases we have?

Q. Does are release have an alias?

Q. Its a timed event, that repeats.
* Q. What triggers a new release?
* Q. How is the release, doing?

• are we on track, what monitors do we have in place, do we see problems, can we release on date. https://confluence.atlassian.com/jirasoftwarecloud/checking-the-progress-of-a-version-764478137.html

Q. How is the release, approached?

• new approach to software releases known as Continuous delivery is starting to influence how software transitions from development to a release

Q. How is the release, designed?
Q. How is the release, executed?
Q. How is the release, started/stoped?

Q. When is the release, released?
Check its release status, in Jira (Daily, Weekly, Sprintly)

• issues are complete
• code is checked in
• reviewed and merged
• builds are passing, etc. Warnings
  https://confluence.atlassian.com/jirasoftwarecloud/files/764478141/773981955/2/1483597775170/JIRA+version+release+dev+panel.png
• completed issues with open pull requests
• completed issues with failing builds
• completed issues that have unreviewed commits

Q. Why is the release, released?
Q. Who releases, how do they release it?
Q. How to compare one release to another
Q.

SW-Application

• Features
• Capabilities

SW-OS

HW

• Capabile of meeting perfant needs

Process

What is the Release Path...

• Planning
• Design
• Design
• Developement
• Testing
• Production Readiness
• SME Review
• Commitee Review https://www.google.ie/search?q=jira+release+management+dashboard&client=ubuntu&hs=etS&channel=fs&dcr=0&tbm=isch&source=iu&pf=m&ictx=1&fir=Go-NEoWkK4A4uM%253A%252CQspQ-WhA2JSj5M%252C_&usg=__vYv374f-tPiZwqAapT6vqgYamGI%3D&sa=X&ved=0ahUKEwiozYznsIzXAhXJvBQKHcsuD7UQ9QEIRDAB&biw=1595&bih=863#imgrc=KC2yvWxw9FoDuM:

Metrics

Jira + Metrics

https://www.grow.com/integrations/jira-reporting-tool/?utm_medium=paid&utm_source=google&utm_term=%2Bjira%20%2Bdashboard&utm_campaign=uk_int_search&gclid=EAIaIQobChMIt8WQ57CM1wIVhzLTCh32XwPbEAAYAyAAEgJLw_D_BwE

• Open Tickets
• Count of Completed and Current Issues
• Cumulative Completed Issues Over Time (Week/Month)
• Releases per Dev by Month/Quarter/Year
• Releases Vetted by QA by Week/Month
• Average Work Velocity by Team
• Average Sprint Stage Duration
• Scope Creep by Week/Month
• Issue Cycle Time by Week/Month

Dashboard.

Jira + Dashboard

https://confluence.atlassian.com/jirasoftwarecloud/using-the-release-page-to-check-the-progress-of-a-version-764478141.html

Burn Down

Teams velocity relative to this sprint..

JIRA Ticket Graphics.

Systems Approach

• Inputs---> SYSTEM A --- Outputs ---> System B -- Outputs ----> System C -- Outputs ----> Deliverables <----------------------------------Feed Back Loop-----------------------------------|

• Inputs---> SYSTEM A --- Outputs ---> System B -- Outputs ----> System C -- Outputs ----> Deliverables <----------------------------------Feed Back Loop-----------------------------------|

• Inputs---> SYSTEM A --- Outputs ---> System B -- Outputs ----> System C -- Outputs ----> Deliverables <----------------------------------Feed Back Loop-----------------------------------|