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

Quality Assurance and Project Management:

project training

May 27 2009   10:00AM GMT

Post Implementation Review – Why required?



Posted by: Jaideep
post implementation review, Project Management, project implementation, Software Project, implementation team, end user, project training, project knowledge, project lerning, software features, software functionality, software performance

A successful implementation does not ensure the completion of project. The reality starts when the implementation team has gone back and users have started using the project in full swing with the help of training material, learning, knowledge and product. The health of users in respect of using the product is sustained, deteriorated, or improved will depend on many factors. A post implementation review is always important to understand the users understanding, pains and delights during this tenure. This will translate further into management’s pains and delights. The overall delight weightage has to be higher than the pain. In a blow of project implementation phase users might feel quite confident regarding the product features, functionality and ease. When the whole thing falls upon them, it usually drive them in confusion, wrong actions or stoppages. Or a smooth drive.

A post implementation survey will help in a real measurement on two fronts. One front will be users’ understanding, ease and comfort (or vice versa). Second front will be product’s stability, performance and functionality. It also will assess the after effects of a successful project implementation.

The conclusions could be misleading although and will require a deep analysis. A user’s lack of understanding may spell into products inefficiency or the opposite of it.

AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend

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