Monday, April 2, 2012

So what is "agile coaching" for me?

I recently chatted with @flowchainsensei about his blog post:  Bob referred to Liz's article about agile coaching: which is totally different what I do for my clients as an "agile coach":

  • Setting up teams
  • Conflict resolution
  • Team dynamics
  • Pair programming tests, teaching TDD
  • Facilitating retrospectives, daily scrums, plannings etc.
  • Getting task board up and running, introducing WIP limits etc.
  • Helping them to get CI working, continuous delivery
  • How to steer agile software development
  • How to setup and nurture collaboration
  • How to transform the organization towards the goal
  • Doing more with less managers (by improving the system)
  • Setting goals
  • Improving transparency
  • Fixing incentives
  • Understanding and managing the system
  • Value stream mapping
  • Visualizing the system, making it manageable
Product development:
  • Discovering new business models with the help of business model canvas and customer development
  • Improving the learning cycle (ie. lean startup)
  • Agile contracts and RFQ-processes
  • How to choose the subcontractor
  • How to manage the subcontracting deal, how to obtain transparency
  • Business process modeling, figuring out what should be built
  • Getting the project delivered in agile fashion
Trainings (various topics)

  • International gaming company improved time-to-market from 24 months to 3 months
  • Startup discovered and validated a new business model in 2 months
  • Software product company saved 1,3 Meur / year in management and administration
  • Software buyer got the system 4 times faster than expected and secured business for next 2 years
  • ...

I guess that in the end I do not know a title describing what I do. For now I respond to questions like "what do you?" by just simply stating the benefits I am able to bring to my customers.

Picture credits axlape

No comments: