This applies to technology (software) programmes, even the implementation of pre-pack solutions like OBIA!
For the manager, it's important to understand the RELATIVE impact of software development challenges, when you're delivering solutions driven by software. Why the problem is easy or why it is hard, has a profound impact on programme planning and budgets.
This can greatly increase cost for enterprise programmes, increasing the cash burn rate. For a start up, getting this wrong can be fatal!
Modern day project management methodologies must shoulder some of the blame for producing the pure 'Microsoft Project jockey', but the better manager develops a certain curiosity for software solutions that makes them more able to anticipate difficulties ahead.
As a non-technical manager in these situations, a level of questioning for your development staff is crucial. Try not to make the questioning static, like the real exchange I had recently with a client below:
Manager: That looks technical, what are you doing?
Developer: I'm re-purposing the scripts so they work in both non-clustered and clustered environments!
Manager: That's not something I can help you with, sorry.
Developer: Err... no I guess not!
Questions should be designed to tease out why certain tasks in the solution are important and how they contribute to the overall solution. A better set of questions might have been:
Manager: I understand you're working on X, is that what you're doing just there?
Developer: Not X just now, I'm working on re-purposing the scripts so they work in both clustered and non-clustered environments.
Manager: OK, I'm a little unfamiliar with that work. It sounds important, perhaps you can tell me more about the implications of this?
Developer: Sure... BLAH BLAH BLAH
This level of questioning is extremely important for good project (programme) management!
Once the manager becomes confused by technical complexity, however, they revert to questioning the validity of technical tasks in a plan (solution). This level of questioning can be a waste of time!
As a non-technical manager (read start up CEO working with technical staff), keep in mind what are you trying to achieve by asking these questions...
- enough understanding of the challenges in your project (programme)
- a greater appreciation of the capabilities of your technical staff
- greater control of cost
Recognise, however, once technical aspects become unclear this makes them NO LESS valid. Better developers will have some understanding of the planning and costs you're trying to control.
Keep your questioning open and you'll gain the trust of your developers!
I write a blog under the pseudonym DR. OBI. Feel free to get in touch with me about your programme. You can find me here Justin Townsend.
