Be the first to like this
When a project is born, the battle for power and control begins … over specifications, stakeholders, vendor selection, goals, technology, budget, etc. Power and control, by themselves, are a poor strategy. Control is linear thinking.
Reality, the space where projects happen, is a big ball of wibbly-wobbly timey-wimey stuff where all the best laid schemes of mice and men often go awry. When they do, reality refuses to bow down to power.
Control is man-made power. Strategy is real power. The power to chose, limit and prioritize while allowing for collaborative creativity and shared vision. Yes, strategy (often) defines what needs doing, thinking about, focusing on, and avoiding. But the goal of the work is to shine a light down the straightforward path, or paths, through the complexity while honoring, even savoring, the complexity itself.
Strategy is hard, very hard, to do well. The rules are easy. When applied to software development, strategy is an engineering process sometimes called solution architecture. There are four elements of good strategy:
1. Telling the truth insightfully
2. Defining measurable prioritized goals
3. Overcoming hidden obstacles implicitly
4. Creating a construct, the architecture itself, in the form of a document
Getting a process back on track when it's gone awry is also essential to a good strategy. This session talks about strategy in general and for a Drupal project specifically.