1. Agile Project and Portfolio
Management Using Jira
AgileSolutions

2. Enable teams to use Jira to
support their Scrum practice as
soon as possible
Objective
AgileSolutions

3. Agile and Scrum are about People
Agile values “individuals and interactions over
processes and tools”
Jira is a Tool
If you allow people to use the process to deliver
value you’ll have better outcomes than if you
use the tool to drive your process.
When deciding how or whether to use a feature or
configuration, first ask how it supports the team’s
ability to use Scrum to deliver value
A Word about People, Processes and Tools
AgileSolutions

4. Scrum
Role 3
Role 1 Role 2
Artifact1
Artifact 2
Artifact 4
Artifact 3
Meeting 2
Meeting 5
Meeting 4
Meeting 3
Meeting 1
3 roles
4 Artifacts
5 Meetings

5. Scrum
Backlog
Refinement
3 roles
4 Artifacts
5 Meetings

7. Epic 2
Compon
ent A
Epic 1
Compon
ent B
Compon
ent B
Project: Versions, Epics, Issues
scrumalliance.org website
Project
Version 1.0.0Versions
Epics
Compon
ent A
Components
Release Dates
Issues
Story
1.1
Story
1.2
Story
1.3
Bug Fix
1.1
Bug Fix
1.2
Story
1.4
Sprints
Bug Fix
2.1
Story
2.1
1 2 3 4 5 6
AgileSolutions

8. Story Map: Epics and User Stories
Epics
User
Stories
 Prioritized
 Definition
of Ready
AgileSolutions

9. Epics, Stories, Sprints and Versions
Epics
User
Stories Sprint 1 Sprint 2
Sprint 3
Version 1.0
Release
Date
 Prioritized
 Definition
of Ready
AgileSolutions

10. What’s Your Experience Level with Jira?
Novice Expert
AgileSolutions

11. Jira for Project Management
https://www.youtube.com/watch?v=sGdVEbHTI1A
Jira Portfolio
https://www.youtube.com/watch?v=LexaHkZls3g
Portfolio in less than one minute:
https://www.youtube.com/watch?v=-BzznvUuAaU
Jira Overview
AgileSolutions

12. Jira Project Overview
AgileSolutions

13. Issue Types
Bug - a problem that impairs or
prevents functions
Epic – a large, complex user story
that needs to be broken into
smaller stories
Story – a new feature or piece of
functionality delivered in a Sprint
Task – a generic work item that
isn’t a Bug or Story
Sub-task – the detailed work
to be done on an Issue

14. Issue Details

15. Exercise
Organize Your scrumalliance.org Website Project
1.Create at least 2 Versions
2.Create at least 5 Epics
3.Create at least 1 Sprint
4.Create at least 5 Bugs
5.Assign at least 20 Issues to Versions and Epics
6.Assign arbitrary Point Values of 1, 2, 3, and 5 to at least 20
Issues
7.Assign at least 10 Issues to a Sprint and Start the Sprint
8.Create Sub-tasks for at least 5 Issues in the Sprint
9.Create at least 5 Components and assign Issues to them AgileSolutions

16. Version/Release Examples

17. Release Examples
https://developer.salesforce.com/releases/release/Spring+%2716
https://www.salesforce.com/blog/category/seasonal-release.html
AgileSolutions

18. Release Schedule Example
Version 1.0
Spring ’17 Release 1
2017 Release 1
February ’17 Release
AgileSolutions

19. Create A Sprint
By default all projects are able to select Sprints from other
projects. For example, on the Edit Issue page, there is a Sprint
field that allows a user to assign an Issue to a Sprint. The drop-
down list on the Sprint field shows all available Sprints,
including those from other Projects in the system.
<Team Name> <Sprint#> <Sprint start date: DDMMM>-<Sprint
end date: DDMMMYYYY>
Sprint# sequence starts with 1 at the beginning of each year
Example:
VMF Sprint 3 07Sep-20Sep2016
AgileSolutions

20. scrumalliance.org website Epics
1. As a member of the Scrum Alliance, I want to
create and maintain my profile on the website
2. As a Scrum Trainer, I want to create and maintain
my profile on the website
3. As a visitor to the site, I want to see a schedule of
courses
AgileSolutions

21. Components

22. scrumalliance.org website Components
1. Home Page / Landing Page
2. Site Search
• Search Results Display and Filters
3. Menu
4. Course Calendar
5. Course Search
6. Administration
7. Login Page
8. File upload
9. PDF creation
10. Event Calendar
11. Blog
12. Find A Coach (Certificant Directory)
13. Certification Dashboard
14. Member Community
• Membership
• Groups
• Forums
• Resources
• AgileCareers
• Store
15. Help Center
https://scrumalliance.zendesk.com/hc/en-us
16. CMS
• Landing page scrolling banner
• Training content
• Videos
• Press Releases
• Newsletter subscribe
• Privacy Policy / Terms of Use
• Advertising banners
AgileSolutions

23. Keys to Success with Jira
1.Backlog Grooming
• Create Epics and Assign Issues to Them
• Rank Order (Prioritize) Issues Top to Bottom
2.Opportunity to make changes based on
retrospective, for example:
• Logging work
• Reporting work
3.Print issues for each sprint and create a
physical board
4.Plan to spend some capacity in upcoming
Sprints on transition to Jira
AgileSolutions

24. Make a Commitment
Jira Vision
Use this as an opportunity not just to keep doing what you’ve
been doing, but to implement one or two changes for
improvement
• Story Writing
• Backlog Grooming
• Backlog Prioritization
• Definition of Ready Criteria
• Story Point Estimating
• Sprint Planning
• Sprint Execution
• Accurate work progress tracking and reporting
• Daily Standup quality
AgileSolutions

25. Additional Resources
AgileSolutions

27. Atlassian Answers

28. Jira Administrator Certification

29. Jira Portfolio
https://www.youtube.com/watch?v=LexaHkZls3g
Portfolio in less than one minute:
https://www.youtube.com/watch?v=-BzznvUuAaU
Jira Portfolio Overview
AgileSolutions

30. Project
Contains Versions, Epics, and Issues. Worked on by one or more teams
Version / Release (Project)
A Version of a product or project contains a major feature or set of features.
Note: Version at the Project level is synonymous with Release at the Portfolio level.
Epic (Project)
An Epic is a Feature or a set of Issues
Issue (Project)
An Issue is one of these: Story, Bug, Task, Epic
Component (Project)
A Component is a persistent part of a system or product
Portfolio Plan
The collection Projects, Initiatives, and Investment Themes for a period of time
Release (Portfolio)
A Release is the Portfolio-level equivalent to a Version at the Project level
Initiative (Portfolio)
An Initiative is part of the business strategic plan and contains Epics
Theme (Portfolio)
A Theme is a business investment category
Jira Terms
AgileSolutions

31. Portfolio Plan
Comprised of multiple Projects and Teams
AgileSolutions

32. Initiatives
Examples of Initiatives:
• Anything with “Program” in its title, e.g., “Affiliate
Marketing Program”
• Anything identified as a Strategic Business Objective
• Multi-quarter/multi-phase “Big Rocks”
• New Line of Business
• Company Acquisition
• Regulatory Requirement
AgileSolutions

33. Themes
Themes are high-level strategic focus areas, value streams or investment categories used to set
priorities. Themes are a strategic planning tool that