Project Cost archives - Quality Assurance and Project Management
Home > IT Blogs > Quality Assurance and Project Management >

Quality Assurance and Project Management:

project cost

Apr 24 2009   10:06AM GMT

5 ways to control project overrun



Posted by: Jaideep
Project Management, Software Project, project momentum, project velocity, project cost, project time, project organization, customer engagement, project sign-off, project closure, project training, Project Plan, Project Planning, management involvement

Project overrun is simply a project crossing its boundaries set by the organization. These boundaries may vary from organization to organization depending on how they blindly or how over-extensively (both extremes) they want to look at it.

5 ways to control project overrun could be:

  • 1. Requirements: With any change in requirements from customer, effort estimation and change in plan is important to drive the project in right direction.

    2. Customer engagement: At customer site (or earlier as and when customer involvement is required) if customer project team is not justifiably involved in project by means of specifying requirements, providing master inputs, in training, timely sign-offs at various stages, hands-on exposures, etc. effects project drastically and plan may go haywired, without anybody’s accountability to prove, if alarm is not raised well in time.

    3. Milestones: If appropriate milestones are not identified and monitored at every stage of the project, it affects the project finish off in time.

    4. Management involvement: If management let the project go off without their involvement in it, it has high chances to overrun.

    5. Celebrations: No celebrations of achievements during the project can decelerate the tempo and momentum of the team at both ends to finish off the project in time.

    • AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend

    Apr 22 2009   9:51AM GMT

    5 myths about Project Overrun



    Posted by: Jaideep
    Project Plan, Project Planning, Software Project, project overrun, project acceptance, project organization, customer requirements, software requirements, Project Management, project closure, project manpower management, project cost, project timeline, project timeframe

    All projects are prone to overrun. An overrun acceptance is directly proportional to an organization’s fault absorption capacity. Accordingly the definition of overrun is framed to demonstrate an overrun project as rightly completed project.

    5 myths about Project Overrun could be:

  • 5. Planning: After the initial plan is made, customer requirements have shrunk but it is good not to revise the plan to achieve in-time project closure (or even earlier).

    4. Manpower: Project Plan is made after which additional manpower is inducted in the project, but no need to revise the plan.

    3. Cost: Customer is ready to pay the full payment to complete the project, even if it overshoots the timeframe decided as per plan.

    2. Time: A project had to complete in 5 months, but it took 10 months to complete. Imagine the manpower engaged in this project that could have finished another project if this project finished in time.

    1. Customer: Customer is not able to cope up with plan but not ready to pay for extra efforts being done by the project team on behalf of customer thereby overshooting cost and time. We have a valid reason for this overshoot.

    • AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend