A lot has changed in the ways teams work since Portfolio for Jira joined the Atlassian family. Team structures have shifted, and more and more teams are doing their work in Jira with greater agility. They have more autonomy but must stay connected to their adjacent teams and communicate their plans effectively with stakeholders. Portfolio for Jira can help you on this journey. If you’ve ever used Portfolio in the past, and are curious about how we’ve reinvented the product, or are looking for an agile tool to help you plan, collaborate, and get visibility across teams in Jira, then this session is for you! In it, we’ll share how we used Portfolio ourselves, setting product direction, identifying the right solution scope, winning internal adoption, and taking your feedback when it came to planning our roadmap.

1. RHYS CHRISTIAN | PRODUCT MANAGER | ATLASSIAN
The Journey to Portfolio 3.0

2. 3.0
Portfolio for Jira Server and Data Center

3. Critical stages of Portfolio
Planning principles
Growing needs
Portfolio 3.0 showcase
Q&A

4. Critical stages of Portfolio
Planning principles
Growing needs
Portfolio 3.0 showcase
Q&A

5. 2014

6. PORTFOLIO JOURNEY
Acquisition
Portfolio joins the
Atlassian family
2014

7. PORTFOLIO JOURNEY
Acquisition
Portfolio joins the
Atlassian family
2014
Portfolio 1.0
Scheduling
algorithm
2014

8. PORTFOLIO JOURNEY
Acquisition
Portfolio joins the
Atlassian family
Portfolio 2.0
Jira integration
2014 2016
Portfolio 1.0
Scheduling
algorithm
2014

9. PORTFOLIO JOURNEY
Acquisition
Portfolio joins the
Atlassian family
Portfolio 2.0
Jira integration
Programs
Top-level visibility
2014 2016 2017
Portfolio 1.0
Scheduling
algorithm
2014

10. PORTFOLIO JOURNEY
Acquisition
Portfolio joins the
Atlassian family
Portfolio 2.0
Jira integration
Programs
Top-level visibility
Portfolio 3.0
2014 2016 2017 2019
Portfolio 1.0
Scheduling
algorithm
2014
What’s new?

11. Critical stages of Portfolio
Planning principles
Growing needs
Portfolio 3.0 showcase
Q&A

12. Data-driven decisions
Insights and warnings
provided by Portfolio
Background on Portfolio
Visibility
Across multiple projects and
teams
Realistic roadmap
Plan in context of real issues
and data in Jira

13. Scope
Iron
Triangle
Cost Time

14. Scope
Iron
Triangle
Cost Time

15. Iron triangle
Scope
Cost
Time
Scope of work to be delivered
• Start big
Initiative Initiative

16. Iron triangle
Scope
Cost
Time
Scope of work to be delivered
• Start big
• Break it down
Initiative Initiative
Epic Epic Epic
Stories
Epic Epic
}

17. Iron triangle
Scope
Cost
Time
Scope of work to be delivered
• Start big
• Break it down
• Estimate
Initiative Initiative
Epic Epic Epic
Stories
Epic Epic
}
7
3
2
1
1
4
3
4
1
1
3
3
5
3
3
3
3 3
11

18. Scope
Cost
Time
Cost of available resources
• Determine the velocity of your team:
• Story points / working hours / throughput
Iron triangle

19. Scope
Cost
Time
Time: When to deliver scope
• Time constraints
• Due dates
• Releases dates
Iron triangle

21. Critical stages of Portfolio
Planning principles
Growing needs
Portfolio 3.0 showcase
Q&A

22. Growing customer needs
Control / flexibility

23. Teams of teams
Growing customer needs
Control / flexibility

24. Teams of teams
Growing customer needs
Visibility / communicationControl / flexibility

25. PORTFOLIO FOR JIRA HELPS
PLAN FOR THE FUTURE IN AN
AGILE WORLD.

26. Critical stages of Portfolio
Planning principles
Growing needs
Portfolio 3.0 showcase
Q&A

32. 2.03.0

33. 3.0 interface
Intuitive UI
Data in context
Drill into details
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
Managing scope

34. Intuitive UI
Data in context
Drill into details
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
3.0 interface
Managing scope

35. Intuitive UI
Data in context
Drill into details
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
3.0 interface
Managing scope

36. Data in context
Drill into details
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
Intuitive UI
3.0 interface
Managing scope

37. Data in context
Drill into details
3.0 interface
Intuitive UI
Managing scope

38. Data in context
Drill into details
Managing scope
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
3.0 interface
Intuitive UI

39. Data in context
Drill into details
Managing scope
Shape usage
Please only use circles, rectangles, and
rounded rectangles to call attention to a
particular part of a screenshot, for the
sake of consistency.
3.0 interface
Intuitive UI

40. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

41. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

42. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

43. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

44. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

45. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

46. Creating a call-out
Watch the tutorial in the
Presentation Guidelines at
Atlassian.design to learn how to
create call-outs on screenshots
within this template.

47. Planning in Portfolio 3.0

50. Dependencies

56. Release
tracking

57. RELEASE TRACKING
Version integration
Aligns 1:1 with Fix versions in Jira
projects.
Milestones
Group issues and mark
important dates on the timeline.
Off-track warning
Warn when plans are slipping.

58. RELEASE TRACKING
Version integration
Aligns 1:1 with Fix versions in Jira
projects.
Milestones
Group issues and mark
important dates on the timeline.
Off-track warning
Warn when plans are slipping.

59. RELEASE TRACKING
Version integration
Aligns 1:1 with Fix versions in Jira
projects.
Milestones
Group issues and mark
important dates on the timeline.
Off-track warning
Warn when plans are slipping.

67. Team capacity
planning

69. View capacity
Group by team so you can enable the
capacity view.

78. Questions?

80. RHYS CHRISTIAN | PRODUCT MANAGER | ATLASSIAN
Thank you!