(Illustration) Map the entire process to know the where the improvement oppurtunities lie

Map the entire process to know the where the improvement oppurtunities lie

Doc : Welcome to Step C of Define. This final step will allow us to develop the process that we are trying to improve. The overall layout is signified by the acronym COPIS. It start with the Customer and run through outputs, processes, inputs, and finally, the supplier.

Doc : The high-level process map displays the relationship between the customer and the process as well as the overall flow of the process.
Doc : Having said that, a high-level process map identifies key inputs
Doc : As well as identifies project requirements. Basically a process is defined as a collection of activities that takes one or more kinds of input and creates output that is valuable to the customer. The contents of a high-level process map will explain the process. Take a look.

Doc : The contents of a process map for a project includes:Customers and their key requirements
Doc : Outputs, which result from the process, and meet or exceed the customer’s needs and related requirements
Doc : Process Steps, which are selected in order to improve something
Doc : Inputs, which are parts and personnel provided by the suppliers
Doc : And suppliers, who as we just mentioned, provide the inputs. This information can be more easily illustrated in a diagram. Take a look and you be the judge.

Doc : Well, what do you think? See where each of the pieces fit? The project flows from right to left while the customer’s thinking flows from left to right. The most significant thing to remember is: The focus is on the Customer: COPIS Next, we will create a process map relevant to the Rockledge case.

Doc : Examining the generic process map just now has given you the experience for what you are about to do. Brainstorm about the Rockledge Case: think about who the supplier and the customer are, the problem and the goal statements, the systems needed to accomplish the goal, and the people and supplies need to operate the systems.

Doc : Congratulations! You have completed step C in Define, which means you have worked your way through the entire Define phase. In measure, we will add more details to the process map so that measurements can be taken to locate sources of improvement.

Doc : Well, we have accomplished all of the objectives in Step C of Define. We defined the purpose of a high-level process map and described its contents. Then, we developed the Rockledge high-level process map.

Master: In step B of Define, you learned about a team charter. Defining the business case,
Master: Developing a problem and goal statement,
Master: Assessing the project scope,
Master: And selecting the team and defining each members?roles are components of developing a team charter.

Master: In Step C of define you defined the purpose,
Master: Described the contents
Master: And, finally, developed a high-level process map.

Master: Did you do Ok in define? I hope so. Just in case you have any doubts I will give you a brief review before asking you some questions. The define phase has three steps:
Master: In Step A you identified project's C T Qs. If you recall, identifying the customer is the first step in understanding the projects C T Qs.
Master: Next, we analyzed data from the customer to figure out what the customer wanted.
Master: Finally, you learned about the process product drill-down tree, which is a way to integrate C T Qs and business strategy.

Master: If you want more of a review than that, you can access all of the steps from the Define Menu on your screen.