Technical Agile Coaching with the Samman method

Foreword

Introduction

1. Samman Technical Coaching
2. Why would an organization engage in Samman Technical Coaching?
3. Why would you choose to coach using the Samman method?
4. Elevator pitch for Samman Technical Coaching
5. What is in this book
6. How this book relates to my other books
7. Acknowledgments

The purpose of Samman Coaching

1. Development techniques
2. Levelling up a whole team together
3. Expected outcomes
4. Part 1: Ensemble Working

Ensemble Primer

1. Typist
2. Navigator
3. Team-members
4. Group Discussions
5. Facilitator
6. Rotating roles
7. Other ensemble roles
8. The Coach role

Let the Ensemble give you Superpowers

1. Everyone understands the code
2. Skills are multiplied
3. Visitors are quickly contributors
4. Joining a smoothly functioning ensemble
5. A Coach is a Visitor with an Agenda

Coaching Behaviours in an Ensemble

1. Teach
2. Mentor
3. Facilitate
4. Coach
5. Observe
6. Take Short Breaks
7. Retrospect
8. Breathing space between and during sessions

Kindness, Consideration and Respect

1. Woody’s Legacy Code rule
2. Yes, and
3. Take time out
4. Too much thinking at the keyboard
5. I think <name> has a good idea we should listen to
6. Consideration means paying attention
7. Call out bad behaviour that can’t wait until the retrospective

Coaching Situations Illustrated with Stories

1. What should we do now?
2. Team, help your navigator
3. Can we do an experiment?
4. Discover scenarios
5. Intention, Location, Details
6. Reminder to test first
7. Typist, use your shortcuts
8. Consume-First Design
9. How long is it since we saw feedback?
10. How long is it since we made a commit?
11. Only one person knows what’s going on
12. Nobody knows what is going on
13. Chapter Summary

Retrospectives

1. Ask for Observations
2. “Liked, Learned, Lacked” Observations
3. Turn up the good
4. Your private retrospective
5. Retrospective skills are essential

Remote Ensembles

1. Seeing people’s faces
2. Be considerate and time your comments
3. Take breaks
4. Make it quick to change typist
5. Typist lag is deadly
6. Design discussions
7. Retrospectives
8. Part 2: Learning Hours

Explaining Why you should hold a Learning Hour

1. Learning TDD is like learning to ski²
2. Why should you spend a whole hour every day on learning?
3. Who should come to the Learning Hour?

The Theory and Practice of Teaching and Learning

1. Learning Outcomes and Objectives
2. The ‘4C’ learning model
3. Design learning experiences that fit with how the brain works
4. Deliberate Practice

Sample Learning Hours

1. 1. Incremental working, Driven by Tests
2. 2. Selecting and ordering test cases
3. 3. Golden Rule of TDD
4. 4. Names of Refactorings, especially ‘Extract Function’
5. 5. Misconceptions about Refactoring
6. 6. Make a test list
7. 7. Arrange - Act - Assert
8. 8. Start with the Assertion
9. 9. One function at a time
10. 10. Inspirational Demo

Learning Topics

1. Small steps
2. Refactoring safely
3. Legacy Code
4. Testable Design
5. Designing Tests
6. Behaviour-Driven Development
7. Agile
8. Add your own ideas

Remote Learning Hours

1. Cyber-dojo
2. VNC
3. Everyone uses their local machine and screenshares
4. Retrospectives
5. Part 3: Samman Coaching Engagements

Finding an Organization and Teams to Engage with

1. Sales and Marketing principles
2. The Coaching Proposal
3. Proposal for a large organzation with hundreds of teams
4. Closing the Deal
5. Identify your sponsor

Beginning Coaching with a New Organization

1. Present yourself
2. Kick-off Workshop with each team
3. Chartering Workshop
4. Offer Samman Coaching
5. Persuading Reluctant Teams to be Coached

Practicalities Before Coaching Begins

1. When should we hold the coaching?
2. What task should we work on in the ensemble?
3. What physical space should we use for ensemble working?
4. Should we use a branch for the code we write in an ensemble?

Turn Up the Good

1. Decide on the next coaching
2. Enquire about bringing in a visiting coach or two
3. Networking
4. Days Spent Away from the Teams

A Career as a Samman Technical Coach

1. Pair Coaching in a larger organization
2. A Visiting Coach Programme
3. Preparing for a Technical Coaching Career
4. How I became a Technical Coach

Final Thoughts

1. What is the most important thing to remember?
2. Where can I find out more?

References

1. Working incrementally in small steps
2. Refactoring safely
3. Legacy Code
4. Testable Design
5. Designing Tests
6. Behaviour-Driven Development
7. Teaching
8. Other
9. Image attributions