In the software development domain we quite often need to engage a diverse range of professionals to achieve a successful outcome. To begin with, software development implementations involve not just the soft side of developing software but, quite often, have a significant hardware and infrastructure components involved as well.
One of the issues associated with having such a diverse set of project resources is that quite often these resources, being highly technical by their very nature (both personally and professionally) seem to forget (or more correctly ‘not remember’) why is it that they are doing what are supposed to be doing. In other words, they fail to relate back to the project’s vision.
I’ve referred in an earlier post to the concept of “Commander’s Intent“. I have been having a growing sensation, in recent times, that many of the people working on mine and other related projects lack the understanding or appreciation of the ‘Commander’s Intent’.
So what does it actually mean to be conscientious of the ‘Commander’s Intent’?
- Design and technical solutions should be set support the vision and not to justify the technical capability of the organization
- Any decision made should pass the “is this cost-effective given what we are trying to achieve?” test
So, does your team, your WHOLE team, have a 50/50 understanding of the vision?
Think about it!