Question

ASSIGNMENT:

• The purpose of a quality management plan is to define overall project quality guidelines that will be applied to the project. Using your selected RFP or Desktop Lab Project - in a written assignment, develop a quality management plan for your project.
• This plan should contain information about:
  1. How you will control changes to the project?
  2. How you will ensure that the information technology you selected meets requirements?
  3. How you will ensure that the technology works properly?
  4. How you will plan for and execute testing, during development and when completed?
  5. How you will track and resolve defects?
  6. What metrics will you use to gauge quality?

Answer 1

1. Control Changes

Change control is an important part of the project management process. With the pace of change today, it is almost certain that projects will face the demand for change during their life. While change may help ensure the project's alignment with business needs, it is important to consider and approve each change carefully.

The change control process in project management ensures that each change proposed during a project is adequately defined, reviewed and approved before implementation. The change control process helps avoid unnecessary changes that might disrupt services and also ensures the efficient use of resources.

Change control contains five stages:

1. Proposing a Change : The proposal must include a description of the change and expected benefits or other reason for the change.
2. Summary of Impact : This process is carried out by the project manager, who will consider the overall effect on the project.
3. Decision : This process involves a review of the change request by an approved authority who will consider all the information provided by the project manager and person making the request.
4. Implementing a Change : If the change is approved it is planned, scheduled and executed at a time agreed with the stakeholders.As part of the planning, a regression test plan is needed in case the change needs to be backed out.After implementation, it is usual to carry out a post-implementation review.
5. Closing a Change : Once implemented, the requester checks and agrees on the change, and it is closed in the Change Log by the project manager.

2. Ensure Technology Selected meets requirement

It Compromises in following Steps:

1. Understanding the client's business problems.

2. Defining the scope of the requirement.

3. Identifying the appropriate software

4. Eavaluating Software to see how it can meet each of the key problems that need to be addressed.

5. Determinig when to bring the client into review to explain which packages to choosen and why.

6. Making the final decision regarding the solutions that each system will provide to the issues/problems identified at the start of the review.

7. Determining your on going role after implementation.

3. Ensure technology works properly : The technology which are chosen are based on the factors like what are the client's requirement?, how that particular technology solve those problems?, what will be the risk involve? etc.

First of all the technology chosen must have proper documentation so that it can be understand by anyone who is working on the project to make it efficient.

The risk involve in implementing the problem should very less with that particular technology.

4. Execute testing, during development and when completed :

It involves following activities :

Analyze the product and design the test strategy : It involves analyzing the product by researching  clients and the end users to know their needs and expectations from the application. It can be achieved by interviewing developer, designer as well as client. Also reviewing the project document can help.

Strategy involves mainly analyzing the scope of testing, identifying testing type (like unit testing,integration testing, regression testing, performance testing etc.), document risk and issues.

5. Defect Management

Three important components of defect management are :

1. defect management process

The defect must be discovered. After the discovery the defect must be categorized appropriately in category as defined by the organization. The Priority must be assigned to the defect based on the impact it creates. Priority can be low, medium and high. After priority it should be assigned to developer for the fix. After resolution of defect, it should  be moved to environment. The resolution must be verified to check if fix actually solves the issue. After verifiaction defect should be closed and proper reporting should be done.

2. defect management tools

Provides a centralized repository for tracking defects across projects.

Provides automated notifications of resource assignments.

Ability to define defect resolution status in order to map back to your defect management process.

Ability to provide management reporting, like the number of open defects grouped by various criteria such as open defects by project, severity, and priority.

6. Metric to Gauge Quality

Following metric can be used to gauge quality

1. Algorithm Analysis

2. Number of Code lines

3. Complexity of software

4. Functional point analysis

5. Number of bugs per 1000 code lines

6. Level of testing

7. Number of classes and interfaces

8. Cohesion