Reference no: EM133989510

Process Improvement Stages: "Software Process Improvement"

1. Describe a software process at your workplace.

2. Describe the existing software process and choose a problem to solve.

3. Find process problems, and choose a problem to solve.

4. Find solutions, compare solutions, and choose a solution.

5. Produce a solution with an implementation action plan.

6. Produce an evaluation plan, justification, and executive summary.

7. Collate, edit, and hand in the whole report about Software Process Improvement

I need a great explanation for all the stages below:

Software Process Improvement

Stage 1

1. Write an introduction that sets the scene for the process for someone that does not Know your place of work.

2. Give a brief description of the process.

3. State the business objectives that the process supports.

4. Set the objectives and rationale for the process.

Stage 2

1. Description of Existing Process

2. Describe fully your process as it is actually done not as it is supposed to happen, using a Process Flow Diagram to help. Show all flows of material, people, and information, including abnormal paths as they actually occur not as they are supposed to occur. Show all decision points and recycle loops. If who does what is important, you may want to consider using a swimming pool PFD. If flows occur only occasionally then still put them in.

3. Consider the following tactical operational dimensions and state as they apply to your process (some or many of these may not apply to your process) and what the associated challenges are; product/service type, process type, capacity, quality, location, layout, humans, supply chain, inventory, scheduling, and maintenance.

Stage 3

State what all the problems are, their relative importance, and their root causes. Then chose a problem(s) to solve.
You will probably do the following:

1. Brainstorm for all the problems with the process, use a Fishbone Diagram or similar to organize the problems.

2. Choose a problem(s) to solve using tools like Pareto Diagram, Check sheets, etc., and state why you chose this problem(s). This may include data collection. 

3. Collect detailed data on the problem using tools like Control Charts, Histograms, etc. to find its root causes.

Stage 4

Consider all alternative solutions to the problem, and their pros and cons. Then chose a the solution to implement.

1. Brainstorm all solutions for the problem.

2. State the pros and cons of each solution (including those later rejected), which may involve finding costs involved and using tools like payback time and NPV, if necessary.

3. Choose a solution(s) and state why you chose it.

Stage 5

1. Implementation of Solution

2. Describe your project action plan for implementing your solution(s) to the problem(s) in your process, using at least a Gantt chart with activity-related arrows connecting all activities. You need to at a minimum state who will do what and by when.

3. Please include the following; all activities with their due dates, costs (may be estimated), and responsible people.

4. Please put in your targets (in numbers) that you hope to achieve once you implement the improvement.

Stage 6

1. Evaluation Plan State how you will check that your implemented solution has solved your process problem(s) and not created new problems. This should say who measures what and when.

2. Cost/Benefit Analysis and Capital Investment Justification If you have the information then do a cost/benefit capital investment justification, which you will summarize in the executive summary.

3. Executive Summary

When you have produced the rest of the assignment report, produce a less than one-page executive summary. This should include the process, problem(s), solution(s), and justification and will be at the front of the report. You should write the report as one narrative in a way that "sells" the proposal.

This should be a standalone document, which "sells" your ideas (elevator pitch) and thus should not refer to the rest of the report.