The document discusses the challenges faced in managing large initiatives, such as lack of visibility and resource mismanagement. It introduces Jira Portfolio as a solution that provides a single view for aligning projects with strategic goals, enabling realistic delivery forecasts and improved resource utilization. The document also highlights the ease of setup and assessment for new projects using Jira Portfolio.

1. “
Introduction to JIRA Portfolio
”Execution is the ability to mesh strategy with reality, align people
with goals, and achieve the promised results.”
Larry Bossidy

2. Large initiative’s challenges
1. No visibility cross projects
2. Resources over or under utilized
3. Disconnect between strategic goals and development reality
4. PM’s time is primary occupied in schedule updates and reports preparation

3. A solution by

4. What is JIRA Portfolio?
S
Single view
G R
Align to goals
Track investments
across strategic
themes to ensure that
those investments
align with business
priorities
Realistic delivery
forecasts
Generate realistic
delivery forecasts with
automatic scheduling
algorithms supporting
time-based estimates
as well as story points.
The best way to manage multiple JIRA projects!
A single, accurate view
for planning and
managing initiatives
across multiple teams
and projects with ease.

5. Initiatives view
Multiple projects, one view

6. Teams view
Manage people, skills, weekly hours

7. Teams view
Manage availability and vacations

8. Releases view
Releases add a third dimension to your planning: time

9. Automatic scheduling

10. Automatic scheduling

11. Automatic scheduling
The easiest way to get a realistic schedule

12. Reporting view
Alignment of execution to strategic goals

13. Reporting view
Resource utilization per week/sprint

14. Our first impressions
1. Using JIRA Portfolio to gain visibility on existing JIRA projects:
• 4 hours to setup and import real JIRA data in
• Themes report showed us alignment of JIRA projects to strategic goals
• The new visibility lead to discussions and plan changes
• Epics usage proved to be more difficult (if not standardized across projects)
2. Using JIRA Portfolio to assess feasibility of a new project:
• 1 hour to setup the tasks and a team (no stages)
• We were able to asses feasibility of a new project-to-be having the load of our
team on current projects

15. Time for questions

16. Want to know more?
Nemetschek experts are available to show you JIRA Portfolio in depth!

17. Thank you!
Annie Ioceva,
Atlassian Unit Lead, Nemetschek Bulgaria

18. Bringing to you the beauty of
Atlassian solutions!
Atlassian Summer Day, 2015, Sofia