開発の背景、JIRA Softwareのプロダクトマネージメント

1808e3f36ce79bfc58b4cfd890f4f780?s=47 jasewong
December 09, 2016

開発の背景、JIRA Softwareのプロダクトマネージメント

ジェイソンが社内でJIRA Softwareのプリンシパルプロダクトマネージャーの役割や経験について話します。日々の仕事、ロードマップの作り方、チームと連携して顧客に価値のあるソフトウエアを開発し、出荷することについてプレゼンテーションでシェアします。

Video recording: https://youtu.be/5Ac6ZFiPe-g

Blog: http://japan.blogs.atlassian.com/2017/02/behind-the-scenes-product-manegement-with-jirasoftware/

1808e3f36ce79bfc58b4cfd890f4f780?s=128

jasewong

December 09, 2016
Tweet

Transcript

  1. Jଜ • ϓϦϯγύϧϓϩμΫτϚωʔδϟʔ • ΞτϥγΞϯ • @JASEWONG ։ൃͷഎܠ JIRA SoftwareͷϓϩμΫτϚωʔδϝϯτ

  2. Jଜ • ϓϦϯγύϧϓϩμΫτϚωʔδϟʔ • ΞτϥγΞϯ • @JASEWONG ։ൃͷഎܠ JIRA SoftwareͷϓϩμΫτϚωʔδϝϯτ

  3. • Big cool statistic • 2,56 9 • Add-Ons in

    Marketplace ॳΊ·ͯ͠ɺ ʮ+ଜʯͱਃ͠·͢
  4. None
  5. None
  6. ϩʔυϚοϓͷ੡࡞ํ๏ ϓϩμΫτϚωʔδϟʔͷ࢓ࣄ ։ൃͷഎܠ Ͳ͏΍ͬͯग़ՙ͢Δͷ͔ʁ

  7. ϩʔυϚοϓͷ੡࡞ํ๏ ϓϩμΫτϚωʔδϟʔͷ࢓ࣄ ։ൃͷഎܠ Ͳ͏΍ͬͯग़ՙ͢Δͷ͔ʁ

  8. None
  9. ***** Boardwalk

  10. ***** Demos ༵ۚ೔

  11. ***** Design wall

  12. ***** Data analysis

  13. ***** Documentation

  14. ***** Retrospectives & Team health monitors

  15. ސ٬ͱνʔϜͱର࿩ ෆ࣮֬ੑ΁ͷରԠ ࢥ͍੾ܾͬͨஅྗ ϓϩμΫτϚωʔδϟʔͷ೔ৗεΩϧ ༏ઌॱҐΛ؅ཧ͢Δ

  16. ϚʔέςΟϯά 0,3 ϩʔυϚοϓ ઓུ͔Βग़ՙ΁

  17. VS PM PRODUCT MANAGER PM PROJECT MANAGER

  18. None
  19. None
  20. ϩʔυϚοϓͷ੡࡞ํ๏ ϓϩμΫτϚωʔδϟʔͷ࢓ࣄ ։ൃͷഎܠ Ͳ͏΍ͬͯग़ՙ͢Δͷ͔ʁ

  21. A good starting point for roadmaps જࡏతͳཁ๬ ձࣾͷཁ๬ ސ٬ͷཁ๬

  22. ސ٬ͷཁ๬ જࡏతͳཁ๬ ձࣾͷཁ๬ How likely are you to recommend JIRA

    to a friend or
  23. None
  24. ʮࣗಈंͷͳ͍࣌୅ʹɺ٬ʹཁ๬Λฉ͍ͨΒɺ ΋ͬͱૣ͍അ͕ཉ͍͠ͱ౴͍͑ͯͨͩΖ͏ʯ Henry Ford ސ٬ͷཁ๬ જࡏతͳཁ๬ ձࣾͷཁ๬

  25. + ϦϦʔε 14% more often ՝୊ղܾ཰ 23% more issues

  26. None
  27. જࡏతͳཁ๬ ձࣾͷཁ๬ Ϧιʔεͱٕज़ ސ٬ͷཁ๬ ڝ૪ϙδγϣϯ ໨ඪ ϏδωεϞσϧ

  28. ϓϩδΣΫτ JIRA JIRA Agile όʔγϣϯ ϫʔΫϑϩʔ ίϯϙʔωϯτ ՝୊ͷछྨ ΧελϜϑΟʔϧυ ՝୊Ϩϙʔτ

    Ϙʔυ ܭը ։ൃ εΫϥϜ ؃൘ "HJMFϨϙʔτ Ϙʔυ
  29. JIRA JIRA Agile JIRA Software

  30. 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
  31. ീํ࠹͕Γ

  32. ಇ͖ํΛϞσϧʹͨ͠ΒɺՁ஋͕ݟ΍͘͢ͳΔ ϖϧιφ ϫʔΫϑϩʔ X ʹ 1SPEVDU4FSWJDF7BMVF.BQ

  33. ΃ϧιφ *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
  34. 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 ϖϧιφYϫʔΫϑϩʔ1SPEVDU4FSWJDF7BMVF.BQ
  35. 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 ϖϧιφYϫʔΫϑϩʔ1SPEVDU4FSWJDF7BMVF.BQ
  36. 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 ܭը ։ൃ ग़ՙ ӡӦ ϖϧιφYϫʔΫϑϩʔ1SPEVDU4FSWJDF7BMVF.BQ
  37. 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 ܭը ։ൃ ग़ՙ ӡӦ ؃൘όοΫϩά +*3"ͱ##ͷ࿈ܞ ϏδωεϢʔβʔ ϖϧιφYϫʔΫϑϩʔ1SPEVDU4FSWJDF7BMVF.BQ
  38. ϩʔυϚοϓͷ੡࡞ํ๏ ϓϩμΫτϚωʔδϟʔͷ࢓ࣄ ։ൃͷഎܠ Ͳ͏΍ͬͯग़ՙ͢Δͷ͔ʁ

  39. Labs Usability Opt-in Experiments ϕʔλʔϦϦʔεͰɺૣΊʹࢼ͢

  40. Labs Usability Opt-in Experiments ମݧͷઃܭΛ޲্͢Δ

  41. None
  42. >70%ͷΫϦοΫ͕ “All Issues”΁

  43. Ͱ΋AgileϘʔυ͸Ͳ͜Ͱ͔͢ʁ

  44. VS

  45. None
  46. None
  47. ൓෮ܕιϑτ΢ΣΞ։ൃ

  48. As of JIRA 6.4 Launch 95% ͷϢʔβʔ͕৽͍͠ମݧΛड͚औΓ·ͨ͠ʂ

  49. ग़ՙ͢ΔՁ஋Λૣ͔֬͘ΊΔ Labs Usability Opt-in Experiments A B Control Group Experiment

    Group
  50. ϓϩδΣΫτΛ੡࡞͢Δςετ

  51. ϓϩδΣΫτΛ੡࡞͢Δςετ

  52. ϓϩδΣΫτΛ੡࡞͢Δςετ

  53. Ձ஋্͕͕Δ·Ͱɺ ൓෮͢Δ ໰୊ͳ͘ಈ͍͍ͯͯɺ ܧଓతʹग़ՙͯ͠ ՝୊Λ׬ྃͯ͠ɺ ։ൃϕϩγςΟ ΑΓྑ͍ιϑτ΢ΤΞΛग़ՙ͢Δ Agile + GIT

    / CI / CD + Metrics
  54. Stay lean, stay loveable

  55. as is a Service Software

  56. People are the product / service

  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.
  59. None
  60. ͋Γ͕ͱ͏͍͟͝·͢ Jଜ • ϓϦϯγύϧϓϩμΫτϚωʔδϟʔ • ΞτϥγΞϯ • @JASEWONG