This page contains information about the roadmap for DevOps but may also include a description of actual issues and related developments.

This service roadmap should not be confused with a software or technology development roadmap. Individual service offerings, elements, components, developments or teams can have their own roadmaps which should be referenced here and mutually aligned; most of them are normally not visible to users.

Instead of using the provided Roadmap Planner macro and the table of activities, the team may give a link or attach a presentation (for example, one based on this multi-service/offering PLM Roadmap Template) or a spreadsheet or content in any other format and keep it up to date using an external (project management) application or tool such as JIRA or Trello. However, it should be accessible to anyone who is able to see this page.

RESPONSIBLE: Content is defined and maintained by the DevOps team.

Overview Roadmap

The visual overview roadmap is a communication tool used to set the expectations of what planned service changes are and what they will deliver in terms of a high-level strategic plan.

  • Bars indicate individual named phases of work – each may correspond to an action, activity or feature group. If several items listed in the table below are associated with the individual work phase, they should reference it by name.
  • Lanes indicate teams, work streams, general work areas, offerings or components.
  • Vertical markers highlight important tentative or fixed dates or (named or numbered) service stages, milestones, releases or rollouts.

It is better not to name bars with release or milestone codes or names of individual features – the release numbers are not very informative, while a release typically includes works by several teams (i.e. bars in several lanes) or several features, some of which may be postponed.

While the visual roadmap provides a general overview of the planned work, the associated table of actions is used to deliver additional details and needed descriptions.


Jan2019FebMarAprMayJunJulAugSepOctNovDecMarker 1
Lane 1
Lane 2

Bar 1

Bar 2

Bar 3

Actions

The table of actions serves to support the visual roadmap by providing additional information. It can be used as a high-level backlog, to do list or list of main changes, but the individual items need to be understandable by laymen. Each item is a phase of work, action or activity or feature group (marked by a bar), or one of bar or marker-related tasks or features. The rows either correspond to the bars in the visual roadmap or represent the individual actions or features associated with bars or markers. Using this table for individual assignments or minor changes would make it unmanageable, uninformative or overly technical in a long run; the detailed tasks and assignment should be managed with a dedicated project management tracker.

If rows need to be grouped by theme or lane(s) (team, stream or offering), it is better to split them into several tables then to merge adjacent cells (to group releases or multi-part actions), as this prohibits sorting.

  • When several items are associated with a marker, Release (or Milestone) column on the left indicates the associated release or milestone. Cells may also contain commitment indication codes, or these codes may be placed in the separate Commitment column following Release:

COMMITTED – Will be in this release.

PLANNED – Is planned to be in this release but additional work is required before it could be Committed.

POTENTIAL – Early stages of planning, more work is to be done before the item is moved it to Planned.

  • Action – Name of a phase of work or of its part. It may be renamed to Feature if the planning is not action, but feature based.
  • Description – One sentence or short paragraph explanation of what action or feature is about, but not how it is implemented.
  • Priority: 5 – Highest (i.e. Critical/Emergency), 4 – High, 3 – Normal, 2 – Low and 1 – Lowest
  • Status – examples for implementation status codes:

NOT STARTED (eduTEAMS ON HOLD?) (Core Team NOT NECESSARY, TBD?), Deferred, Waiting (on Something/Someone)?

FINISHED (Core Team DONE, COMPLETE?), Completed, Resolved?

IN PROGRESS (eduTEAMS ONGOING?)

CANCELLED

  • Due (planned completion, target) date – When will this action be done?
  • Assigned to (Responsible, Owner) – Who is responsible for actively working the issue?
  • Comment can elaborate on what is being done, its benefits, prerequisites, constraints, restrictions, consequences, risks, resource estimates, supporting documents etc.
  • (Created on – Date action was opened)
  • (Closed on – Actual date action was completed or cancelled)

(Simple version)

ActionDescriptionPriorityStatusDue dateAssigned toComment

 

      

(More detailed variant)

ReleaseCommitmentAction/Feature (choose one to indicate what is in rows)DescriptionPriorityStatusDue dateAssigned toCommentCreated onClosed on


 

      

  • No labels