This document discusses thriving under uncertainty using options thinking and lean kanban principles. It describes how projects are often planned optimistically but end up delivering less than expected due to unforeseen variations. It advocates adopting an options mindset to minimize risks and costs from failures while maximizing learning. This involves using techniques like classes of service, probes, enablers and options expiration dates to balance exploration and exploitation. The overall goal is to absorb variations and make projects more anti-fragile by benefiting from disruptions.
Many lean-agile teams are being challenged in their growth path. They are not able to grasp the emergent opportunities that are presented by a changing environment and they cannot overcome the barriers to get to the next level of performance.In this interactive presentation, lean-agile practitioners will learn how resiliency thinking can bring them to the next level. Resilience is the ability to survive, adapt, and even grow amidst disruption. It is the capacity to absorb disturbance without losing (team) identity. While resilience models have been mainly developed n socio-ecological research, we will show how they can drastically enhance lean-agile thinking. We will show how to analyze a team from a resilience perspective using the panarchy model and its adaptive cycles; and we will demonstrate how to improve resiliency through modularity, diversity, and translational leadership.
Participant will leave the session with the insights to bounce back from disruptions.
Rubin agile 2012_strategies_for_porfolio_management.pdfdrewz lin
油
Kenny Rubin gave a presentation on strategies for portfolio management. He discussed optimizing a portfolio to maximize lifecycle profits by focusing on variables like cost of delay, accuracy of estimates over precision, applying an economic filter, and managing project arrival and completion rates. He advocated for establishing work-in-process limits based on team capacity, waiting for complete teams to be available before starting new work, and using marginal economics to determine when to terminate a project.
Henry Simonds of Planet Positive provides sustainability consulting services to businesses. His presentation outlines why businesses should become more sustainable by addressing regulations, costs savings, reputation, and resources. He discusses sustainability measures and certifications. Case studies show how Marks & Spencer, Bowmer & Kirkland, and PWA Unlimited achieved financial benefits and carbon reductions through sustainable practices. The presentation provides guidance on measuring impacts, engaging employees, setting goals and targets, and communicating sustainability efforts.
The document discusses how taking a sustainability approach to business processes can uncover greater efficiencies than a lean approach alone. A sustainability lens considers wider system boundaries and identifies opportunities between different business silos by viewing waste from one process as a potential input for another. Case studies show companies achieving significant cost savings through collaborative sustainability projects across their operations and supply chains. Managing collaboration at scale requires online platforms and communities like those provided by 2degrees.
Estimating the principal of Technical Debt - Dr. Bill Curtis - WTD '12OnTechnicalDebt
油
This study summarizes results of a study of Technical Debt across 745 business applications comprising 365 million lines of code collected from 160 companies in 10 industry segments. These applications were submitted to a static analysis that evaluates quality within and across application layers that may be coded in different languages. The analysis consists of evaluating the application against a repository of over 1200 rules of good architectural and coding practice. A formula for estimating Technical Debt with adjustable parameters is presented. Results are presented for Technical Debt across the entire sample as well as for different programming languages and quality factors.
Three Confluence Deployments That Will Blow You AwayAtlassian
油
There are lots of great Confluence deployment stories. And then there are a few that are just mind-blowing. This session highlights three incredible Confluence deployments that will make your head turn.
Customer Speakers: Nate Nash of BearingPoint, Tim Colson of Cisco, Connie Taylor of Premier Inc
Key Takeaways:
* Incredible Confluence examples
* Innovative uses of a wiki and enterprise collaboration
EclipseCon 2012 talk describing the use of domain specific languages in development; use of Xtext, EMF as DSL tooling. Learned lessons, impact on development process, and some best practices.
The document discusses Discovery Kanban, an approach for managing exploration and exploitation in organizations. It begins by explaining the need for a new management discipline that excels at both exploiting existing business models and exploring new opportunities. Discovery Kanban uses visualization techniques to manage issues, risks, options, actions and other items across the organization. This helps balance incremental improvement with disruptive change. The approach can be customized for large transformation programs or product renewal efforts. Discovery Kanban templates are available online and the conclusion emphasizes that the approach helps organizations develop the dynamic capabilities needed to thrive in uncertain, disruptive business landscapes.
This document discusses using a customer kanban system to improve workflow for a IT maintenance team. Currently, customer lead times vary widely from a few days to over 30 weeks. The team implements a kanban system with work-in-progress limits to visualize and limit work throughout the process. This helps reduce lead times and backlogs by focusing on continuous flow. However, challenges remain in coordinating work between the upstream process of requirements gathering and the downstream fulfillment process. Fully realizing benefits requires collaboration between customers, business users, and the team at each stage of the workflow.
This document discusses using Kanban principles to manage knowledge work and the balance between discovery and delivery. It introduces different types of knowledge work from exploiting existing knowledge to exploring new knowledge. It then discusses using various "Discovery Kanbans" to visualize and limit work-in-progress for ideas, experiments, decisions, and actions to balance upstream discovery with downstream delivery. Different approaches are needed depending on what is known versus unknown in the work.
Key Note - Devlin 2013 - No crystal ball gazing - The Pragmatism of The Kanba...David Anderson
油
The Kanban Method is based in the philosophy of pragmatism. Kanban encourages you to use facts and actual data to make decisions and plans. This approach improves risk management and business outcomes
Key Note - Stop Starting, Start Finishing 2013 - Aligning Creative Work with ...David Anderson
油
time
When it arrived
The document discusses using qualitative risk assessment and Kanban systems to better align creative work with business risks. It provides examples of how to assess different dimensions of risk like urgency, schedule risk, market risk of change, and product lifecycle risk. Dimensions are assessed qualitatively and visualized to provide information on work scheduling. The document also discusses understanding an organization's tolerance for different risks and aligning capabilities with strategies to avoid being "doomed before starting".
Key Note - PMI Congress Poland - The Role of the Project Manager with KanbanDavid Anderson
油
Kanban systems are used to improve service delivery in creative knowledge work. This presentation looks at how use of Kanban affects the role of a project manager. It takes a look at how planning, scheduling, estimating, issue and risk management are affected by adopting Kanban.
"Fitness for Purpose" - Resilience & Agility in Modern BusinessDavid Anderson
油
Understanding "fitness for purpose". A new way to look at market segmentation based on identity. Defining fitness criteria metrics. Sense and respond. Using Kanban Systems to increase service delivery agility. Using the Kanban Method to catalyze and evolve your business to be "fitter for purpose". Making sense of a complex market using clustering of narratives from front-line staff. Remaining resilient through frequent "fitness" reviews
This document provides an overview of Visual Workflow in Salesforce, including common use cases such as call scripts, smart forms, and wizards. It demonstrates how to build a donation/pledge management app from scratch using only Visual Workflow with no code. The presentation emphasizes that Visual Workflow allows users to draw out business processes and logic, interact with data from forms, databases, and external systems, all through a simple drag-and-drop interface. Resources for learning more about Visual Workflow such as online help, forums, and training sessions are also listed.
Talk delivered by Craig Smith at YOW! 2015 in Melbourne, Brisbane and Sydney on 4-10 December 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Discovery Kanban is a synthesis of a number of distinct threads of entrepreneurial thinking --Lean Startup, Kanban, OODA, PCDA, and Optionality--into an approach that helps firms address the challenge of executing and refining proven business models in parallel with exploring options for novel business opportunities. It fosters a management discipline of dual strategies of both exploitation and exploration, delivery and discovery that is applicable at different levels of scale in the organization.
In this presentation we will elaborate on the core principles of Discovery Kanban and some practical examples. We will show how (traditional) Delivery and Discovery Kanban are similar but different. We will discuss several examples of Discovery Kanban systems based on dual strategies and how they catalyze a different change in the organization. We will demonstrate how Discovery Kanban assists the discovery process and the integration of discovery and delivery at the different levels of scale.
Enterprise Services Planning: Defining Key Performance IndicatorsDavid Anderson
油
Defining KPIs for use in Enterprise Services Planning and with Kanban systems. Understanding the difference between KPIs, Improvement Guides, and General Health Indicators. Understanding how KPIs drive behavior such as establishing multiple classes of service. Relating KPIs to evolutionary change. KPIs are Fitness Criteria Metrics with defined threashold values
The document discusses systems for change and creating an effective system of change. It describes different types of change, including planned, retrospective, directed, and evolutionary change. It also discusses different approaches to change, such as using constraints to enable collaboration and experimentation, applying the PDCA (plan-do-check-act) loop for hypothesis-driven change, and combining reflective observation and active experimentation using a Kanban system. The overall goal is to view change as a dynamic system and establish a system of change that incorporates planned change, emergent constraints, and retrospective change to drive measurable yet adaptive organizational change.
Make the invisible visible - Visual management in agile product developmentH奪kan Forss
油
Most of today's knowledge work is almost exclusively done digitally. If you would step into an office and try to observe the process you will most likely find it hard to understand what is really happening. Most of the work is as ones and zeros hidden in many different digital repositories.
To create a common and shared understanding in knowledge work we often need to make the invisible visible.
During this session H奪kan Forss will share his experiences of creating common and shared understanding of the invisible knowledge work using visual management.
Visual Management: Leading With What You Can SeeCraig Smith
油
Presentation by Craig Smith and Renee Troughton delivered at Agile Australia 2013 on 20 June 2013. Using task boards or story walls is a key Agile practice, but are you making the most of it? Visual Management is more than just putting cards on a wall, it is a growing style of management that focuses on managing work only by what you can see rather than reports or paper being shuffled around. Visual Management allows you to understand the constraints in the system, mitigate risks before they become issues, report on progress from the micro to the macro. Visual Management can also be used to demonstrate to customers and clients where the work they care about is at. This presentation is all about taking the management of your work to the next stage of transparency.
Estimation a waste of time master 2013 sdc gothenburg w hp rulestom gilb
油
The document discusses estimation and risk management in software projects. It argues that traditional estimation methods are doomed to fail because they cannot account for uncertainties in requirements, technical solutions, staffing, and sensitivity to small changes. Instead, it proposes principles for dynamic design-to-cost and radical management, including learning in small increments to understand root causes of deviations, prioritizing critical requirements, implementing high-risk ideas early, and applying lessons continuously. The goal is to deliver high value within available resources through an adaptive approach.
How using visibility supports effective decision makingThoughtworks
油
The document discusses how visibility supports effective decision making. It notes that companies need to change how they operate given increased ambiguity and faster pace. Visibility provides better alignment, more frequent results, and leads to better, smaller decisions. However, visibility is difficult due to politics, budgets, and resistance to change. Transparency leads to trust and makes decisions easier by depersonalizing issues and showing connections. To create visibility requires vision, location, introspection, protection, unity, and ongoing investment. The document warns against justifying the status quo and other anti-patterns that prevent effective visibility.
The document discusses resilience and business continuity management. It is authored by an independent management consultant with 20 years experience in IT disaster recovery and business continuity. The consultant defines resilience as the ability to resist impacts and recover operational state after an impact. Key aspects of resilience include robustness, redundancy, agility and adaptability. Vulnerability is identified as the opposite of resilience. The document also discusses uncertainty, risk, wicked problems, the importance of moving beyond just compliance to developing real response capabilities, and finding elegant solutions.
Are you involved in the development and introduction of hardware technology products to the market? Would you like to understand how to assess a products feasibility for moving into development?
During this session, Micah Bongberg, the President of Annuvia and his development partners will share their experiences in determining the feasibility of Annuvias innovative new Beacon product.
Learn how they figured out that the product was NOT classified as a medical device, even though it attached to a Class III Automated Electronic Defibrillator (AED). Find out how they navigated a technological pivot, after the team discovered an optimal sensing methodology that was more reliable and scalable than originally planned.
The document discusses Discovery Kanban, an approach for managing exploration and exploitation in organizations. It begins by explaining the need for a new management discipline that excels at both exploiting existing business models and exploring new opportunities. Discovery Kanban uses visualization techniques to manage issues, risks, options, actions and other items across the organization. This helps balance incremental improvement with disruptive change. The approach can be customized for large transformation programs or product renewal efforts. Discovery Kanban templates are available online and the conclusion emphasizes that the approach helps organizations develop the dynamic capabilities needed to thrive in uncertain, disruptive business landscapes.
This document discusses using a customer kanban system to improve workflow for a IT maintenance team. Currently, customer lead times vary widely from a few days to over 30 weeks. The team implements a kanban system with work-in-progress limits to visualize and limit work throughout the process. This helps reduce lead times and backlogs by focusing on continuous flow. However, challenges remain in coordinating work between the upstream process of requirements gathering and the downstream fulfillment process. Fully realizing benefits requires collaboration between customers, business users, and the team at each stage of the workflow.
This document discusses using Kanban principles to manage knowledge work and the balance between discovery and delivery. It introduces different types of knowledge work from exploiting existing knowledge to exploring new knowledge. It then discusses using various "Discovery Kanbans" to visualize and limit work-in-progress for ideas, experiments, decisions, and actions to balance upstream discovery with downstream delivery. Different approaches are needed depending on what is known versus unknown in the work.
Key Note - Devlin 2013 - No crystal ball gazing - The Pragmatism of The Kanba...David Anderson
油
The Kanban Method is based in the philosophy of pragmatism. Kanban encourages you to use facts and actual data to make decisions and plans. This approach improves risk management and business outcomes
Key Note - Stop Starting, Start Finishing 2013 - Aligning Creative Work with ...David Anderson
油
time
When it arrived
The document discusses using qualitative risk assessment and Kanban systems to better align creative work with business risks. It provides examples of how to assess different dimensions of risk like urgency, schedule risk, market risk of change, and product lifecycle risk. Dimensions are assessed qualitatively and visualized to provide information on work scheduling. The document also discusses understanding an organization's tolerance for different risks and aligning capabilities with strategies to avoid being "doomed before starting".
Key Note - PMI Congress Poland - The Role of the Project Manager with KanbanDavid Anderson
油
Kanban systems are used to improve service delivery in creative knowledge work. This presentation looks at how use of Kanban affects the role of a project manager. It takes a look at how planning, scheduling, estimating, issue and risk management are affected by adopting Kanban.
"Fitness for Purpose" - Resilience & Agility in Modern BusinessDavid Anderson
油
Understanding "fitness for purpose". A new way to look at market segmentation based on identity. Defining fitness criteria metrics. Sense and respond. Using Kanban Systems to increase service delivery agility. Using the Kanban Method to catalyze and evolve your business to be "fitter for purpose". Making sense of a complex market using clustering of narratives from front-line staff. Remaining resilient through frequent "fitness" reviews
This document provides an overview of Visual Workflow in Salesforce, including common use cases such as call scripts, smart forms, and wizards. It demonstrates how to build a donation/pledge management app from scratch using only Visual Workflow with no code. The presentation emphasizes that Visual Workflow allows users to draw out business processes and logic, interact with data from forms, databases, and external systems, all through a simple drag-and-drop interface. Resources for learning more about Visual Workflow such as online help, forums, and training sessions are also listed.
Talk delivered by Craig Smith at YOW! 2015 in Melbourne, Brisbane and Sydney on 4-10 December 2015.
With 73% of the world using Scrum as their predominant Agile method, this session will open up your eyes to the many other Agile and edgy Agile methods and movements in the world today For many, Agile is a toolbox of potential methods, practices and techniques, and like any good toolbox it is often more about using the right tool for the problem that will result in meaningful results.Take a rapid journey into the world of methods like Mikado, Nonban, Vanguard and movements like Holocracy,Drive and Stoos where we will uncover 40 methods and movements in 40 minutes to help strengthen your toolbox.
Discovery Kanban is a synthesis of a number of distinct threads of entrepreneurial thinking --Lean Startup, Kanban, OODA, PCDA, and Optionality--into an approach that helps firms address the challenge of executing and refining proven business models in parallel with exploring options for novel business opportunities. It fosters a management discipline of dual strategies of both exploitation and exploration, delivery and discovery that is applicable at different levels of scale in the organization.
In this presentation we will elaborate on the core principles of Discovery Kanban and some practical examples. We will show how (traditional) Delivery and Discovery Kanban are similar but different. We will discuss several examples of Discovery Kanban systems based on dual strategies and how they catalyze a different change in the organization. We will demonstrate how Discovery Kanban assists the discovery process and the integration of discovery and delivery at the different levels of scale.
Enterprise Services Planning: Defining Key Performance IndicatorsDavid Anderson
油
Defining KPIs for use in Enterprise Services Planning and with Kanban systems. Understanding the difference between KPIs, Improvement Guides, and General Health Indicators. Understanding how KPIs drive behavior such as establishing multiple classes of service. Relating KPIs to evolutionary change. KPIs are Fitness Criteria Metrics with defined threashold values
The document discusses systems for change and creating an effective system of change. It describes different types of change, including planned, retrospective, directed, and evolutionary change. It also discusses different approaches to change, such as using constraints to enable collaboration and experimentation, applying the PDCA (plan-do-check-act) loop for hypothesis-driven change, and combining reflective observation and active experimentation using a Kanban system. The overall goal is to view change as a dynamic system and establish a system of change that incorporates planned change, emergent constraints, and retrospective change to drive measurable yet adaptive organizational change.
Make the invisible visible - Visual management in agile product developmentH奪kan Forss
油
Most of today's knowledge work is almost exclusively done digitally. If you would step into an office and try to observe the process you will most likely find it hard to understand what is really happening. Most of the work is as ones and zeros hidden in many different digital repositories.
To create a common and shared understanding in knowledge work we often need to make the invisible visible.
During this session H奪kan Forss will share his experiences of creating common and shared understanding of the invisible knowledge work using visual management.
Visual Management: Leading With What You Can SeeCraig Smith
油
Presentation by Craig Smith and Renee Troughton delivered at Agile Australia 2013 on 20 June 2013. Using task boards or story walls is a key Agile practice, but are you making the most of it? Visual Management is more than just putting cards on a wall, it is a growing style of management that focuses on managing work only by what you can see rather than reports or paper being shuffled around. Visual Management allows you to understand the constraints in the system, mitigate risks before they become issues, report on progress from the micro to the macro. Visual Management can also be used to demonstrate to customers and clients where the work they care about is at. This presentation is all about taking the management of your work to the next stage of transparency.
Estimation a waste of time master 2013 sdc gothenburg w hp rulestom gilb
油
The document discusses estimation and risk management in software projects. It argues that traditional estimation methods are doomed to fail because they cannot account for uncertainties in requirements, technical solutions, staffing, and sensitivity to small changes. Instead, it proposes principles for dynamic design-to-cost and radical management, including learning in small increments to understand root causes of deviations, prioritizing critical requirements, implementing high-risk ideas early, and applying lessons continuously. The goal is to deliver high value within available resources through an adaptive approach.
How using visibility supports effective decision makingThoughtworks
油
The document discusses how visibility supports effective decision making. It notes that companies need to change how they operate given increased ambiguity and faster pace. Visibility provides better alignment, more frequent results, and leads to better, smaller decisions. However, visibility is difficult due to politics, budgets, and resistance to change. Transparency leads to trust and makes decisions easier by depersonalizing issues and showing connections. To create visibility requires vision, location, introspection, protection, unity, and ongoing investment. The document warns against justifying the status quo and other anti-patterns that prevent effective visibility.
The document discusses resilience and business continuity management. It is authored by an independent management consultant with 20 years experience in IT disaster recovery and business continuity. The consultant defines resilience as the ability to resist impacts and recover operational state after an impact. Key aspects of resilience include robustness, redundancy, agility and adaptability. Vulnerability is identified as the opposite of resilience. The document also discusses uncertainty, risk, wicked problems, the importance of moving beyond just compliance to developing real response capabilities, and finding elegant solutions.
Are you involved in the development and introduction of hardware technology products to the market? Would you like to understand how to assess a products feasibility for moving into development?
During this session, Micah Bongberg, the President of Annuvia and his development partners will share their experiences in determining the feasibility of Annuvias innovative new Beacon product.
Learn how they figured out that the product was NOT classified as a medical device, even though it attached to a Class III Automated Electronic Defibrillator (AED). Find out how they navigated a technological pivot, after the team discovered an optimal sensing methodology that was more reliable and scalable than originally planned.
Steve Barsh Of Dream It Ventures On De Risking For Wharton Entrepreneurship C...Steve Barsh
油
Presentation given by Steve Barsh of DreamIt Ventures for the Wharton Entrepreneurship Club February 2009 on techniques for identifying key assumptions and de-risking them early in a capital-efficient manner to lower risks and increase value.
This document outlines a portfolio management strategy for braving economic storms like hurricanes. It begins with an economic outlook analysis and then discusses portfolio allocation, backup strategies, and implementation. The backup strategy section describes using leading economic indicators to forecast disasters, value at risk analysis to estimate potential losses, and guidelines for rebalancing to limit losses. Specific holdings are then analyzed for their exposure to disasters, with recommendations to reduce exposure to financials but increase exposure to construction and metals companies expected to benefit from rebuilding. The portfolio is rebalanced to reflect these views.
The document is a presentation about designing change and triggering cultural metamorphosis. It discusses why projects fail due to lack of user adoption and outlines the phases of adoption including awareness, deployment, ongoing adoption, and usage and availability. It then describes personas that represent different types of users, including innovators, early adopters, early majority, late majority, and hangar backs. The presentation concludes by recapping why projects fail related to user adoption, the phases of adoption, and the personas.
1. Thriving under
uncertainty with
Discovery Kanban
London Lean Kanban Day
March 2013
patrick.steyaert@okaloa.com
@PatrickSteyaert
息 Patrick Steyaert, 2013 Thriving under uncertainty
2. Options and variation 2
Option 1
Effort = 300MD
Most likely delivery = May 31
Variation = 賊10 days
Deadline = May 15
Option 2
Effort = 300MD
Most likely delivery = May 31
Variation = 賊20 days
息 Patrick Steyaert, 2013 Thriving under uncertainty
3. Thriving under uncertainty 3
Plan perspective Risk perspective Options perspective
(Robust but fragile) (Resilient) (Anti-fragile)
則р variation and 則р absorb variation and 則р thrive from disruption;
disruption are not tolerate disruption variation can be
tolerated very well without collapsing beneficial
Customers/ Users /
Stakeholders
TEAM
FLEXIBLE BOUNDARY
息 Patrick Steyaert, 2013 Thriving under uncertainty
4. 4
Pains and gains in the history of projects
Absorbing variation - Classes of Service
Thriving on variation - Options
Kanban variations
息 Patrick Steyaert, 2013 Thriving under uncertainty
5. A calamitous history of 5
projects*
Project Cost overrun Project Actual traffic
Channel tunnel 80% as percentage
UK-FR of forecast
resund 70% Channel tunnel 18%
access link, DE UK-FR
Great belt link, 54% Miami metro, 15%
DE USA
resund coast- 26% Denver 55%
to-coast International
Airport, USA
Conclusion: dont trust
Conclusion: dont trust
cost estimates
usage forecasts
*Source: Megaprojects and risk, an anatomy of ambition, Bent
Flyvbjerg, Nils Bruzelius and Werner Rothengatter, 2003
息 Patrick Steyaert, 2013 Thriving under uncertainty
6. IT projects 6
ps of issues that cause most project failures.
IT projects >$15 million1
2 45%
ssues Bene鍖ts shortfall 56%
Delivering large-scale IT projects on time, on budget, and on
value, Michael Bloch, Sven Blumberg, and J端rgen Laartz
3 Skill issuesof
17 percent IT projects go so bad that they can
4 Execution issues
threaten the very existence of the company (cost
overruns of +200% and schedule slippage of nearly 70%)
Double Whammy How ICT Projects are Fooled by Randomness and
Screwed by Political Intent, Alexander Budzier, Bent Flyvbjerg, Aug
2011.
6
息 Patrick Steyaert, 2013 Thriving under uncertainty
7. Delusions and deception
則р Imperfect forecasting techniques and
inadequate data
7
則р Planning fallacy & optimism bias
則р Strategic misrepresentation and
asymmetric information
息 Patrick Steyaert, 2013 Thriving under uncertainty
8. How projects are sold 8
Gains/Losses
f(X)
Gain Convexity
Unknown
X
Pain
Gain more than pain
息 Patrick Steyaert, 2013 Thriving under uncertainty
10. How projects turn out in practice 10
Gains/Losses
f(X)
Gain
Unknown
X
Pain
Concavity
Pain more than gain
息 Patrick Steyaert, 2013 Thriving under uncertainty
11. 11
Variation and disruption
則р Order of magnitude (size) 則р Political intervention
則р Customer 則р Interrupt work
則р Team 則р Technical problems
則р Policies 則р Changing requirements
則р Technology 則р Resources not available
則р Environment 則р Environmental problem(s)
則р 則р
息 Patrick Steyaert, 2013 Thriving under uncertainty
12. Amplification pain 12
Changes
Prioritization
Requirements Product
Work
Failure
load /
Rework
息 Patrick Steyaert, 2013 Thriving under uncertainty
14. Complex projects 14
How they are planned How they turn out
Convexity Concavity
息 Patrick Steyaert, 2013 Thriving under uncertainty
15. Absorbing variation 15
Plan perspective Risk perspective Options perspective
(Robust but fragile) (Resilient) (Anti-fragile)
則р variation and 則р absorb variation and 則р thrive from disruption;
disruption are not tolerate disruption variation can be
tolerated very well without collapsing beneficial
Customers/ Users /
Stakeholders
TEAM
FLEXIBLE BOUNDARY
息 Patrick Steyaert, 2013 Thriving under uncertainty
16. Kanban systems Less pain 16
Variable
capability Variable
demand
Capability
Bottlenecks
Uncertainty Demand
Loopbacks
Kanban
息 Patrick Steyaert, 2013 Accredited Kanban Training
17. Cost of delay 17
EXPEDITE
Cost/Value
FIXED DATE
STANDARD
INTANGIBLE
x time
息 Patrick Steyaert, 2013 Thriving under uncertainty
18. Classes of service - Minimize Cost 18
of delay while retaining flexibility
Cost of delay Urgent Respond Policy
則р critical and immediate EXPEDITE 則р will be pulled immediately
cost of delay by a qualified resource
則р cost of
delay goes up FIXED DATE 則р will be pulled based on
risk assessment
Cost of delay
significantly after
Flexibility
deadline (delivering on time)
則р cost of
delay is shallow STANDARD 則р will use first in, first out
but accelerates before (FIFO) queuing approach to
leveling out prioritize pull
則р cost of
delay may be INTANGIBLE 則р will be pulled through the
significant but is not system in an ad hoc
incurred until much fashion
later
Important Anticipate
息 Patrick Steyaert, 2013 Thriving under uncertainty
19. Capacity allocation across classes of 19
service
EXPEDITE
Expedite +1 = +5%
Cost/Value
Fixed
date 4 = 20%
FIXED DATE
Standard 8 = 50%
Intangib
le 6 = 30%
STANDARD
INTANGIBLE
x time
息 Patrick Steyaert, 2013 Thriving under uncertainty
20. Thriving under uncertainty 20
Plan perspective Risk perspective Options perspective
(Robust but fragile) (Resilient) (Anti-fragile)
則р variation and 則р absorb variation and 則р thrive from disruption;
disruption are not tolerate disruption variation can be
tolerated very well without collapsing beneficial
Customers/ Users /
Stakeholders
TEAM
FLEXIBLE BOUNDARY
息 Patrick Steyaert, 2013 Thriving under uncertainty
21. Amplification of gains 21
Opportunities
Resources
Requirements Product
Work
User
feedback/
Revenue
息 Patrick Steyaert, 2013 Thriving under uncertainty
22. Opportunity for learning 22
Risk/Options Cost/Value
Probes Enablers Table stakes Exceptionals
Is there a Can we build What is Protect & exploit
need? it? essential? existing value
time
息 Patrick Steyaert, 2013 Thriving under uncertainty
23. Never commit early (unless you 23
know why)
Potential
option Validate
PROBE
Potential
option Validate
ENABLERS
Potential Validate
option
TABLE STAKES
Potential
option
EXCEPTIONAL
息 Patrick Steyaert, 2013 Thriving under uncertainty
24. Exercising options 24
Potential Exercised
Option Option
Option
息 Patrick Steyaert, 2013 Thriving under uncertainty
25. 25
Options expire
則р Expedite critical and immediate
cost of delay
竪 will be pulled immediately by
a qualified resource
則р Fixed date cost of delay goes
up significantly after deadline
竪 will be pulled based on risk
assessment (delivering on time)
則р Standard cost of delay is
shallow but accelerates before
leveling out
竪 will use first in, first out (FIFO)
queuing approach to prioritize pull
則р Intangible cost of delay may be
significant but is not incurred until
much later; important but not
urgent
竪 will be pulled through the
system in an ad hoc fashion
息 Patrick Steyaert, 2013 Thriving under uncertainty
26. Options have value 26
Gains/Losses
f(X)
Gain Convexity
Unknown
X
Pain
Gain more than pain
息 Patrick Steyaert, 2013 Thriving under uncertainty
27. Options - Maximize learning,
27
minimize cost of failure
Option Exploration
則р Fragmented functionality, PROBE 則р Explore customers
Lo-Fi implementation and needs
Learning opportunity
則р Minimally coherent end- ENABLERS 則р Explore feasibility
to-end functionality and critical quality
Cost of failure
showing critical quality
則р End-to-end functionality TABLE STAKES 則р Explore what is
with standard quality essential for
exploitation
則р Broad and detailed EXCEPTIONAL 則р Protect & exploit
functionality, Hi-Fi existing value
implementation
Commitment Exploitation
息 Patrick Steyaert, 2013 Thriving under uncertainty
28. Exploration versus exploitation 28
Potential
option Validate
PROBE
Exploitation
Potential
option Validate
ENABLERS
Potential
Exploration option Validate
TABLE STAKES
Potential
option
EXCEPTIONAL
息 Patrick Steyaert, 2013 Thriving under uncertainty
29. 29
Real options*
An option is the right to do
something but not the obligation
則р Options have value
則р Options expire
則р Never commit early (unless you
know why)
*Ref: Chris Matts & Olav Maassen
息 Patrick Steyaert, 2013 Thriving under uncertainty
30. The knowledge discovery process 30
Narrative,
fragmented, Working product Decision to
possibly (i.e. probe, dampen or
conflicting enabler,) amplify
Potential Exercise Validate Abandoned
Option
option option option / Continue
Coherent, Feedback
shared (e.g. user
concept feedback)
Discovery front-end Development Discovery back-end
Forming hypotheses Validating hypotheses
息 Patrick Steyaert, 2013 Thriving under uncertainty
31. Discovery Kanban Board 31
WIP limits express exploration exploitation balance
Exploration Exploitation
Legend
Expedite Potential Option Exercise Validate Abandon /
option option option Continue
Fixed
date 3/3/9/4 1/1/5/2 1/1/4/2
Probe
Standard probe probe
28/3
Intangib Enabler
le enabler
Intangible
Fixed date probe
probe
F
Table Demo for tradeshow
table R&D
L
stakes on 28/3
stakes O
W
Exceptional
Expedite table stakes
Overdue regulatory Standard enabler
development Framework development
FLOW
息 Patrick Steyaert, 2013 Thriving under uncertainty
32. Kanban variations 32
Delivery Kanban Discovery Kanban
1. Visualize work 1. Visualize options
2. Limit work in progress 2. Minimal options / maximum un-
validated assumptions
3. Manage Flow flow of work
3. Manage Flow flow of customer/
4. Make Process Policies Explicit user acquisition
work policies (e.g. in terms of
cost of delay) 4. Make Process Policies Explicit
option policies (e.g. in terms of
5. Implement Feedback Loops at cost of failure)
workflow, inter-workflow and
organizational levels 5. Implement Feedback Loops
customer feedback loops
6. Improve Collaboratively, Evolve
Experimentally (using models/ 6. Improve Collaboratively, Evolve
scientific method) Experimentally (using models/
scientific method)
息 Patrick Steyaert, 2013 Thriving under uncertainty
33. Not just for start-ups
則р Product development (mature product)
33
則р Business-IT programmes
則р Business transformation
則р Lean agile coaching
息 Patrick Steyaert, 2013 Thriving under uncertainty
34. Thriving under uncertainty 34
Plan perspective Risk perspective Options perspective
(Robust but fragile) (Resilient) (Anti-fragile)
則р variation and 則р absorb variation and 則р thrive from disruption;
disruption are not tolerate disruption variation can be
tolerated very well without collapsing beneficial
Customers/ Users /
Stakeholders
TEAM
FLEXIBLE BOUNDARY
息 Patrick Steyaert, 2013 Thriving under uncertainty
35. Inspiration 35
Knowledge discovery process:
http://alistair.cockburn.us/
The+Design+as+Knowledge
+Acquisition+Movement
息 Patrick Steyaert, 2013 Thriving under uncertainty
36. Thank You
patrick.steyaert@okaloa.com
@PatrickSteyaert
息 Patrick Steyaert, 2013 Thriving under uncertainty
37. Classifying features 37
Epic Epic Epic
Story Story Story Story Story Story Story
Story Story Story Story Story
Story Story
Story Story
Story
Story
Story Story Story
息 Patrick Steyaert, 2013 Anti-fragile projects
38. Classifying features - probes 38
Epic Epic Epic
Story Story Story Story Story Story Story
Story Story Story Story Story
Story Story
Story Story
Story
Story
Story Story Story
息 Patrick Steyaert, 2013 Anti-fragile projects
39. Classifying features - enablers 39
Epic Epic Epic
Enablers
Story Story Story Story Story Story Story
Story Story Story Story Story
Story Story
Story Story
Story
Story
Story Story Story
息 Patrick Steyaert, 2013 Anti-fragile projects
40. Classifying features table stakes 40
Epic Epic Epic
Enablers
Story Story Story Story Story Story Story
Story Story Story Story Story
Table stakes
Story Story
Story Story
Story
Story
Story Story Story
息 Patrick Steyaert, 2013 Anti-fragile projects
41. Classifying features exceptionals 41
Epic Epic Epic
Enablers
Story Story Story Story Story Story Story
Story Story Story Story Story
Table stakes
Story Story
Story Story
Story
Story
Exceptionals Story Story
Story
息 Patrick Steyaert, 2013 Anti-fragile projects