Just like many developers like pair programming, I like to pair in my role as a change agent. And when you think about it, most of the benefits from pair programming are not related to programming specifically.
In part one I touched briefly on plans and forecasts. In this post about customer focus and flow for the PMO i come back to them.
Flow: don’t work in the system, work on the system
In our PMO we had plans covering about three to 15 months: there were high-level milestone plans, mid-level milestone plans and low-level detailed milestone plans.