Scaling Agile with Portfolio for Jira

1. Scaling agile with   Portfolio for Jira BREE DAVIES | PRODUCT MANAGER | @BREEDAVIES

2. Scaled agile feels Source: Shutterstock

3. It’s not just   about tools;   it’s about people* THE STORY OF A SCALED AGILE JOURNEY *but tools help a bunch

4. Agenda Keep Jira simple Optimise your hierarchy for comms Plan to plan Takeaways

5. Agenda Why should I scale agile? Keep Jira simple Optimise your hierarchy for comms Plan to plan Takeaways

6. How did a fast-growing   auto insurance company  scale their agile operations? Source: Shutterstock

7. Needed management of cross-team dependencies Planning was inefficient We were relying on spreadsheets Managing teams was a manual and time-consuming effort

10. Scaled agile allowed the management and coordination of multiple teams that work on all stages of   a large project Source: Shutterstock

11. 2014 1 scrum team Scaling agile doesn’t happen overnight

12. 2014 1 scrum team 2017 13 scrum teams Scaling agile doesn’t happen overnight

16. PORTFOLIO FOR JIRA Data-driven roadmap Visibility for everyone on progress Seamless integration   with Jira

18. ‘Programs’   = ?  let’s clarify

19. SAFe ‘program’ A level within the SAFe framework ‘Programs’ Portfolio ‘program’ A feature which allows you to aggregate many plans into a single view Customer ‘program’ How you may structure your teams. Many feature teams, for example, may make up a ‘Program’ in your company

22. Agenda Why should I scale agile? Optimise your hierarchy for comms Plan to plan Takeaways

24. Be clear how you will organize your teams   before you put tools   around them. SET STRONG FOUNDATIONS

25. What’s under our customer’s Jira hood? Each board is based based on a filter using a custom field for ‘Program’ and then, separated by team.

26. FixVersion Essential for using   Releases in Portfolio Estimate We rely on this to understand the size of your work Team Field See and share your team assignments Parent Link Surface hierarchy   on your   Jira issues Jira fields for Portfolio success

28. FixVersion field The link for communicating Release assignment for issues from Portfolio

30. Creating a call-out Watch the tutorial in the Presentation Guidelines Keynote to learn how to create call-outs on screenshots within this template. Estimate field Needed to share sizing information between Portfolio and Jira

32. Team field Add to your screens to   see team assignment from Portfolio

34. View your hierarchy See where your issues fit into the next level of hierarchy upwards within Jira

35. Creating a call-out Watch the tutorial in the Presentation Guidelines Keynote to learn how to create call-outs on screenshots within this template. And, in reverse See all epics that fit into an initiative within Jira by using the Parent Link field

36. Introduced minor customizations Jira was kept simple with minimal changes The experience is consistent for all Each issue type and team use the same workflow Top down meets bottom up Teams plan three sprints ahead to their   maximum capacity

37. Introduced minor customizations Jira was kept simple with minimal changes The experience is consistent for all Each issue type and team use the same workflow Top down meets bottom up Teams plan three sprints ahead to their maximum capacity

38. Introduced minor customizations Jira was kept simple with minimal changes The experience is consistent for all Each issue type and team use the same workflow Top down meets bottom up Teams plan three sprints ahead to their maximum capacity

39. Custom fields are powerful. But think carefully before   re-creating standard Jira fields with your own. CUSTOM FIELD WARNING

40. Determine what’s essential Keep it simple Audit your customizations I’m worried we are   not set up for success

43. Agenda Why should I scale agile? Keep Jira simple Plan to plan Takeaways

45. Match your issue hierarchy to the structure of your org, making   plans and reports digestible for   all audiences ALIGN YOUR HIERACHY

46. Match your issue hierarchy to your org Product Owner Product Owner Product Managers & Business Partners Scrum Master & Team Scrum Master & Team

47. Product Owner Scrum Master & Team Match your org to your issue hierarchy Product Managers / Business Partners / Program Management Executive Strategic Objectives   & Programs Initiatives & Programs Epics Epics & Stories

48. Use Portfolio’s hierarchy to   roll up your   work items

49. It’s a lot of people to keep aligned   especially when your program is moving quickly Source: Shutterstock

50. Supporting team collaboration Inspect, adapt and plan  Product Mangers, Product Owners and Business Partners meet regularly throughout the month.

