This is my knowledge management view of the business coach role. There are things we know and things we do not know. "A" represents stuff that we do not know we do not know (We do not know what question to ask). "B" is stuff that we know that we do not know (We know the question but not the answer). "C" is stuff that we know (We know the answer).
When we know something, it is a matter of transfering that knowledge to the developers on the project. This knowledge transfer is traditionally done using documentation. The Agile Business Coach will use whatever teaching/coaching aid necessary to transfer the knowledge. From experience documentation is the worst way to do this and face to face coaching at a whiteboard is the best way.
Issue resolution allows us to find the answer to the question.
Learning which uses the traditional analysis tools allows us to form the question. From my experience, using analysis tools ( Object models drawn on paper) is best performed in pairs. At Dresdner Kleinwort Wasserstein we called this eXtreme Analysis or Pair Analysis.
