Behind the scenes with product management

Presented at JAIT on Aug 8th 2019
https://jait.com.au/51-what-a-product-manager-does-at-atlassiang/

Jason will be giving us a talk from the inside, about his role and experience as Principal PM at Atlassian. What his days are like, how product roadmaps come together and interactions with the team to build and ship value to customers.

Transcript

1. JASON WONG | PRINCIPAL PM | ATLASSIAN | @JASEWONG Behind the scenes with product management
3. A day in the life… Composing a roadmap Shipping stuff Behind the scenes Trends
5. ***** Boardwalk
6. ***** Demos ༵ۚ೔
7. ***** Design wall
8. ***** Data analysis
9. ***** Documentation
10. ***** Retrospectives & Team health monitors
11. The customer champion Dealing with uncertainty Decision making Balancing priorities Product management competencies
12. OKRs From strategy to execution GTM Roadmap
13. VS PM PRODUCT MANAGER PM PROJECT MANAGER
16. A day in the life… Composing a roadmap Shipping stuff Behind the scenes Trends
17. A good starting point for roadmaps Unspoken needs Business model Feature requests
18. Balanced roadmap Feature requests Unspoken needs Business model How likely are you to recommend JIRA to a friend or colleague?
20. Balanced roadmap Feature requests Unspoken needs Business model l*G
    *
    IBE
    BTLFE
    QFPQMF
    XIBU
    UIFZ
    XBOUFE
    UIFZ
    XPVME
    IBWF
    TBJE
    GBTUFS
    IPSTFTz Henry Ford
21. + Release 14% more often Complete 23% more issues
23. Balanced roadmap Feature requests Unspoken needs Business model Competitive position Goals Pricing & packaging Resources & Capabilities
24. Projects JIRA JIRA Agile Versions Workflows Components Issue types Custom Fields Issue Reports Board Visualisation Plan Work Scrum Kanban Agile Reports Boards
25. JIRA JIRA Agile JIRA Software
26. PROJECT TYPES Boards Sprints Agile Reports Software Service Desk Queues SLAs Customer portal KB integration Focused JIRA projects Business Focused JIRA projects Business Focused JIRA projects Business
27. Direction?
28. A model that can help you identify opportunities for value creation Personas Workflow X ʹ Product/Service Value Map
29. PERSONAS *DUGHQHU $VVHPEOHU 5LQJOHDGHU Ű,ŮPDERXWWRPDNHWKHFDOORQWKLVVRVKRZPH HYHU\WKLQJ,QHHGWRNQRZ 7KHPRUH,NQRZHQGWRHQGWKHEHWWHUP\ GHFLVLRQVDUHű $ / $ 1 $ &RQɤJXUHU 'HWHFWLYH 0DNHU Ű,I\RXFDQVKRZPHWKHGDWD,ŮOOɤJXUHRXWWKLV FKDOOHQJLQJSUREOHPWRHYHU\RQH VEHQHɤWű : , / / 7LQNHUHU &RQQHFWRU 6KDUHU Ű,JHWDNLFNRXWRIJHWWLQJP\WHDPWR WU\QHZWKLQJV 8QWLOWKHQH[WEHVWWKLQJFRPHVDORQJű ( 0 0 $ 6 2 ) 7 :$ 5 (  ' ( 9 ( /2 3 0 ( 1 7  7 ( $ 0 $* ( 1 &<  7 ( $ 0 ' ( 9 ( / 2 3 ( 5 6 2 ) 7 :$ 5 (  ' ( 9 ( /2 3 0 ( 1 7  7 ( $ 0 3 5 2 ' 8 & 7 0 $ 1 $ * ( 5 6 2 ) 7 :$ 5 (  ' ( 9 ( /2 3 0 ( 1 7  7 ( $ 0 $* ( 1 &<  7 ( $ 0 '(9(/230(17 0$1$*(5
30. PERSONAS X WORKFLOWS = PRODUCT & SERVICE VALUE MAP Rough backlog Get to release plan Story estimation Story estimation Story estimation Break down into smaller epics Break down into stories Story grooming, ensure everything is captured Story grooming, ensure everything is captured Story grooming, ensure everything is captured Create multiple high-level release plans Evaluate and choose a release plan Break down into smaller epics Ideation Ideation Ideation Product definition Epic creation Estimation Estimation Prioritisation Prioritisation Alana Product Owner Will Team Lead Emma Developer BACKLOG PERSONA Backlog p
31. PERSONAS X WORKFLOWS = PRODUCT & SERVICE VALUE MAP Review sprint health Fulfill conditions of success Get work accepted Prep for release Release Process improvements / sprint wrap up Check for problems / working as expected Dealing with impediments and unblocking Updates workflow Write code Handover to next status, or move to Done Demo Demo Demo Sprint demo / review Make GO / NO-GO decision Ensure release notes are published Start gathering feedback Perform anaytics Make GO / NO-GO decision Deploy Check release is OK Organise final QA Ensure JIRA statuses are correct Lock down release branch Look at release or epic chart to check progress of bigger picture Sprint demo / review Close sprint Sprint retrospective Share retrospective outcomes Decides what to do with unfinished issues Check code health Review outstanding items for release completeness Sprint retrospective Sprint retrospective Sprint demo / review Reads details of issue and understands the work Check broken builds, build status, outstanding PRs Accepts work RELEASE MONITORING Rough backlog Get to release plan More prioritised backlog Scope for sprint 1 accepted What do I need to work on? Story estimation Story estimation Story estimation Sprint planning Break stories into smaller tasks Break stories into smaller tasks Estimation of sub-tasks Understand team velocity to know what to put into sprint Understand team velocity to know what to put into sprint Estimation of sub-tasks Agreement of sprint scope Agreement of sprint scope Start sprint Pre-assign issues to specialists Daily standup meeting Make sure board is up-to-date Raising, flagging and dealing with impediments Daily standup meeting Choose next thing to work on Agreement of sprint scope Check team progress on burndown chart, gadget or wallboard Update release plan Commenting and asking questions on stories Sprint planning Sprint planning Break down into smaller epics Break down into stories Story grooming, ensure everything is captured Story grooming, ensure everything is captured Story grooming, ensure everything is captured Create multiple high-level release plans Evaluate and choose a release plan Break down into smaller epics SPRINT Ideation Ideation Ideation Product definition Epic creation Estimation Estimation Prioritisation Prioritisation Alana Product Owner Will Team Lead Emma Developer BACKLOG PERSONA Backlog prioritisation
32. PERSONAS X WORKFLOWS = PRODUCT & SERVICE VALUE MAP Review sprint health Fulfill conditions of success Get work accepted Prep for release Release Process improvements / sprint wrap up Check for problems / working as expected Dealing with impediments and unblocking Updates workflow Write code Handover to next status, or move to Done Demo Demo Demo Sprint demo / review Make GO / NO-GO decision Ensure release notes are published Start gathering feedback Perform anaytics Make GO / NO-GO decision Deploy Check release is OK Organise final QA Ensure JIRA statuses are correct Lock down release branch Look at release or epic chart to check progress of bigger picture Sprint demo / review Close sprint Sprint retrospective Share retrospective outcomes Decides what to do with unfinished issues Check code health Review outstanding items for release completeness Sprint retrospective Sprint retrospective Sprint demo / review Reads details of issue and understands the work Check broken builds, build status, outstanding PRs Accepts work RELEASE MONITORING Rough backlog Get to release plan More prioritised backlog Scope for sprint 1 accepted What do I need to work on? Story estimation Story estimation Story estimation Sprint planning Break stories into smaller tasks Break stories into smaller tasks Estimation of sub-tasks Understand team velocity to know what to put into sprint Understand team velocity to know what to put into sprint Estimation of sub-tasks Agreement of sprint scope Agreement of sprint scope Start sprint Pre-assign issues to specialists Daily standup meeting Make sure board is up-to-date Raising, flagging and dealing with impediments Daily standup meeting Choose next thing to work on Agreement of sprint scope Check team progress on burndown chart, gadget or wallboard Update release plan Commenting and asking questions on stories Sprint planning Sprint planning Break down into smaller epics Break down into stories Story grooming, ensure everything is captured Story grooming, ensure everything is captured Story grooming, ensure everything is captured Create multiple high-level release plans Evaluate and choose a release plan Break down into smaller epics SPRINT Ideation Ideation Ideation Product definition Epic creation Estimation Estimation Prioritisation Prioritisation Alana Product Owner Will Team Lead Emma Developer BACKLOG PERSONA Backlog prioritisation Plan Work Ship Run KanPlan Dev Status Unify the Jira Project + Jira Agile Board Experience Jira for IT Services & Business teams
33. from backlog to release
34. from backlog to release
35. Behind the scenes A day in the life… Composing a roadmap Shipping stuff Trends
36. Working software Beta Usability opt-in Experiments Early access Beta / Labs
37. Working software Beta Usability opt-in Experiments Improving the UI design
38. >70% clicks went to “All Issues”
39. Where’s my board?
40. VS
41. VS VS
43. Jira Issue Collector was used to gather feedback
44. ITERATIVE UNTIL IT’S READY
45. As of JIRA 6.4 Launch 95% 6TFS
    BDDFQUBODF
    SBUF
    "
    XIPMF
    NBKPS
    SFMFBTF
    BIFBE
    PG
    TDIFEVMF
46. Working the software Beta Usability opt-in Experiments Faster validation of customer value Control Group Experiment Group
47. Experiment on Project Create Quickly get started with this basic setup. Simple software development
48. Experiment on Project Create
49. Experiment on Project Create
50. Behind the scenes A day in the life… Composing a roadmap Shipping stuff Trends
51. OUTCOMES, OVER OUTPUTS Shipping customer value, value that is visible Focus on the working software, shipping continuously Task completion, Development velocity Agile + GIT / CI / CD + Metrics
52. as Software a Service
53. as is a Service Software
54. People are the product / service
55. Stay lean, stay loveable
56. V P M
57. Fugro Roames
 sees into the future with drones. With Atlassian, developers create new technology to assess risk to existing power infrastructure.
58. For Cochlear, 
 it’s all about connections. Atlassian helps Cochlear bring missing sounds to young and old.
60. JASON WONG | PRINCIPAL PM | ATLASSIAN | @JASEWONG Thank you!