51. Bi-weekly portfolio planning Review the next three releases, including; • Work release • Work per sprint • Work per team Adjust for priority,   team velocity and cross-team dependencies EPIC LEVEL Source: Shutterstock INITIATIVE LEVEL

52. Supporting team collaboration Prioritise communication across levels  The scrum teams escalate any issues in program meetings, which occur fortnightly.

53. Scrum of scrums meeting Escalate issues Manage cross team dependencies Keep communication flowing Resolve blockers STORY LEVEL EPIC LEVEL Source: Shutterstock

54. Agenda Why should I scale agile? Keep Jira simple Optimise your hierarchy for comms Takeaways

56. Think about the streams of work and issue types you want to see in your plan. PLAN TO PLAN

57. Creating a call-out Watch the tutorial in the Presentation Guidelines Keynote to learn how to create call-outs on screenshots within this template. A project Each connected issue source will appear as a separate project in your Portfolio plan

58. Releases   = Versions  =  Time

59. Red on your schedule means your release   is overbooked

60. I want to align several streams of work to the   same goal ONE RELEASE PER PI/MILESTONE/GOAL

61. Use Cross- Project Releases Align your teams towards a single (time) goal Easy filtering of the schedule ONE RELEASE PER PI / MILESTONE / GOAL

62. ONE RELEASE PER PI / MILESTONE / GOAL Clear reporting Group releases together and create an aggregate report across all your teams.

63. I want to clearly visualize all the dependencies in my plan so I can manage them MANAGE CROSS-TEAM DEPENDENCIES

64. DEPENDENCY REPORT Manage your project’s risk See all the dependencies that exist between teams in your plan, so you can reduce your project’s risk Feel confident in your release date When you’re on top of your dependencies, you’ll feel more confident that you will make your release date

65. I want to connect the   team’s work to strategy   so execs know we are working on the right things USE THEMES TO CONNECT WORK TO STRATEGY

66. Set strategic objectives Define how much time you want to dedicate to certain objectives and monitor over time how much is being invested in each area. USE THEMES TO CONNECT WORK TO STRATEGY Please remember You don’t always need the line or text at all.

68. I want to combine   several plans into a   single view ROLL IT UP TO A PORTFOLIO PROGRAM VIEW

69. ROLL IT UP TO A PORTFOLIO PROGRAM VIEW See your schedule for multiple plans in a single view

70. ROLL IT UP TO A PORTFOLIO PROGRAM VIEW See progress and status of your scope across multiple plans

71. I want to build a   reporting dashboard   for visibility SHARE REPORTS IN CONFLUENCE

72. Create a dashboard Embed several different reports to give full visibility into team progress SHARE REPORTS IN CONFLUENCE Dynamic updates Reports are always in real-time, so no manual updates are needed Add context Use Confluence to add commentary and context around the data Please remember You don’t always need the line or text at all.

73. Source of Truth Product Managers and Owners use this view to make sure the right work is going to be executed Collaboration Teams can see what’s been scheduled. Work can be easily shared across teams if capacity and velocity allows Visibility One plan per program allows a clear view of the work   in each sprint What have been the benefits for Acme?

76. There’s different ways to scale agile Do your research and understand which is the best framework for your company. It might not be just one.

77. Scrum of Scrums Next ‘level’ up from one-team scrum, with a daily meeting of ambassadors from each team to emphasise communication and coordination Large Scale Scrum Takes the scrum ceremonies and has two frameworks to scale across different sized teams Disciplined Agile A decision making framework which is a modification of scrum and also borrows from Agile Modeling, XP, Kanban and Lean

80. When scaling agile across an entire organization, focus on “just enough” DAN RADIGAN - THE AGILE COACH

81. Agenda Why should I scale agile? Keep Jira simple Optimise your hierarchy for comms Plan to plan

83. Keep Jira simple Match your hierarchy to your org Plan to plan Scaling is more than just a set of tools Takeaways

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

Scaling Agile with Portfolio for Jira

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (17)

Semelhante a Scaling Agile with Portfolio for Jira

Semelhante a Scaling Agile with Portfolio for Jira (20)

Mais de Atlassian

Mais de Atlassian (20)

Último

Último (20)

Scaling Agile with Portfolio for Jira