Tweet
Tweet

Slide 1

Slide 1 text

SUPPORTING TEAMS
 WHEN THE TECH IS UNKNOWN @emmajanehw www.gitforteams.com

Slide 2

Slide 2 text

AGENDA • Define the underlying purpose • Scope out the challenge you’re facing • Plan (and pace) sprints • Maintain focus and motivation

Slide 3

Slide 3 text

FRAMING
 THE CHANGE Yeah... but why?

Slide 4

Slide 4 text

Change management is
 a business approach to transitioning
 individuals, teams, and organisations
 to a desired future state. Organisational change

Slide 5

Slide 5 text

Urgency Assemble Enlist Vision Enable Generate Wins Sustain Corp. Culture 8-STEP PROCESS FOR LEADING CHANGE http://www.kotterinternational.com/the-8-step-process-for-leading-change/

Slide 6

Slide 6 text

Urgency Assemble Enlist Vision Enable Generate Wins Sustain Corp. Culture 8-STEP PROCESS FOR LEADING CHANGE http://www.kotterinternational.com/the-8-step-process-for-leading-change/

Slide 7

Slide 7 text

Simon Sinek "Average companies give their people something to work on. 
 “In contrast, the most innovative organisations give their people something to work toward."

Slide 8

Slide 8 text

PLAN TO DEAL WITH EMOTIONS Denial Anger Bargaining Depression Acceptance Kubler-Ross's five stages of grief

Slide 9

Slide 9 text

Simon Sinek “People who come to work with a clear sense of WHY are less prone to giving up after a few failures because they understand the higher cause.”

Slide 10

Slide 10 text

REWARDS & RISKS Expose fears and hesitations with the change. Allows team to uncover motivators that will keep people engaged throughout the project. Name, and explicitly plan for the biggest risk factors in the project. If not managed, can surface differences between team members that are difficult to recover from. Define Your Why.

Slide 11

Slide 11 text

ENSURING SUCCESS 1. Define scope. 2. Plan (and pace) sprints. 3. Maintain focus and motivation.

Slide 12

Slide 12 text

DEFINING THE SCOPE OF WORK What are we going to do?

Slide 13

Slide 13 text

REWARDS & RISKS Allows you to identify and name project gremlins. Allows you to get a read on how / when stakeholders want to be involved in the project. Allows you to start the idea of a “won’t build” list. Define Scope Can cause tensions if stakeholder thinks you’re trying to avoid work with the “won’t build” list.

Slide 14

Slide 14 text

RADICALLY TRANSPARENT PLANNING ARTEFACTS • Inception Deck. • User Story Map. • Project Approach Document. • Epics / Backlog • The “Won’t Build” List.

Slide 15

Slide 15 text

https://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

Slide 16

Slide 16 text

https://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

Slide 17

Slide 17 text

https://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

Slide 18

Slide 18 text

https://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

Slide 19

Slide 19 text

https://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

Source: http://winnipegagilist.blogspot.co.uk/2012/03/how-to-create-user-story-map.html More: http://agileproductdesign.com/ Book: User Story Mapping (http://shop.oreilly.com/product/0636920033851.do)

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

PLAN THE SPRINTS; SPRINT THE PLAN. When are we going to do it?

Slide 24

Slide 24 text

REWARDS & RISKS Allows team to understand the scaffolding they should put in place for features they’ll build. Place “hard” tasks when team is likely to be most engaged (e.g., consider holidays). Build in capacity for iteration; plan to replace elements with increasingly more complex code. Plan your project If your plan is too rigid, you start getting into waterfall-style promises.

Slide 25

Slide 25 text

A PROJECT IS A MARATHON

Slide 26

Slide 26 text

A PROJECT IS A MARATHON Pace sprints to be increasingly difficult with periodic rest weeks.

Slide 27

Slide 27 text

A PROJECT IS A MARATHON Pace sprints to be increasingly difficult with periodic rest weeks.

Slide 28

Slide 28 text

MITIGATE THE LEARNING CURVE

Slide 29

Slide 29 text

MITIGATE THE LEARNING CURVE • Plan and review:
 technical review board. • Allow fluid scheduling:
 Kanban-style pull, not push-based Scrum. • Share learning often:
 demo -> Q&A.

Slide 30

Slide 30 text

Difficulty of Task (amount of new knowledge required) easier tasks Time easier tasks taper as you get ready for initial release INCORPORATING LEARNING INTO SPRINT PLANNING

Slide 31

Slide 31 text

Difficulty of Task (amount of new knowledge required) easier tasks Time easier tasks taper as you get ready for initial release INCORPORATING LEARNING INTO SPRINT PLANNING

Slide 32

Slide 32 text

LEAVE ROOM FOR UNEXPECTED DELIGHTS.

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

MAINTAINING MOMENTUM Are we almost there yet?

Slide 36

Slide 36 text

REWARDS & RISKS Getting to know your stakeholders means you can mitigate their impact on the developers. Getting to know your developers allows you to pace the project with more grace. Know your team Seeing today’s capacity might make you hesitant to push the team to do better tomorrow. It’s time consuming,
 and if you stop it will be noticed.

Slide 37

Slide 37 text

MOTIVATE ME:
 WHISK(E)Y NOT REQUIRED

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

MOTIVATE

Slide 43

Slide 43 text

MOTIVATE • Ask the team what motivates them. • Give choice. • Have high standards
 which allow for creative solutions. • Celebrate wins.

Slide 44

Slide 44 text

RESOURCES Managing Change
 http://gitforteams.com/resources/change-management.html A Developer’s Primer To Managing Developers
 https://austin2014.drupal.org/session/developers-primer-managing-developers.html Things I Learned From Managing My First Project
 https://drupalize.me/blog/201312/things-i-learned-managing-my-first-project