ZOMG I'm Leading a Project - Velocity 2019

C7393b7ba7ec9c8890dd77d209fbb3c9?s=47 maltzj
June 12, 2019

ZOMG I'm Leading a Project - Velocity 2019

C7393b7ba7ec9c8890dd77d209fbb3c9?s=128

maltzj

June 12, 2019
Tweet

Transcript

  1. @maltzj 1

  2. @maltzj 2

  3. @maltzj 3 1. Write code 2. Review code 3. Write

    JIRA tickets
  4. @maltzj 4 1. Write JIRA tickets 2. Review code 3.

    Write code
  5. @maltzj 5

  6. @maltzj 6 When leading a project, everything changes

  7. @maltzj Jonathan Maltz @maltzj 06-13-19 AUTHOR DATE ZOMG I'm Leading

    A Project
  8. @maltzj 8

  9. @maltzj 9 Different Names in Different Places

  10. @maltzj 10 Deliver on time, with a high bar, without

    people quitting
  11. @maltzj • Accountable for project being successful Responsibilities 11

  12. @maltzj • Accountable for project being successful • Deciding on

    a project plan Responsibilities 12
  13. @maltzj • Accountable for project being successful • Deciding on

    a project plan • Prioritizing work for delivery Responsibilities 13
  14. @maltzj 14

  15. @maltzj 15 Before

  16. @maltzj 16 You

  17. @maltzj 17 You Engineering Manager Are you happy?

  18. @maltzj 18 You Engineering Manager Are you happy? Project Lead

    Here are the priorities
  19. @maltzj 19 After

  20. @maltzj 20 You

  21. @maltzj 21 You Engineer 1 Engineer 2 Engineer 2

  22. @maltzj 22 You Engineer 1 Engineer 2 Engineer 2 What

    should we do next? What should we do next? What should we do next?
  23. @maltzj 23 You Engineer 1 Engineer 2 Engineer 2 Team

    Lead What should we do next? Is your technical bar high? What should we do next? What should we do next?
  24. @maltzj 24 You Engineering Manager Engineer 1 Engineer 2 Engineer

    2 Team Lead What should we do next? Is your technical bar high? Are you being fair? What should we do next? What should we do next?
  25. @maltzj 25 You Engineering Manager Engineer 1 Engineer 2 Engineer

    2 Team Lead What should we do next? Is your technical bar high? Are you being fair? What should we do next? What should we do next? Product Manager Can we get it sooner?
  26. @maltzj 26 You Engineering Manager Engineer 1 Engineer 2 Engineer

    2 Team Lead What should we do next? Is your technical bar high? Are you being fair? What should we do next? What should we do next? Product Manager Can we get it sooner? Other Project Leads Can you unblock us?
  27. @maltzj @maltzj Getting Started

  28. @maltzj 28 Write a design document

  29. @maltzj 29 Write a design document, with milestones

  30. @maltzj 30 Write a design document, with milestones, and relevant

    signoffs
  31. @maltzj 31 "I never write a design document without knowing

    it will get signed off"
  32. @maltzj Gather Requirements GETTING STARTED 1

  33. @maltzj • What does your product owner want to build?

    4 Key Questions 33
  34. @maltzj • What does your product owner want to build?

    • Why do they want it built? 4 Key Questions 34
  35. @maltzj • What does your product owner want to build?

    • Why do they want it built? • What's the core of this feature? 4 Key Questions 35
  36. @maltzj • What does your product owner want to build?

    • Why do they want it built? • What's the core of this feature? • What's less important? 4 Key Questions 36
  37. @maltzj 37 Importance Difficulty/Risk

  38. @maltzj 38 Importance Difficulty/Risk

  39. @maltzj 39 "{Feature} seems like it will be hard, can

    we do that as a follow-up"
  40. @maltzj Build a Skeleton GETTING STARTED 2

  41. @maltzj 41

  42. @maltzj 42

  43. @maltzj 43 Solution Exploring

  44. @maltzj 44 "So I'm trying to figure out {problem}, can

    we talk about approaches"
  45. @maltzj 45 Fewer people

  46. @maltzj 46 Fewer people: Less confidence in decision, quicker

  47. @maltzj 47 Fewer people: Less confidence in decision, quicker More

    people
  48. @maltzj 48 Fewer people: Less confidence in decision, quicker More

    people: More confidence in decision, takes longer
  49. @maltzj • Your team lead • Experts on any affected

    systems • One/Two People on the Project At A Minimum 49
  50. @maltzj 50 Solution Exploring Solution Deciding

  51. @maltzj Define Milestones GETTING STARTED 3

  52. @maltzj 52 Shippable Chunks

  53. @maltzj 53 Importance Difficulty/Risk

  54. @maltzj 54 Importance Difficulty/Risk

  55. @maltzj 55 Unblock Future Work

  56. @maltzj Get Sign-Off GETTING STARTED 4

  57. @maltzj 57 Consent vs. Consensus

  58. @maltzj 58 Sign-off Meetings!

  59. @maltzj Kick-off GETTING STARTED 5

  60. @maltzj @maltzj Execution

  61. @maltzj 61 You Engineering Manager Product Manager Engineer 1 Other

    Project Leads Engineer 2 Engineer 2 Team Lead What should we do next? Is your technical bar high? Can we get it sooner? Are you being fair? Can you unblock us? What should we do next? What should we do next?
  62. @maltzj 62 Goal #1: Answer all these questions

  63. @maltzj 63 Goal #2: Spend as little time as possible

    doing this
  64. @maltzj 64 1. Write JIRA tickets 2. Review code 3.

    Write code
  65. @maltzj 65 1. Manage tasks 2. Review code 3. Write

    code
  66. @maltzj 66 Task Management

  67. @maltzj • All work is in your task tracker Task

    Management 67
  68. @maltzj • All work is in your task tracker •

    Ideally broken down in 1-4 day chunks Task Management 68
  69. @maltzj • All work is in your task tracker •

    Ideally broken down in 1-4 day chunks • In progress/up next/done work is visible Task Management 69
  70. @maltzj 70 Task Breakdown

  71. @maltzj 71 Meetings

  72. @maltzj • Daily standups (sync or async) Meetings 72

  73. @maltzj • Daily standups (sync or async) • 1:1 with

    your product manager every 2 weeks Meetings 73
  74. @maltzj • Daily standups (sync or async) • 1:1 with

    your product manager every 2 weeks • 1:1s with people on your team every 2-3 weeks Meetings 74
  75. @maltzj • Daily standups (sync or async) • 1:1 with

    your product manager every 2 weeks • 1:1s with people on your team every 2-3 weeks • Regular meeting (default 2 weeks) to agree on next priorities Meetings 75
  76. @maltzj 76

  77. @maltzj • Confusion about what to work on next Failure

    modes 77
  78. @maltzj • Confusion about what to work on next ◦

    Have you prioritized your backlog well enough? Failure modes 78
  79. @maltzj • Confusion about what to work on next ◦

    Have you prioritized your backlog well enough? • People are confused about progress Failure modes 79
  80. @maltzj • Confusion about what to work on next ◦

    Have you prioritized your backlog well enough? • People are confused about progress ◦ Are you updating your per-sprint progress? Failure modes 80
  81. @maltzj • Confusion about what to work on next ◦

    Have you prioritized your backlog well enough? • People are confused about progress ◦ Are you updating your per-sprint progress? • Team is working hard but not hitting milestones Failure modes 81
  82. @maltzj • Confusion about what to work on next ◦

    Have you prioritized your backlog well enough? • People are confused about progress ◦ Are you updating your per-sprint progress? • Team is working hard but not hitting milestones ◦ Are you actually doing work on the milestone? ◦ Are you trying to do too many things? Failure modes 82
  83. @maltzj 83 Reviewing Code

  84. @maltzj 84

  85. @maltzj 85

  86. @maltzj 86 Boards + Daily Status

  87. @maltzj 87 Writing Code

  88. @maltzj 88 Enable writing more code

  89. @maltzj 89 Accelerate important areas

  90. @maltzj 90 You'll do this less

  91. @maltzj @maltzj

  92. @maltzj @maltzj 3 Things

  93. @maltzj @maltzj 1. You're responsible for delivering the whole project

  94. @maltzj @maltzj 2. Write a design document with milestones and

    get sign-off
  95. @maltzj @maltzj 3. Manage tasks, review code, then write code

  96. @maltzj https://boards.greenhouse.io/nuna/

  97. @maltzj @maltzj