Skip to main content
System StatusContact Support
VersionOne Community

Role: Development Manager - Governance

Objective

As a Development Manager, you may want to see what controls are in place to keep software from moving from what phase to the next, and from a governance perspective see the history of a particular release of software.

Steps

  1. From the Top Menu, select "perspectives, progressions" (1, below). The "In Progress" tab should be selected already.

  2. This page shows software development work in progress sectioned into phases of delivery. Each larger box displays an application and version under way in the software delivery process and a range of what we call revisions (2, above). A revision is essentially a software application build.

  3. For a given software application and version, you will notice that there are a range of revisions within a single phase. This illustrates the concept we call "pooling" where revisions, or builds, get created at a faster and move into a downstream phase faster than they most into the next phase.
  4. Take for example the screenshot below. The webstore 5.0 application, build 5.0.1974 is currently in Performance Test. There are 23 "workitems" (stories or bug fixes) that are represented in several builds or revisions. Each of the smaller boxes (green for stories, yellow for bug fixes) represents one of these workitems.

  5. Click on any revision range on this page. This will take you to the Package Revision Detail page. As you scroll through the page you will notice all of the Activities (manual and automated) that that particular range of revisions as passed through as well as any controls that have been met, not met or overridden as they make their way through.

Results

As software is delivered through various phases of delivery and pauses in each, value is pooled up in that phase. Therefore when a software release candidate is being tested you are not just testing one set of changes, but the collective changes that have accumulated.

Controls can be put in place to safeguard software release candidates from proceeding from one phase to another. Continuum brings visibility to unmet controls and allows for overrides and approvals to be may by decision makers satisfying regulatory and audit requirements.

  • Was this article helpful?