Project Management using Jira

Structure 

A project must be structure as below for the moment. We are currently within a transition period because the tool version and feature will evolved within the next few months. 

Item type:

There is a few type of tasks you can create within Jira for the moment:

Sub item type:

There is two type of subtasks 

1. The High level one is the Top level initiative. It is used to capture the main information related to a project.
   ## The usage of this item aims to ease the reporting and link creation between all items of a define project. This is partially achieved for now. 
2. Below the Top level initiative we are using Epic to display the organisation of the project and backlog. 
   1. An Epic that would be used to manage the PMO - Admin task
      This item is using a Kanban process (Backlog, In progress, Done) for all tasks below it. Those task are mainly create automatically. 
      Rules: This Epic must have a label "Project" and a start date 
   2. Other Epic that are used for project content. 
      1. If an Epic is used to group all project contents activities we used the termination "- Project" in the name of the project. 
      2. If each Epic are used to define features we have to deliver there are no restriction. 
3. Below each Epic they are two types of item. There is a general agreement to use them. 
   1. User Story - It is used for delivery activity that is organise by Sprint
   2. Task -  It is used for all activities that is organise through a Kanban model (Backlog, In Progress, Done). 

Globally it means we are having the following structure based on item types. 

Risk : 

A risk must be linked to a Task or User Story. It must be created from the related item and using the below button. 

To explore: https://solvayagile.atlassian.net/plugins/servlet/project-config/EBR/administer-components

Atlas project orga: https://team.atlassian.com/project/SOLVA2-15/updates

Project structure example:

Robustify :

• PMO follow-up : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Project : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Global overview & statistics: https://solvayagile.atlassian.net/jira/dashboards/10396
  • Backlog with Status
  • Issue Statistics - Epic 
  • Issue Statistics - Status 
• Atlas : https://team.atlassian.com/project/SOLVA2-16/
  • General Updates?
  • Risks
  • Decisions