Quality Assurance and Project Management

Feb 23 2009   10:43AM GMT

Top 15 Pain Areas in a Software Project Lifecycle

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Following are the top 15 pain areas of a software project. All points listed below appear somewhere or the other in a software project lifecycle. The ratio of pain from a particular below listed item may vary from project to project within an organization, and also from organization to organization. So although the hierarchy may vary, the pain areas somehow remain the same. A lack in addressing any one of the issue listed below may call for a big hiccup in the smooth running and closure of a project. The project size (and in turn the time and team size also) will vary depending on customer and customer requirements. Although all points listed below are self explanatory, but the understanding and perception may vary from individual to individual.

In that respect, I would like to take each of the points below one by one in my forthcoming blogs to explain how much impact each of the instrument listed below will have on the project and how to overcome this pain not only for that projects but for all the projects in that organization to come in future. The most important activity for each individual is, now, to re-arrange the points (with any additions/ or replacements) according to the ratio of pain it is giving, and then learn how to convert that pain into pleasure once for all (in my future blogs for the later part!)

  • 1. Methodology and Standards
    2. Documentation
    3. Customer requirements understanding
    4. Measurement of Overrun is in money terms immaterial of time overrun (time is not measured in terms of money)
    5. Frequent Status review in a forum
    6. Status of project movement is person based
    7. Role clarity to project manager and team on site
    8. Risk analysis
    9. Team building
    10. Customer clarity in terms of milestones and payments
    11. Project Repository
    12. Learning from Past
    13. Post implementation support
    14. Quality – man, methods, approach and deliverables
    15. Version Control
  •  Comment on this Post

    There was an error processing your information. Please try again later.
    Thanks. We'll let you know when a new response is added.
    Send me notifications when other members comment.

    Forgot Password

    No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

    Your password has been sent to:

    Share this item with your network: