Speaker: Phil Heijkoop, ALM Works Adopting agile methodologies in a large organization is never easy—what looks great on paper, may not work in real life. Luckily, Jira offers the flexibility to support almost any process. And it can adapt to changes as the process evolves. In this session we'll talk about some of the challenges associated with Scaling Agile, the things you need to consider when choosing the right Jira apps, and some of the successful approaches we've seen customers use. We’ll show you some easily-implemented use cases for common agile rituals such as PI planning, release planning, and backlog grooming, at scale.

1. Phil Heijkoop
Scaling Agile

2. Agenda
• Why Scale Agile
• How does one Scale Agile
• Jira and Scaling Agile
• Examples

3. Why Scale Agile

4. Benefits
Faster Time To Market
Better Business and IT Alignment
Quality and More Consistent Delivery
Happier Teams

5. Lean and Agile
Principles
Value Driven
Synchronized Cross-Functional Teams
Systems Thinking
Improvement and Innovation

6. How to Scale Agile

7. Available
Methodologies
SAFe (Scaled Agile Framework)
LeSS (Large Scale Scrum)
DA (Disciplined Agile (Delivery))
Spotify Model
Others…

8. What’s Your Profile
How Complex the Project?
How Many Teams?
Are Teams Agile?
Scaling Top-Down or Bottom-Up?
How Business Plans Now?

10. Pros / Cons
Complete Framework
Top-Down
Evolves Based on Results/Feedback
Guidelines For Adoption
Easy to Find Consultants

11. LeSS

12. Pros / Cons
Principles and Rules vs Processes
Simplicity
Very Agile
Scaling Up
Works Great With Right Teams

14. Jira, Scaling Agile,
and you!

16. Jira Out-Of-The-Box
Works Great for Teams and Teams Love It
Highly Configurable
Provides Great Foundation
Lacks Tools For Managing Complex Projects

17. Projects/Issue Types per level

18. Workflows and Boards

19. Scrum Boards

20. Link Items

21. Leverage Confluence

22. What About Tools?
• Portfolio for Jira
• Big Picture
• Structure Family
• Jira Align
• Etc

23. Examples

24. What is Structure
Visualization tool that allows to:
• Build Hierarchies
• Show Data

26. Full Hierarchy
• Share information with everyone
• Buy-in and knowledge empowerment
• Report to leadership status and progress
• Track risks, blockers, issues in real-time

29. Focused Hierarchies
• Track your PIs
• RTEs can track their ARTs
• Team can track their own work
• Teams can also track work of related teams too!

30. PI Planning
• We have the PI hierarchy, use in-line editing
to update information like status
• We can perform extra issue information
lookup and updating with issue details
• AND we can make it even easier for our
teams to look up feedback and give it

33. Using Gantt Charts
• Gantt charts are your friend (when used correctly)
• They can show live data
• Can be responsive not prescriptive
• Part of the feedback loop

37. Level Up

40. Lessons Learned
• Understand where you are and what the goals are
• Don’t get hung up on a particular methodology. Cherry-pick
• Run a pilot project - clear everything up early even though you can
adjust later
• Evaluate the tools and test drive a solution - don’t believe what it says
on the box

41. Lessons Learned
• Get consultants (at least to see the options)
• Invest in trainings
• Have a dedicated person to support the process
• Some things that may seem expensive, like in person PI plannings,
actually work
• Measure the results

42. Questions?

43. phil@almworks.com
More info at alm.works/safe