Forgetting to Drain The Swamp + Other Lessons of Running a Creative BusinessDoug Eymer
As a creative professional, know that at some point, during your professional career (through either desire or necessity) you will have the opportunity to “strike out on your own”. These are some lessons that I have learned during my 30 year career.
Measuring and Managing the Social Context of TeamsBarbara Walton
It is possible to measure and manage the social context of teams to minimize the risk of failure resulting from lack of trust and/or drama across relationships.
Back from Red - How to assess the health of your projectTorsten Koerting
Learn how to assess the health of your project besides the day-to-day status. Look into all specific areas of project management that need to be addressed (such as risk, quality, communication, team building, vendor management, stakeholder management) and look into specific areas of your project (eg. for a software development project) including requirements analysis, design, development, test and deployment. A tool will be presented to assess the project health and how to use it. We will also discuss how this tool could be adapted for specific work environments and project methods used (a five step process) and, should time permit, a live demo will be given based on a sample project (picked out of the audience).
Webinar on power, leadership and change, for the Strategy, Execution and Leadership meetup, Adelaide, July 2020
For more details on the Strategy, Execution and Leadership meetup, see https://www.meetup.com/StrategyExecutionLeadership/
The document describes an exercise called the "Red Bead Factory" used to demonstrate concepts from quality expert W. Edwards Deming. In the exercise, participants take on roles in a simulated factory producing beads, with some beads coming out red due to variation. The exercise shows how blaming individual workers is misguided when variation is due to systemic problems. It also illustrates how management should focus on understanding and reducing variation in the system rather than reacting to normal daily fluctuations in performance. Deming's teachings emphasize examining processes for improvement rather than blaming individuals for "special causes" outside their control.
CactusCon 2017 - OODA Loop in life & cyber threat intelligenceDave Eilken
Explanation of John Boyd's OODA Loop for better decision making in life and how we can first take action to gain better visibility with cyber intelligence that will help us make risk decisions.
http://www.cactuscon.com/not-your-grandmas-cti-ooda-loop
Forgetting to Drain The Swamp + Other Lessons of Running a Creative BusinessDoug Eymer
As a creative professional, know that at some point, during your professional career (through either desire or necessity) you will have the opportunity to “strike out on your own”. These are some lessons that I have learned during my 30 year career.
Measuring and Managing the Social Context of TeamsBarbara Walton
It is possible to measure and manage the social context of teams to minimize the risk of failure resulting from lack of trust and/or drama across relationships.
Back from Red - How to assess the health of your projectTorsten Koerting
Learn how to assess the health of your project besides the day-to-day status. Look into all specific areas of project management that need to be addressed (such as risk, quality, communication, team building, vendor management, stakeholder management) and look into specific areas of your project (eg. for a software development project) including requirements analysis, design, development, test and deployment. A tool will be presented to assess the project health and how to use it. We will also discuss how this tool could be adapted for specific work environments and project methods used (a five step process) and, should time permit, a live demo will be given based on a sample project (picked out of the audience).
Webinar on power, leadership and change, for the Strategy, Execution and Leadership meetup, Adelaide, July 2020
For more details on the Strategy, Execution and Leadership meetup, see https://www.meetup.com/StrategyExecutionLeadership/
The document describes an exercise called the "Red Bead Factory" used to demonstrate concepts from quality expert W. Edwards Deming. In the exercise, participants take on roles in a simulated factory producing beads, with some beads coming out red due to variation. The exercise shows how blaming individual workers is misguided when variation is due to systemic problems. It also illustrates how management should focus on understanding and reducing variation in the system rather than reacting to normal daily fluctuations in performance. Deming's teachings emphasize examining processes for improvement rather than blaming individuals for "special causes" outside their control.
CactusCon 2017 - OODA Loop in life & cyber threat intelligenceDave Eilken
Explanation of John Boyd's OODA Loop for better decision making in life and how we can first take action to gain better visibility with cyber intelligence that will help us make risk decisions.
http://www.cactuscon.com/not-your-grandmas-cti-ooda-loop
The Real Lessons of Dr. Deming’s Red Bead FactoryMark Graban
The red bead experiment, created by Dr. Deming, demonstrates how variation exists in any process and is mostly due to common causes within the system, not individual performance. In the experiment, workers try to produce a standard number of beads per trial but often fail due to the inherent variation in the bead drawing process. This shows that blaming individuals and incentivizing performance does not work. The key lessons are that the system, not individuals, is usually the cause of variation, and the focus should be on understanding and reducing common cause variation through systematic improvements.
You are a young researcher on your first independent position. What can you do to get your research work funded? How do you frame your work, find the right partners, address the funding body?
Slides from Andreas Zeller's presentation at the New Faculty Symposium at ICSE 2017, Buenos Aires, Argentina.
This document summarizes key findings from the book "Good to Great" by Jim Collins. It identifies several components that differentiated companies that went from good to great, including level 5 leadership, focusing first on the right people before direction, confronting brutal facts with discipline, and developing a hedgehog concept. It also notes implications for applying these lessons in schools, such as child-focused leadership, prioritizing dedicated faculty, using data to improve, and ensuring technology enhances learning.
This document outlines the topics and activities to be covered in a university course on research design. It includes discussions of research ethics, developing a research plan and time management strategies, qualitative and quantitative research methods, and examples of developing research questions and designs. Students will engage in paired and group exercises to practice developing ethical research protocols, timelines, and questions aligned with different methodological approaches. The goal is to help students understand the logical process of designing sound social science research.
[SIGGRAPH ASIA 2011 Course]How to write a siggraph paperI-Chao Shen
I found this slide on the forum. Thx for the guy that wrote most of the content down for us to review. Hope everyone can learn and think a lot from it!
The document summarizes a presentation about using Theory of Constraints (TOC) and the Russian Theory of Inventive Problem Solving (TRIZ) to speed up product innovation. It discusses how TOC and TRIZ can help break the dilemma between getting products to market quickly while avoiding design compromises. TRIZ is introduced as a methodical process for innovation based on analyzing over 3 million patents to identify patterns of technical evolution and invention. Both TOC and TRIZ provide techniques for resolving contradictions during problem solving without tradeoffs. The presentation aims to show how focusing TRIZ with TOC can rapidly create breakthrough products that satisfy market needs for speed.
Managing Using Intuition and Rules of Thumb 050113MWMantle
This document discusses managing using intuition and rules of thumb. It provides examples of how managers can use intuition, as discussed by Malcolm Gladwell, to make instant conclusions. It also gives numerous "rules of thumb" used by successful managers over time to guide decisions when facts are lacking. These rules of thumb cover topics like communication, hiring, team performance, and managing people. The document advocates that good managers rely on both intuition developed from experience as well as borrowing wisdom from rules of thumb to help make decisions.
Lean is a set of concepts and tools used to maximize value and minimize waste from the customer's perspective. It involves engaging employees in continuous improvement. Examples show how lean helped improve processes in healthcare, manufacturing, and government. Key lean principles include specifying value, mapping the value stream, creating flow, establishing pull, and seeking perfection. Continuous improvement involves small, incremental tests of changes through the Plan-Do-Check-Act cycle.
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Hawkins
With a growing product portfolio and limited capacity to expand in Melbourne, the opportunity arose to build a testing capability in the Dell office in Zhuhai, in the Guangdong province of China. He's been working closely with this growing team of young inexperienced testers for the last two years. Collaborating with this enthusiastic offshore team has been a three-way challenge: dealing with cultural differences, overcoming the language barrier, and challenging the traditional software testing status quo. In this presentation, he will share his personal experience of collaborating with these young testers to develop a performance & creative context-driven testing team - the first time this had been attempted within this office in China. By sharing this experience, he hopes to highlight areas where offshore teams themselves can help those working with them, particularly across significant cultural divides.
On 7th January 2016 Crafitti was invited to deliver a talk on Dr. Reddy's Labs Innovation day on "ALVIS for Innovation and Decision making" The talk was well received and these slides were used.
National Science Foundation I-Corps bay area node 2013 updateStanford University
The document provides an update on Year 1 of the NSF I-Corps Bay Area Node. It highlights that 96 teams are projected to be trained, including 24 NSF teams, 20 Bay Area teams, and 28 healthcare teams. It also notes that 12 local faculty members and a broad range of adjunct faculty, mentors, and TAs have been trained. A new healthcare-specific curriculum is being tested with 28 healthcare teams over 12 weeks. Efforts are underway to create instructional videos and scale the I-Corps program beyond the initial grant period by integrating it into other entrepreneurship programs in the region.
This document discusses TWI Problem Solving, a program developed in the 1950s to help Japanese companies improve problem solving skills. It provides an overview of TWI Problem Solving's origins and compares its approach to the Toyota Production System. The TWI Problem Solving method involves 4 steps: 1) Isolating the problem through evidence analysis, 2) Preparing for solution by analyzing causes, 3) Correcting the problem by implementing solutions, and 4) Checking results and evaluating improvements. The document uses examples to illustrate how each step is applied to solve both mechanical problems and people-related problems.
PI Boot Camp 2015.06 Participant PacketMike Rudolf
This document provides an overview of a performance improvement boot camp. It begins with an icebreaker exercise about problems with the Jefferson Memorial. It then discusses various quality improvement tools and methodologies like DMAICS, Lean Six Sigma, root cause analysis, and process mapping. The document emphasizes defining problems, collecting meaningful data, and using a structured process like DMAICS to drive improvement. It provides examples of how to measure processes, analyze data, identify issues, and implement solutions to optimize performance.
This document discusses Toyota Kata and the Toyota Production System. It explains that Toyota Kata involves an Improvement Kata using the Plan-Do-Check-Act cycle for continuous improvement, guided by a Coaching Kata between a mentor and mentee. The Improvement Kata focuses problem-solving on achieving a target condition through small, measurable steps. The Coaching Kata uses questions to guide the mentee through the problem-solving process. Implementing Toyota Kata and following the Toyota Way can help companies close performance gaps through lean implementation and culture change.
The Toyota Way, also known as Lean, was born from hardship and survival. It is an approach that does not rely on the accidental fortunate circumstance of being in a positive business climate. The system that propelled Toyota to the top of the global automotive industry is designed to succeed in both good times and bad.
Lean thinking fundamentally changes the engagement model between IT and the business, challenging traditional relationships with staff,customers and partners.
This session, presented by a partnership between ThoughtWorks and KM&T, explains the Lean approach to challenges, continuous improvement, productivity, and quality, and how these principles can help you deliver high-value,high-quality software solutions to reduce operational costs, increase profitability, and survive.
With presenters bringing deep expertise from Toyota, Lean and Agile principles, learn how to:
-Identify and eliminate non-value adding work and cost (i.e., waste)
-Build quality into processes to remove unnecessary rework
-Apply Just-in-Time (JIT) principles to software delivery
-Build processes that optimise use of resources and productivity for the entire end-to-end value stream
-Engage everyone to continuously improve your team and practices
-Understand the differences between repetitive processes, product development and software development
Join us to discover how to do more with less.
»
»
»
»
»
»
BRISBANE
Tuesday 17 March, 2009
8am –- 9.30am
Hilton
190 Elizabeth Street, Brisbane
SYDNEY
Tuesday 24 March, 2009
8am –- 9.30am
Hilton
488 George Street, Sydney
MELBOURNE
Tuesday 31 March, 2009
8am –- 9.30am
Marriott
Cnr Exhibition & Lonsdale
Streets, Melbourne
PERTH
Tuesday 7 April, 2009
8am –- 9.30am
Hilton
14 Mill Street, Perth
A light buffet breakfast will be provided *
*
The Toyota Way, also known as Lean, was born from hardship and survival. It is an approach that does not rely on the accidental fortunate circumstance of being in a positive business climate. The system that propelled Toyota to the top of the global automotive industry is designed to succeed in both good times and bad.
Lean thinking fundamentally changes the engagement model between IT and the business, challenging traditional relationships with staff,customers and partners.
This session, presented by a partnership between ThoughtWorks and KM&T, explains the Lean approach to challenges, continuous improvement, productivity, and quality, and how these principles can help you deliver high-value,high-quality software solutions to reduce operational costs, increase profitability, and survive.
With presenters bringing deep expertise from Toyota, Lean and Agile principles, learn how to:
-Identify and eliminate non-value adding work and cost (i.e., waste)
-Build quality into processes to remove unnecessary rework
-Apply Just-in-Time (JIT) principles to software delivery
-Build processes that optimise use of resources and productivity for the entire end-to-end value stream
-Engage everyone to continuously improve your team and practices
-Understand the differences between repetitive processes, product development and software development
Join us to discover how to do more with less.
»
»
»
»
»
»
BRISBANE
Tuesday 17 March, 2009
8am –- 9.30am
Hilton
190 Elizabeth Street, Brisbane
SYDNEY
Tuesday 24 March, 2009
8am –- 9.30am
Hilton
488 George Street, Sydney
MELBOURNE
Tuesday 31 March, 2009
8am –- 9.30am
Marriott
Cnr Exhibition & Lonsdale
Streets, Melbourne
PERTH
Tuesday 7 April, 2009
8am –- 9.30am
Hilton
14 Mill Street, Perth
A light buffet breakfast will be provided *
*
Michael de la Maza gave a presentation on using kanban. He began with an overview of his background and credentials in agile coaching. He then discussed how corporations can become too complicated for humans to understand, and introduced kanban as a way to make companies more effective by making processes simpler and more visual. The presentation covered the history and principles of kanban, how to create an initial kanban board with states and workflows, and examples of electronic and physical kanban boards in use. It concluded with a survey on attendees' plans to implement kanban boards.
Principles of interaction design and user testingJulie Stanford
This document discusses user testing and interaction design. It provides an agenda for the topics, including interaction design and user testing. It discusses elements of good design such as meeting specific goals, making possible actions and the current state visible and easy to understand, following natural mappings, and reducing mental load. It then discusses planning a user test, including defining goals, choosing a target audience, creating tasks/scenarios to test, and refining the test plan. The overall summary is that the document provides guidance on user testing and outlines the key aspects of planning an effective user test to evaluate a prototype or design.
A look at some of the methodologies that have shaped the direction of agile software development. We take a look at Lean Software Development (and the Toyota Production System), the Theory of Constraints and Systems Thinking.
This document outlines a 5-step process for performing a root cause analysis: 1) Define the problem by describing symptoms and what is observed. 2) Collect data on how long the problem has existed, its impact, and different perspectives using a CATWOE analysis. 3) Identify possible causal factors using tools like appreciation, 5 whys, drill down, and cause-and-effect diagrams. 4) Identify the root cause of why the causal factor exists. 5) Recommend and implement solutions to prevent future occurrences, assign responsibilities, and manage risks, using continuous improvement strategies like kaizen. It provides an example task to diagnose a network printing problem at CycleWorld using this root cause analysis model.
http://raskar.info or CameraCulture Wiki Page
How to come up w ideas: Idea Hexagon
How to write a paper
How to give a talk
Open research problems
How to decide merit of a project
How to attend a conference, brainstorm
Strive for Five
Before 5 teams
Be early, let others do details
Beyond 5 years
What no one is thinking about
Within 5 steps of Human Impact
Relevance
Beyond 5 mins of instruction
Deep, iterative, participatory
Fusing 5+ Expertise
Fun, barrier for others
The document discusses the importance of focusing on outcomes over outputs for team performance. It argues that teams perform best when they have a clear, measurable purpose and understand how their work impacts outcomes. This is illustrated through the example of NASA's mission to return Apollo 13's crew safely to Earth. The document advises defining an inspiring outcome-focused problem, establishing baseline metrics and success criteria, and breaking the problem down into sub-problems that each connect to and help achieve the overall outcome. Regularly measuring impacts on outcomes allows teams to prioritize, make data-driven decisions, and stay aligned on a shared vision and purpose.
The Real Lessons of Dr. Deming’s Red Bead FactoryMark Graban
The red bead experiment, created by Dr. Deming, demonstrates how variation exists in any process and is mostly due to common causes within the system, not individual performance. In the experiment, workers try to produce a standard number of beads per trial but often fail due to the inherent variation in the bead drawing process. This shows that blaming individuals and incentivizing performance does not work. The key lessons are that the system, not individuals, is usually the cause of variation, and the focus should be on understanding and reducing common cause variation through systematic improvements.
You are a young researcher on your first independent position. What can you do to get your research work funded? How do you frame your work, find the right partners, address the funding body?
Slides from Andreas Zeller's presentation at the New Faculty Symposium at ICSE 2017, Buenos Aires, Argentina.
This document summarizes key findings from the book "Good to Great" by Jim Collins. It identifies several components that differentiated companies that went from good to great, including level 5 leadership, focusing first on the right people before direction, confronting brutal facts with discipline, and developing a hedgehog concept. It also notes implications for applying these lessons in schools, such as child-focused leadership, prioritizing dedicated faculty, using data to improve, and ensuring technology enhances learning.
This document outlines the topics and activities to be covered in a university course on research design. It includes discussions of research ethics, developing a research plan and time management strategies, qualitative and quantitative research methods, and examples of developing research questions and designs. Students will engage in paired and group exercises to practice developing ethical research protocols, timelines, and questions aligned with different methodological approaches. The goal is to help students understand the logical process of designing sound social science research.
[SIGGRAPH ASIA 2011 Course]How to write a siggraph paperI-Chao Shen
I found this slide on the forum. Thx for the guy that wrote most of the content down for us to review. Hope everyone can learn and think a lot from it!
The document summarizes a presentation about using Theory of Constraints (TOC) and the Russian Theory of Inventive Problem Solving (TRIZ) to speed up product innovation. It discusses how TOC and TRIZ can help break the dilemma between getting products to market quickly while avoiding design compromises. TRIZ is introduced as a methodical process for innovation based on analyzing over 3 million patents to identify patterns of technical evolution and invention. Both TOC and TRIZ provide techniques for resolving contradictions during problem solving without tradeoffs. The presentation aims to show how focusing TRIZ with TOC can rapidly create breakthrough products that satisfy market needs for speed.
Managing Using Intuition and Rules of Thumb 050113MWMantle
This document discusses managing using intuition and rules of thumb. It provides examples of how managers can use intuition, as discussed by Malcolm Gladwell, to make instant conclusions. It also gives numerous "rules of thumb" used by successful managers over time to guide decisions when facts are lacking. These rules of thumb cover topics like communication, hiring, team performance, and managing people. The document advocates that good managers rely on both intuition developed from experience as well as borrowing wisdom from rules of thumb to help make decisions.
Lean is a set of concepts and tools used to maximize value and minimize waste from the customer's perspective. It involves engaging employees in continuous improvement. Examples show how lean helped improve processes in healthcare, manufacturing, and government. Key lean principles include specifying value, mapping the value stream, creating flow, establishing pull, and seeking perfection. Continuous improvement involves small, incremental tests of changes through the Plan-Do-Check-Act cycle.
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Hawkins
With a growing product portfolio and limited capacity to expand in Melbourne, the opportunity arose to build a testing capability in the Dell office in Zhuhai, in the Guangdong province of China. He's been working closely with this growing team of young inexperienced testers for the last two years. Collaborating with this enthusiastic offshore team has been a three-way challenge: dealing with cultural differences, overcoming the language barrier, and challenging the traditional software testing status quo. In this presentation, he will share his personal experience of collaborating with these young testers to develop a performance & creative context-driven testing team - the first time this had been attempted within this office in China. By sharing this experience, he hopes to highlight areas where offshore teams themselves can help those working with them, particularly across significant cultural divides.
On 7th January 2016 Crafitti was invited to deliver a talk on Dr. Reddy's Labs Innovation day on "ALVIS for Innovation and Decision making" The talk was well received and these slides were used.
National Science Foundation I-Corps bay area node 2013 updateStanford University
The document provides an update on Year 1 of the NSF I-Corps Bay Area Node. It highlights that 96 teams are projected to be trained, including 24 NSF teams, 20 Bay Area teams, and 28 healthcare teams. It also notes that 12 local faculty members and a broad range of adjunct faculty, mentors, and TAs have been trained. A new healthcare-specific curriculum is being tested with 28 healthcare teams over 12 weeks. Efforts are underway to create instructional videos and scale the I-Corps program beyond the initial grant period by integrating it into other entrepreneurship programs in the region.
This document discusses TWI Problem Solving, a program developed in the 1950s to help Japanese companies improve problem solving skills. It provides an overview of TWI Problem Solving's origins and compares its approach to the Toyota Production System. The TWI Problem Solving method involves 4 steps: 1) Isolating the problem through evidence analysis, 2) Preparing for solution by analyzing causes, 3) Correcting the problem by implementing solutions, and 4) Checking results and evaluating improvements. The document uses examples to illustrate how each step is applied to solve both mechanical problems and people-related problems.
PI Boot Camp 2015.06 Participant PacketMike Rudolf
This document provides an overview of a performance improvement boot camp. It begins with an icebreaker exercise about problems with the Jefferson Memorial. It then discusses various quality improvement tools and methodologies like DMAICS, Lean Six Sigma, root cause analysis, and process mapping. The document emphasizes defining problems, collecting meaningful data, and using a structured process like DMAICS to drive improvement. It provides examples of how to measure processes, analyze data, identify issues, and implement solutions to optimize performance.
This document discusses Toyota Kata and the Toyota Production System. It explains that Toyota Kata involves an Improvement Kata using the Plan-Do-Check-Act cycle for continuous improvement, guided by a Coaching Kata between a mentor and mentee. The Improvement Kata focuses problem-solving on achieving a target condition through small, measurable steps. The Coaching Kata uses questions to guide the mentee through the problem-solving process. Implementing Toyota Kata and following the Toyota Way can help companies close performance gaps through lean implementation and culture change.
The Toyota Way, also known as Lean, was born from hardship and survival. It is an approach that does not rely on the accidental fortunate circumstance of being in a positive business climate. The system that propelled Toyota to the top of the global automotive industry is designed to succeed in both good times and bad.
Lean thinking fundamentally changes the engagement model between IT and the business, challenging traditional relationships with staff,customers and partners.
This session, presented by a partnership between ThoughtWorks and KM&T, explains the Lean approach to challenges, continuous improvement, productivity, and quality, and how these principles can help you deliver high-value,high-quality software solutions to reduce operational costs, increase profitability, and survive.
With presenters bringing deep expertise from Toyota, Lean and Agile principles, learn how to:
-Identify and eliminate non-value adding work and cost (i.e., waste)
-Build quality into processes to remove unnecessary rework
-Apply Just-in-Time (JIT) principles to software delivery
-Build processes that optimise use of resources and productivity for the entire end-to-end value stream
-Engage everyone to continuously improve your team and practices
-Understand the differences between repetitive processes, product development and software development
Join us to discover how to do more with less.
»
»
»
»
»
»
BRISBANE
Tuesday 17 March, 2009
8am –- 9.30am
Hilton
190 Elizabeth Street, Brisbane
SYDNEY
Tuesday 24 March, 2009
8am –- 9.30am
Hilton
488 George Street, Sydney
MELBOURNE
Tuesday 31 March, 2009
8am –- 9.30am
Marriott
Cnr Exhibition & Lonsdale
Streets, Melbourne
PERTH
Tuesday 7 April, 2009
8am –- 9.30am
Hilton
14 Mill Street, Perth
A light buffet breakfast will be provided *
*
The Toyota Way, also known as Lean, was born from hardship and survival. It is an approach that does not rely on the accidental fortunate circumstance of being in a positive business climate. The system that propelled Toyota to the top of the global automotive industry is designed to succeed in both good times and bad.
Lean thinking fundamentally changes the engagement model between IT and the business, challenging traditional relationships with staff,customers and partners.
This session, presented by a partnership between ThoughtWorks and KM&T, explains the Lean approach to challenges, continuous improvement, productivity, and quality, and how these principles can help you deliver high-value,high-quality software solutions to reduce operational costs, increase profitability, and survive.
With presenters bringing deep expertise from Toyota, Lean and Agile principles, learn how to:
-Identify and eliminate non-value adding work and cost (i.e., waste)
-Build quality into processes to remove unnecessary rework
-Apply Just-in-Time (JIT) principles to software delivery
-Build processes that optimise use of resources and productivity for the entire end-to-end value stream
-Engage everyone to continuously improve your team and practices
-Understand the differences between repetitive processes, product development and software development
Join us to discover how to do more with less.
»
»
»
»
»
»
BRISBANE
Tuesday 17 March, 2009
8am –- 9.30am
Hilton
190 Elizabeth Street, Brisbane
SYDNEY
Tuesday 24 March, 2009
8am –- 9.30am
Hilton
488 George Street, Sydney
MELBOURNE
Tuesday 31 March, 2009
8am –- 9.30am
Marriott
Cnr Exhibition & Lonsdale
Streets, Melbourne
PERTH
Tuesday 7 April, 2009
8am –- 9.30am
Hilton
14 Mill Street, Perth
A light buffet breakfast will be provided *
*
Michael de la Maza gave a presentation on using kanban. He began with an overview of his background and credentials in agile coaching. He then discussed how corporations can become too complicated for humans to understand, and introduced kanban as a way to make companies more effective by making processes simpler and more visual. The presentation covered the history and principles of kanban, how to create an initial kanban board with states and workflows, and examples of electronic and physical kanban boards in use. It concluded with a survey on attendees' plans to implement kanban boards.
Principles of interaction design and user testingJulie Stanford
This document discusses user testing and interaction design. It provides an agenda for the topics, including interaction design and user testing. It discusses elements of good design such as meeting specific goals, making possible actions and the current state visible and easy to understand, following natural mappings, and reducing mental load. It then discusses planning a user test, including defining goals, choosing a target audience, creating tasks/scenarios to test, and refining the test plan. The overall summary is that the document provides guidance on user testing and outlines the key aspects of planning an effective user test to evaluate a prototype or design.
A look at some of the methodologies that have shaped the direction of agile software development. We take a look at Lean Software Development (and the Toyota Production System), the Theory of Constraints and Systems Thinking.
This document outlines a 5-step process for performing a root cause analysis: 1) Define the problem by describing symptoms and what is observed. 2) Collect data on how long the problem has existed, its impact, and different perspectives using a CATWOE analysis. 3) Identify possible causal factors using tools like appreciation, 5 whys, drill down, and cause-and-effect diagrams. 4) Identify the root cause of why the causal factor exists. 5) Recommend and implement solutions to prevent future occurrences, assign responsibilities, and manage risks, using continuous improvement strategies like kaizen. It provides an example task to diagnose a network printing problem at CycleWorld using this root cause analysis model.
http://raskar.info or CameraCulture Wiki Page
How to come up w ideas: Idea Hexagon
How to write a paper
How to give a talk
Open research problems
How to decide merit of a project
How to attend a conference, brainstorm
Strive for Five
Before 5 teams
Be early, let others do details
Beyond 5 years
What no one is thinking about
Within 5 steps of Human Impact
Relevance
Beyond 5 mins of instruction
Deep, iterative, participatory
Fusing 5+ Expertise
Fun, barrier for others
The document discusses the importance of focusing on outcomes over outputs for team performance. It argues that teams perform best when they have a clear, measurable purpose and understand how their work impacts outcomes. This is illustrated through the example of NASA's mission to return Apollo 13's crew safely to Earth. The document advises defining an inspiring outcome-focused problem, establishing baseline metrics and success criteria, and breaking the problem down into sub-problems that each connect to and help achieve the overall outcome. Regularly measuring impacts on outcomes allows teams to prioritize, make data-driven decisions, and stay aligned on a shared vision and purpose.
Important elements of this presentation are better covered in my later presentation titled "What Is Jobs-To-Be-Done?" I recommend that readers start with that.
Are you an innovator, entrepreneur or product manager? Do you want to understand what causes people to purchase, adopt and re-purchase products and services? This presentation gives you an introduction to Jobs-To-Be-Done—a theory of the market that seeks to answer these questions and more.
The document summarizes a meeting of the eSource Stakeholders Group that took place on March 18, 2016 in Silver Springs, MD. The group discussed developing a charter to address challenges of implementing electronic source data capture projects. They agreed to decompose the problem into 5 topics and form teams to identify gaps and solutions for each topic. The teams will work over the next year to produce deliverables including a primer on eSource processes and a white paper on lessons learned from demonstration projects. Regular meetings will integrate the teams' work to advance eSource implementation.
TAPOST Conference 2016 Riga // Better Products Faster: Let's bring the user i...icemobile
"Better products faster: let's bring the user in the userstory"
as presented at TAPOST conference in Riga 2016.
Why is it that everyone knows the importance of frequent user
testing, yet hardly anyone does it? Because user testing often is time
consuming, complex and expensive. It probably doesn’t fit in your
development process and thus feels like extra work.
To feel reassured you tell yourself to test with users once you have
something working, or at the very end of the process. This is strange,
because everybody knows that changing your product late in the
process will increase costs exponentially.
We created a way so that user testing saves time, improves the
quality and doesn’t cost a lot of money. Team driven, pragmatic and
no extra resources needed.
The talk will show how, with only 2 hours every sprint, we focused on
creating better products faster. We would love to share our learnings
and simple DIY tools that let you start user testing with your current
teams tomorrow!
Managing strategically for environmental sustainability complete pptJohn Hulpke
the complete set of slides, Summer 2014 course, Copenhagen Business School. John Hulpke (hulpke@ust.hk) and Cubie Lau (cubie@ust.hk): Managing Strategically for Environmental Sustainability: Lessons from China. DRAFT as of 24 July 2014.
Better products faster: let's bring the user into the userstory // TAPOST_201...Anna Witteman
Why is it that everyone knows the importance of frequent user
testing, yet hardly anyone does it? Because user testing often is time
consuming, complex and expensive. It probably doesn’t fit in your
development process and thus feels like extra work.
To feel reassured you tell yourself to test with users once you have
something working, or at the very end of the process. This is strange,
because everybody knows that changing your product late in the
process will increase costs exponentially.
We created a way so that user testing saves time, improves the
quality and doesn’t cost a lot of money. Team driven, pragmatic and
no extra resources needed.
The talk will show how, with only 2 hours every sprint, we focused on
creating better products faster. We would love to share our learnings
and simple DIY tools that let you start user testing with your current teams tomorrow!
The document describes steps in a problem-solving process including defining the problem, analyzing data to understand the scope and key factors, and identifying what is different between conditions when the problem occurs versus when it does not. A key part of the analysis is creating a table to document known facts about the problem and ask questions to understand differences that could point to root causes and areas for further investigation. The goal is to thoroughly understand the problem before identifying potential solutions.
Chris Soderquist presentation at the 2016 Science of HOPE
Description:
This session will introduce participants to a powerful approach to orchestrating useful learning across difficult boundaries using system dynamics. Through real world examples and interactive exercises, participants will learn how system dynamics can help them gain far more useful leverage when addressing complex, adaptive challenges. Participants will also see how this approach was used in a project funded by the Foundation for Healthy Generations to guide strategic decisions in Washington (and other states) for building community capacity and resilience.
A presentation on mastering key management concepts across projects, products, programs, and portfolios. Whether you're an aspiring manager or looking to enhance your skills, this session will provide you with the knowledge and tools to succeed in various management roles. Learn about the distinct lifecycles, methodologies, and essential skillsets needed to thrive in today's dynamic business environment.
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies™ in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.
Originally presented at XP2024 Bolzano
While agile has entered the post-mainstream age, possibly losing its mojo along the way, the rise of remote working is dealing a more severe blow than its industrialization.
In this talk we'll have a look to the cumulative effect of the constraints of a remote working environment and of the common countermeasures.
12 steps to transform your organization into the agile org you deservePierre E. NEIS
During an organizational transformation, the shift is from the previous state to an improved one. In the realm of agility, I emphasize the significance of identifying polarities. This approach helps establish a clear understanding of your objectives. I have outlined 12 incremental actions to delineate your organizational strategy.
Enriching engagement with ethical review processesstrikingabalance
New ethics review processes at the University of Bath. Presented at the 8th World Conference on Research Integrity by Filipa Vance, Head of Research Governance and Compliance at the University of Bath. June 2024, Athens
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...Alexey Krivitsky
Is Agile dead? It depends on what you mean by 'Agile'. If you mean that the organizations are not getting the promised benefits because they were focusing too much on the team-level agile "ways of working" instead of systemic global improvements -- then we are in agreement. It is a misunderstanding of Agility that led us down a dead-end. At Org Topologies, we see bright sparks -- the signs of the 'second wave of Agile' as we call it. The emphasis is shifting towards both in-team and inter-team collaboration. Away from false dichotomies. Both: team autonomy and shared broad product ownership are required to sustain true result-oriented organizational agility. Org Topologies is a package offering a visual language plus thinking tools required to communicate org development direction and can be used to help design and then sustain org change aiming at higher organizational archetypes.
Sethurathnam Ravi: A Legacy in Finance and LeadershipAnjana Josie
Sethurathnam Ravi, also known as S Ravi, is a distinguished Chartered Accountant and former Chairman of the Bombay Stock Exchange (BSE). As the Founder and Managing Partner of Ravi Rajan & Co. LLP, he has made significant contributions to the fields of finance, banking, and corporate governance. His extensive career includes directorships in over 45 major organizations, including LIC, BHEL, and ONGC. With a passion for financial consulting and social issues, S Ravi continues to influence the industry and inspire future leaders.
A team is a group of individuals, all working together for a common purpose. This Ppt derives a detail information on team building process and ats type with effective example by Tuckmans Model. it also describes about team issues and effective team work. Unclear Roles and Responsibilities of teams as well as individuals.
Ganpati Kumar Choudhary Indian Ethos PPT.pptx, The Dilemma of Green Energy Corporation
Green Energy Corporation, a leading renewable energy company, faces a dilemma: balancing profitability and sustainability. Pressure to scale rapidly has led to ethical concerns, as the company's commitment to sustainable practices is tested by the need to satisfy shareholders and maintain a competitive edge.
Colby Hobson: Residential Construction Leader Building a Solid Reputation Thr...dsnow9802
Colby Hobson stands out as a dynamic leader in the residential construction industry. With a solid reputation built on his exceptional communication and presentation skills, Colby has proven himself to be an excellent team player, fostering a collaborative and efficient work environment.
Comparing Stability and Sustainability in Agile SystemsRob Healy
Copy of the presentation given at XP2024 based on a research paper.
In this paper we explain wat overwork is and the physical and mental health risks associated with it.
We then explore how overwork relates to system stability and inventory.
Finally there is a call to action for Team Leads / Scrum Masters / Managers to measure and monitor excess work for individual teams.
Impact of Effective Performance Appraisal Systems on Employee Motivation and ...Dr. Nazrul Islam
Healthy economic development requires properly managing the banking industry of any
country. Along with state-owned banks, private banks play a critical role in the country's economy.
Managers in all types of banks now confront the same challenge: how to get the utmost output from
their employees. Therefore, Performance appraisal appears to be inevitable since it set the
standard for comparing actual performance to established objectives and recommending practical
solutions that help the organization achieve sustainable growth. Therefore, the purpose of this
research is to determine the effect of performance appraisal on employee motivation and retention.
3. Outline
• Background
• Brief history of Lean
• How to…
• Examples
• Work through the process together (time
permitting)
4. About me….
• Have lived in Eastern WA for 11 years
• Married to my beautiful wife 15 years
• 6 children –one of each
– (Bennett 14, Rachel 11, Elizabeth 9, Emma 8,
Valor 4, Isaac 2)
• Wife homeschools our children
5. Background
• Grew up on the Central Coast of California
• Worked in manufacturing before returning to
college
• Worked in Information Technology during college
• Graduated from CalPoly SLO, BS Industrial
Technology
• 2005 moved to WA to be near family and took a
job at Pacific Northwest National Laboratory in IT
6. Effective Problem Solving
• How did we get here?
• Contexts
– Organization (business, government, etc)
– Home
– Individual
• Beware of legalism! Who can change a
sinner’s heart?
7. “We can't solve problems
by using the same kind of
thinking we used when we
created them.”
Different kind of thinking
-Albert Einstein
8. We need to have the right
expectation!
http://www-
personal.umich.edu/~mrother/Extras.html
9. We need a different kind of thinking
Here is Edward Bear, coming
downstairs now, bump, bump, bump,
on the back of his head, behind
Christopher Robin.
It is, as far as he knows, the only way
of coming downstairs, but
sometimes he feels that there really
is another way, if only he could stop
bumping for a moment and think of
it.
(Alexander Alan Milne, Winnie-the-
Pooh, emphasis, mine)
9
10. Beware… duh moments ahead
• Lean is simple; fix what bugs you!
– Paul Akers –FastCap Ferndale, WA
11. Lean is…
• A way of thinking for creating a highly
effective organization
– Applying methodical problem solving to eliminate
waste and variation to drive quality
– Value Stream focus to flow value to the customer
– Learning through seeing, doing, asking why, being
present and showing respect
– Mike Orzen & Associates, Inc
12. Lean history
12
Kiichiro Toyoda 1937:
Just-In-Time
American meat packers 1890’s:
Moving Disassembly line
French Army 1700’s: Interchangeable parts
Fredrick Taylor 1890’s:
Standard Work
Henry Ford 1926: Mass production
http://www.lean.org/WhatsLean/timeline.cfm
Venetians 1500’s: Standard designs
Standard work stations
14. Where is this useful?
Not useful
• Solution is obvious
• Solution is simple
• Solution sustainable
• Divine general or specific
revelation
Is useful
• Difficult problems
• Many steps
• Hard to sustain
• No shared vision/direction
• To build problem solvers
(and coaches)
Beware of legalism!
Task management Man on the moon
17. Improvement Kata
• Understand the vision/direction (long-range)
• Define “Challenge[s]” (mid-range)
• Grasp the current situation
• Set “Next Target Condition” (short[er]-range)
• Define obstacles and pick one
• Experiment towards “NTC”
20. Vision (long range / lofty goal)
• What does the ideal state look like?
• Where are you trying to go?
• What are you trying to achieve?
• Be specific and how would you measure
success?
22. Improvement kata: Grasp the Current
Situation
http://www-
personal.umich.edu/~mrother/Homepage.htm
l
23. Grasp the Current Situation:
SDCA -> PDCA
Stand
ardize
Do
CheckAdjust
Plan Do
CheckAdjust
PDCASDCA
24. Grasp the Current Situation:
Standardize
• Standard work (not documentation)
– Used to do the work
– Clear steps
– Clear expected outcomes
• OK vs Not-OK?
• Ahead or behind?
– Visual and helpful vs Documentation
25. Grasp the Current Situation
• What data could you look at?
• What data could you create?
– Talley sheets?
– Manual count?
– Sample count?
26. Improvement kata: Set “Next Target
Condition”
http://www-
personal.umich.edu/~mrother/Homepage.htm
l
27. Target Condition Selection: “Circle of
Control”
28
Control
Influence
Concern
“Just do it”
Need
help/input/support
from others
Need leadership
28. Setting “Next Target Condition”
• Increase/Decrease/Stop/Start… __________
• By ______ inches/units/pounds/dollars
• By ________ date
• While [not]/with/without _________
• Tension metrics are important.
32. Experiment towards Next Target
Condition: Where to start?
• Options
– Ease * Impact = Priority
– Market opportunity
– Quickest feedback loop
• What happens if you don’t choose the right
one? –It will wait for you. Substantial
problems don’t often go away on their own.
39. Example: CH Vendor hall
• Distributed team of volunteers and CH ED
• Responsible for:
– Invite previous vendors back
– Recommend new vendors
– Vet vendors
– Select/reject vendors
– Manage vendor orders and special needs
– Create vendor hall layout
– Order vendor hall booths/table/chairs/etc
– Setup, manage and break down the vendor hall
40. Example: CH Vendor hall
• 4 Spreadsheets
• Many Word documents
• Many handoffs
• Very limited visibility
• OK, Not OK not obvious in many cases
41. Example: CH Vendor hall
• Vision: VH process that is visible, removed
duplicated efforts and information where flow,
ownership, status and next steps are obvious.
• Next target condition: reduce to 2 spreadsheets
where information flows and status is visible
• Obstacles: spreadsheets have different purposes
• Experiment: identify unique purposes for each
and how they relate, build mockup and share
with team.
• Result: walked team through vision to
experiment. All agreed it was an improvement
49. Grasp the current situation: Problem Statement
• Problem statement builds
shared vision and experience.
The current _____________
process is, ______________
Which causes, ___________
Which impacts, __________
50
50. 5 Whys: Washington Monument
• Why is the Washington monument deteriorating?
– Harsh cleaning chemicals
• Why is a harsh chemical being used to clean the
Washington monument?
– Harsh chemicals must be used to remove heavy
droppings from birds
• Why are there a lot of droppings from birds?
– There are a lot of birds.
• Why are there a lot of birds?
– There are a lot of spiders. Birds eat spiders.
• Why are there a lot of spiders?
– There are a lot of gnats. Spiders eat gnats
• Why are there a lot of gnats?
– They are attracted to light during dusk time
51
51. 5 Whys: Washington Monument
validation (which causes)
Gnats are attracted to light at dusk which causes
More gnats than at the other monuments
There are more gnats which causes
More spiders than at the other monuments
There are more spiders which causes
More birds than at the other monuments
There are more birds which causes
More droppings than at the other monuments
There are more droppings which causes
Harsh chemicals to be used than at the other
monuments
Harsh chemicals are being used which
causes
Washington Monument to deteriorate.
52
52. 5 Why’s: Countermeasure
• Didn’t shoot/poison the birds
• Didn’t poison the spiders
• Didn’t poison the gnats
• Did turn the lights on ½ hour
later.
53