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 (
$cap 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 (
$f$
)

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 (
$cap 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

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

4 T's - Technology, Time, Teamwork, Transparency

1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished. 3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...

High-Tech Yuga

Search This Blog