Six Sigma

Overview:
Six Sigma is a set of techniques and tools for process improvement. It was introduced by engineer Bill
Smith while working at Motorola in 1986. Jack Welch made it central to his business strategy at General
Electric in 1995.
Key Concepts:
DMAIC:
Define: Identify the problem, project goals, and customer (internal and external) requirements.
Measure: Collect data and determine the current performance level.
Analyze: Identify the root causes of defects and opportunities for improvement.
Improve: Implement and verify the solution.
Control: Maintain the solution and ensure continuous improvement.

DMADV (also known as DFSS - Design for Six Sigma):

Define: Define design goals that are consistent with customer demands and the enterprise strategy.
Measure: Measure and identify CTQs (characteristics that are Critical To Quality), product capabilities,
production process capability, and risks.
Analyze: Develop and design alternatives, create a high-level design, and evaluate design capability to
select the best design.
Design: Develop detailed design and process details, optimize the design, and plan for design verification.
Verify: Verify the design, set up pilot runs, implement the production process, and hand it over to the
process owner(s).

Tools and Techniques:

Statistical Process Control (SPC)
Failure Modes and Effects Analysis (FMEA)
Process Mapping
Root Cause Analysis
Control Charts
Pareto Charts
Histograms

Sensitivity
: Internal
Benefits:
Improved quality and customer satisfaction
Reduced process variability
Cost savings and increased profitability
Enhanced problem-solving capabilities

Agile
Overview:
Agile is a project management and product development approach that emphasizes flexibility,
collaboration, and customer satisfaction. It was formalized with the Agile Manifesto in 2001 by a group
of software developers who were frustrated with the traditional, rigid methods of software development.
Agile Manifesto:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Principles:
Satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development.
Deliver working software frequently, from a couple of weeks to a couple of months.
Business people and developers must work together daily.
Build projects around motivated individuals, giving them the environment and support they need.
Face-to-face conversation is the most efficient and effective method of conveying information.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
Continuous attention to technical excellence and good design.
Simplicity—the art of maximizing the amount of work not done—is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
Regularly reflect on how to become more effective and adjust accordingly.

Frameworks and Practices:

Sensitivity
: Internal
Scrum: An iterative and incremental framework.
Kanban: A visual approach to managing work.
Extreme Programming (XP): Emphasizes technical excellence and customer satisfaction.
Lean Software Development: Focuses on eliminating waste and improving flow.
Crystal: A collection of methodologies that adapt to project size and criticality.

Scrum
Overview:
Scrum is an Agile framework used for developing, delivering, and sustaining complex products. It is
designed for teams of ten or fewer members who break their work into actions that can be completed
within time-boxed iterations, called sprints (typically 2-4 weeks).
Key Roles:
Product Owner: Represents the stakeholders and the voice of the customer. Responsible for the backlog
and ensuring the team delivers value.
Scrum Master: Facilitates the Scrum process, helps resolve impediments, and ensures the team adheres
to Scrum practices.
Development Team: Cross-functional team members who do the work (design, develop, test, etc.).

Artifacts:
Product Backlog: An ordered list of everything that is known to be needed in the product.
Sprint Backlog: A list of tasks the team commits to during a sprint.
Increment: The sum of all the Product Backlog items completed during a Sprint and all previous Sprints.

Events:
Sprint Planning: The team plans the work for the sprint.
Daily Scrum (Standup): A 15-minute time-boxed event where the team synchronizes activities and plans
for the next 24 hours.
Sprint Review: The team demonstrates the work done during the sprint to stakeholders.
Sprint Retrospective: The team reflects on the past sprint to identify and implement improvements.
Benefits:
Increased visibility and transparency
Improved collaboration and communication

Sensitivity
: Internal
Faster delivery of valuable products
Continuous improvement through regular reflection and adaptation
Scrum Values:
Commitment: Team members commit to achieving their goals.
Courage: Team members have the courage to do the right thing and work on tough problems.
Focus: Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
Openness: The team and its stakeholders agree to be open about all the work and the challenges with
performing the work.
Respect: Team members respect each other to be capable, independent people.
Summary
Six Sigma, Agile, and Scrum are all methodologies aimed at improving processes and delivering high-
quality products, but they differ in their approaches and focus areas. Six Sigma is heavily data-driven and
focuses on reducing defects and process variability. Agile emphasizes flexibility, customer collaboration,
and responding to change, while Scrum provides a structured framework within Agile to manage project
work and deliver increments of valuable product through collaborative teamwork and iterative cycles.

Sensitivity
: Internal