WALTER BUGGENHOUT • ATLASSIAN EXPERT • ACA IT-SOLUTIONS

Failing to plan: your best plan for failureAnd how JIRA Portfolio can help you avoid this

Familiar situations?

Can you tell me exactly when you will be releasing

to production?

Can someone show me if all our

strategic projects are still on track?

Sorry, but priorities have changed. Can you

show me what that means for our business

goals?

Whoever is careless with the truth in small matters cannot be trusted with important matters.

ALBERT EINSTEIN

”“

Whoever is careless with the truth in small matters cannot be trusted with important matters.

ALBERT EINSTEIN

”“

Introducing JIRA Portfolio

Strategic initiatives

Issues / Epics

Versions

Projects

Issues / Epics

Versions

Projects

Strategic initiatives

Organised backlog

Team Capacity Release Cadence

Portfolio Plan

Organizingthe Backlog

Creating the backlog

Create issues manually

Import issues from a file

Import issues from JIRA

Selection through saved filters

Hierarchy and priority from JIRA are retained

Status, estimate and progress information are retained

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Story

Epic Epic

Initiative

ManagingTeam Capacity

Info at organization level

Global holiday calendar

At team level

Team Schedule (scrum / kanban)

Team velocity (for scrum teams)

JIRA users or Virtual Team Members (e.g. for new hires)

Info at individual level

Working hours in team

Membership of 1/more teams

Exceptions to normal presence

Absences (vacation, illness, …)

Releases and Streams

Fixed start date (e.g. to apply to first release)

Start date relative to previous release (before / after)

Stories can only be linked to 1 release

Stories from 1 Epic can be linked to different releases

Initiatives and Epics can span multiple releases

Planning withJIRA Portfolio

Organised backlog

Team Capacity Release Cadence

Capacity Utilisation

Booked Capacity

Free Capacity

Releases view

Initiatives and Epics views

Story viewStories in a sprint: estimates, iteration length, team velocity

Planning Engine of JIRA Portfolio

Considers backlog items to be in priority order

Always tries to have work start as early as possible

Distributes work evenly and automatically across available capacity …

… unless otherwise determined by the user

Velocity evolution

Assigning the right teamsAnd getting an overview of work by Teams

Different teams, different schedules

Assigning Team MembersAnd getting an overview of work by Team member

Considering specializationUsing stages and skills

Dependencies

Can be set between issues at any level

Schedule work of the dependent issue after its parent

Are clearly indicated in the Initiative and epic views

Taken into account when recalculating

The big picture

Takeaways

Remember these?

Can you tell me exactly when you will be releasing

to production?

Can someone show me if all our

strategic projects are still on track?

Sorry, but priorities have changed. Can you

show me what that means for our business

goals?

Know when you can deliver

React to change

Stay focused on the bigger picture

Keep everyone on the same page

Portfolio Management for JIRA