Let's face it. Keeping track of statuses and making sure plans are up to date across multiple teams is a tough challenge. Portfolio for JIRA is an add-on to JIRA Software which does away with the heavy lifting by providing an automatic forecast of your roadmap. But, how can it actually work for your organisation? How do you best set it up for everyone to use; from the team on the ground through to the executive suite? Join Bree Davies, Product Manager for Portfolio for JIRA, as she takes you through the end-to-end steps of creating a portfolio plan. She'll provide various team member perspectives on usage and expectations, plus she'll share some real world examples of how teams of different sizes and styles have used Portfolio for JIRA. You will leave with a solid understanding of how to use Portfolio JIRA with JIRA Software, along with tips and tricks for best practice long-term agile planning. Bree Davies, Senior Product Manager, Atlassian

1. Making Portfolio for JIRA
work for your team
BREE DAVIES | PRODUCT MANAGER | @BREEDAVIES

2. Does staying on top of
your teams feel like
chasing your tail?
INTRODUCTION

4. INTRODUCTION
Data-driven
roadmap
Visibility for
everyone on
progress
Seamless
integration
with JIRA

5. How can I
get Portfolio for JIRA
to work for me
and my teams?
INTRODUCTION

6. How can I best
get Portfolio for JIRA
to work for me
and my teams?
INTRODUCTION

7. Agenda

8. Agenda
Set your JIRA foundation
Automate your plan
Estimation for all teams
Visibility for everyone

9. IRON TRIANGLE OF PLANNING

10. Using versions
Set board filters
Configure your
hierarchy
JIRA versions translate
to ‘time’
Your JIRA
foundation

11. The bigger picture
Create a hierarchy to begin your planning
with strategic objectives and for high level
tracking and reporting.Using versions
Set board filters
Configure your
hierarchy
Your JIRA
foundation

12. Filters to focus your plan
Create a board from a filter, and your Portfolio plan
will contain only the types of issues you’d like to see.
Your JIRA
foundation
Using versions
Set board filters
Configure
your hierarchy

13. Configure hierarchy
Map your issue types in JIRA
first, then name in Portfolio
JIRA foundations
Filters to focus
Refine your plan by filtering
out what you don’t want first
Versions = time
This will have an impact on
your first calculated schedule

14. Agenda

15. Agenda
Set your JIRA foundation
Automate your plan
Estimation for all teams
Visibility for everyone

18. Connect your
plan to
a board for
extra features

20. Releases are how
you represent ‘time’
in your plan

25. Is it…

27. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

29. The greedy
scheduler will fit in as
much as possible

30. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

32. Change your team’s
velocity to affect
their capacity

33. Use days or hours for
Kanban or traditional
teams

35. Vacation time will be
taken into account by
the scheduler.

36. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

38. Dependencies are more important than issue ranking

39. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

40. Scheduling will occur on
the next available date

41. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

43. Red on your schedule
means your release
is overbooked

44. Play with a few different
scenarios and collaborate
with your team to decide
which will work best

45. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

47. AUTOMATE YOUR PLAN
How is scheduling different
for Kanban teams?

49. Use dynamic
release end dates
Tips for Kanban teams
Think about
estimation
Daily scheduling for
your roadmap

50. Use dynamic
release end dates
Kanban tips
Think about
estimation
Daily scheduling for
your roadmap

51. Use dynamic
release end dates
Kanban tips
Think about
estimation
Daily scheduling for
your roadmap

52. Schedule constraints are
the same for Kanban teams,
just without sprint
assignments
CONTEXT

53. Scheduler
cheat sheet
Release assignment
Sprint assignment
Dependencies
Capacity
Earliest start date
Issue rank

54. Agenda

55. Agenda
Set your JIRA foundation
Automate your plan
Estimation for all teams
Visibility for everyone

56. ESTIMATION FOR ALL TEAMS
My teams don’t
estimate the
same way

57. Your teams Portfolio plan

58. Your teams Portfolio plan
?

59. Your teams Portfolio-only

60. Your teams Portfolio-only

61. Your teams Portfolio-only

62. ESTIMATION FOR ALL TEAMS
Convert your
teams to the
same time
measure in
your plan

63. Nothing changes for
your teams and their
day to day estimation method
ESTIMATION FOR ALL TEAMS

64. ESTIMATION FOR ALL TEAMS

65. ESTIMATION FOR ALL TEAMS
We don’t estimate
more than a sprint
ahead at the moment

66. Set defaults
Assign a value to your unestimated
item issue types in your preferred
time measure for scheduling.

67. Use conservative
past estimates to help
establish your default values
ESTIMATION FOR ALL TEAMS

68. Use a date range
Manage unestimated items
by setting a date range

69. Target start and
end dates
Handling your unestimated issues
Size with your teamDefault estimates

70. Target start and
end dates
Handling your unestimated issues
Size with your teamDefault estimates

71. Target start and
end dates
Handling your unestimated issues
Size with your teamDefault estimates

72. Use data to help improve your
estimation over time
ESTIMATION FOR ALL TEAMS

73. Use the delta to learn
Compare your original estimate with
your final position to improve over time

74. Agenda

75. Agenda
Set your JIRA foundation
Automate your plan
Estimation for all teams
Visibility for everyone

76. So, how are we tracking?
EVERY PROJECT STAKEHOLDER, SINCE EVER

77. Release tracking
See if you’re still on target to make your planned release date.
Maximise capacity
Ensure you’re making the most of your team’s available time.
Check on focus
Use the themes report to compare against projections of how you
expected to spend your time.

79. Are we on track?
Use release reports to track how
close you are to your planned
release date.

80. Release tracking
See if you’re still on target to make your planned release date.
Maximise capacity
Ensure you’re making the most of your team’s available time.
Check on focus
Use the themes report to compare against projections of how you
expected to spend your time.

82. Release tracking
See if you’re still on target to make your planned release date.
Maximise capacity
Ensure you’re making the most of your team’s available time.
Check on focus
Use the themes report to compare against projections of how you
expected to spend your time.

83. Ongoing
area of
business
focus,
with no end
High level
strategic
objective,
with an
end date
INITIATIVES THEMES

85. Track focus areas
Tag your issues with a theme

88. VISIBILITY FOR EVERYONE
Be on the same
page with
minimum effort

89. Use the HTML
include macro
to embed your report

90. I want easy visibility into
the status and progress of
multiple plans in a
single view
VISIBILITY FOR EVERYONE

92. Agenda
Set your JIRA foundation
Automate your plan
Estimation for all teams
Visibility for everyone

93. Keep your JIRA
issues focused
by using filters
Harness the
power of the
scheduling
algorithm
Manage your
unestimated
items
Share reports
for max
visibility
Takeaways

94. Say goodbye to your
spreadsheets once
and for all
FINALE

95. BREE DAVIES | PRODUCT MANAGER | @BREEDAVIES
Thank you!

96. Thank you!
BREE DAVIES | PRODUCT MANAGER | @BREEDAVIES