Now that recession became reality, software development professionals must show their best game every time - just to keep their jobs. They also need to learn some new techniques if they planning on winning. Budgets and time lines of IT projects are shrinking by a minute yet quality software is required more often than before.



"When a software development effort goes awry, people are quick to blame software design, requirements management or project process. What almost always overlooked is the human aspect that software developers are bringing into the picture", says Dmitri Khanine, nation's leading authority on troubled projects.

Dmitri's revolutionary Software Project Success course holds a great promise to the industry. He is about to show you how almost every project can be recovered in 30 days or less.

These mistakes cost time, money or, in the worst case, entire projects. Here are 7 common, but easily avoidable mistakes that make a software project disaster just about a sure thing:

Mistake #1: Ignoring the people aspect of a project. This is where the single biggest breakthrough in project process success rates is happening yet millions of professionals are still shocked to find out

Mistake #2: Ignoring management training can seriously damage your software process. Paying attention to it can help your team deliver quality software on time and on budget - time and time again.

Mistake #3: Believing that software architecture should or even can drive a project. This is a fatal mistake. Software architecture is a medium where business vision is realized. The reverse is also true. When management team fails to understand the core architecture principles - they force ineffective decisions or have no choice but to abdicate control to their technical team - just to see their vision distorted in translation.

Mistake #4: Believing that someone can supply capable and productive software developers for your project. The truth is - you have to do your own hiring to achieve best results. Most recruiters don't go much further then reading resumes and asking candidates about their years of experience.

Mistake #5: Believing that simply asking your candidates a bunch of technical and behavioral questions makes up a good interview. Not only this "spontaneous" approach is unreliable - it makes you waste many hours you could've used for project delivery.

Mistake #6: Ignoring the most common ways requirements management kills projects and what teams can do about it. The key here is having the entire team understand them. Not only developers and architects but also the management team need to become familiar with the core principles of requirement management and its biggest pitfalls.

Mistake #7: Ignoring the biggest application software development disaster and its effects that sabotage any methodology. The biggest disaster is not the lack of methodology or an unresolved technology issue. The biggest threat - once again - comes from a human aspect of software development, people's believes and emotions. Project teams need to understand its warning signs and have their act together.