Change Needs Management

Slide 1

Slide 1 text

CHANGE NEEDS MANAGEMENT Emma Jane Hogbin Westby @emmajanehw www.gitforteams.com

Slide 2

Slide 2 text

CHANGE NEEDS MANAGEMENT • Learn how adults learn. • Become an effective mentor. • Value the difﬁculty of trivial change.

Slide 3

Slide 3 text

CHANGE NEEDS MANAGEMENT • Learn how adults learn. • Become an effective mentor. • Value the difﬁculty of trivial change.

Slide 4

Slide 4 text

“I’VE TRIED! I CAN’T LEARN THIS STUFF.” A typical student in one of my workshops.

Slide 5

Slide 5 text

IT IS HARD TO LEARN. It is harder to learn Git.

Slide 6

Slide 6 text

THE “HELLO WORLD”  FOR GIT WORKSHOPS $ git init $ touch file $ git add . $ git commit -m ‘First!’

Slide 7

Slide 7 text

CONSTRUCTIVISM Piaget, Papert, Montessori

Slide 8

Slide 8 text

BLOOM’S TAXONOMY Source: http://lb.cm/bt Knowledge Work Foundation Skills

Slide 9

Slide 9 text

ANDRAGOGY • Readiness: Want immediate relevance. • Rationale: Reason for learning. • Orientation: problem-based learning. http://en.wikipedia.org/wiki/Andragogy

Slide 10

Slide 10 text

BLOOM’S TAXONOMY (REVISED) Source: http://bit.ly/1CU1gYJ

Slide 11

Slide 11 text

Source: http://bit.ly/1Cn5vsg

Slide 12

Slide 12 text

EH?

Slide 13

Slide 13 text

THE “HELLO WORLD”  FOR GIT WORKSHOPS $ git init $ touch file $ git add . $ git commit -m ‘First!’

Slide 14

Slide 14 text

“Please memorise all Git commands and use only rebasing when merging your work.” -- No one, ever

Slide 15

Slide 15 text

An interesting fact does not result in the ability to analyse, evaluate,  or create an effective outcome.

Slide 16

Slide 16 text

CHANGE NEEDS MANAGEMENT • Learn how adults learn. • Become an effective mentor. • Value the difﬁculty of trivial change.

Slide 17

Slide 17 text

ANTI-PATTERNS • “It’s easy!” • “It’s just a directed acyclic graph!” • “You should use rebasing.” • “Don’t ____. It’s really dangerous.”

Slide 18

Slide 18 text

DON’T TEACH SOFTWARE; TEACH TEAM WORK. Git Shell, cross- platform

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

START WITH WHOLE, REAL PROBLEMS.

Slide 21

Slide 21 text

Sample lesson

Slide 22

Slide 22 text

Who is on your code team? Write down a list of all of the people on your code team. This list may include: • developers • designers • project managers • clients

Slide 23

Slide 23 text

What do you do? Write a list of all the tasks you work on. This might include: • Writing code. • Reviewing code. • Pushing tested code to the server. • Fixing broken code.

Slide 24

Slide 24 text

What are your tools and restraints? Often there are other things we need to ﬁt into our workﬂow. Create a third list of any tools and constraints you are aware of. This list might include: • Code hosting system (Bitbucket, GitHub, self-hosted) • Server ecosystem (dev / staging / live) • Automated testing systems or review “gates”

Slide 25

Slide 25 text

I tricked you. Now you’ve got a cheat sheet of topics to put into  your diagrams and your documentation.

Slide 26

Slide 26 text

Sketch out your workﬂow • Identify the roles on your team. • Identify the relationships between the team members. • Draw arrows to show how code ﬂows between team members.

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

Learn a visual language. https://github.com/gitforteams/diagrams

Slide 32

Slide 32 text

BECOME AN EFFECTIVE MENTOR. • Have learners “build” their knowledge by applying their own expert knowledge about their team to a diagram. • Teach people to talk about their work flow. • Once the learner can describe their own situation, bridge them into new scenarios.

Slide 33

Slide 33 text

PEDAGOGY OF THE OPPRESSED Paulo Freire

Slide 34

Slide 34 text

CHANGE NEEDS MANAGEMENT • Learn how adults learn. • Become an effective mentor. • Value the difﬁculty of trivial change.

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

Urgency Core Team Get  Volunteers Vision Enable Action Generate Wins Sustain Codify 8-STEP PROCESS FOR LEADING CHANGE http://www.kotterinternational.com/the-8-step-process-for-leading-change/

Slide 38

Slide 38 text

PLAN TO DEAL WITH GRIEF Denial Anger Bargaining Depression Acceptance Kubler-Ross's ﬁve stages of grief

Slide 39

Slide 39 text

If you want to go fast, go alone. If you want to go far, go together.

Slide 40

Slide 40 text

MOTIVATE • Ask the team what motivates them. • Give choice. • Leave room for excellent, creative solutions. • Celebrate wins.

Slide 41

Slide 41 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 42

Slide 42 text

CHANGE NEEDS MANAGEMENT • Learn how adults learn. • Become an effective mentor. • Value the difﬁculty of trivial change.

Slide 43

Slide 43 text

@emmajanehw www.gitforteams.com