Session Title: Thinking Business Agility
Session Overview: The session will cover key concepts of Business Agility as per Institute of Business Agility. These concepts will be touched upon in a business agility case study to increase learning. The session will continue towards a Game-based workshop on how Kanban help in Business Agility. The game will end with the Attendees playing in group/ team summarizing their learnings from the Game
An OBIEE Success Story: How a Regional Utility Created Visibility in Supply Chain provides an overview about a project utilizing both OBIEE and Business Intelligence Analytics products. The project’s goal was to provide timely data and reporting to Supply Chain for aiding in strategic decision making. The result was a reduction in overall operational costs, performance and productivity tracking, inventory management in partnership with business operations and the initiation of basic governance practices for the data within the Oracle E-Business Suite.
This document discusses applying lean principles to optimize business processes in an office setting. It introduces the concepts of resistance to change and using a lean office kaizen model and methodology. Key aspects of the model include creating a vision, identifying opportunities through current state process mapping, and developing a future state with action items. Core business processes like sales, quality, and product engineering are identified as areas of opportunity. The document advocates targeting significant metrics and activities to improve processes in areas like customer engagement and product development.
The document discusses moving the role of business analysts from a focus on writing requirements to synthesizing information. It advocates taking an end-to-end process perspective, developing a case for change by assessing stakeholders and consequences of inaction, and identifying what needs to change by evaluating six process enablers. The document provides examples of these techniques and emphasizes the importance of workflow mapping in requirements identification.
This document summarizes an agile business requirements workshop presented by British Gas Trading. The workshop covered agile business requirements, group exercises discussing challenges and solutions, and lessons learned from past projects. Attendees participated in discussions on clarifying requirements, managing scope changes, settling stakeholders, and dealing with time constraints. The workshop concluded with a networking session and prize draw.
Business Processes - What Are They, Anyway ?
adapted from:
Alec Sharp, Patrick McDermott!
Workflow Modeling
Tools for Process Improvement and Application Development
2nd ed. by Alec Sharp
Chapter 3
The document discusses getting traction for process improvement initiatives. It notes that people often have negative reactions to the word "process" and see it as boring, dehumanizing, or a threat to their jobs. It emphasizes the importance of clearly defining what constitutes a business process and providing guidelines for naming and understanding processes. These include processes being triggered by external events and having discrete, countable results. The document also stresses that while functions are important and efficient, they can conflict with overall process goals if the process is not clearly defined and managed as a whole. It argues for identifying process owners to set direction and resolve conflicts between functions.
Process modeling in agile environment alec sharpLoihde Advisory
Esitys on osa joulukuussa 2015 pidettyä Talent Base aamiaistilaisuutta: Data. Prosessit. Innovaatiot. Esityksen piti Alec Sharp, Clariteq Systems Consulting.
Presentation is part of the Talent Base Breakfast Seminar: Data. Processes. Innovations.
- Rapid and innovative process design in an Agile environment
- Why the Agile community is embracing data and process modeling
- Getting clarity on “business process”
- Why slowing down and getting out of the details is critical for rapid process design
- Two assessment frameworks to dispel resistance to change
- A feature-based approach to process design
The document discusses lean principles and techniques for reducing waste in offices. It outlines concepts like 5S, visual controls, kaizen, value streams, and mistake proofing. It also identifies common types of waste in offices like errors, unnecessary motion, waiting, and underutilized employees. Case studies show that applying lean led to major reductions in sales order cycle time, engineering change order time, and response time to customer requests, as well as a large drop in employee errors. The document advocates using 5S and visual controls to eliminate waste and gain control over processes, standardize improvements, and maintain critical parameters. It asks the reader to identify waste in photos and discusses implementing visual workplace techniques like flow arrows and color coding floors and areas
An OBIEE Success Story: How a Regional Utility Created Visibility in Supply Chain provides an overview about a project utilizing both OBIEE and Business Intelligence Analytics products. The project’s goal was to provide timely data and reporting to Supply Chain for aiding in strategic decision making. The result was a reduction in overall operational costs, performance and productivity tracking, inventory management in partnership with business operations and the initiation of basic governance practices for the data within the Oracle E-Business Suite.
This document discusses applying lean principles to optimize business processes in an office setting. It introduces the concepts of resistance to change and using a lean office kaizen model and methodology. Key aspects of the model include creating a vision, identifying opportunities through current state process mapping, and developing a future state with action items. Core business processes like sales, quality, and product engineering are identified as areas of opportunity. The document advocates targeting significant metrics and activities to improve processes in areas like customer engagement and product development.
The document discusses moving the role of business analysts from a focus on writing requirements to synthesizing information. It advocates taking an end-to-end process perspective, developing a case for change by assessing stakeholders and consequences of inaction, and identifying what needs to change by evaluating six process enablers. The document provides examples of these techniques and emphasizes the importance of workflow mapping in requirements identification.
This document summarizes an agile business requirements workshop presented by British Gas Trading. The workshop covered agile business requirements, group exercises discussing challenges and solutions, and lessons learned from past projects. Attendees participated in discussions on clarifying requirements, managing scope changes, settling stakeholders, and dealing with time constraints. The workshop concluded with a networking session and prize draw.
Business Processes - What Are They, Anyway ?
adapted from:
Alec Sharp, Patrick McDermott!
Workflow Modeling
Tools for Process Improvement and Application Development
2nd ed. by Alec Sharp
Chapter 3
The document discusses getting traction for process improvement initiatives. It notes that people often have negative reactions to the word "process" and see it as boring, dehumanizing, or a threat to their jobs. It emphasizes the importance of clearly defining what constitutes a business process and providing guidelines for naming and understanding processes. These include processes being triggered by external events and having discrete, countable results. The document also stresses that while functions are important and efficient, they can conflict with overall process goals if the process is not clearly defined and managed as a whole. It argues for identifying process owners to set direction and resolve conflicts between functions.
Process modeling in agile environment alec sharpLoihde Advisory
Esitys on osa joulukuussa 2015 pidettyä Talent Base aamiaistilaisuutta: Data. Prosessit. Innovaatiot. Esityksen piti Alec Sharp, Clariteq Systems Consulting.
Presentation is part of the Talent Base Breakfast Seminar: Data. Processes. Innovations.
- Rapid and innovative process design in an Agile environment
- Why the Agile community is embracing data and process modeling
- Getting clarity on “business process”
- Why slowing down and getting out of the details is critical for rapid process design
- Two assessment frameworks to dispel resistance to change
- A feature-based approach to process design
The document discusses lean principles and techniques for reducing waste in offices. It outlines concepts like 5S, visual controls, kaizen, value streams, and mistake proofing. It also identifies common types of waste in offices like errors, unnecessary motion, waiting, and underutilized employees. Case studies show that applying lean led to major reductions in sales order cycle time, engineering change order time, and response time to customer requests, as well as a large drop in employee errors. The document advocates using 5S and visual controls to eliminate waste and gain control over processes, standardize improvements, and maintain critical parameters. It asks the reader to identify waste in photos and discusses implementing visual workplace techniques like flow arrows and color coding floors and areas
OEE Financial Benefits From Component ImprovementLean Teams USA
OEE has long been used as a Lean measure for the effectiveness of production equipment. It is mainly used to determine where to focus improvement efforts, Availability, Performance, or Quality. This presentation provides an explanation of OEE and a case study of how improvements to each of the OEE factors can demonstrate financial results
What do 'Lean' manufacturing techniques have to offer service companies? Lean production practices generally reduce costs, eliminate waste, and increase efficiency. However, translating these practices to an office environment is often less than obvious. Fully achieving 'Lean' also entails value stream mapping, root cause problem solving, and 5S methodology (to name a few). But these ideas are far from difficult to grasp and often enlightening.
This document discusses various Lean concepts and tools including 5S, visual controls, Kaizen, value stream mapping, pull vs push scheduling, mistake proofing, changeover time, Six Sigma, activity-based costing, Theory of Constraints, ergonomics, and knowledge management. It also briefly discusses costs of accidents and conducting effective meetings.
[Process Day 2011] Alec Sharp – Making Process Real Engaging the CXOs RecursoEloGroup
This document summarizes a presentation by Alec Sharp on engaging executives in business process management. Some key points from the presentation include:
1) Executives may not view process management favorably and see it as a threat. Stories and examples can help engage them more than claims of cost savings.
2) Promoting process management based only on claims of reduced costs and improved efficiency may not be effective since all disciplines make similar claims.
3) Starting process initiatives from the middle levels of an organization, rather than the top, can gain more traction initially before bringing executives on board.
4) Processes need to be clearly defined and understood across an organization, as different roles see them differently, and this
This document discusses applying lean principles and value stream mapping to administrative and office processes. It provides an overview of value stream mapping and how to map both production and non-production processes. The document outlines a process for mapping the current state, which includes documenting customer needs, identifying processes, selecting metrics, and calculating performance. It also discusses designing a future state and applying lean thinking at the functional level throughout an organization.
- Angela Ibrahim is seeking a career position utilizing her 13+ years of experience in office administration, quality control, and customer service roles
- She has strong skills in scheduling, time management, organization, problem solving, and multi-tasking
- Her experience includes quality inspection, auditing, data entry, administrative support, and reception work for various industries
The document discusses the implementation of the M5 system at Orbotech to improve their customer support processes. Some key points:
- The project involved implementing 50 main business processes across operations, logistics, finance and more in the M5 system. It also integrated various other systems and included business intelligence capabilities.
- Challenges included the distributed nature of Orbotech's global operations, different working styles across divisions, and demands from customers.
- The implementation followed Orbotech's methodology and had a steering committee and dedicated project teams. It involved defining requirements, customizing the system, converting data, developing reports and training users.
- After two pilot phases, the system went live across major
This document describes a case study of mapping the value stream for Jax Taxes, a CPA business providing tax preparation services. It includes a description of Jax Taxes' current tax preparation process, which involves multiple handoffs, delays, and errors. The document then provides an overview of value stream mapping concepts and tools to analyze Jax Taxes' current process, identify sources of waste, and develop a future state map to design a leaner workflow. Key aspects discussed include defining customer value, mapping the current state, identifying types of waste, determining root causes of problems, and using metrics to measure improvements.
Tara Detweiler has over 20 years of experience in IT project support, service desk management, and business analysis. She has extensive experience managing projects from start to finish, including gathering requirements, creating schedules and reports, and tracking deliverables. She is proficient in various project management software and tools.
This document provides an overview of Siedge, an engineering services company focused on manufacturing. Its vision is to become a reference for engineering services with high standards in quality and customer service. The company's mission centers on offering unique services with a focus on continuous learning and improvement. Siedge's services include lean implementation, new product introduction support, technology coaching, quality assurance systems, and manufacturing engineering solutions tailored to customer needs.
As more customers consider OneStream for their Corporate Performance Management (CPM) needs we are frequently being asked questions like:
How are other customers using OneStream?
We know how we do "X", but what have you seen other companies do to make "X" better/easier/faster in OneStream?
We want to do "Y", but we aren't sure what it would mean to do "Y" in OneStream?
These questions apply to a wide range of topics. In this and future webinars we will review what Finit has helped companies "do" in regards to the following topics using OneStream:
Automating / Streamlining Cash Flow Reporting
Integrating Multiple Charts of Accounts
Functional versus Natural Account Reporting
Rolling / Seeding Forecasts
Bridge and Variance Analysis
Acquisition Reporting
Multiple Currency Reporting
Hear how Finit has helped companies approach these topics and helped them design and implement solutions that allow them to maximize their OneStream investment.
Presenter: Jay Hampton
www.finitsolutions.com
Lean Thinking is a management philosophy based on the Toyota Production System (TPS). With Lean Thinking, you will be able to enhance value for your customers by improving service delivery and eliminating waste. Simply put, by becoming a Lean organization, you will be able to improve personal effectiveness, increase productivity and create greater customer value with less resources.
This training presentation is especially tailored for service industries. By teaching this presentation to managers and employees, they will have a better understanding of the Lean principles and approach to eliminating waste, and will be more forthcoming to lead and participate in the Lean implementation process.
LEARNING OBJECTIVES
1. Understand the principles and key concepts of Lean
2. Acquire knowledge on the key Lean methods and tools and their applications to improve personal effectiveness, value creation and waste elimination
3. Identify ways to develop “Kaizen eyes” to look for improvement opportunities
4. Describe the various Lean roles
CONTENTS
1. Introduction to Lean Thinking
2. Key Concepts of Lean Thinking
3. Overview of Lean Methods & Tools
4. Ways to develop "Kaizen Eyes"
5. Lean Roles
6. Sustaining a Lean Culture
To download this complete presentation, please visit: http://www.oeconsulting.com.sg
Steven Wilson has over 20 years of experience in financial services, including expertise in tax reporting, regulatory issues, and system enhancements. He has held several roles at SunGard Asset Arena Transfer Agency, including Senior Business/Quality Analyst, providing support to 4 clients. Currently he assists clients, manages projects and disaster recovery exercises, and acts as a key point of contact.
Optimizing Materials Handling on the Cheap: How to Lean your Workflowsloriayre
The document provides an overview of Lean methodology for optimizing materials handling workflows. It defines Lean as focusing on delivering the most value to customers while using the fewest resources. The document discusses key Lean concepts like value streams, value-added activities, waste, and the PDCA continuous improvement cycle. It also provides tips for applying Lean tools like value stream mapping, process mapping, visual management systems, and the "five S's" for efficiency. The overall summary is that Lean aims to streamline workflows and eliminate waste through empowering staff to systematically analyze and improve processes.
This document discusses project scope management. It begins with an agenda that outlines key topics like why manage project scope, defining project and product scope, and processes for planning, collecting requirements, defining, validating, and controlling scope. It then defines each process in more detail, providing inputs, tools and techniques, and outputs for planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. It also discusses the differences between project and product scope, and defines scope creep and gold plating, providing examples of each.
How to Capture Better Business Requirements in Software ProjectsGabor Schönekker
When a software project gets off the rails in most cases the blame is on inaccurate business requirements.
There is no difference between Traditional or Agile projects. If business requirements were not captured correctly the project is doomed to fail before it even started.
I put together a slide deck on structuring, improving the requirements gathering process to ensure that everything is ready to start the delivery of the project.
Another slide deck will follow describing useful methodologies, techniques to ease the process.
The importance of managing process and requirementsJeff Herz
The document discusses the importance of managing processes and requirements for projects. It states that projects often begin without clearly defining objectives or requirements, leading to wasted time and costs from reworking functionality. Proper requirements gathering and documentation in the areas of business, functional, and technical requirements can help ensure projects are successful. This includes defining requirements, processes, designs, and getting stakeholder approval before development begins. Managing requirements is likened to building a house with proper blueprints rather than starting construction without plans.
INGINIX Systems Corporation is a privately held company founded in 2002 that provides project and vendor management software. Their software allows users to manage work orders, vendors, customers, projects, sites and assets in one centralized system. Key benefits of their software include increased control over projects, reduced costs, improved transparency and reporting, and increased capacity for project managers. Their software solution is used across industries like retail, deployment, services, healthcare, and communications to streamline project management and vendor coordination.
The document summarizes an intern's end of assignment report at Eaton Corporation in Waukesha, Wisconsin. Over the course of the internship, the intern assisted with an ISO audit to receive less than 3 findings, disposed of expired paint while updating inventory records, updated lead times for vendors in the system, implemented digital printing to reduce decal lead times, and designed a new layout for the paint shed. The intern gained experience with inventory management, purchasing, and continuous improvement systems and processes during plant tours and projects.
The document discusses how AAA implemented a service catalog to improve their business processes and customer experience. It describes how AAA was facing issues with inconsistent and inefficient service request fulfillment. They implemented a service catalog to standardize requests into a structured workflow with automated fulfillment steps and communication updates. This provided benefits like reduced costs, increased efficiency and consistency compared to the previous ad-hoc process.
OEE Financial Benefits From Component ImprovementLean Teams USA
OEE has long been used as a Lean measure for the effectiveness of production equipment. It is mainly used to determine where to focus improvement efforts, Availability, Performance, or Quality. This presentation provides an explanation of OEE and a case study of how improvements to each of the OEE factors can demonstrate financial results
What do 'Lean' manufacturing techniques have to offer service companies? Lean production practices generally reduce costs, eliminate waste, and increase efficiency. However, translating these practices to an office environment is often less than obvious. Fully achieving 'Lean' also entails value stream mapping, root cause problem solving, and 5S methodology (to name a few). But these ideas are far from difficult to grasp and often enlightening.
This document discusses various Lean concepts and tools including 5S, visual controls, Kaizen, value stream mapping, pull vs push scheduling, mistake proofing, changeover time, Six Sigma, activity-based costing, Theory of Constraints, ergonomics, and knowledge management. It also briefly discusses costs of accidents and conducting effective meetings.
[Process Day 2011] Alec Sharp – Making Process Real Engaging the CXOs RecursoEloGroup
This document summarizes a presentation by Alec Sharp on engaging executives in business process management. Some key points from the presentation include:
1) Executives may not view process management favorably and see it as a threat. Stories and examples can help engage them more than claims of cost savings.
2) Promoting process management based only on claims of reduced costs and improved efficiency may not be effective since all disciplines make similar claims.
3) Starting process initiatives from the middle levels of an organization, rather than the top, can gain more traction initially before bringing executives on board.
4) Processes need to be clearly defined and understood across an organization, as different roles see them differently, and this
This document discusses applying lean principles and value stream mapping to administrative and office processes. It provides an overview of value stream mapping and how to map both production and non-production processes. The document outlines a process for mapping the current state, which includes documenting customer needs, identifying processes, selecting metrics, and calculating performance. It also discusses designing a future state and applying lean thinking at the functional level throughout an organization.
- Angela Ibrahim is seeking a career position utilizing her 13+ years of experience in office administration, quality control, and customer service roles
- She has strong skills in scheduling, time management, organization, problem solving, and multi-tasking
- Her experience includes quality inspection, auditing, data entry, administrative support, and reception work for various industries
The document discusses the implementation of the M5 system at Orbotech to improve their customer support processes. Some key points:
- The project involved implementing 50 main business processes across operations, logistics, finance and more in the M5 system. It also integrated various other systems and included business intelligence capabilities.
- Challenges included the distributed nature of Orbotech's global operations, different working styles across divisions, and demands from customers.
- The implementation followed Orbotech's methodology and had a steering committee and dedicated project teams. It involved defining requirements, customizing the system, converting data, developing reports and training users.
- After two pilot phases, the system went live across major
This document describes a case study of mapping the value stream for Jax Taxes, a CPA business providing tax preparation services. It includes a description of Jax Taxes' current tax preparation process, which involves multiple handoffs, delays, and errors. The document then provides an overview of value stream mapping concepts and tools to analyze Jax Taxes' current process, identify sources of waste, and develop a future state map to design a leaner workflow. Key aspects discussed include defining customer value, mapping the current state, identifying types of waste, determining root causes of problems, and using metrics to measure improvements.
Tara Detweiler has over 20 years of experience in IT project support, service desk management, and business analysis. She has extensive experience managing projects from start to finish, including gathering requirements, creating schedules and reports, and tracking deliverables. She is proficient in various project management software and tools.
This document provides an overview of Siedge, an engineering services company focused on manufacturing. Its vision is to become a reference for engineering services with high standards in quality and customer service. The company's mission centers on offering unique services with a focus on continuous learning and improvement. Siedge's services include lean implementation, new product introduction support, technology coaching, quality assurance systems, and manufacturing engineering solutions tailored to customer needs.
As more customers consider OneStream for their Corporate Performance Management (CPM) needs we are frequently being asked questions like:
How are other customers using OneStream?
We know how we do "X", but what have you seen other companies do to make "X" better/easier/faster in OneStream?
We want to do "Y", but we aren't sure what it would mean to do "Y" in OneStream?
These questions apply to a wide range of topics. In this and future webinars we will review what Finit has helped companies "do" in regards to the following topics using OneStream:
Automating / Streamlining Cash Flow Reporting
Integrating Multiple Charts of Accounts
Functional versus Natural Account Reporting
Rolling / Seeding Forecasts
Bridge and Variance Analysis
Acquisition Reporting
Multiple Currency Reporting
Hear how Finit has helped companies approach these topics and helped them design and implement solutions that allow them to maximize their OneStream investment.
Presenter: Jay Hampton
www.finitsolutions.com
Lean Thinking is a management philosophy based on the Toyota Production System (TPS). With Lean Thinking, you will be able to enhance value for your customers by improving service delivery and eliminating waste. Simply put, by becoming a Lean organization, you will be able to improve personal effectiveness, increase productivity and create greater customer value with less resources.
This training presentation is especially tailored for service industries. By teaching this presentation to managers and employees, they will have a better understanding of the Lean principles and approach to eliminating waste, and will be more forthcoming to lead and participate in the Lean implementation process.
LEARNING OBJECTIVES
1. Understand the principles and key concepts of Lean
2. Acquire knowledge on the key Lean methods and tools and their applications to improve personal effectiveness, value creation and waste elimination
3. Identify ways to develop “Kaizen eyes” to look for improvement opportunities
4. Describe the various Lean roles
CONTENTS
1. Introduction to Lean Thinking
2. Key Concepts of Lean Thinking
3. Overview of Lean Methods & Tools
4. Ways to develop "Kaizen Eyes"
5. Lean Roles
6. Sustaining a Lean Culture
To download this complete presentation, please visit: http://www.oeconsulting.com.sg
Steven Wilson has over 20 years of experience in financial services, including expertise in tax reporting, regulatory issues, and system enhancements. He has held several roles at SunGard Asset Arena Transfer Agency, including Senior Business/Quality Analyst, providing support to 4 clients. Currently he assists clients, manages projects and disaster recovery exercises, and acts as a key point of contact.
Optimizing Materials Handling on the Cheap: How to Lean your Workflowsloriayre
The document provides an overview of Lean methodology for optimizing materials handling workflows. It defines Lean as focusing on delivering the most value to customers while using the fewest resources. The document discusses key Lean concepts like value streams, value-added activities, waste, and the PDCA continuous improvement cycle. It also provides tips for applying Lean tools like value stream mapping, process mapping, visual management systems, and the "five S's" for efficiency. The overall summary is that Lean aims to streamline workflows and eliminate waste through empowering staff to systematically analyze and improve processes.
This document discusses project scope management. It begins with an agenda that outlines key topics like why manage project scope, defining project and product scope, and processes for planning, collecting requirements, defining, validating, and controlling scope. It then defines each process in more detail, providing inputs, tools and techniques, and outputs for planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. It also discusses the differences between project and product scope, and defines scope creep and gold plating, providing examples of each.
How to Capture Better Business Requirements in Software ProjectsGabor Schönekker
When a software project gets off the rails in most cases the blame is on inaccurate business requirements.
There is no difference between Traditional or Agile projects. If business requirements were not captured correctly the project is doomed to fail before it even started.
I put together a slide deck on structuring, improving the requirements gathering process to ensure that everything is ready to start the delivery of the project.
Another slide deck will follow describing useful methodologies, techniques to ease the process.
The importance of managing process and requirementsJeff Herz
The document discusses the importance of managing processes and requirements for projects. It states that projects often begin without clearly defining objectives or requirements, leading to wasted time and costs from reworking functionality. Proper requirements gathering and documentation in the areas of business, functional, and technical requirements can help ensure projects are successful. This includes defining requirements, processes, designs, and getting stakeholder approval before development begins. Managing requirements is likened to building a house with proper blueprints rather than starting construction without plans.
INGINIX Systems Corporation is a privately held company founded in 2002 that provides project and vendor management software. Their software allows users to manage work orders, vendors, customers, projects, sites and assets in one centralized system. Key benefits of their software include increased control over projects, reduced costs, improved transparency and reporting, and increased capacity for project managers. Their software solution is used across industries like retail, deployment, services, healthcare, and communications to streamline project management and vendor coordination.
The document summarizes an intern's end of assignment report at Eaton Corporation in Waukesha, Wisconsin. Over the course of the internship, the intern assisted with an ISO audit to receive less than 3 findings, disposed of expired paint while updating inventory records, updated lead times for vendors in the system, implemented digital printing to reduce decal lead times, and designed a new layout for the paint shed. The intern gained experience with inventory management, purchasing, and continuous improvement systems and processes during plant tours and projects.
The document discusses how AAA implemented a service catalog to improve their business processes and customer experience. It describes how AAA was facing issues with inconsistent and inefficient service request fulfillment. They implemented a service catalog to standardize requests into a structured workflow with automated fulfillment steps and communication updates. This provided benefits like reduced costs, increased efficiency and consistency compared to the previous ad-hoc process.
Agile Network India| Kanban Day @Chennai | Statik | Sreeanand Chandran and Sa...AgileNetwork
This document describes the Systems Thinking Approach to Introducing Kanban (STATIK) methodology. STATIK is a 8 step approach that uses systems thinking principles to connect a Kanban implementation to the needs of the organization. The 8 steps are: 1) Understand what makes the service "fit for purpose", 2) Understand sources of dissatisfaction, 3) Analyze demand and current capability, 4) Map the service delivery workflow, 5) Identify classes of service, 6) Design the Kanban system, 7) Socialize the design and negotiate implementation. Key aspects of the approach include understanding customer criteria for satisfaction, identifying sources of internal and customer dissatisfaction, analyzing historical demand patterns and capability, and using workflow mapping
The document discusses IT managed services and the benefits of a fixed bid model. IT managed services involves outsourcing IT projects and functions to a third party vendor. A fixed bid model provides known costs, deliverables, and a flexible team size. This allows clients to free up time for IT managers and add staff as needed. Benefits include establishing rates with multiple vendors, improved staffing options, reduced project costs and legal obligations. The document cautions that projects require clear definitions and contingencies to avoid potential issues between multiple outsourced vendors. Establishing checkpoints and a post-production support period helps ensure successful delivery and transition of projects.
Code Yellow: Helping operations top-heavy teams the smart wayMichael Kehoe
We will look at the process for Code Yellow, the term we use for this process of "righting the ship," and discuss how to identify teams that are struggling. Through a look at three separate experiences, we will examine some of the root causes, what steps were taken, and how the engineering organization as a whole supports the process.
Eliminate Bottlenecks in Software Development & DeliveryMicro Focus
Great approach demonstrated via slides from a recent @archie_borland @MarkKulak webinar for Borland Software.
Key take-aways:
- Agile is filled with benefits, but has some unintended consequences which “bottleneck” delivery
- The market trend has this getting worse – backed by analysts & customers
- Take practical steps now to overcome with a few key process improvements to eliminate
The frantic pace of change, driven by mobile, cloud and the rise of the consumer, is introducing new levels of complexity to the software industry and forces organizations into more fragmented ways of working. Today's development managers are subjected to constant change that they cannot control, yet must manage, and are responsible for delivering the applications their customers need at an unprecedented scale and pace. To stay relevant and meet customer demand in the face of constant change requires a truly optimized approach.
This document discusses key elements and best practices for effective quality assurance programs in construction contracting. It recommends understanding who controls quality, fulfilling all project requirements, and using process controls as an opportunity for best practices. Specific best practices include having management support, the right people, effective internal inspection procedures, traceability of materials, leveraging technology for data analysis and reporting, reporting key performance indicators, and clear communication. The goal is to implement a systems approach to quality assurance that continuously improves performance.
Keswick Computer Services asked consultants to evaluate their workflow processes for handling customer calls. The consultants observed inefficiencies including bottlenecks between calls and responses, indefinite call handling procedures, and underutilization of engineers. They created process maps of the current and recommended systems. The recommended system included call scripts, job sheets, and assigning calls and progress updates to appropriate engineers. Other recommendations were training call handlers and engineers, and establishing on-site call pricing based on call duration.
This document discusses the journey of a company transitioning from a waterfall development process to an agile development process. Some key points:
- The company initially tried introducing agile in 2012 but did not make much progress until hiring an agile coach in late 2012 and forming an agile champions team in early 2013.
- The transition involved reorganizing teams, training staff in agile practices, and shifting roles like business analysts becoming product owners. It took time for people to adapt to their new roles and responsibilities.
- Challenges included staff adjusting to writing user stories instead of long requirements documents, estimating story points consistently across teams, planning releases, and managing expectations around faster delivery from management.
The document provides Nicole Larsen's contact information and a summary of her projects and training. It lists several projects she has led or participated in relating to IT systems and processes. It also outlines her ongoing training through the International Institute of Business Analysis, covering topics such as documentation, analytical techniques, and activities used for business analysis.
Radical Requirements: Tips For Delivering What They WantRob Bogue
Requirements are the bedrock in the software development process. Here are some tips for creating requirements and recording them in a way that people can use them.
This presentation can be now be downloaded by visiting https://www.thorprojects.com/connect/gifts/presentations/radical-requirements-tips-for-delivering-what-they-want.
The document provides advice on adopting virtual workspaces based on Kyle Davies' experience. It outlines a 6 step process for a successful adoption: 1) Assess the existing environment; 2) Design the architecture and plans; 3) Build the architecture and standard operating environment; 4) Test functionality and applications; 5) Transition users in a phased approach starting with "troublesome" users; 6) Deploy to all users over time. Key recommendations include extensive testing, sizing appropriately based on actual usage rather than averages, phasing rollouts, and having support available during transitions.
This document provides an overview of business process reengineering (BPR). It discusses BPR as fundamentally rethinking and redesigning processes to dramatically improve performance metrics like cost, quality and speed. Six key principles of BPR are outlined, along with the typical steps of selecting processes and teams, understanding the current process, developing a new vision, identifying an action plan, and executing that plan. Phases of a BPR project and examples of organizations that have implemented BPR are also summarized.
Similar to Lean Kanban India 2019 Conference | Thinking Business Agility | Saikat Das (20)
Kanban India 2023 | Ashwinee Singh and Masa Maeda | A Kanban-centric Ecosyste...LeanKanbanIndia
This document describes how a large telecommunications company transformed its enterprise using a Kanban-centric approach. It involved assessing the entire ecosystem, implementing Kanban across technical and non-technical organizations for improved alignment and flow. They started with workshops to establish mindsets and collaboration frameworks, then implemented Kanban boards at the portfolio, program and team levels. This improved visibility, reduced blockers and cycle times. The approach paid attention to both processes and human elements, and benefited the entire organization by maturing practices rapidly and increasing flexibility, flow and value delivery.
Kanban India 2023 | Dilip Mysore Devaraj | Efficient Deployment Flow with Dev...LeanKanbanIndia
The document describes Dilip Mysore Devaraj's presentation on IBM's adoption of a DevSecOps model to enable efficient deployment flows. Some key points:
1) IBM implemented specialized DevSecOps teams using practices like continuous integration/delivery, test automation, infrastructure as code, and security measures across all stages.
2) This approach helped achieve highly secured and rapidly deployable applications through standardized and explicit policies, workflow visualization, and continuous feedback.
3) Benefits included reduced cycle times from 4 weeks to 5 days, near zero production deployment time, and improved customer satisfaction, security, and uptime.
Kanban India 2023 | Renjith Achuthanunni and Anoop Kadur Vijayakumar | DevOps...LeanKanbanIndia
- The document discusses how an engineering team at Epsilon India established a DevOps metrics dashboard to improve their product development flow and quality.
- Key metrics like defects submitted, open defects, time to resolve issues, and time from commit to deploy were visualized. Tiered service level thresholds were also defined.
- Through iterative refinement and embracing continuous improvement (Kaizen), the team improved predictability from 90 to 30 days, and reduced defects and SLA breaches by 30-50% after implementing the dashboard and optimization efforts.
Kanban India 2023 | Ravishankar N | Don’t implement SRE like this!LeanKanbanIndia
This document discusses site reliability engineering (SRE) and how Kanban practices can enable SRE teams. It defines SRE as engineers with both software development and operations expertise who work to create scalable and reliable systems. The document outlines best practices for organizing SRE teams, including having persistent SRE teams integrated with product teams that use Kanban to manage workflows. It highlights how principles like backlog management, work visualization, and limiting work-in-progress can help SRE teams be successful when adopting a Kanban approach.
Kanban India 2023 | Vishal Prasad | Agility in the World of ITES BusinessLeanKanbanIndia
This document describes an experience report of achieving agility with Lean Value Trees. It discusses identifying constraints, removing constraints, and repeating this process to make improvements cross-functional. It outlines setting up a matrix team structure and going through an iterative process of goal setting and alignment, getting to work on measures each day alongside regular work, and retrospective meetings. Lean Value Trees are presented as a way to visualize this approach with the vision, goals, bets, and initiatives. The document encourages getting hands-on experience with this process.
Kanban India 2023 | Seshabhargavan R and Shobha Kumari | Project IgniteLeanKanbanIndia
Project Ignite aims to help new projects get off to the right start by establishing clear objectives, stakeholder engagement, and risk management strategies. It will do this by implementing Kanban practices to track project initiation activities and reduce the cycle time for project setup. This is expected to improve operational efficiency, stakeholder management, and predictability. Kanban is not a project methodology itself but can be used to incrementally improve existing processes.
Kanban India 2023 | Mohit Anand |Continuous Improvement aligned to Business V...LeanKanbanIndia
This document discusses establishing alignment between business and technical objectives using Kanban principles to address common challenges. It proposes adopting Kanban to align engineering OKRs to business OKRs, prioritize work, limit work in progress, visualize work and dependencies, understand measures focused on flow, and continuously improve around flow. A 9-step success model is presented including assessing maturity, agreeing objectives and measures, extracting metric data, setting baselines and goals, and regularly reporting and analyzing metrics to improve. An example from a platform that adopted this model and saw progress reported on agreed key results is provided.
Kanban India 2023 | Sriram Rajagopalan | Using Kanban to Boost Business Agili...LeanKanbanIndia
This document provides an overview of a presentation on using Kanban to boost business agility. The presentation introduces the STEP framework, which focuses on strategic agility, technical agility, execution agility, and portfolio agility. It discusses how Kanban can help maximize value when implemented to support these four areas of business agility. Case studies are used to illustrate how Kanban was previously implemented in a transactional way rather than focusing on business value. The framework aims to operationalize Kanban in a way that better aligns with business objectives and increases agility.
Kanban India 2023 | Jayalatha Ramachandran and Sanjay Adasul | Embracing sim...LeanKanbanIndia
The document describes an organization's implementation of Kanban principles to improve their support workflow. They started by visualizing their current work and processes on a Kanban board. They identified different ticket types and implemented work-in-progress limits to prioritize work. Policies were made explicit to manage workflow. Feedback loops and transparency were introduced by giving all stakeholders access to dashboards. This evolutionary approach reduced lead times by 4x, improved throughput by 2x, increased innovation and client satisfaction, and boosted team morale.
Kanban India 2023 | Mike Burrows | Between Spaces Scopes and Scales What the ...LeanKanbanIndia
This document summarizes Mike Burrows' model of the deliberately adaptive organization. The model presents an organization as having three overlapping spaces - delivery, discovery, and renewal - which are managed through adaptive strategizing, mutual trust building, and relationships across multiple scales. The document discusses how this model can help organizations deal with common problems like structures with poor fit, managing the wrong things in the wrong places, dealing poorly with surprise, and failures of context that disappoint customers.
The document discusses strategies for a Scrum Master's key responsibilities, including applying Kanban concepts to Scrum. It advocates moving beyond meetings-focused workflows to focus on continuous flow. This includes visualizing and improving the flow of work through workflows, eliminating wait times, improving content quality, and implementing entry and exit criteria at workflow steps like "ready", "commit", "done" and "release". The goal is to establish an upstream-downstream connected flow and cadence of delivery to optimize productivity.
Kanban India 2023 | Mahadevan and Rajsekhar | Startup's and Hiccups.pptxLeanKanbanIndia
This document discusses how Kanban practices can help address operational challenges at startups. It notes that startups face limited resources, uncertain demand, competition, funding issues, and team churn. Common reasons for startup failure include no market need, running out of cash, the wrong team, and being outcompeted. Kanban practices like visualization, work-in-progress limits, and feedback loops can help startups prioritize work, align teams, manage flow, and improve collaboratively. Specifically, minimum viable boards for hypotheses flow, information flow, functions flow, and people flow can optimize cash burn and reduce operational chaos. Kanban aims to help startups navigate the unknown through quick decision making.
Kanban India 2023 | Usha Ramaswamy | Kanban Chronicles - A Tale of Plans and ...LeanKanbanIndia
This document summarizes Kanban implementation at an organization with multiple teams across locations. It describes establishing ways of working using Kanban including defining classes of service, cadences, metrics and Kanban boards. An implementation plan involved workshops, trainings, socialization and a pilot with one team. Results included a Kanban starter kit and ongoing journey with frequent releases and evolving ways of working. Key lessons included understanding stakeholders, packaging changes as experiments, aligning on goals, flexibility to tune processes to the team needs, and encouraging experimentation.
Kanban India 2023 | Debbie Siah | Building Agile Communities with Kanban.pptx...LeanKanbanIndia
This document describes how Debbie Siah used Kanban principles to build the Kanban SG community in Singapore. It discusses how the organizers applied the STATIK framework iteratively to identify needs, model workflows, and continuously improve their Kanban board for managing community events. Through this approach, Kanban SG saw increased engagement, volunteers inspired to use Kanban in their work, and the community impact of avoiding duplicated efforts across organizations.
Kanban India 2023 | Vinod and Umesh | Evolution of Supply Chain Management th...LeanKanbanIndia
This document discusses the evolution of supply chain management through the use of systems thinking and new technologies. It provides examples of how operations research models have historically been used for supply chain planning and optimization. Recent developments in machine learning, artificial intelligence, computing power and data availability are driving increased interest in applying these techniques. The document advocates adopting an integrated platform approach and reimagining business processes to fully leverage new technologies. Key considerations for successful transformation include choosing the right use cases, data, talent and change management approach.
Kanban India 2023 | Debopom Sanyal |Do you have the courage to break your sys...LeanKanbanIndia
The document discusses implementing Kanban to improve workflow processes. It begins by describing some typical problems with existing systems like lack of prioritization, long queues and missed deadlines. Implementing Kanban involved defining workflows, limiting work in progress, introducing visual controls and policies. This led to continuous improvement through small experiments, identifying bottlenecks, celebrating wins and building a feedback culture. The results included increased flow efficiency of around 10%, better collaboration and elimination of non-value adding work. The purpose of Kanban is to surface problems and enable continuous design improvements.
Kanban India 2023 | Sudipta Lahiri | Deliver MVV from your Kanban System.ppsm...LeanKanbanIndia
This document provides tips for delivering value from a Kanban system, beginning with the basics. It recommends using the STATIK method to structure the Kanban system and define the workflow. It suggests distinguishing between upstream and downstream work, with upstream focused on clarifying work and removing impediments. Tips include enforcing user work-in-progress limits to improve flow, monitoring card aging to address slippage, conducting meaningful retrospectives, and humanizing work by celebrating individuals and milestones. For software development teams, it recommends following INVEST principles for user stories, automating where possible, and stopping estimating in favor of prioritizing completed work. The overall message is to start with the basics of Kanban and focus on continuous improvement over
Kanban India 2023 |Gopal Devanahalli | Modern Work Management in Healthcare....LeanKanbanIndia
The document discusses opportunities to improve efficiency in India's healthcare system through modern work management practices. It notes that public health infrastructure is below WHO norms and there are disparities in health outcomes across states. While government initiatives like Ayushman Bharat and investments in digital health are positive, the majority of healthcare spending remains out of pocket. There is a shift from communicable to non-communicable diseases. The document outlines challenges like long wait times and identifies areas like appointments, discharges, and chronic disease management where work processes could be streamlined using tools like Kanban. It concludes that healthcare is complex with many stakeholders and there is significant potential to improve patient experience and operations through structural changes and efficiency gains.
Kanban India 2022 | Priyank Pathak |Evangelising Agile Environment - to not l...LeanKanbanIndia
The document discusses reasons why Agile implementations may fail and how to create an environment for Agile success. It suggests that inconsistencies in practices, culture conflicts, resistance to change, skills gaps, and lack of leadership involvement or sponsorship support can cause Agile to fail. However, the key factor for success or failure is the environment where Agile is being implemented, which can be complex, complicated or chaotic. Elements like governance, education, inclusion, cooperation, information flow and developing a growth mindset are proposed to establish an environment that enables Agile to succeed.
Kanban India 2022 | Poornima V | Bringing Agile to schoolsLeanKanbanIndia
Agile Shaala is a month-long program that aims to teach Agile principles and practices. The program includes daily sessions that cover topics like Scrum, Kanban, testing, continuous integration and delivery. Participants work on hands-on exercises and real-world scenarios to gain experience applying Agile concepts.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
Lean Kanban India 2019 Conference | Thinking Business Agility | Saikat Das
1. Driving Business Agility And Use Of Kanban
Saikat Das
Associate Director – Cognizant (Digital Engineering
Linkedin - https://in.linkedin.com/in/saikatdas16
Twitter - @dsaikats
2. BUSINESS AGILITY is the capacity
and willingness of an organization
to adapt to, create, and leverage
change for their customer’s benefit
The purpose of this model is to show
what organization strive for and how to
get started.
These are essential building blocks for
agile organizations.
This work is licensed by the Business Agility Institute under a Creative Commons Attribution-ShareAlike 4.0 International License
3. • Create Psychological Safety
• Change Incentive Schemes
• Refocus Talent Acquisition
• Understand Agile Governance
• Represent the Customer
• Ensure Transparency of Information
• Adopt Agile Procurement
• Develop Agile Contracts
• Onboard Partners
Relationship
• Understand Your Customer
• Develop Customer Journeys
• Build Trust
This work is licensed by the Business Agility Institute under a Creative Commons Attribution-ShareAlike 4.0 International License
4. • Develop an Agile Mindset
• Build Empathy
• Delegate Outcomes
• Communicate the Greater
Purpose
• Charter the Team
• Gain Buy-In
• Set a Clear Market Vision
• Emergent Strategy
• Market Creating Innovations
This work is licensed by the Business Agility Institute under a Creative Commons Attribution-ShareAlike 4.0 International License
5. • Say “I Don’t Know”
• Celebrate Failure & Learning
• Shorten Feedback Loops
• Adopt Agile Techniques
• Automate Repetitive Work
• Measure Quality of Outcomes
• Give Authority
• Align to Outcomes
• Create Autonomy
This work is licensed by the Business Agility Institute under a Creative Commons Attribution-ShareAlike 4.0 International License
6. • Create Value Delivery Teams
• Maintain Continuity of Ownership
• Create Stable Teams
• Map the Value Streams
• Adopt Agile Methods
• Move to Audit Governance
• Create a Value Stream Network
• Create an Adaptive Portfolio
• Fund Outcomes or Teams
This work is licensed by the Business Agility Institute under a Creative Commons Attribution-ShareAlike 4.0 International License
7. BUSINESS
CONTEXT
Case Study: Business Agility
Operation Centre
100000+ Customers
1000+ miles of over head Lines
Primary serving a Key cities in
near vicinity
Handling 100+ Contractors
Staffs
100+ internal Staffs
Customer Service
Engineering & Mainttenance
Work Schedulers
Material Supply
Labour Arrangers
SET OF
TEAMS
8. KEY BUSINESS
DRIVERS
Lack of
Ownership
Improper
Status
Spent
Management
Customer
Satisfaction
No one is responsible for ensuring a job is done
No one communicate work start date to customer
No material Delivery Details and progress
No update from Internal Departments
No consolidate details of effort spent
Complex reconciliation of material spent
No notification of delay or completion to a Customer
Sometime customer has to confirm back to close tickets
9. Changes Done to bring in Agility
Bots and
Automate
Upstream
KANBAN
Business Agility
Initiatives
Application
Conceptualization
Define
Work Stream
Cross Team
Collaboration
Agile
Transformation
Legacy App
Support
New App
Development
Scaling Pilot for
Key Areas
Measurement
Driven
Progression
Reduction of
Response Time
Closed Loop
Customer
Feedback
10. Backlog Intake
Gather Work
Order Detail
Field Action (CONWIP)
CCO calling and check
(WIP)
Case Closure
Worked
Picked
Material
Arrived
Work
Finish
Un-
finished
Finished W O
Updated
Ticket
Closed
EXPEDITED/ EMERGENCY LANE
Entry Criteria:
actual request
validated for
address and
location
Exit Criteria:
Adequate
information
updated
Entry
Criteria:
Adequate
information
available ;SLA
identified
Exit Criteria:
Priority
identified
Entry Criteria:
Details of
requests
available
Exit Criteria:
Estimated and
dependencies
identified/resol
ved. Due Date
Entry Criteria: Estimated,
prioritized, milestone identified,
delivery date identified.
Exit Criteria: All field action tasks
are completed,
Entry Criteria: All
completed field action
tasks
Exit Criteria: All key
cases are called
Entry Criteria: All
successful attended
case
11. Lack of
Ownership
Improper
Status
Effort Spend
Management
Customer
Satisfaction
• Dedicated crews not being pulled
off their jobs
• Schedule adherence of jobs
• The metrics generated out of real
data, better planning
• Field report on Call Closure
• Finish own work 1st and then
based on Bandwidth
• Each department helped
resolving workload and planning
issues
• Schedule jobs for days (Not
weeks)
• Status of work order and work
order tasks.
• Declare job site readiness
• Exposing issues within the
process
• Accountability of the effort waste
• Improper work Allocation
• One person heroism
• Work taken not completed
• No status sent from field
• No across department clarity
• Uninformed work Passing
• Delayed status from site
• Effort spent per call not tracked
• Material used per call not tracked
• Effort Wastages not considered
• Lots of Heroism by one person
• Customer feedback was bad
• Repeat complains of Work not
complete
• CC needs to call Customer
• Reduction in expedites from
escalated complaints.
• Reduction in calls to CCO
• CSAT improvement
• Kanban Board with Work stages
• CONWIP defined for few stages
• Card assigned to individual
• Card are mover across boards
• Track kept based on work type
effort and materials used
• Work loading evenly distributed
• Junior people mentioned
Progress on Business Drivers
12. Lack of
Ownership
Improper
Status
Spent
Management
Customer
Satisfaction
• SPOC Details
• Expertise based info pull-up
• Send Notification for SPOC
• Escalation Matrix
• Improved Work Allocation
• Better Employee Satisfaction
• More Ownership of work
• Planned work handover
• Operational Effciency
• Create list of work orders
• Work order status
• Work order task status
• Customer Feedback and
satisfaction Index per order
• Site Readiness Status
• On Click JIT status report
• Status, SLA and Aging based
follow-ups
• Escalation Metrics for calls
• Effective Service Delivery
• Customer signoff of WO in
Handheld Devices
• Online Notification to rate service
• Capacity based work Allocation
• Effort, Manpower, Time &
material Spent per WO
• Control on wastages
• Tracking of materials used for call
• Expense & Investment Optimized
Field APP – Driving Operational Efficiency
14. Order Card
Types
Order Receiver
Task addition
Resource Manager
Resource Addition
Field engineer
Execution Addition
Customer
Care Review
• Order Type 1
• Order Type 2
• Order Type 3
• Order Type 4
• Resource required
= 4,8, 12, 16
• Location = A, B, C
and D
• Time to be Finished
= 8, 16, 32, 64
Poles
• Steel Pole
• Concrete Pole
• Joist pole
Wires
• New Wires
• Old wires
• Mixed wires
Switches
• Switches/ Receptacles
• GFCI Outlets
• Small/Med Ceiling Fixtures
• Large Exterior Fixture
Others
• service panel box
• beakers in panel
• exterior breaker box
• MCB
Installations
• Install new service panel box
• Install new breakers in panel
• Install exterior breaker box
• Install MCB
Fixtures
• Fix Steel Poles
• Fix Concrete Poles
• Fix Joist Poles
• Rough-in work
Wiring
• Lay New Wiring
• Fix Old wirings
• Fix the new instead of old
damaged
Adjust
• Adjust Switches/ Receptacles
GFCI Outlets
• Adjuat Small/Med Ceiling
Fixtures
• Adjust Large Exterior Fixture
• Work
accepted
• Work
rejected
• Work
Pending
• Work
Reopened
15. Order Type Order Receiver
Task addition
Resource Manager
Resource Addition
Field engineer
Execution Addition
Order Type 1 • Resource required = 4
• Location = A
• Time to be Finished = 8
Poles
• Steel Pole
Wires
• New Wires
Switches
• Switches/ Receptacles
Others
• service panel box
Installations
• Install new service panel box
Fixtures
• Fix Steel Poles
Wiring
• Lay New Wiring
Adjust
• Adjust Switches/ Receptacles GFCI
Outlets
Order Type 2 • Resource required = 8
• Location = A and B
• Time to be Finished = 16
Poles
• Steel Pole
• Concrete Pole
Wires
• Old wires
Switches
• Switches/ Receptacles
• GFCI Outlets
Others
• Service panel box
• Beakers in panel
Installations
• Install new breakers in panel
• Install exterior breaker box
Fixtures
• Fix Steel Poles
• Fix Concrete Poles
Wiring
• Lay New Wiring
• Fix Old wirings
Adjust
• Adjust Switches/ Receptacles GFCI
Outlets
• Adjust Small/Med Ceiling Fixtures
Order Type Details of Done
16. Order Type Order Receiver
Task addition
Resource Manager
Resource Addition
Field engineer
Execution Addition
Order Type 3 • Resource required = 12
• Location = A, B and C
• Time to be Finished = 32
Poles
• Steel Pole
• Concrete Pole
Wires
• Old wires
• Mixed wires
Switches
• Small/Med Ceiling Fixtures
• Large Exterior Fixture
Others
• beakers in panel
• exterior breaker box
• MCB
Installations
• Install new service panel
box
• Install new breakers in
panel
• Install MCB
Fixtures
• Fix Steel Poles
• Fix Concrete Poles
• Fix Joist Poles
Wiring
• Lay New Wiring
• Fix Old wirings
Adjust
• Adjust Small/Med Ceiling
Fixtures
• Adjust Large Exterior
Fixture
Order Type Details of Done
17. Order Type Order Receiver
Task addition
Resource Manager
Resource Addition
Field engineer
Execution Addition
Order Type 4 • Resource required = 16
• Location = A, B, C and D
• Time to be Finished = 64
Poles
• Steel Pole,
• Concrete Pole
• Joist pole
Wires
• New Wires,
• Old wires
• Mixed wires
Switches
• Switches/ Receptacles
• GFCI Outlets
• Large Exterior Fixture
Others
• service panel box
• beakers in panel
• Exterior breaker box
• MCB
Installations
• Install new service panel box
• Install new breakers in panel
• Install MCB
Fixtures
• Fix Steel Poles
• Fix Concrete Poles
• Fix Joist Poles
• Rough-in work
Wiring
• Lay New Wiring
• Fix Old wirings
• Fix the new instead of old
damaged
Adjust
• Adjust Switches/ Receptacles
GFCI Outlets
• Adjust Small/Med Ceiling
Fixtures
• Adjust Large Exterior Fixture
Order Type Details of Done
18. ORDER
RECEIVER
RESOURCE
MANAGER
FIELD
ENGINEER
CUSTOMER
CARE
Flow of the Game – 1st round
1. Pickup pre-made order cards.
2. Add details to the order, as mentioned in the guidelines
3. Write in readable form in the area provide
4. Keep the card in accessible area for next stage
1. Add details to the order, as mentioned in the guidelines
2. Write in readable form in the area provide
3. Review the cards as per stage wise Specification
4. If not complete send the card back to the respective
stage
19. ORDER
RECEIVER
RESOURCE
MANAGER
FIELD
ENGINEER
CUSTOMER
CARE
Flow of the Game – 2nd round
1. Pickup pre-made order
cards.
2. Add a chit with Order
Type and Order # the
Kanban Board
3. Add details to the order,
as mentioned in the
guidelines
4. Write in readable form in
the area provide
5. Keep the card in
accessible area for next
stage
1. Pull the Chit in the
Kanban Board to
current stage
2. Add details to the
order, as
mentioned in the
guidelines
3. Write in readable
form in the area
provide
4. Keep the card in
accessible area for
next stage
1. Pull working Card in
Kanban Board – in
review stage.
2. Review the cards as
per stage wise
Specification
3. Push the card to
Work Done stage
4. If not compelte send
the card back to the
respective stage
5. Add new chit in
Kanban board using
different color
sticky.notes for
defects
1. Pull the Chit in the
Kanban Board to
current stage
2. Add details to the
order, as
mentioned in the
guidelines
3. Write in readable
form in the area
provide
4. Keep the card in
accessible area for
next stage
20. 2 round Rounds (25-30 mins each)
1. Plan 5-10 mins how and who will execute. Setup Kanban Boards
2. Execute for 10 mins
• Work can only be passed on from stage to another based Details Of Done
3. Retro for 5 mins
4. 5 -10 mins Debrief and next planning
• Observe number of Card and type of card done and plan accordingly. Build Predictability.
• Set WIP for each stage.
• Number of unfinished cards at what states.
5. Business Agility Challenge will be added before 2nd . Figure out how to hand
6. Execute for 10 mins
• Work can only be passed on from stage to another based DOD
7. 5 -10 mins Debrief and final learning sharing
Timing:
Activity Time: 55-60 Mins
Materials:
• Marker Pens
• Sketch Pens ( 1 packet per Table)
• Sticky notes of 3 or 4 different Colors
• Chart Papers
• Scale
• Transparent Tapes
Exercise Details
21. Order Type = 1
ORDER
RECEIVER
RESOURCE
MANAGER
Order Type = 1
Order Type = 1 Order Type = 1
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
Order #= Order #=
Order #= Order #=
22. Order Type = 1 Order Type = 1
Order Type = 1 Order Type = 1
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
Order #= Order #=
Order #= Order #=
23. Order Type = 2
ORDER
RECEIVER
RESOURCE
MANAGER
Order Type = 2
Order Type = 2 Order Type = 2
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
Order #= Order #=
Order #= Order #=
24. Order Type = 2 Order Type = 2
Order Type = 2 Order Type = 2
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
Order #= Order #=
Order #= Order #=
25. Order Type = 3
ORDER
RECEIVER
RESOURCE
MANAGER
Order Type = 3
Order Type = 3 Order Type = 3
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
Order #= Order #=
Order #= Order #=
26. Order Type = 3 Order Type = 3
Order Type = 3 Order Type = 3
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
Order #= Order #=
Order #= Order #=
27. Order Type = 4
ORDER
RECEIVER
RESOURCE
MANAGER
Order Type = 4
Order Type = 4 Order Type = 4
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
ORDER
RECEIVER
RESOURCE
MANAGER
Order #= Order #=
Order #= Order #=
28. Order Type = 4 Order Type = 4
Order Type = 4 Order Type = 4
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
FIELD
ENGINEER
CUSTOMER
CARE
Order #= Order #=
Order #= Order #=
29. Did you get following Learnings
• Understanding the steps to complete the order working with various line of service/ business
preparing the jobcard and visualize the hand-off’s via the use of Kanban squares (Visualizing the
Work).
• Discussing what happens when we try to do too much work at once (Limiting WIP).
• Identifying where the bottlenecks are occurring in the process using metrics (Kaizen).
• Experiment with alternate ways of doing the work and observing that as we improve, the bottleneck
moves around the process (Understanding the Whole).
• Demonstrating how certain individuals will become more confident with their task and becoming
more productive (Managing Specialization).
• Using Standard Work to help reveal problems.