How will you know something will solve your problem if you are not even sure what your problem is:
- Is it lack of specs and vision? Maybe you really never specified what you wanted to do, so all sorts of random things are getting done?
- Scope - did you scope the project so that it has a chance of getting done on time with the resources you have?
- Talent - do you have a bunch of asp.net programmers trying to write kernel code or vice versa :)
- Managing change - did new things happen to which you have to react?
- Learning from mistakes - did you ever have a honest post mortem? Did you learn something from it?
How the heck will any of the above problems get solved by following a different process or by asking for status mails more frequently?
1 comment:
Absolutely! We have a tool which is under development for the past one year - its fairly basic tool but its development suffers from most of the problem you have mentioned.
1.Specs were never spelt out clearly - so everyone is trying to make it do what they want.
2. The developer doesn't either plan or communicate to the client (i.e. us) how long each feature is going to take to implement and test.
3. Lots of things have changed since inception and they are just being patched up.
4. There is no post mortem or project tracking
Post a Comment