November 24th, 2009 | 
Author: These mistakes cost time, green or, in the worst case, entire projects. Here are 7 universal, but easily avoidable mistakes that make a software project disaster very nearly a guaranteed to be successful:
?1: paying no attention to the human factor of a project. This is where the single biggest step forward in project process success rates is happening yet millions of professionals are still shocked to find out.
?2: paying no attention to management training can substantially damage your software process. Observing it can help your team deliver quality software on time and on budget – time and time again.
?3: relying on that software architecture should or even can drive a project. This is a catastrophic mistake. Software architecture is a medium where business vision is realized. The reverse is also true. When management team is unsuccessful in understanding the core architecture principles – they make ineffective decisions or have no choice but to abdicate control to their technical team – just to see their vision distorted in translation.
?4: Believing that someone can endow with capable and creative software developers for your project. The truth is – you have do your own recruitment to get best results. Most recruiters do nothing except reading resumes and asking candidates about their years of experience.
?5: relying on that simply asking your candidates a bunch of technical and behavioural questions make a good interview. Not only this “spontaneous” approach is unreliable – it makes you spend many hours you could’ve used for project delivery.
?6: taking no notice of the most common ways requirements management kills projects and what teams can do about it. The key here is having the whole team understand them. Not only developers and architects but also the management team need to become knowledgeable about the core principles of requirement management and its biggest pitfalls.
?7: taking no notice of the biggest application software development disaster and its effects that sap the foundations of any methodology. The biggest disaster is not the lack of methodology or an unresolved technology issue. The biggest threat – once again – comes from the human factor of software development, people’s believes and feelings. Project teams need to understand its warning signs and have their act together.
Now when you know the missteps, how many of them are you making? Do you need help improving your software design? Is your software development effort on track? Be sure to consider management training before you run out of time.
The answers to this and other questions about software design, software development and web software design you can find in our sites.
Posted in 
Tags: 