Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Change Needs Management

Change Needs Management

For over a decade Emma Jane Hogbin Westby has been teaching people how to use version control systems. Most people she's encountered still find Git hard to learn on their own. In this session you will learn why most approaches to teaching Git fail to appropriately address the adult learner, and what you can do to make the on-boarding experience easier for others. She will touch on adult education best practices, and also share the secrets that make it easier for very large (and corporate) teams to transition to Git.

Emma Jane Hogbin Westby

April 05, 2016
Tweet

More Decks by Emma Jane Hogbin Westby

Other Decks in Technology

Transcript

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

    View Slide

  2. CHANGE NEEDS MANAGEMENT
    • Learn how adults learn.
    • Become an effective mentor.
    • Value the difficulty of trivial change.

    View Slide

  3. CHANGE NEEDS MANAGEMENT
    • Learn how adults learn.
    • Become an effective mentor.
    • Value the difficulty of trivial change.

    View Slide

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

    View Slide

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

    View Slide

  6. THE “HELLO WORLD”

    FOR GIT WORKSHOPS
    $ git init
    $ touch file
    $ git add .
    $ git commit -m ‘First!’

    View Slide

  7. CONSTRUCTIVISM
    Piaget, Papert, Montessori

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  12. EH?

    View Slide

  13. THE “HELLO WORLD”

    FOR GIT WORKSHOPS
    $ git init
    $ touch file
    $ git add .
    $ git commit -m ‘First!’

    View Slide

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

    View Slide

  15. An interesting fact does not result in
    the ability to analyse, evaluate,

    or create an effective outcome.

    View Slide

  16. CHANGE NEEDS MANAGEMENT
    • Learn how adults learn.
    • Become an effective mentor.
    • Value the difficulty of trivial change.

    View Slide

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

    View Slide

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

    View Slide

  19. View Slide

  20. START WITH WHOLE,
    REAL PROBLEMS.

    View Slide

  21. Sample lesson

    View Slide

  22. 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

    View Slide

  23. 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.

    View Slide

  24. What are your tools and restraints?
    Often there are other things we need to fit into our workflow. 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”

    View Slide

  25. I tricked you.
    Now you’ve got a cheat sheet of topics to put into

    your diagrams and your documentation.

    View Slide

  26. Sketch out your workflow
    • Identify the roles on your team.

    • Identify the relationships between the team members.

    • Draw arrows to show how code flows between team members.

    View Slide

  27. View Slide

  28. View Slide

  29. View Slide

  30. View Slide

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

    View Slide

  32. 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.

    View Slide

  33. PEDAGOGY OF
    THE OPPRESSED
    Paulo Freire

    View Slide

  34. CHANGE NEEDS MANAGEMENT
    • Learn how adults learn.
    • Become an effective mentor.
    • Value the difficulty of trivial change.

    View Slide

  35. View Slide

  36. Change management is

    a business approach to transitioning

    individuals, teams, and organisations

    to a desired future state.
    Organisational change

    View Slide

  37. 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/

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  41. -- 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.”

    View Slide

  42. CHANGE NEEDS MANAGEMENT
    • Learn how adults learn.
    • Become an effective mentor.
    • Value the difficulty of trivial change.

    View Slide

  43. @emmajanehw
    www.gitforteams.com

    View Slide