ZOMG I'm Leading a Project - Velocity 2019

Slide 1

Slide 1 text

@maltzj 1

Slide 2

Slide 2 text

@maltzj 2

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

@maltzj 5

Slide 6

Slide 6 text

@maltzj 6 When leading a project, everything changes

Slide 7

Slide 7 text

@maltzj Jonathan Maltz @maltzj 06-13-19 AUTHOR DATE ZOMG I'm Leading A Project

Slide 8

Slide 8 text

@maltzj 8

Slide 9

Slide 9 text

@maltzj 9 Different Names in Different Places

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

@maltzj ● Accountable for project being successful Responsibilities 11

Slide 12

Slide 12 text

@maltzj ● Accountable for project being successful ● Deciding on a project plan Responsibilities 12

Slide 13

Slide 13 text

@maltzj ● Accountable for project being successful ● Deciding on a project plan ● Prioritizing work for delivery Responsibilities 13

Slide 14

Slide 14 text

@maltzj 14

Slide 15

Slide 15 text

@maltzj 15 Before

Slide 16

Slide 16 text

@maltzj 16 You

Slide 17

Slide 17 text

@maltzj 17 You Engineering Manager Are you happy?

Slide 18

Slide 18 text

@maltzj 18 You Engineering Manager Are you happy? Project Lead Here are the priorities

Slide 19

Slide 19 text

@maltzj 19 After

Slide 20

Slide 20 text

@maltzj 20 You

Slide 21

Slide 21 text

@maltzj 21 You Engineer 1 Engineer 2 Engineer 2

Slide 22

Slide 22 text

@maltzj 22 You Engineer 1 Engineer 2 Engineer 2 What should we do next? What should we do next? What should we do next?

Slide 23

Slide 23 text

@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?

Slide 24

Slide 24 text

@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?

Slide 25

Slide 25 text

@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?

Slide 26

Slide 26 text

@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?

Slide 27

Slide 27 text

@maltzj @maltzj Getting Started

Slide 28

Slide 28 text

@maltzj 28 Write a design document

Slide 29

Slide 29 text

@maltzj 29 Write a design document, with milestones

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

@maltzj 31 "I never write a design document without knowing it will get signed off"

Slide 32

Slide 32 text

@maltzj Gather Requirements GETTING STARTED 1

Slide 33

Slide 33 text

@maltzj ● What does your product owner want to build? 4 Key Questions 33

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

@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

Slide 36

Slide 36 text

@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

Slide 37

Slide 37 text

@maltzj 37 Importance Difﬁculty/Risk

Slide 38

Slide 38 text

@maltzj 38 Importance Difﬁculty/Risk

Slide 39

Slide 39 text

@maltzj 39 "{Feature} seems like it will be hard, can we do that as a follow-up"

Slide 40

Slide 40 text

@maltzj Build a Skeleton GETTING STARTED 2

Slide 41

Slide 41 text

@maltzj 41

Slide 42

Slide 42 text

@maltzj 42

Slide 43

Slide 43 text

@maltzj 43 Solution Exploring

Slide 44

Slide 44 text

@maltzj 44 "So I'm trying to ﬁgure out {problem}, can we talk about approaches"

Slide 45

Slide 45 text

@maltzj 45 Fewer people

Slide 46

Slide 46 text

@maltzj 46 Fewer people: Less conﬁdence in decision, quicker

Slide 47

Slide 47 text

@maltzj 47 Fewer people: Less conﬁdence in decision, quicker More people

Slide 48

Slide 48 text

@maltzj 48 Fewer people: Less conﬁdence in decision, quicker More people: More conﬁdence in decision, takes longer

Slide 49

Slide 49 text

@maltzj ● Your team lead ● Experts on any affected systems ● One/Two People on the Project At A Minimum 49

Slide 50

Slide 50 text

@maltzj 50 Solution Exploring Solution Deciding

Slide 51

Slide 51 text

@maltzj Deﬁne Milestones GETTING STARTED 3

Slide 52

Slide 52 text

@maltzj 52 Shippable Chunks

Slide 53

Slide 53 text

@maltzj 53 Importance Difﬁculty/Risk

Slide 54

Slide 54 text

@maltzj 54 Importance Difﬁculty/Risk

Slide 55

Slide 55 text

@maltzj 55 Unblock Future Work

Slide 56

Slide 56 text

@maltzj Get Sign-Off GETTING STARTED 4

Slide 57

Slide 57 text

@maltzj 57 Consent vs. Consensus

Slide 58

Slide 58 text

@maltzj 58 Sign-off Meetings!

Slide 59

Slide 59 text

@maltzj Kick-off GETTING STARTED 5

Slide 60

Slide 60 text

@maltzj @maltzj Execution

Slide 61

Slide 61 text

@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?

Slide 62

Slide 62 text

@maltzj 62 Goal #1: Answer all these questions

Slide 63

Slide 63 text

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

Slide 64

Slide 64 text

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

Slide 65

Slide 65 text

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

Slide 66

Slide 66 text

@maltzj 66 Task Management

Slide 67

Slide 67 text

@maltzj ● All work is in your task tracker Task Management 67

Slide 68

Slide 68 text

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

Slide 69

Slide 69 text

@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

Slide 70

Slide 70 text

@maltzj 70 Task Breakdown

Slide 71

Slide 71 text

@maltzj 71 Meetings

Slide 72

Slide 72 text

@maltzj ● Daily standups (sync or async) Meetings 72

Slide 73

Slide 73 text

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

Slide 74

Slide 74 text

@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

Slide 75

Slide 75 text

@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

Slide 76

Slide 76 text

@maltzj 76

Slide 77

Slide 77 text

@maltzj ● Confusion about what to work on next Failure modes 77

Slide 78

Slide 78 text

@maltzj ● Confusion about what to work on next ○ Have you prioritized your backlog well enough? Failure modes 78

Slide 79

Slide 79 text

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

Slide 80

Slide 80 text

@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

Slide 81

Slide 81 text

@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