Skip to main content

Lean Six Sigma Process

Everything! Any activity, process or procedure that transforms a number of input (s) into a number of output (s).


VOP = Voice of Process
VOB = Voice of Business
VOC = Voice of Customer

Non-Value-Added/  Value-Added Analysis (NVAA)



Example 1: Processing a lab test 
This example focuses on the process of taking a blood sample and generating a lab report. 

Inputs (
Xcap X
)
 
These are the resources and information required to perform the process. 
  • Patient information: Demographics, medical history, and specific test orders from the physician.
  • Physical resources: Sterile syringes, needles, collection tubes, labeling materials, and the lab's analytical equipment.
  • Personnel: Trained phlebotomists to draw the blood, lab technicians to analyze the sample, and pathologists to verify the results.
  • Procedures: Standard operating procedures (SOPs) for blood collection, handling, analysis, and quality control. 
Process (
ff
)
 
This is the series of steps that transforms the inputs into the desired output. 
  • Patient registration and sample collection: Patient arrives, verifies their identity, and a blood sample is drawn.
  • Sample preparation: The blood sample is labeled correctly and prepared for transport to the lab.
  • Analysis: The lab technician uses specialized equipment to perform the required tests on the blood sample.
  • Result interpretation: A qualified pathologist reviews the results, noting any abnormalities.
  • Report generation: The final report is compiled and delivered to the requesting physician and patient. 
Outputs (
Ycap Y
)
 
This is the product or service delivered by the process. 
  • Accurate lab report: A document containing the patient's test results, verified by a pathologist.
  • Timely delivery: The report is provided within the expected turnaround time.
  • Patient satisfaction: The patient has a positive experience during the collection process and receives their results in a timely manner. 

Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .