Feedback-focussed process improvement (2006)Neil Thompson
This document summarizes a presentation on process improvement for information systems learning from manufacturing methods. It discusses how Toyota achieved success through its Toyota Production System focusing on quality, then global dominance, and now innovation. It compares Toyota's approach to the Theory of Constraints by Eliyahu Goldratt. The presentation will explore how these new manufacturing paradigms can translate to agile methods and process improvement in IT/information systems using examples and thinking tools to facilitate continuous learning and improvement.
Using DynoChem to Inform Experimental Design of Batch Crystallization. Rahn M...Scale-up Systems
The document discusses using modeling software to inform experimental design of batch crystallization processes. It presents two models - Model A acts as a "nucleation detector" to predict peak supersaturation without considering nucleation, while Model B solves the cooling or antisolvent addition curve. Case studies demonstrate how the models were used for optimization, robustness analysis, and scoping of new compounds. The models provide a simple tool to aid experimental design for scientists unfamiliar with crystallization kinetics.
Thinking tools - From top motors through s'ware proc improv't to context-driv...Neil Thompson
This document summarizes Neil Thompson's presentation on applying principles from manufacturing process improvement to software development processes. Some key points:
1. Toyota's production system and product development system emphasize continuous process flow, problem solving, visual controls, and a learning organization to drive quality and innovation.
2. Principles from Toyota, the Toyota Production System, and Eliyahu Goldratt's Theory of Constraints can be applied beyond manufacturing to areas like software development.
3. Analogies will be drawn between manufacturing concepts like value streams, constraints, and critical chains, and how they relate to software development processes and problem solving. The presentation aims to provide simple thinking tools to identify and address constraints in software development lif
Este documento presenta un resumen de 3 oraciones de un trabajo de Scratch realizado por un estudiante en el Colegio Nacional Nicolás Esguerra JM. El trabajo involucra mover objetos como un niño y fantasmas en el programa Scratch, con uno caminando y otro riéndose mientras el otro mira feo.
The document discusses Porter's five forces model for analyzing industry competition. It describes the five competitive forces as the bargaining power of suppliers, the bargaining power of customers, the threat of new entrants, the threat of substitutes, and competitive rivalry between existing players. The model helps analyze the attractiveness of industries, compare competitive situations, and identify options for influencing the competitive forces in a company's favor through strategic actions.
The document discusses how social intelligence and social collaboration can drive social CRM strategies. It provides examples of how Cisco uses social listening, scoring, and profiling to enhance customer and partner experiences across different parts of the customer journey. This includes identifying issues, engaging influencers, launching new campaigns, and improving customer service. Cisco's social CRM approach aims to integrate social data and insights into existing processes to better target, support, and develop relationships with customers and partners.
The document discusses lessons learned from using Cucumber acceptance tests. It describes challenges faced with early attempts at automation that just replicated manual tests, resulting in brittle tests. Collaboration between testers and developers was initially lacking. Over time, the team improved by focusing on executable specifications through behavior-driven development, keeping automated tests clean, DRY and abstracted. They learned test code is also production code. Quality is a team effort requiring collaboration at all stages of development.
The document discusses strategies for effective pair programming. It notes that pairing helps bring novices up to speed, shares knowledge, produces higher quality code faster, and reduces errors. However, pairing is challenging because it requires more work, can be difficult with less experienced developers or those zoning out, and when rapid work is needed or individual focus is required. The document provides tips for making pairing work better such as focusing on the code, arguing briefly then moving on, letting wrong solutions prove themselves, and developing trust and teamwork over time.
The document discusses quality assurance and the software development lifecycle. It emphasizes that quality assurance is a team effort involving developers, testers, product owners, and other roles working together through stages of development, testing, review, and completion. Ensuring quality requires communication, prioritization of issues, and addressing problems that prevent tasks from being marked as done.
This document discusses moving from cooperation to collaboration. It describes collaboration as cooperation plus ensuring all voices are heard, building new solutions, and seeking consensus. Key aspects of collaboration include getting people talking, using techniques like "fist to five" to gauge opinions anonymously, and helping introverts contribute. The document emphasizes that collaboration ultimately requires being open-minded and not clinging to individual ideas.
The document provides examples of using quotation marks to indicate when someone is speaking and examples of using quotation marks to indicate the exact words being spoken. It shows "Very good!" being said by Miss McCrum, "I like sweets!" being said by the little boy, "I am really happy!" being said by the clown, and "I like toys!" being shouted by the little girl.
Feedback-focussed process improvement (2006)Neil Thompson
This document summarizes a presentation on process improvement for information systems learning from manufacturing methods. It discusses how Toyota achieved success through its Toyota Production System focusing on quality, then global dominance, and now innovation. It compares Toyota's approach to the Theory of Constraints by Eliyahu Goldratt. The presentation will explore how these new manufacturing paradigms can translate to agile methods and process improvement in IT/information systems using examples and thinking tools to facilitate continuous learning and improvement.
Using DynoChem to Inform Experimental Design of Batch Crystallization. Rahn M...Scale-up Systems
The document discusses using modeling software to inform experimental design of batch crystallization processes. It presents two models - Model A acts as a "nucleation detector" to predict peak supersaturation without considering nucleation, while Model B solves the cooling or antisolvent addition curve. Case studies demonstrate how the models were used for optimization, robustness analysis, and scoping of new compounds. The models provide a simple tool to aid experimental design for scientists unfamiliar with crystallization kinetics.
Thinking tools - From top motors through s'ware proc improv't to context-driv...Neil Thompson
This document summarizes Neil Thompson's presentation on applying principles from manufacturing process improvement to software development processes. Some key points:
1. Toyota's production system and product development system emphasize continuous process flow, problem solving, visual controls, and a learning organization to drive quality and innovation.
2. Principles from Toyota, the Toyota Production System, and Eliyahu Goldratt's Theory of Constraints can be applied beyond manufacturing to areas like software development.
3. Analogies will be drawn between manufacturing concepts like value streams, constraints, and critical chains, and how they relate to software development processes and problem solving. The presentation aims to provide simple thinking tools to identify and address constraints in software development lif
Este documento presenta un resumen de 3 oraciones de un trabajo de Scratch realizado por un estudiante en el Colegio Nacional Nicolás Esguerra JM. El trabajo involucra mover objetos como un niño y fantasmas en el programa Scratch, con uno caminando y otro riéndose mientras el otro mira feo.
The document discusses Porter's five forces model for analyzing industry competition. It describes the five competitive forces as the bargaining power of suppliers, the bargaining power of customers, the threat of new entrants, the threat of substitutes, and competitive rivalry between existing players. The model helps analyze the attractiveness of industries, compare competitive situations, and identify options for influencing the competitive forces in a company's favor through strategic actions.
The document discusses how social intelligence and social collaboration can drive social CRM strategies. It provides examples of how Cisco uses social listening, scoring, and profiling to enhance customer and partner experiences across different parts of the customer journey. This includes identifying issues, engaging influencers, launching new campaigns, and improving customer service. Cisco's social CRM approach aims to integrate social data and insights into existing processes to better target, support, and develop relationships with customers and partners.
The document discusses lessons learned from using Cucumber acceptance tests. It describes challenges faced with early attempts at automation that just replicated manual tests, resulting in brittle tests. Collaboration between testers and developers was initially lacking. Over time, the team improved by focusing on executable specifications through behavior-driven development, keeping automated tests clean, DRY and abstracted. They learned test code is also production code. Quality is a team effort requiring collaboration at all stages of development.
The document discusses strategies for effective pair programming. It notes that pairing helps bring novices up to speed, shares knowledge, produces higher quality code faster, and reduces errors. However, pairing is challenging because it requires more work, can be difficult with less experienced developers or those zoning out, and when rapid work is needed or individual focus is required. The document provides tips for making pairing work better such as focusing on the code, arguing briefly then moving on, letting wrong solutions prove themselves, and developing trust and teamwork over time.
The document discusses quality assurance and the software development lifecycle. It emphasizes that quality assurance is a team effort involving developers, testers, product owners, and other roles working together through stages of development, testing, review, and completion. Ensuring quality requires communication, prioritization of issues, and addressing problems that prevent tasks from being marked as done.
This document discusses moving from cooperation to collaboration. It describes collaboration as cooperation plus ensuring all voices are heard, building new solutions, and seeking consensus. Key aspects of collaboration include getting people talking, using techniques like "fist to five" to gauge opinions anonymously, and helping introverts contribute. The document emphasizes that collaboration ultimately requires being open-minded and not clinging to individual ideas.
The document provides examples of using quotation marks to indicate when someone is speaking and examples of using quotation marks to indicate the exact words being spoken. It shows "Very good!" being said by Miss McCrum, "I like sweets!" being said by the little boy, "I am really happy!" being said by the clown, and "I like toys!" being shouted by the little girl.