/
Project Status Tracking in JIRA Proposal

Project Status Tracking in JIRA Proposal


Background

The wiki has been used to track the status of projects (scorecards) and achievement of release milestones.

Problem

The update of the wiki pages is manual and time-consuming for PTLs and Release Manager.

Proposal

Raise JIRA tickets in each ONAP project for each milestone and/or release requirement

  • JIRA tickets are assignable to people for implementation and follow-up.
  • JIRA tickets communicate priority, completion status and dates.
  • JIRA tickets can be queried and filtered to provide summary reports.
  • JIRA tickets can be linked to other JIRA tickets for dependencies, blockers and related issues.

Frankfurt Proposal

  • Move the source of truth from wiki_checklists to Jira Epic/Story/Task 
    • ?TSC Jira project OR new Release project?
  • All stories must be tied to a UseCase OR Infra (using tags)  
    • Move OVP to a usecase
  • Each milestone has a user story and subtasks 
    • subtasks are milestone deliverables (eg. Story=M4, Subtask=Completion of Vulnerability table)
    • ?Special type task that has only open/complete states?
  • Create wiki/Jira dashboard using tags/queries


Maybe there could be new JIRA configs to assist, e.g.

  • Issue Types for Scorecards
  • project Components for Milestones
  • Labels for cross-cutting concerns like needing TSC approval and being POC

Based on all that JIRA ticket information, a Kanban board will show visually when a Milestone or Release is Done!

Discussion

  • Integration with Development process and "definition of done"
  • Time element
    • Creating a framework with a time line to hang activities would be necessary
    • Epics for each milestone?
      • tasks replicated per project due for each milestone
      • can use the TSC JIRA project for the epic, then distribute Scorecard/Story JIRA cases to individual ONAP projects
    • Probably could diagram this out to get some idea how it all would work
    • Automation via JIRA CLI tool could be used to script the creation of releases and milestones, since it's a fairly static config consisting of many instances of known templates
  • Follow-ups
  • Skeptics Corner
    • Feels like we're re-inventing scrum
    • As a release mgr, it sounds like the same amount of paper chasing with a different user interface...

Experiments

Implementation

  • Tools
    • TBC
  • Processes
    • TBC


Related content

Documenting Release Requirements and Use Cases in JIRA
Documenting Release Requirements and Use Cases in JIRA
More like this
Logging Casablanca RC1 Deliverables for RC1 Milestone Checklist Template
Logging Casablanca RC1 Deliverables for RC1 Milestone Checklist Template
More like this
External API Framework Deliverables for Planning Milestone Checklist Template
External API Framework Deliverables for Planning Milestone Checklist Template
More like this
M1 Release planning Milestone
M1 Release planning Milestone
More like this
M1 Deliverables for Planning Milestone Checklist Template
M1 Deliverables for Planning Milestone Checklist Template
More like this
Deliverables for Planning Milestone Checklist - Doc Project
Deliverables for Planning Milestone Checklist - Doc Project
More like this