| Topic : Biggest Project Management Mistakes |
|
|
Project Management ++
|
|
Activity:
132 views;
last activity : 07 06 2010 20:18:09 +0000
|
|
|
|
1
Multiple Factors
2
Communication gap either with clients or amongst team
3
Not monitoring Project Progress
4
Wrong analysis due to communication gap and understanding
5
Failure to nail requirements
6
First "Understand" what is to be developed.
7
Low Budget
8
Poor Communication
9
Inadequate Testing
|
||||||||||||||||||||||
|
|
I posted this idea elsewhere also, Periodically check your project for the following factors, these are the most obvious reasons for failures: - Lack of user inputs |
2
|
Mr.Suneel has perfectly gave the desription for the reasons of the software project failure. He has almost given a complete description and left nothing to add to that.
Its also depends whether its a
1. Development Project
2. Maintainence or Support project.
In a development project its important
1. To understand the business requirements properly which is actually a continuous process through out the phase of the deveopment because even if the client gives the requirements the developers will get complete business understanding once the development starts .
2. Estimation of the project is also an important aspect of the project delivery keeping in mind different risks during the development.
3. Clear documentation of requirements must be done before the development starts
4. Communication with the client and among the team must be clearly documented whenever any changes the existing requirements are done. This is important because if there is no clarity among the team about the changes it can lead to major bugs.
5. Unit/Integration/Stress Testing needs to be done depending on the size of the project.dedicated testing team would really minimize the no of bugs.
In a maintenance/support project (if the project is done by a third party and it is getting take over by a new team) it is important
1. To take the transition of knowledge from the original vendor.
2. Clear documentation about the business logic in the existing project.
3. Clear process for the change management whenever new changes are done. Impact analysis is a very important aspect in such scenario so that the changes doesnt affect the existing project.
|
|
Project may also suffer even if there is a communication gap with clients at each and every tiny point and same thing applies amonst team as well. Its always preferable to minimize loopholes in this areas |
2
|
|
|
Things change as the project progresses. This changes should be monitored on a regular basis so that you can deal with the on coming challenges.
|
2
|
This is the most important aspect. Project Monitoring includes every aspect of the project: Risk, Plan, Resources, Issues, Action Items, Budget, Communication - every single aspect. If this is not done properly, the project is bound to fail.
I strongly believe that the project fails from the start - not at the end. If the monitoring is in place, then the aspect of failure is limited.
I agree with Mr.Mishra that they don't monitor and review the project progress on a regular basis.
You should monitor and review progress with your team on regular basis, and make necessary adjustments.
|
|
Most of the projects goes in RED in the Initial analysis phase itself and they are due to 1) Poor communication with clients 2) Lack of understanding the requirements and sometimes 3) Poor cooperation from 3rd party vendor causes this. |
1
|
|
|
Too many assumptions made and guesswork applied. Inability to conceptualise. Working to preconceptions and misassociation with past experience. Lack of understanding of client differentials leading to a generalised design not tailored to needs. Requirements documented and sign-off obtained at too high a level. |
1
|
|
|
Most of the softwares fail due to poor understanding of the problem of requirement. This is the single most important thing. Next comes designing the software (architecting it) which most of the time is not done and people just start with adhoc development. Architecting a sofware increases some delay initially but that will be paid off in the long run. It also is not a very simple task to do , it requires a visionary and expert to do so. Next comes communitcation and tracking. If they do not happen properly whole project is in jeopardy. Budget I would not count here. It's simple, you don't have money than please don't put your hands inside and cry later. |
1
|
|
|
Many Software projects have an unrealistically low budget. With low budget everything slows down, resources are slow to arrive or never arrive, corners are cut and quality suffers.
To overcome failure :Be realistic about the budget and it should be based on the actual requirements.Select supplier or team that has a proven track record of delivery within budget. |
0
|
|
|
Poor communication leads to failure.
Good communication is vital for project success with the customer, users and especially the development team. Make sure that everyone in team understands you,what is expected from them. |
0
|
|
|
Often all the testing is left until the end of the development cycle as the pressure is to deliver the product on time. This results in product filled with bugs which further leads to an unhappy customers.
If you don't want your software project to failure and have an unhappy customer ,carry out testing throughout the development lifecycle, testing each module or component as it's developed. |
0
|

- Create a confidential Career Profile and Resume/C.V. online
- Get advice for planning their career and for marketing of experience and skills
- Maximize awareness of and access to the best career opportunities
|
|
|
|
|
|
|
|
|
|
Create an impression around you that you are the one who can solve this problem and no one else, and do things street smart and not the routine way, which keeps people interested in you all the time, and important to have varied knowledge on most of... |
Google chrome wont be able to out perform Mozilla, mozilla firefox is way better than any other internet browser and also the addon's of mozilla helps the developer to the tester in many ways... |
Thank you for the insights it has answered the question I had .... Do participate in the idea contest created by me about How to successful manage your Offshore Software Project Team ? http://toostep.com/idea/how-to-successful-manage-your-offshore-soft... |
