Page tree

This documentation relates to an older version 5.0 of the Structure for Jira. Visit the current documentation home.

Skip to end of metadata
Go to start of metadata

This is a detailed instruction how to visualize SAFe in Structure.

What do you need:

  • JIRA Software and Confluence 
  • Structure 
  • Structure.Pages
  • Structure.Testy

Ready-to-use demo space: Live Demo

Step-by-step guide

We assume that your JIRA is prepared for scaling. The most common configuration is to create separate project for each level, Kanban project for Portfolio level, with Epic issue type and statuses Funnel, Reviewing, Analyzing, Portfolio Backlog, Implementing, Done; Kanban project for Solution level, with Issue types Capability and Enabler, Kanban project for Program level, issue types Feature and Enabler will be here. Note, that Features are named "Epics" in JIRA, so you can rename them in Administration, Projects for each Team (Scrum or kanban, Scrum is preferrable), Issue types User Story, Bug, Improvement, Enabler should leave here


    1. Define your company Strategy in Confluence
      Create your Space in Confluence for High-Level documents and describe the Strategy of your company

    2. Define Themes
      Define Strategy more accurately, divide it into several Themes as sub-pages for Strategy

    3. Link Themes to Epics
      Define Epics, high-level tasks for implementing your theme. Link JIRA issues with corresponding themes in Confluence.

    4. Add Capabilities
      Since you have separate project for Capabilities, divide you epics into more precise capability issues and put them to Capability Board. Don't forget to link your Capability with corresponding Epics! You can use standard JIRA issue link types, but it will be more convenient to create you own "implements"/ "is implemented by" link type 

    5. Add Features
      Let's add details into huge Capability and divide it into Features. Don't forget to link Feature and corresponding Capability

    6. Story
      Each Feature can be divided into more detailed stories. Let's Do it! Don't forget to link Feature and Story with epic link

    7. Subtask
      If you need more detailed tasks, divide story into sub tasks.

    8. The time has come!
      Create empty Structure and visualize everyting in one place: http://recordit.co/lFYAzeBezV
      - Find you Strategy page and add it to the Structure: http://recordit.co/0vt6mNYsqR
      - Click Automation button and add the rule for adding all child pages: http://recordit.co/5l5fqPM4c3
      - Add rule to add issue linked to pages 
      - Add rule to add Capabilities linked to Epics
      - Add rule to add Features linked to Capabilities
      - Add rule to add Stories linked to Features
      - Add rule to add Sub Tasks linked to Stories

    9. Now you can Group issue on some specific level, for example by Sprint on Team level to track progresses
    10. You also can prioritize issues by sorting by WSJF
    11. Specify your Oblective during PI planning in Notes