Scrum of ScrumsScrum of ScrumsBringing JIRA & Bringing JIRA & GreenHopper GreenHopper

to entire companyto entire company

Wojciech Seligawojciech.seliga@spartez.com

2

Scenario

● One major product with multiple Scrum teams working on it (Scrum of Scrums)

● Product split into several subsystems● Global product backlog● Team product backlogs● Monthly sprints (parallel...)● Internal releases every N sprints● Public releases every M internal releases

3

Release Cycle

SprintSprint SprintSprint SprintSprint SprintSprint SprintSprint

Internal ReleaseInternal Release Internal ReleaseInternal Release Internal ReleaseInternal Release

Marketing ReleaseMarketing Release

Team ATeam A

Team BTeam B

Team NTeam N

...

SprintSprint SprintSprint

Time

4

Requirements

● Current Sprint Progress Tracking● Current Internal Release Progress Tracking● Current Marketing Release Progress Tracking● Measuring Progress in Story Points (“done”/all)● Trends

Per Scrum TeamPer Scrum Team Per SubsystemPer Subsystem GloballyGlobally

5

GH take on Scrum of Scrums

GreenHopper allows you to nest child versions to provide flexibility in Scrum project management. For example, you might want to group all issues that need addressing in a major product version at the highest level of a version hierarchy. Since you might have separate teams, each working on different components that constitute this major product version, you may wish to represent each of those components as an immediate child ('component') version of the major product version. From here, you may wish to break up a given component into sprints, depending on the amount of work required to develop it. Therefore, each of these sprints would be an immediate child ('sprint') version of its respective 'component version'.

GH online documentation

6

Problems

● Combinatorial explosion of Versions x Teams● Inability to aggregate easily results● Inability slice and dice backlogs (per team, per

component/subsystem)● Many reports base on issue count or hours● Trends need more love

7

Solution

Business Domain → JIRA/GH EntityProduct Project

Team Component

Subsystem Multi-Select Custom Field

Product Backlog GH Project Backlog

Team Backlog Component Backlog

Marketing Release Top-Level Version

Internal Release Mid-Level Version

Sprint Bottom-Level Version

8

Product Backlog

Story 1Story 1

Story 2Story 2

Story 3Story 3

Story 4Story 4

Story 5Story 5

Story 6Story 6

Story 7Story 7

Story 8Story 8

Story 9Story 9

Story 10Story 10

Story 1Story 1

Story 4Story 4

Story 5Story 5

Story 9Story 9

Story 2Story 2

Story 3Story 3

Story 5Story 5

Story 6Story 6

Story 7Story 7

Story 8Story 8

Story 10Story 10

Product Backlog Team B Product Backlog Subsystem P Backlog

GH Component Board

GH Contexts

9

Backlog Management

Live Demo

10

Progress & Trend Tracking

● Sprint burndowns (hours, stories)● Internal release burndowns (stories)● Public release burndowns (stories)● Scheduled vs. unscheduled stories● Committed stories vs. stretch goals● Team Velocity Trends

11

Progress & Trends Tracking

Live Demo

12

Forgotten “Small” Thing

“Hey, our parallel sprints are not so parallel...”

“Gosh, we need to modify GreenHopper itself”

13

World is not perfect

● Stories fixed in several releases● Unfinished work● Hierarchical versions are awesome, but ... JIRA

does not know about them● Sometimes GH behaviour is not what we

expect

14

Future

● Rapid Board● Pluggable date strategies in GreenHopper● Executive Dashboard / Project Portfolio

Management● Automatic Velocity calculations

15

Summary

● GreenHopper is amazingly flexible● Think out of the box (or: the mapping is tricky)● Try to satisfy your needs by existing

functionality, write plugins if you really cannot● Dashboards and gadgets FTW● JIRA + GH works in Scrum of Scrums

environment pretty well

16

Credits

● Huge thanks to Lumesse Limited for allowing me to talk about it publicly and use their prod data

● Many thanks to Mariusz Chrapko for his creativity, great Scrum attitude and passion