1. The document discusses designing experiments for organizational learning and describes a workshop on experiment thinking.
2. The workshop covers topics like the improvement kata approach, experiment mindsets, scientific thinking, and conducting experiments through activities, discussions and exercises.
3. The goal is to help participants develop skills in experimentation, hypothesis testing, and learning through failure in order to support innovation and improvement initiatives within their organizations.
Immer mehr Organisationen setzen Flight Levels als ein Denkmodell ein, damit das Unternehmen agil am Markt agieren kann. Dafür braucht es sehr viel mehr, als einfach nur ein paar Teams zu agilisieren. In diesem Vortrag werde ich anhand eines Unternehmens zeigen, wie Flight Levels dafür verwendet werden, teamübergreifende Business Agilität zu erreichen. Ich werde auch darauf eingehen, welche Boards gebaut wurden, um agile Interaktionen zwischen den Teams zu etablieren und wie sich die Arbeit über die Boards bewegt, damit strategisches Alignment in der gesamten Organisation erreicht wird.
Slides as presented at the Lean Agile London / Lean Agile Global meetup, Oct. 20, 2022 (https://www.linkedin.com/feed/update/urn:li:activity:6989216827318882304/)
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
The 8 Stances of a Transformational LeaderMatthew Philip
Patterned after the popular "Eight Stances of a Scrum Master," this talks introduces the eight stances -- "mental or emotional positions adopted with respect to something" -- of leaders at all levels who want to enable high-performing people, teams and organizations. To improve organizational outcomes, the eight stances are aimed at:
- Reducing friction to allow teams to do what they do best
- Fostering a learning environment to enable high performance, mastery and innovation
- Creating aligned autonomy to scalably connect strategy to action
20220607 Introduction to Flight LevelsCraeg Strong
The Flight Levels framework represents a breakthrough achievement in the Agile community, finally living up to the promise of true Business Agility. It does this by encompassing every part of the organization and encouraging participation at every level, across all disciplines. The flight level model recognizes that we need three “viewpoints” for managing our work—flight level three, or the strategy level, flight level two, or the coordination level, and flight level one, or the team level. Flight Levels provide a simple and clear way to connect strategy to execution—facilitating alignment and enabling innovation to occur at every level. Unlike complex and prescriptive frameworks, Flight Levels fit in smoothly with your existing processes like Scrum or Kanban and can be adopted quickly and incrementally.
In this talk I will introduce the flight levels framework, focusing on the problems that it solves and how it differs from other well-known frameworks. Unlike other frameworks, flight levels can be used by the entire company—it is non-IT specific. In addition, flight levels can happily coexist with other Agile frameworks. Rather than specify what teams should be doing, the flight levels framework focuses on helping teams coordinate in value streams and connecting strategy to execution at the portfolio and corporate strategy level. Unlike traditional org charts, the flight level system maps the flow of work and helps us understand the needs for coordination--where we need daily touchpoints and feedback loops. A flight level system consists of a flight level three, or strategy level board mapping corporate strategy to our portfolio of work via OKRAs—(objectives key results and Actions) as well as one or more flight level two boards to help us coordinate the work of multiple teams within a given value stream. These boards all connect to our standard flight level one team-level Scrum or Kanban boards. This talk introduces an exciting new approach to enterprise agility that is neither vague nor overly prescriptive. Participants will come away with a new perspective on scaling Agile that they can apply immediately, no matter which Agile framework(s) their organization is using.
Pre Mortem Retrospectives are a powerful way to prevent project failures before they occur.
Resting on the standard Agile Retrospective format you flash-forward to a date after the scheduled release date and assume that the project has failed miserably
Explains the 3 main phases of Agile Transformation identified by the DACH30 exchange group. Contains a definition of the phases of an agile transformation and some glimpses on the education program.
Immer mehr Organisationen setzen Flight Levels als ein Denkmodell ein, damit das Unternehmen agil am Markt agieren kann. Dafür braucht es sehr viel mehr, als einfach nur ein paar Teams zu agilisieren. In diesem Vortrag werde ich anhand eines Unternehmens zeigen, wie Flight Levels dafür verwendet werden, teamübergreifende Business Agilität zu erreichen. Ich werde auch darauf eingehen, welche Boards gebaut wurden, um agile Interaktionen zwischen den Teams zu etablieren und wie sich die Arbeit über die Boards bewegt, damit strategisches Alignment in der gesamten Organisation erreicht wird.
Slides as presented at the Lean Agile London / Lean Agile Global meetup, Oct. 20, 2022 (https://www.linkedin.com/feed/update/urn:li:activity:6989216827318882304/)
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
The 8 Stances of a Transformational LeaderMatthew Philip
Patterned after the popular "Eight Stances of a Scrum Master," this talks introduces the eight stances -- "mental or emotional positions adopted with respect to something" -- of leaders at all levels who want to enable high-performing people, teams and organizations. To improve organizational outcomes, the eight stances are aimed at:
- Reducing friction to allow teams to do what they do best
- Fostering a learning environment to enable high performance, mastery and innovation
- Creating aligned autonomy to scalably connect strategy to action
20220607 Introduction to Flight LevelsCraeg Strong
The Flight Levels framework represents a breakthrough achievement in the Agile community, finally living up to the promise of true Business Agility. It does this by encompassing every part of the organization and encouraging participation at every level, across all disciplines. The flight level model recognizes that we need three “viewpoints” for managing our work—flight level three, or the strategy level, flight level two, or the coordination level, and flight level one, or the team level. Flight Levels provide a simple and clear way to connect strategy to execution—facilitating alignment and enabling innovation to occur at every level. Unlike complex and prescriptive frameworks, Flight Levels fit in smoothly with your existing processes like Scrum or Kanban and can be adopted quickly and incrementally.
In this talk I will introduce the flight levels framework, focusing on the problems that it solves and how it differs from other well-known frameworks. Unlike other frameworks, flight levels can be used by the entire company—it is non-IT specific. In addition, flight levels can happily coexist with other Agile frameworks. Rather than specify what teams should be doing, the flight levels framework focuses on helping teams coordinate in value streams and connecting strategy to execution at the portfolio and corporate strategy level. Unlike traditional org charts, the flight level system maps the flow of work and helps us understand the needs for coordination--where we need daily touchpoints and feedback loops. A flight level system consists of a flight level three, or strategy level board mapping corporate strategy to our portfolio of work via OKRAs—(objectives key results and Actions) as well as one or more flight level two boards to help us coordinate the work of multiple teams within a given value stream. These boards all connect to our standard flight level one team-level Scrum or Kanban boards. This talk introduces an exciting new approach to enterprise agility that is neither vague nor overly prescriptive. Participants will come away with a new perspective on scaling Agile that they can apply immediately, no matter which Agile framework(s) their organization is using.
Pre Mortem Retrospectives are a powerful way to prevent project failures before they occur.
Resting on the standard Agile Retrospective format you flash-forward to a date after the scheduled release date and assume that the project has failed miserably
Explains the 3 main phases of Agile Transformation identified by the DACH30 exchange group. Contains a definition of the phases of an agile transformation and some glimpses on the education program.
Lean Portfolio Strategy Part 2: Shifting from Imitation to Real LPM - The Mov...Cprime
Download the associated webinar: https://www.cprime.com/resource/webinars/lean-portfolio-strategy-part-2-shifting-from-imitation-to-real-lpm-the-move-to-true-value-streams/
Lean Portfolio Management (LPM) is touted as a world-changing paradigm. A shift that promises to boost productivity, time to market, quality, customer satisfaction, revenue, and a host of other vital business metrics. It promises to transform the organization to a leaner, more agile version of itself, primed to innovate effortlessly and outperform its competition at every turn.
Most organizations who have tried to establish LPM find the reality to be more nuanced than that. These companies end up implementing “Imitation LPM” where actions and some process changes may be in place and functioning, but the real promise of LPM- the increased agility and reduced waste- is not occurring.
Real LPM assumes that work is funded by value streams with teams organized around delivery of products and services that are valuable to customers. This is, perhaps, the hardest part of implementing LPM.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In this second of our series, we join Michiko Quinones (Jira Align Consultant) and Jean Dahl (General Manager, Scaled Agility) to explore:
- How to organize around value streams
- Real world examples of organizations who have successfully shifted from imitation value streams to true value streams
- The impact to funding and budgeting cycles
In this slide deck I collected basic things you better to know about Agile and its most popular frameworks:
- Where did Agile come from?
- What is usually implied when people say "we're implementing Agile"?
- When Agile works well?
- Scrum and its basic characteristics
- Typical confusions
- Agile at scale of whole enterprise
- Typical pitfalls and mistakes
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]Matthew Philip
Slides as presented on Dec 8, 2020 at FlowConf organized by Agile Kanban Istanbul. https://www.flowconf.com/
Organizational change often stalls out at departmental boundaries, whether that is IT or another division. How do we help organizations connect vertically and horizontally to realize the outcomes that they have when undertaking large-scale change efforts?
Join this session to learn from a case study of a bank that combined flight levels and metrics to bridge their departmental boundaries and recognize gains not only in software delivery effectiveness but unifying higher-level strategy.
Where can Kanban be embedded in the organizational context? Sounds like an easy question, however, it is not always easy to answer - especially in bigger organizations. In this session I will introduce the Kanban Flight Levels model which provides an overview of the different fields of application of Kanban and helps to understand the implications for the organizational context. Furthermore, the model helps to clarify where to start with your Kanban change initiative: on team level, on the value stream, or on portfolio level - every level has it's own challenges, pros and cons.
This Hands-on Agile webinar addresses the agile maturity and a possible agility assessment of organizations before the start of an agile transition.
Moreover, learn about the survey results what indicates an agile organization, whether agile maturity is a fad, and what the open source project of the ‘Agility Assessment Framework’ is about.
BLOG: https://age-of-product.com/webinar-agile-maturity/
YOUTUBE: Tba.
Data driven coaching - Agile 2016 (troy magennis)Troy Magennis
Team data and dashboards can be misused and cause more pain than results. Having the team run blind to its historical data though is often worse, with solely opinions and gut-feel driving process change. Helping your teams see and understand a holistic balance of their data will give your coaching advice context and encourage team constant improvement through experiments and reflection.
Coaching dashboards are about balancing trade-offs. Trading something your team is great at for something they want (or need) to improve. Having the team complete the feedback loop and confirm than an experiment had the intended impact, will process improvement be continuous and sustainable.
This presentation shows how to expose data to teams in order for them to retrospect productively, determine if a process experiment is panning out as expected, and to vigorously explore process change opportunities. Recent research shows strong relationships of certain metrics to process and practices, and this session demonstrates how these metrics have and can be tied to timely coaching advice.
The real-world dashboards demonstrated in this session show most common problems and how to avoid them with before and after shots and quotes from the teams impacted by them.
In this session you will –
- Learn how you can not only gather data, but use it to improve the process, with examples!
- Learn how your can tie data insights to coaching advice (data driven coaching)
- Learn how you can detect, predict and avoid data gaming and dashboard misuse
- Learn from my mistakes, and mistakes I’ve seen others with real examples of Agile coaching dashboards (good and bad)
Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR Felipe Castro
Slides from my talk during Agile2016. Although we have been using Agile mindset and processes tactically, when it comes to strategy and goal setting the waterfall command&control mindset is still the norm.
Most organizations are still using an annual, waterfall, top-down process to create a static set of goals that conflicts directly with Agile.
This talk shows how to define agile goals using OKR (Objectives and Key Results), the goal setting framework adopted by Google, Twitter, LinkedIn and Dropbox.
Path to Agility: Outcome-Driven Transformation at Lean-Agile-Digital Transfor...Agile Velocity
In this live, online session, David Hawks explored how change agents can help their organizations bypass 5 common transformation pitfalls and accelerate their momentum towards true organizational agility.
Scrum Teams work best when they collaborate with their product owners to continually refine their backlogs. This is, of course, easier to do when teams are small and collocated. In this webinar, Luke Hohmann, from Conteneo, will present a collection of frameworks that support product owners and Scrum Teams working together to refine backlogs in large and/or distributed teams.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
Top 10 challenges faced by the scrum masterDavid Tzemach
The Role of the Scrum Master (SM) is very challenging. SM responsibilities include Coaching, Training and facilitating both Agile practices and Spirits. In this Presentation, I will review some of the challenges faced by the Scrum Master during his day-to-day activities.
The Agile Manifesto includes 12 key principles that define what it means to “be Agile.” One of those principles states that “the best architectures, requirements, and designs emerge from self-organizing teams.”
But what exactly is a self-organizing team? How do you create one? And why is having one so important to creating an Agile environment?
No (Lab) Jacket Required: Designing Experiments for Learning [2019 Flowcon]Matthew Philip
Slides as presented during the workshop with Karl Scotland at Flowcon, Paris, Dec. 12, 2019. https://www.flowcon.fr/
Hypothesis-Driven Development is thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved, so we need to know how to design and run experiments properly.
This session helps participants understand the importance of using experiments to help teams and organizations learn and improve, while giving hands-on practice in designing experiments to yield measurable evidence for that learning. We’ll even play a couple of inductive-logic games to get us in the mindset of how to write tests to validate – and invalidate – our hypotheses in order to acquire knowledge.
Whether you’re in product development or organizational improvement, for those wanting to move from projects to experiments in the quest of continuous learning and evolutionary improvement, this session will provide the tools and mindset for going beyond simply calling something an experiment, to conducting experiments with the proper rigor to maximize learning.
Lean Portfolio Strategy Part 2: Shifting from Imitation to Real LPM - The Mov...Cprime
Download the associated webinar: https://www.cprime.com/resource/webinars/lean-portfolio-strategy-part-2-shifting-from-imitation-to-real-lpm-the-move-to-true-value-streams/
Lean Portfolio Management (LPM) is touted as a world-changing paradigm. A shift that promises to boost productivity, time to market, quality, customer satisfaction, revenue, and a host of other vital business metrics. It promises to transform the organization to a leaner, more agile version of itself, primed to innovate effortlessly and outperform its competition at every turn.
Most organizations who have tried to establish LPM find the reality to be more nuanced than that. These companies end up implementing “Imitation LPM” where actions and some process changes may be in place and functioning, but the real promise of LPM- the increased agility and reduced waste- is not occurring.
Real LPM assumes that work is funded by value streams with teams organized around delivery of products and services that are valuable to customers. This is, perhaps, the hardest part of implementing LPM.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In this second of our series, we join Michiko Quinones (Jira Align Consultant) and Jean Dahl (General Manager, Scaled Agility) to explore:
- How to organize around value streams
- Real world examples of organizations who have successfully shifted from imitation value streams to true value streams
- The impact to funding and budgeting cycles
In this slide deck I collected basic things you better to know about Agile and its most popular frameworks:
- Where did Agile come from?
- What is usually implied when people say "we're implementing Agile"?
- When Agile works well?
- Scrum and its basic characteristics
- Typical confusions
- Agile at scale of whole enterprise
- Typical pitfalls and mistakes
Metrics at Every (Flight) Level [2020 Agile Kanban Istanbul FlowConf]Matthew Philip
Slides as presented on Dec 8, 2020 at FlowConf organized by Agile Kanban Istanbul. https://www.flowconf.com/
Organizational change often stalls out at departmental boundaries, whether that is IT or another division. How do we help organizations connect vertically and horizontally to realize the outcomes that they have when undertaking large-scale change efforts?
Join this session to learn from a case study of a bank that combined flight levels and metrics to bridge their departmental boundaries and recognize gains not only in software delivery effectiveness but unifying higher-level strategy.
Where can Kanban be embedded in the organizational context? Sounds like an easy question, however, it is not always easy to answer - especially in bigger organizations. In this session I will introduce the Kanban Flight Levels model which provides an overview of the different fields of application of Kanban and helps to understand the implications for the organizational context. Furthermore, the model helps to clarify where to start with your Kanban change initiative: on team level, on the value stream, or on portfolio level - every level has it's own challenges, pros and cons.
This Hands-on Agile webinar addresses the agile maturity and a possible agility assessment of organizations before the start of an agile transition.
Moreover, learn about the survey results what indicates an agile organization, whether agile maturity is a fad, and what the open source project of the ‘Agility Assessment Framework’ is about.
BLOG: https://age-of-product.com/webinar-agile-maturity/
YOUTUBE: Tba.
Data driven coaching - Agile 2016 (troy magennis)Troy Magennis
Team data and dashboards can be misused and cause more pain than results. Having the team run blind to its historical data though is often worse, with solely opinions and gut-feel driving process change. Helping your teams see and understand a holistic balance of their data will give your coaching advice context and encourage team constant improvement through experiments and reflection.
Coaching dashboards are about balancing trade-offs. Trading something your team is great at for something they want (or need) to improve. Having the team complete the feedback loop and confirm than an experiment had the intended impact, will process improvement be continuous and sustainable.
This presentation shows how to expose data to teams in order for them to retrospect productively, determine if a process experiment is panning out as expected, and to vigorously explore process change opportunities. Recent research shows strong relationships of certain metrics to process and practices, and this session demonstrates how these metrics have and can be tied to timely coaching advice.
The real-world dashboards demonstrated in this session show most common problems and how to avoid them with before and after shots and quotes from the teams impacted by them.
In this session you will –
- Learn how you can not only gather data, but use it to improve the process, with examples!
- Learn how your can tie data insights to coaching advice (data driven coaching)
- Learn how you can detect, predict and avoid data gaming and dashboard misuse
- Learn from my mistakes, and mistakes I’ve seen others with real examples of Agile coaching dashboards (good and bad)
Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR Felipe Castro
Slides from my talk during Agile2016. Although we have been using Agile mindset and processes tactically, when it comes to strategy and goal setting the waterfall command&control mindset is still the norm.
Most organizations are still using an annual, waterfall, top-down process to create a static set of goals that conflicts directly with Agile.
This talk shows how to define agile goals using OKR (Objectives and Key Results), the goal setting framework adopted by Google, Twitter, LinkedIn and Dropbox.
Path to Agility: Outcome-Driven Transformation at Lean-Agile-Digital Transfor...Agile Velocity
In this live, online session, David Hawks explored how change agents can help their organizations bypass 5 common transformation pitfalls and accelerate their momentum towards true organizational agility.
Scrum Teams work best when they collaborate with their product owners to continually refine their backlogs. This is, of course, easier to do when teams are small and collocated. In this webinar, Luke Hohmann, from Conteneo, will present a collection of frameworks that support product owners and Scrum Teams working together to refine backlogs in large and/or distributed teams.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
Top 10 challenges faced by the scrum masterDavid Tzemach
The Role of the Scrum Master (SM) is very challenging. SM responsibilities include Coaching, Training and facilitating both Agile practices and Spirits. In this Presentation, I will review some of the challenges faced by the Scrum Master during his day-to-day activities.
The Agile Manifesto includes 12 key principles that define what it means to “be Agile.” One of those principles states that “the best architectures, requirements, and designs emerge from self-organizing teams.”
But what exactly is a self-organizing team? How do you create one? And why is having one so important to creating an Agile environment?
No (Lab) Jacket Required: Designing Experiments for Learning [2019 Flowcon]Matthew Philip
Slides as presented during the workshop with Karl Scotland at Flowcon, Paris, Dec. 12, 2019. https://www.flowcon.fr/
Hypothesis-Driven Development is thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved, so we need to know how to design and run experiments properly.
This session helps participants understand the importance of using experiments to help teams and organizations learn and improve, while giving hands-on practice in designing experiments to yield measurable evidence for that learning. We’ll even play a couple of inductive-logic games to get us in the mindset of how to write tests to validate – and invalidate – our hypotheses in order to acquire knowledge.
Whether you’re in product development or organizational improvement, for those wanting to move from projects to experiments in the quest of continuous learning and evolutionary improvement, this session will provide the tools and mindset for going beyond simply calling something an experiment, to conducting experiments with the proper rigor to maximize learning.
Presented at JavaZone (9th September 2015)
Video available at https://vimeo.com/138863968
The three-act play, the given–when–then BDD triptych, the three steps of the Feynman problem-solving algorithm... a surprising number of things appear to come in threes. This talk walks through — and has some fun with — a number of triples that affect and are found in software development.
Introduction, Terminology and concepts, Introduction to statistics, Central tendencies and distributions, Variance, Distribution properties and arithmetic, Samples/CLT, Basic machine learning algorithms, Linear regression, SVM, Naive Bayes
Scientific Thinking for Agile teams - TOYOTA KATAAndrea Darabos
The ktatatogrow exercise, originally developed by Mike Rother is a great one to practice in your teams, with managers or boards to develop experimentation and conscious learning. Coupled with some examples of its applicability in a digital context from my last 10 years' of experience as an agile DevOps coach. Read more about our experiments with TOYOTA KATA at leanadvantage.co.uk
Free powerpoint to teach the topics of counting principles and probability contents to elementary school kids aspiring to compete in math contests such as the NLMC and Math Kangaroo
Answer questions Minimum 100 words each and reference (questions.docxnolanalgernon
Answer questions Minimum 100 words each and reference (questions #1-3) KEEP questions WITH ANSWER
1) If we had a multiple number of coin tosses and considered this an experiment, what distribution would this experiment follow and why?
2) Virtually all experiments and studies deal with mutually exclusive outcomes. Why is this important?
3) Random variables are part of probability and statistics! Mutual exclusiveness applies to the definition of this. How?
A minimum of 75 words each question and References (IF NEEDED)(Response #1 – 6) KEEP RESPONSE WITH ANSWER
Make sure the Responses includes the Following: (a) an understanding of the weekly content as supported by a scholarly resource, (b) the provision of a probing question. (c) stay on topic
1) I think my friend would have the wrong idea in my opinion. A coin has two sides and if it is a fair coin, then when it is tossed it will have a 50-50 chance of either being heads or tails. There is nothing that would make it tails more than heads. The odds or probability of it landing on tails over heads is 50-50. There is no way of specifically knowing how many times it would be heads or tails an infinite number of times. It will not always land on heads half of the time nor will it always land on tails half of the time, but there is always the probability that it could.
2) No, she is not correct in her theory on the probability of getting heads in a coin toss. The only two outcomes possible are heads or tails. According to the textbook, “the formula for probability then is the frequency of times an outcome occurs, f(x), divided by the sample space or the total number of possible outcomes” (Privitera, 2018). The frequency (f(x)) divided by the sample size is ½. In other words, there is a probability of getting heads one out of two times. The coins could be flipped multiple times and the chances are still 50/50 of getting heads or tails.
3) Considering that tossing a coin can be considered a random event, fixed event, or possibly have a sample space the outcome may vary. “Probability is the frequency of times the outcome occurs divided by the total number of possible outcomes.” (Privitera, G. J., 2018, p.139) If a friend and I had a single coin toss, I would have to disagree on the likeliness of landing on heads having the advantage. The coin toss is a fixed event and there are only 2 options in a single toss. Heads or tails both have a 50 % chance of being the outcome.
Tossing the coin an infinite number of times would be consist of different variations on probability. The outcome could vary amongst every individual. For instance, my father, my son, and I, all just tossed a quarter 10 times each. I landed heads twice, my father landed heads 6 times and my son landed heads 4 times. Therefore, no outcome was the same. The probability of landing heads in 30 tosses was 12, there for two times out of every 6 tosses. However that is if we added up all 3 sets of 10 tosses otherwise with my tosses the.
Techniques for Effective RetrospectivesProwareness
Every month Prowareness organizes a session called “Mastering Scrum”. In these sessions Scrum Masters share their knowledge about a central theme. On January 19 2012 we focused on Retrospectives.
In these slides we share 15 different ways to gather data and create insights. We hope this will inspire you to have Effective Retrospectives!
Strategy Deployment: Aligning Action to VisionMatthew Philip
Strategy Deployment is any form of organizational improvement in which solutions emerge from the people closest to the problems. This is an example of how to bring about such improvement through fast, focused, collaborative activities like Visioning, X-Matrix and Experiment Canvas.
Stop writing stories, start validating working softwareMatthew Philip
Slides as presented at the 2020 Ágiles Latam Conference.
Abstract:
Barry O’Reilly exhorts today’s leaders to “break the cycle of behaviors that were effective in the past but are no longer relevant in the current business climate, and now limit or may even stand in the way of your success.” After more than two decades of writing, refining, grooming, estimating and documenting user stories, it’s time to unlearn them.
In a vast and sad irony, user stories have become the heavyweight documentation and process that they were meant to replace. This session proposes that we strip away the accrued behaviors and get back to the heart of agile and focus on delivering — and measuring progress by — working software.
No (Lab) Jacket Required: Designing Experiments for Learning [XP2020 Conference]Matthew Philip
Slides as presented at the XP2020 Conference (Copenhagen/Online) by Matthew Philip (Accenture | SolutionsIQ).
Abstract
Hypothesis-Driven Development is thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved, so we need to know how to design and run experiments properly. This workshop session helps participants understand the importance of using experiments to help teams and organizations learn and improve, while giving hands-on practice in designing experiments to yield measurable evidence for that learning. We’ll even play a couple of inductive-logic games to get us in the mindset of how to write tests to validate — and invalidate — our hypotheses in order to acquire knowledge. Whether you’re in product development of organizational improvement, for those wanting to move from projects to experiments in the quest of continuous learning and evolutionary improvement, this session will provide the tools and mindset for going beyond simply calling something an experiment to conducting experiments with the proper rigor to maximize learning.
This 60-minute workshop session helps participants:
understand the importance of using experiments to help teams and organizations learn and improve
gain hands-on practice in designing experiments to yield measurable evidence for that learning
understand how to properly measure outcomes without confirmation bias
https://www.agilealliance.org/xp2020/xp-2020-online-program/industry-and-practice-abstracts/#Philip
From Andon to Yokoten: Japanese for AgilistsMatthew Philip
Slides as presented at the 2020 Lean Agile US conference (https://www.leanagileus.com/schedule-2020).
Kanban, Andon, Kaizen as we are using these words in our English-speaking knowledge workplaces, but what do they mean? The fact that many of these Japanese terms originate in manufacturing complicates matters. We all discuss what they mean and why they are important in knowledge work today and go beyond the simple buzzwords. To help us remember not only the words but, more importantly, the concepts, we all use our own version of the popular Point travelers books so that participants can have a little fun learning.
Slides as presented at the 2019 Prairie DevCon Deliver Conference. http://www.prdcdeliver.com/
Leadership at Every Level: Practices for Aligned Autonomy
What does it mean to have leadership at every level of an organization? How do you create aligned autonomy in your team or organization? This talk connects the philosophy of intent-based leadership with practices that enable you to realize the benefits of aligned autonomy, regardless of where your name is in your org chart. By discovering virtual safety nets and vision balloons, you’ll learn how to pragmatically establish psychological safety and alignment of purpose, two of the core traits of high-performing teams.
No (Lab) Jacket Required [Agile Midwest Conference]Matthew Philip
Slides as presented at the 2019 Agile Midwest Conference.
https://agilemidwest.org
Abstract: Hypothesis-Driven Development is thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved, so we need to know how to design and run experiments properly.
This session helps participants understand the importance of using experiments to help teams and organizations learn and improve, while giving hands-on practice in designing experiments to yield measurable evidence for that learning.
Leadership at Every Level: Practices for Aligned AutonomyMatthew Philip
[Slides from track talk at Lean Agile US 2019]
What does it mean to have leadership at every level of an organization? How do you create aligned autonomy in your team or organization? This talk connects the philosophy of intent-based leadership with practices that enable you to realize the benefits of aligned autonomy, regardless of where your name is in your org chart. By discovering virtual safety nets and vision balloons, you’ll learn how to pragmatically establish safety and alignment of purpose, two of the core traits of high-performing teams.
http://www.leanagileus.com/ #leanagileus19
Portfolio kanban (St. Louis Agile Product Ownership Meetup)Matthew Philip
Slides as presented at the St. Louis Agile Product Ownership Meetup, Dec. 10, 2018. https://www.meetup.com/Agile-Product-Ownership/events/tnhplqyxqbnb/
Thriving (Not Merely Surviving) the First Year: Redesigning the Onboarding Ex...Matthew Philip
Slides as presented at XP2018 Conference, Porto, Portugal in the Agile in Education and Training/Building competence in industry track https://www.agilealliance.org/xp2018/program/
The Service-Delivery Review: The Missing Agile Feedback Loop [2017 Lean Kanba...Matthew Philip
Slides as presented at the Lean Kanban France Conference, 30 Nov 2017. http://2017.leankanban.fr/sessions/the-service-delivery-review-the-missing-agile-feedback-loop/
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
Oprah Winfrey: A Leader in Media, Philanthropy, and Empowerment | CIO Women M...CIOWomenMagazine
This person is none other than Oprah Winfrey, a highly influential figure whose impact extends beyond television. This article will delve into the remarkable life and lasting legacy of Oprah. Her story serves as a reminder of the importance of perseverance, compassion, and firm determination.
Modern Database Management 12th Global Edition by Hoffer solution manual.docxssuserf63bd7
https://qidiantiku.com/solution-manual-for-modern-database-management-12th-global-edition-by-hoffer.shtml
name:Solution manual for Modern Database Management 12th Global Edition by Hoffer
Edition:12th Global Edition
author:by Hoffer
ISBN:ISBN 10: 0133544613 / ISBN 13: 9780133544619
type:solution manual
format:word/zip
All chapter include
Focusing on what leading database practitioners say are the most important aspects to database development, Modern Database Management presents sound pedagogy, and topics that are critical for the practical success of database professionals. The 12th Edition further facilitates learning with illustrations that clarify important concepts and new media resources that make some of the more challenging material more engaging. Also included are general updates and expanded material in the areas undergoing rapid change due to improved managerial practices, database design tools and methodologies, and database technology.
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
4. WHO’STALKINGABOUTEXPERIMENTS?
IN COMPLEX ENVIRONMENTS, YOU CAN’T FOLLOW RECIPES OR CONDUCT DETAILED ANALYSIS
TO UNDERSTAND THE SITUATION. RATHER, YOU MUST EXPERIMENT (PROBE). Cynefin
IMPROVE COLLABORATIVELY, EVOLVE EXPERIMENTALLY. Kanban Method
EACH FEATURE INCLUDES A BENEFIT HYPOTHESIS. SAFe
EXPERIMENT AND LEARN RAPIDLY. Modern Agile
…A CULTURE THAT FOSTERS … CONTINUAL EXPERIMENTATION, TAKING RISKS AND LEARNING FROM FAILURE…
DevOps
PLAN, DO, CHECK (STUDY), ACT Deming
SCALE EXPERIMENTING-LEARNING-ADAPTING-EVOLVING GUIDED BY COMPLEXITY, LEAN AND AGILE.
Generative
Scaling
PIVOTING …. A STRUCTURED COURSE CORRECTION DESIGNED TO TEST … HYPOTHESIS ABOUT THE
PRODUCT, STRATEGY, AND ENGINE OF GROWTH.
Lean Startup
8. Scientific thinking is a skill – a habit – that empowers us to better navigate complexity:
1. Acknowledging that our comprehension is always incomplete and possibly wrong.
2. Assuming that answers will be found by test rather than just deliberation. (You make
predictions and test them with experiments.)
3. Appreciating that differences between a prediction and what actually happens can be a
useful source of learning and adjustment.
WHATISANEXPERIMENTMINDSET?SCIENTIFICTHINKING?
13. - Each round, one player is chosen as the oracle, who has a secret rule for which the
cards must be played. (The oracle does not play any cards.)
- For example: Each card has to be a different color from the card before it.
- Other players lay down cards to discover the pattern. If a player lays down a card
correctly, he or she can try to guess the rule.
OBJECT
— Based on Eleusis Express, which itself is a modification of Robert Abbott’s game Eleusis
14. - The oracle places the pile of cards face down, turns over the top
card, and puts it on the table.
- The player to the left of the oracle goes first, then the play
continues clockwise.
- A player turns the top card from the deck and lays it on the table.
He or she asserts whether it is follows the rule or not, and the
oracle accepts or rejects:
- If the card follows the rule, the card is placed horizontally to
the right of the last card on the mainline.
- If the card does not follow the rule, the card is placed below
the last correct card (it either starts a new sideline or it adds
to a sideline).
- Whenever a player makes a correct assertion, he or she can
guess aloud the rule.
- All cards are played to a central layout that grows as the round
progresses.
- The round ends when a player guesses the rule.
- Ace is 1 (odd), jack is 11 (odd), queen is 12 (even), and king is 13
(odd)
GAMEPLAY
16. SCIENTIFICMETHODANDELEUSISEXPEDITIOUS
Define a question “What is the rule?"
Gather information and resources
(observe)
“This card apparently follows the
rule, this other one doesn’t.”
Form an explanatory hypothesis “The rule is only number cards.”
Test hypothesis by experimenting
(replicating)
“Numbers 1-10 would follow rule, face
cards would not.”
Analyze the data “2 and 6 followed the rule, but 5 did
not.”
Interpret and form new hypothesis “The rule is only even numbers.”
Share results and learnings
19. - Belief -> bet -> [Set of outcomes]
- Belief -> bet ->
- outcome A (probability of likelihood
%)
- outcome B (probability of likelihood
%)
- outcome C(probability of likelihood %)
THINKINGINBETS
Probability of Success
Information 0% 100%
Low
High
A B C
21. REINERTSEN’SFRONT-LOADEDLOTTERYOPTION
OPTION1 OPTION2
Pay $3 to select all three digits at once Pay $1 for the first digit, find out if it is
correct, then choose if you wish to pay
$1 for the second digit, and then
choose if you wish to pay $1 for the
third digit.
5 8 4 5 ? ?
$$$ $ $ $
25. www.katatogrow.com
Conduct
Experiments
to get there
Grasp the
Current
Condition
Establish
your Next
Target
Condition
Get the
Direction or
Challenge
1
2
3
4
A FEW KEY POINTS
• You don't have to reach the overall challenge right away.
• The path is not predictable or straight.
• You experiment to get to the next goal,
which makes it scientific.
27. www.katatogrow.com
Do the entire exercise
without the
puzzle frame
Go ahead and build the
puzzle one time!
Put the Frame Aside
• Take the puzzle out and study the picture.
• Remove the puzzle pieces from the frame.
• Put the frame away.
• Build the puzzle once, without timing it.
28. www.katatogrow.com
Choose a Team Name
Select a Data Recorder
! Write your team name
on the forms in the kit
Select a Timekeeper
! Each gets a stopwatch
THREE THINGS TO DO NEXT:
29. www.katatogrow.com
TODAY'S GROUND RULES
(1) "START Position" =
- Puzzle pieces shuffled in random order
- Pieces face down in one stack
- Hands flat on the table
- No talking, you're ready to go
(2) All Teams Start Together
a. Instructor calls "START"
b. Build the puzzle (talking allowed)
c. Note the elapsed time on your form
(3) Don't Write on the Puzzle
33. www.katatogrow.com
Key Points About:
UNDERSTANDING THE CHALLENGE
• We often face challenges in life.
No need to worry, because you
don't need to get all the way
there right away!
• A challenge often even gives us
a useful sense of direction.
35. www.katatogrow.com
• It's important to understand where
you currently are, before you set
your next goal.
• Don't pull goals randomly out of the
air. A team should feel like its goals
are meaningful.
Key Points About:
GRASPING THE CURRENT CONDITION
37. www.katatogrow.com
• Break a big challenge down into
smaller goals.
• Set an easier and closer goal
that's on the way to your
challenge. When you get there
you can set the next goal.
Key Points About:
ESTABLISHING YOUR NEXT
TARGET CONDITION
38. www.katatogrow.com
What puzzle build
time does your team
want to reach by the
end of today's class?
Conduct
Experiments
to get there
Grasp the
Current
Condition
Establish
your Next
Target
Condition
Get the
Direction or
Challenge
LET'S DEFINE YOUR TEAM'S
NEXT TARGET CONDITION
We can do five (5) rounds of experimenting today
43. www.katatogrow.com
• You never know in advance exactly
how you will achieve a goal.
• We need to test the ideas we have.
A good way to reach a goal is to
experiment rapidly. Try something,
see what happens, and then adjust
based on what you learn.
• To learn from an experiment you
should write down what you expect
and what actually happens, so you
can compare those two things.
Key Points About:
EXPERIMENTING TO GET THERE
44. www.katatogrow.com
HOW WE'LL EXPERIMENT
Three Steps, and 3 Minutes per Experimenting Round
1) Instructor calls "START"
- Build the puzzle
- Note the elapsed time on your form
2) Based on what happened, discuss what
you plan to do next. Write the ideas you
want to test onto the form.
3) Then we’ll ask one team the
reflection questions on the card.
45. www.katatogrow.com
(Before)
Write down the
next ideas you
want to test
(After)
Write in how
much the time
changed
compared to
the last round
(After)
Mark the
elapsed
time
THE EXPERIMENTING FORM
What to record in each round
46. www.katatogrow.com
PLEASE PLAN YOUR FIRST EXPERIMENT
Write the ideas you want to test next
on your 'Experimenting' form
Write down
the ideas you
want to test
48. www.katatogrow.com
-- HAVE YOUR CARD READY --
After each experimenting round we'll ask
one team this pattern of Reflection Questions
49. www.katatogrow.com
-- NEXT EXPERIMENT --
Please get into starting position
• Instructor calls "START"
Build the puzzle
Note the elapsed time on your form
• Teams discuss what they plan to do next
Write ideas you want to test on the form
• Time's up... ask the Reflection Questions!
(Start each round of experimenting on this slide. The 3-minute timer starts on the next slide.)
This
cycle
repeats
51. DEBRIEF:
WHATDIDWELEARN?
WHAT ARE THE FOUR STEPS OF THE IMPROVEMENT KATA?
HOW DID YOU APPROACH THIS CHALLENGE?
WHAT HAPPENED WHEN THINGS DIDN’T GO THE WAY WE THOUGHT THEY WOULD?
WHAT SHORTCUTS DID WE TAKE IN CONDUCTING EXPERIMENTS?
53. - Quickly write a dozen or more outcomes onto sticky notes, spread out in front of you
such that they all can be read easily
STARTWITHOUTCOMES
— Agendashift: Outcome-oriented change and continuous transformation
54. - Start at the bottom right hand corner of your square.
- Carefully choose from your list the strongest single example of an outcome where
there’s an approach you can all see and agree on.
- If you’re not 100% confident in the reliability of the approach or if there’s not complete
consensus that’s ok; choose the closest example you can find.
- Now place that single best example in the bottom right corner.
BOTTOMRIGHT
— Agendashift: Outcome-oriented change and continuous transformation
55. - Select the strongest single example of an outcome where you’re confident that an
expert or some research will determine a good approach.
- As with the first corner, “good” implies confidence that the outcome will be delivered,
and it’s predicated on the availability (by whatever means) of someone who has the
necessary expertise.
TOPRIGHT
— Agendashift: Outcome-oriented change and continuous transformation
56. - Carefully choose the strongest single example of an outcome where there’s no one
right approach – experts will disagree. 10 experts will give you 20 different ideas, and
even though some of them might be really great, typical of this kind of outcome is the
sense that no single idea is sure to get you the whole way to your outcome.
- Much as you might wish it to be otherwise, you couldn’t just delegate this outcome to
an expert and reasonably expect a reliable plan to be laid out for you.
TOPLEFT
— Agendashift: Outcome-oriented change and continuous transformation
57. - Choose the strongest single example of an outcome where no known approach is
immediately apparent.
- Beyond symptomatic fixes (stem the bleeding, put out the fire, etc) you’re not sure that
an expert will help you in the time available. You don’t know which of your ideas will
stick. You don’t know how things will settle down after they have been disrupted –
whether the source of disruption is accidental or deliberate, internal or external. You
don’t know where to start!
BOTTOMLEFT
— Agendashift: Outcome-oriented change and continuous transformation
58. - Now choose another sticky at random – just one.
- Imagine this new sticky being drawn by imaginary lines of force towards the corner
stickies to which it is most similar in terms of the kind of approach.
- It might end up next to one of them, between two, or somewhere towards the middle,
drawn in various degrees towards three or four corners.
YOURNEXTSTICKY…
— Agendashift: Outcome-oriented change and continuous transformation
59. - Now add your remaining stickies one at a time, trying to place them relative to those
you’ve placed already, rearranging as necessary.
- Some will have a strong affinity approach-wise with one of your four exemplars and will
be easy to place near one of the corners. Others will seem to have a natural position
somewhere relative to two or three existing stickies.
- Any that really won’t be placed authentically this way should be arranged in a central
region.
REMAININGSTICKIES
— Agendashift: Outcome-oriented change and continuous transformation
61. CYNEFIN:“HABITAT”
- Allow ideas that are
not useful to fail in
small, contained
and tolerable ways
(Dave Snowden)
- Make decisions in
situations of high
uncertainty.
PROBE
SENSE
RESPOND
SENSE
ANALYZE
RESPOND
SENSE
CATEGORIZE
RESPOND
ACT
SENSE
RESPOND
64. - Done means coded/tested/released (not Validated)
- Releases are celebrated more than user success
- No feature ever fails
- Planning starts with feature ideas
SIGNSOFBLACK-HOLEAGILE
— Elizabeth Ayer
75. • Time-based
• Measurable
• Single variable (Control!)
• Provable (and disprovable) hypothesis
• Psychological safety to fail
• Learning is the outcome
ELEMENTSOFGOODEXPERIMENTS
76. • Company policy to give a bonus to employees who refer new hires
• Implementing SAFe
• A new team-leadership model
• Work-from home policy
• [Your own example from earlier]
HOWWOULDYOUDESIGNTHESEASEXPERIMENTS?
77. SCOTLANDCANVAS
Karl Scotland Ltd Experiment A3 https://availagility.co.uk/templates
Context Our problem is… Actions
Hypothesis We believe we can solve it by… Results
Failure
Rationale We believe this because… Follow-up
Failure
Title: Owner:
Success
Success
To prove/disprove the hypothesis we will…
We will declare success or failure when…
As a result of success or failure we will…
92. Options Trying (2) Validated Key Result
Strategy 1
(limit=1)
Strategy 2
(limit=1)
Strategy 3
(limit=1)
Strategy 4
(limit=1)
Experiments
linked to
outcomes
Each
item on the
board is an
experiment
93. THEEXPERIMENTBOARD
OPTIONS TRYING (2) VALIDATED
Strategy
1
(limit=1)
Strategy
2
(limit=1)
Strategy
3
(limit=1)
Strategy
4
(limit=1)
This experiment solved the problem/
delivered the key result.
Goals can be
expressed as
OKRs, problems
to be solved.
Limit work-in-
progress for each
goal to one
experiment.
Now that we’ve solved the problem
with a previous option, we can trash
this one, maximizing the amount of
work not done.
Limit work-in-progress
across all goals.
Each item on the
board is an A3
Experiment canvas.
The first option
didn’t solve the
problem, so we
pulled in the next
option.
94. TYPESOFFAILURE
Preventable Complex Intelligent
Definition
Deviations from known
process that produce
unwanted outcomes
Unique and novel
combinations of events
and actions that give
rise to unwanted
outcomes
Novel forays into new
territory that lead to
unwanted outcomes
Common Causes
Behavior, skill, attention
deficiencies
Complexity, variability,
novel factors imposed
on familiar situations
Uncertainty,
experimentation, risk
taking
AKA Process deviation System breakdown Unsuccessful trial
Contexts Where Each Is
Most Salient
Production line
manufacturing
Fast-food services
Basic utilities and
services
NASA shuttle program
Aircraft carrier
Nuclear power plant
Drug development
New product design
— Amy Edmondson, The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth
95. DESTIGMATIZINGFAILURE
Traditional Frame Destigmatizing Frame
Concept of Failure Failure is not acceptable.
Failure is a natural by-product of
experimentation.
Beliefs About Effective
Performance
Effective performers don’t fail.
Effective performers produce, learn
from and share the lessons from
intelligent failures.
Goal Prevent failure. Learn fast.
Impact of Frame
People hide failures to protect
themselves.
Open discussion, fast learning and
innovation.
— Amy Edmondson, The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth
96.
97. PRODUCTIVERESPONSESTOFAILURE
Preventable Failure Complex Failure Intelligent Failure
- Training
- Retraining
- Process improvement
- System redesign
- Sanctions, if repeated or
otherwise blameworthy
actions are found
- Failure analysis from
diverse perspectives
- Identification of risk factors
to address
- System improvement
- Failure parties
- Failure awards
- Thoughtful analysis of
results to figure out
implications
- Brainstorming of new
hypotheses
- Design of next steps or
additional experiments
— Amy Edmondson, The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth
105. - 1. Any experiment must be something you can do something about and that you believe
stands a chance of having a positive effect.
- 2. Secondly, it has to be a change with an observable or measurable effect – so that
you can see if the change was good or bad.
- 3. The experiment must be something you believe you can dampen down if it goes
wrong (ie safe to fail) or amplify the effect if it goes well.
SELECTINGSAFE-TO-FAILEXPERIMENTS
—Snowden, D and Boone, M (2007) A leader's framework for decision making, Harvard Business Review
106. - Product Owners: Measurable outcomes from user stories
- Coaches: Impact on people, teams, departments
- Transformation Agents: Evolutionary organizational fitness
- Developers
- Teams: Retrospective actions
- Organizations: Leverage scale by running multiple experiments
WHOCANBENEFITFROMEXPERIMENTS?
108. 1. Eleusis Expeditious and Eleusis Express (https://
availagility.co.uk/resources/games/eleusis-expeditious/)
2.A3 Experiment Canvas from Karl Scotland (https://
availagility.co.uk/)
3.Safe-to-Fail Probes (http://cognitive-edge.com/methods/
safe-to-fail-probes/)
4.How to Fail like a Pro, Freakonomics Radio: 370.
5.Unlearn by Barry O’Reilly
6.Company-wide Agility with Beyond Budgeting, Open
Space & Sociocracy by John Buck and Jutta Eckstein
7. Principles of Product Development Flow by Don
Reinertsen
8.How to Measure Anything by Douglas W. Hubbard
9.pretty much anything from John Cutler
10.Jurgen Appelo: https://management30.com/practice/
celebration-grids/
11.The Surprising Power of Online Experiments (https://
hbr.org/2017/09/the-surprising-power-of-online-
experiments)
12.Online Controlled Experiments: Lessons from Running
A/B/n Tests for 12 years (http://bit.ly/KDD2015Kohavi)
13.Thinking in Bets by Annie Duke
14.How to Implement Hypothesis-Driven Development
(https://barryoreilly.com/how-to-implement-hypothesis-
driven-development/)
15.Beyond the Black Hole: Product Management for
Continuous Delivery, Elizabeth Ayer, FlowCon 2019
16.The Fearless Organization by Amy Edmondson
17.Don’t Be a Ditka, Dan Vacanti (https://www.infoq.com/
presentations/prioritization-scarcity-stress-uncertainty/)
18.Goldratt User Stories (https://yorkesoftware.com/
2018/03/09/goldratt-user-stories/)
19."Online Experimentation at Microsoft" Kohavi et al
(http://stanford.io/130uW6X)
20.Robert Hooke, first Curator of Experiments (https://
royalsociety.org/science-events-and-lectures/2003/
summer-science/mr-hooke/)
21.https://itrevolution.com/the-three-ways-principles-
underpinning-devops/
22.Complexity Thinking Dimitar Bakhardzhiev
23.Mike Burrows, Agendashift
24.Adam Light
25.https://www.katatogrow.com
26.https://docondev.com/blog/2019/11/8/the-experiment-
canvas
27.mattphilip.wordpress.com