Zeige mehr…

Step 1 - SAFe Project Configuration

After all the schemes described above have been created, the projects can be created and equipped with the schemes.


Navigation

Die Seiten können in der Mobilversion leider nicht aufgelistet werden.

SAFe Projektkonfiguration

How should Jira projects be configured so that they are compatible with Agile Hive and SAFe?W

a solid basis for your Jira projects so that you can use them as project templates for Agile Hive SAFe projects.

Before projects are created, the components of the project configuration should be modeled. These primarily include the following components:

All not mentioned Jira schemes can be freely configured.


Tutorial: How are Jira projects configured in general?

If you have no experience with the Jira project configuration or are a bit out of practice, we recommend you take a look at the tutorial video on the left.

Please feel free to watch more "Jans Einfach" videos (german only) to dive deeper into Jira, Confluence and Agile Hive. The complete YouTube playlist can be found here.

Issue type schemes

We recommend using the following names and icons for the issue types on the four SAFe levels:

Issue Type Scheme PORTFOLlO - Issue Type Scheme LARGE SOLUTION - Issue Type Scheme PROGRAM - Issue Type Scheme TEAM - Issue Type Scheme
Issue Types

Workflow Schemes

Workflows

The following workflows can be imported as *.jwb files directly into your Jira environment.

Portfolio Workflow Large Solution Workflow ART Workflow Team Workflow Risk Management Workflow


Workflow Schemes

Create a separate workflow scheme for all four SAFe levels and use the respective workflow from the table above as default workflow.

In addition, the workflow schemes of the Large Solution, Program and Team levels include the risk workflow for the risk issue type.

# Workflow Scheme Default Risks
1 PORTFOLIO - Workflow Scheme Portfolio Workflow -
2 LARGE SOLUTION - Workflow Scheme Large Solution Workflow Risk Management Workflow
3 PROGRAM - Workflow Scheme ART Workflow Risk Management Workflow
4 TEAM - Workflow Scheme Team Workflow Risk Management Workflow

Custom fields

Please create the following fields:

# Feldname Feldtyp Konfiguration
1 Epic Owner User Picker (single user) -
2 Acceptance Criteria Checklist

Context: Portfolio

  • Epic Hypothesis Statement
  • Lean Business Case
  • WSJF rating completed

Context: Large Solution

  • Benefit Hypothesis Statement
  • WSJF rating completed

Context: Program

  • WSJF rating completed
3 Definition of ready Checklist
  • Item is estimated
  • Item is small enough
  • Item is understandable
  • Item has acceptance criteria (min. 1)
4 SMART PI Objectives Checklist
  • Specific – States the intended outcome concisely and explicitly as possible. (Hint: Try starting with an action verb.)
  • Measurable – It should be clear what a team needs to do to achieve the objective. The measures may be descriptive, yes/no, quantitative, or provide a range.
  • Achievable – Achieving the objective should be within the team’s control and influence.
  • Realistic – Recognize factors that cannot be controlled. (Hint: Avoid making ‘happy path’ assumptions.)
  • Time-bound – The time period for achievement must be within the PI, and therefore all objectives must be scoped appropriately.
5 Objective Business Value Select List (single choice)

Default Value: None

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
6 Stretch Objective Select List (single choice)

Default Value: None

  • Yes

Issue type screen schemes

Screens

Please create the following screens:

(For the sake of simplicity, we do not make a distinction here between the different masks Create, Edit and View.)

Name Portfolio Screen Large Solution Screen Large Solution - Objective Screen Art Screen Art - Objective Screen Team Screen Team - Objective Screen Team - Subtask Screen Team - Bug Screen Risk Screen
Felder
  • Issue Type
  • Summary
  • Assignee
  • Epic Owner
  • Acceptance Criteria
  • Description
  • Linked Issues
  • Job Size
  • User-business Value
  • Time Criticality
  • RROE
  • Cost of Delay
  • WSJF
  • Issue Type
  • Summary
  • Assignee
  • Acceptance Criteria
  • Description
  • Linked Issues
  • Job Size
  • User-business Value
  • Time Criticality
  • RROE
  • Cost of Delay
  • WSJF
  • Issue Type
  • Summary
  • Description
  • Linked Issues
  • Issue Type
  • Summary
  • Assignee
  • Acceptance Criteria
  • Program Increment
  • Affects Version/s
  • Fix Version/s
  • Description
  • Linked Issues
  • Job Size
  • User-business Value
  • Time Criticality
  • RROE
  • Cost of Delay
  • WSJF
  • Issue Type
  • Summary
  • Program Increment
  • Description
  • Linked Issues
  • Issue Type
  • Summary
  • Assignee
  • Definition of ready
  • Story Points
  • Affects Version/s
  • Fix Version/s
  • Description
  • Sprint
  • Linked Issues
  • Issue Type
  • Summary
  • SMART PI Objectives
  • Description
  • Objective Business Value
  • Stretch Objective
  • Linked Issues
  • Issue Type
  • Summary
  • Assignee
  • Affects Version/s
  • Fix Version/s
  • Description
  • Sprint
  • Linked Issues
  • Issue Type
  • Summary
  • Assignee
  • Affects Version/s
  • Fix Version/s
  • Priority
  • Description
  • Sprint
  • Linked Issues
  • Issue Type
  • Summary
  • Assignee
  • Description
  • Impact
  • Probability
  • Residual Impact
  • Residual Probability
  • Affects Version/s
  • Fix Version/s
  • Linked Issues

Screen Schemes

Create the following ten screen schemes and assign the screens as follows:

(For the sake of simplicity, we do not make a distinction here between the different masks Create, Edit and View.)

# Name Screen
1 Portfolio - Screen Scheme Portfolio Screen
2 Large Solution - Screen Scheme Large Solution Screen
3 Large Solution - Objective Screen Scheme Large Solution - Objective Screen
4 Art - Screen Scheme Art Screen
5 Art - Objective Screen Scheme Art - Objective Screen
6 Team - Default Screen Scheme Team Screen
7 Team - Objective Screen Scheme Team - Objective Screen
8 Team - Subtask Screen Scheme Team - Subtask Screen
9 Team - Bug Screen Scheme Team - Bug Screen
10 Risk Screen Scheme Risk Screen

Issue Type Screen Schemes

Create a separate issue type screen scheme for all four SAFe levels and assign the screen schemes as follows:

# Name Konfiguration
1

PORTFOLIO - Issue Type Screen Scheme

2

LARGE SOLUTION: Issue Type Screen Scheme

3

PROGRAM - Issue Type Screen Scheme

4

TEAM - Issue Type Screen Scheme


Permission schemes

Basically, you are free to configure how this scheme should be configured. It should be noted that every user who works in a Hive should also have at least read access to all projects in the hive. In addition, all users should have "Link issues" permission in the Hive projects.

This ensures that:

Jira Projects

Projekt Configuration

After all the schemes described above have been created, the projects can be created and assigned with those schemes.

The following table provides an overview of the assignment of the above schemes, which thus represents the project configuration:


SAFe Level
Portfolio Large Solution Program Team

Issue types

PORTFOLlO - Issue Type Scheme LARGE SOLUTION - Issue Type Scheme PROGRAM - Issue Type Scheme TEAM - Issue Type Scheme

Workflows

PORTFOLIO - Workflow Scheme LARGE SOLUTION - Workflow Scheme PROGRAM - Workflow Scheme TEAM - Workflow Scheme

Screens

PORTFOLIO - Issue Type Screen Scheme LARGE SOLUTION - Issue Type Screen Scheme PROGRAM - Issue Type Screen Scheme TEAM - Issue Type Screen Scheme
Fields Can be configured as desired
Priorities Can be configured as desired
Permissions See section "Permission schemes" above
Notifications Can be configured as desired

Amount of Projects

Basically, every team, every ART, every solution and every portfolio has its own Jira project. Please note that only one portfolio project is used within a SAFe configuration (Full SAFe, Large Solution SAFe, Portfolio SAFe, Essential SAFe).

Here is an example:

SAFe Configuration
Full SAFe Large Solution SAFe Portfolio SAFe Essential SAFe
  • Portfolio Projekt
    • Solution Projekt 1
      • ART Projekt 1
        • Team Projekt 1
        • Team Projekt 2
        • Team Projekt 3
        • Team Projekt 4
        • Team Projekt 5
      • ART Projekt 2
        • Team Projekt 6
        • Team Projekt 7
        • Team Projekt 8
        • Team Projekt 9
    • Solution Projekt 2
      • ART Projekt 3
        • etc.
      • ART Projekt 4
        • etc.
  • Solution Projekt 1
    • ART Projekt 1
      • Team Projekt 1
      • Team Projekt 2
      • Team Projekt 3
      • Team Projekt 4
      • Team Projekt 5
    • ART Projekt 2
      • Team Projekt 6
      • Team Projekt 7
      • Team Projekt 8
      • Team Projekt 9
  • Solution Projekt 2
    • ART Projekt 3
      • etc.
    • ART Projekt 4
      • etc.
  • Portfolio Projekt
    • ART Projekt 1
      • Team Projekt 1
      • Team Projekt 2
      • Team Projekt 3
      • Team Projekt 4
      • Team Projekt 5
    • ART Projekt 2
      • Team Projekt 6
      • Team Projekt 7
      • Team Projekt 8
      • Team Projekt 9
  • ART Projekt 1
    • Team Projekt 1
    • Team Projekt 2
    • Team Projekt 3
    • Team Projekt 4
    • Team Projekt 5
  • ART Projekt 2
    • Team Projekt 6
    • Team Projekt 7
    • Team Projekt 8
    • Team Projekt 9

Kanban/Scrum Boards

All Agile Hive Jira projects must have Kanban or Scrum Boards. The following is an overview:

SAFe Level

Portfolio Large Solution Program Team
Board type Kanban Board Kanban Board Kanban Board Kanban or Scrum Board
Board name

Portfolio Level Kanban Board

Solution Name Kanban Board Program Kanban Board - Name Team Name Board
Amount 1x One board per solution project One board per program project
One board per team project
Board filter project = Portfolioname ORDER BY Rank ASC project = Solution name ORDER BY Rank ASC project = Program name ORDER BY Rank ASC project = Team name ORDER BY Rank ASC

Zeige mehr…
Zeige mehr…