Skip to content

Instantly share code, notes, and snippets.

@ennisa-ire

ennisa-ire/00-toc.md

Last active February 15, 2018 15:39
Show Gist options
  • Save ennisa-ire/376322acd2622656d55425e8c3ccf62c to your computer and use it in GitHub Desktop.
Save ennisa-ire/376322acd2622656d55425e8c3ccf62c to your computer and use it in GitHub Desktop.
Download ZIP
00 - IOT Tech Release Management Center
Raw
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?

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)

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...

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-----------------------------------|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment