You can't become agile by taking a class,
and I'm speaking as someone teaches classes!
Don't get me wrong, training is critical, but it's not enough.
At the executive level:
- you need to learn to think in a lean/agile way.
Lean businesses approach business development differently.
- you need to establish a culture in which lean/agile can flourish.
- you need to know how to support the new process.
Your existing company is organized to support the old way of doing things.
That has to change.
- you need to plan in a different way, focusing on priority and business value, not time.
At the developer (programmer, tester, UX, operations) level:
- you need to integegrate new practices into your day-to-day work.
- you need to learn to work collaboratively.
- you need to learn how to work iteratively, even at the design level.
- you need to learn how to manage yourself.
- if you have a legacy system, you need to refactor it to accommodate the stresses of agile development.
Sample Consulting Engagements
- Introduce agile into your organization. Typically
a mix of classes and roll-up-the-sleeves work with the
teams. What better way to learn agile techinques than to actually
use them to do real work.
- Improve your agility by looking at how the
teams work and suggesting improvements.
- Meet with executives and key stakeholders and:
- learn what agile is and how it impacts governance.
- discuss successful adoption.
- learn how to plan in an agile way.
- help initiate the transition
- make occasional assessments and help with on-course corrections.
- Help with hiring at all levels from engineering to executives.
- Help develop your first few stories.
- Work one-on-one with team members.
- Work through the first few iterations with the development teams.
- Help you transition your legacy system to an agile-friendly architecture.
- Help you develop an agile-friendly architecture from scratch.
- Help integrate agile development into operations.
- Conduct a retrospective and tweak process.