Part one of this talk revolves around a series of experience reports following the introduction of Kanban at the BBC in mid 2008.
Part two of this talk summarises Systems Thinking, how it can be of benefit, and how Kanban has led to it being applied within BBC Worldwide.
Computer simulations of software teams process helps you gain insight into its inherent complexity and assists in making better decisions about process policies
LKNL12: Kanban for the whole value streamVasco Duarte
You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized?
Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations.
A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an
organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.
Computer simulations of software teams process helps you gain insight into its inherent complexity and assists in making better decisions about process policies
LKNL12: Kanban for the whole value streamVasco Duarte
You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized?
Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations.
A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an
organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.
Let's talk about Agile not because it is popular, new and amazing, but because it is a software development methodology that just works. What are the basics of Agile? How does it work? What issues you may face while adopting Agile?
Why: CQRS is the new 'hotness' but beyond a desire to use the latest 'fad' what might actually lead you to adopt this approach over a conventional layered architecture. Looking back we will explore how some of the debates in the DDD community about how to implement Eric Evans ideas led people to the CQRS solution. We will look at some of the problems with aggregates and repositories that CQRS helps with and how the vision of seperating core from other domains is simplified. We will also look at simple steps to begin moving your layered application in the CQRS direction and give you a taste of what is to come. By the end of this session you should understand the problems that transitioning to CQRS will help you to resolve.
Scrum, Kanban and DevOps Sitting in a tree... Dave West and Yuval Yeret at Ag...Yuval Yeret
Should you use Scrum, Kanban, or DevOps? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and at the higher-level picture of a DevOps culture and process.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
Let's talk about Agile not because it is popular, new and amazing, but because it is a software development methodology that just works. What are the basics of Agile? How does it work? What issues you may face while adopting Agile?
Why: CQRS is the new 'hotness' but beyond a desire to use the latest 'fad' what might actually lead you to adopt this approach over a conventional layered architecture. Looking back we will explore how some of the debates in the DDD community about how to implement Eric Evans ideas led people to the CQRS solution. We will look at some of the problems with aggregates and repositories that CQRS helps with and how the vision of seperating core from other domains is simplified. We will also look at simple steps to begin moving your layered application in the CQRS direction and give you a taste of what is to come. By the end of this session you should understand the problems that transitioning to CQRS will help you to resolve.
Scrum, Kanban and DevOps Sitting in a tree... Dave West and Yuval Yeret at Ag...Yuval Yeret
Should you use Scrum, Kanban, or DevOps? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and at the higher-level picture of a DevOps culture and process.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
WebCamp: Project Management Day: World of Agile: Kanban - Евгений АндрушкоGeeksLab Odessa
World of Agile: Kanban
Евгений Андрушко
Project Manager at Softserve
- Что общего между садом сакуры и тойота?
- Какую методологию выбрать на Вашем проекте?
- Реальная практика примения Kanban SDLC.
- Kanban kick-start.
- Kanban vs Iterative agile.
- Софт для Agile: Lean Kanban vs Jira vs Trello.
Most Agile methodologies focus on individuals and small groups. This allows teams to quickly respond to change. But as organizations grow, maintaining a culture that continuously improves gets complicated.
This is because most project management methods stop short of being able to achieve agile across an entire project organization. The main issue –– limited visibility across teams.
Join Johan Karlsson from Perforce to learn how Hansoft can help you scale Kanban to:
-Increase visibility into all your projects.
-Easily create and maintain new Kanban boards.
-Organize all the details on project levels.
A Kanban board is a work and workflow visualization tool that enables you to optimize the flow of your work. It utilizes a visual cues that tell you what to produce, how much to produce and when to produce it. This presentation contains brief information related to Kanban board like what is Kanban board, how Kanban works and how to start with Kanban board.
20190513 Lean Kanban North America 2019 Conf Kanban In Action Workshop - lkna...Craeg Strong
This two-part interactive workshop begins with a detailed look at how to interpret Kanban boards and ask thoughtful questions so that you can improve the work of your teams. We will provide an overview of the Kanban Method and then proceed through a series of several short exercises that will give you an opportunity to review and interpret various Kanban board configurations with other attendees at your table.
After a short break, part two of the session now puts the attendees in the driver’s seat to create their own board configurations. We provide several business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique system constraints for each scenario.
5 things cucumber is bad at by Richard LawrenceSkills Matter
This talk will look at 5 things Cucumber’s bad at, why that’s a good thing, and what it tells us about Cucumber’s sweet spot in a team’s toolkit.
Many times, when people complain about something Cucumber’s not good at, they’re unwittingly describing something Cucumber shouldn't be good at. They’re revealing that they don’t quite understand BDD and Cucumber’s role in it.
Cucumber is the world's most misunderstood collaboration tool and people need to hear this over and over again.
Patterns for slick database applicationsSkills Matter
Slick is Typesafe's open source database access library for Scala. It features a collection-style API, compact syntax, type-safe, compositional queries and explicit execution control. Community feedback helped us to identify common problems developers are facing when writing Slick applications. This talk suggests particular solutions to these problems. We will be looking at reducing boiler-plate, re-using code between queries, efficiently modeling object references and more.
Scala e xchange 2013 haoyi li on metascala a tiny diy jvmSkills Matter
Metascala is a tiny metacircular Java Virtual Machine (JVM) written in the Scala programming language. Metascala is barely 3000 lines of Scala, and is complete enough that it is able to interpret itself metacircularly. Being written in Scala and compiled to Java bytecode, the Metascala JVM requires a host JVM in order to run.
The goal of Metascala is to create a platform to experiment with the JVM: a 3000 line JVM written in Scala is probably much more approachable than the 1,000,000 lines of C/C++ which make up HotSpot, the standard implementation, and more amenable to implementing fun features like continuations, isolates or value classes. The 3000 lines of code gives you:
The bytecode interpreter, together with all the run-time data structures
A stack-machine to SSA register-machine bytecode translator
A custom heap, complete with a stop-the-world, copying garbage collector
Implementations of parts of the JVM's native interface
Although it is far from a complete implementation, Metascala already provides the ability to run untrusted bytecode securely (albeit slowly), since every operation which could potentially cause harm (including memory allocations and CPU usage) is virtualized and can be controlled. Ongoing work includes tightening of the security guarantees, improving compatibility and increasing performance.
ENJOYIN
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...Skills Matter
Code Quotations: Code-as-Data for F#
This tutorial will cover F# Code Quotations in-depth. You'll learn what Code Quotations are, how to use them, and where to apply them in your applications. We'll work through several real-world examples to highlight the important features -- and potential pitfalls -- of Code Quotations.
Cukeup nyc ian dees on elixir, erlang, and cucumberlSkills Matter
Elixir, Erlang, and Cucumberl
Elixir is a new Ruby-inspired programming language that uses the powerful concurrent machinery of Erlang behind the scenes. Cucumberl is a port of Cucumber to Erlang. Let's see what happens when we put them together.
In this talk, we'll discuss:
How Erlang's concurrency makes it easier to write robust programs
Elixir's approachable syntax
How to test Erlang and Elixir programs using Cucumberl
Attendees will walk away with a solid introduction to the principles of Erlang, and an appreciation of the way Elixir brings the joy of Ruby to the solidity of the Erlang runtime.
Cukeup nyc peter bell on getting started with cucumber.jsSkills Matter
Cukeup NYC. Peter Bell on Getting started with cucumber.js
Ever wished you could use cucumber in your javascript apps? In this talk we'll look at the current state of play of cucumber js, when you should and shouldn't use it, and how to get started writing your step definitions in javascript.
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...Skills Matter
In this engaging experience report, we will present 3 different views – Developer, Tester, Business Analyst – of implementing Acceptance Test Driven Development in a complex, data-driven domain. Hear how we used ATDD for building a ubiquitous language across the entire team, promoting faster feedback, and cultivating a culture where product owners were deeply invested in the quality of both every deliverable and the system as a whole.
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...Skills Matter
In this tutorial, Phil and Rachel will introduce you to the Try F# samples giving you exposure to, and an understanding of, how F# tackles some real-world scenarios. We'll help you explore, generate, and just play around with code samples, as well as talk you through some of the key principles of F#. By the end of this session, you'll have gone from zero to data science in only a few hours!
Progressive f# tutorials nyc don syme on keynote f# in the open source worldSkills Matter
F# is a powerful open-source language which Microsoft, other companies and the F# community all contribute to. In this talk, Don will discuss how the “F# space” has recently opened up significantly in interesting ways. F# now includes contributions that range from Cloud IDE platforms, Cloud Compute frameworks, Data interoperability components, Cross-platform execution, Try F#, MonoDevelop, and even Emacs editor integration with surprising tooling support, as well as the Visual F# tools from Microsoft and the broader NuGet package ecosystem. Don will also talk about some of the latest contributions from Microsoft Research, including new type provider components for F#, and describe how his team work with the Visual F# team and other teams around Microsoft. There will also be demos of some fun new stuff that’s been going on with F# at MSR and the community.
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...Skills Matter
Would you like to learn how to make your software testing practices more effective? And how to use your testing strategy to better capture and reflect customer requirements? Gojko Adzic takes a critical look at the effectiveness of current software testing practices and proposes strategies to make it much more effective.
Dmitry mozorov on code quotations code as-data for f#Skills Matter
Code Quotations: Code-as-Data for F#
This tutorial will cover F# Code Quotations in-depth. You'll learn what Code Quotations are, how to use them, and where to apply them in your applications. We'll work through several real-world examples to highlight the important features -- and potential pitfalls -- of Code Quotations.
Simon Peyton Jones: Managing parallelismSkills Matter
If you want to program a parallel computer, it obviously makes sense to start with a computational paradigm in which parallelism is the default (ie functional programming), rather than one in which computation is based on sequential flow of control (the imperative paradigm). And yet, and yet ... functional programmers have been singing this tune since the 1980s, but do not yet rule the world. In this talk I’ll say why I think parallelism is too complex a beast to be slain at one blow, and how we are going to be driven, willy-nilly, towards a world in which side effects are much more tightly controlled than now. I’ll sketch a whole range of ways of writing parallel program in a functional paradigm (implicit parallelism, transactional memory, data parallelism, DSLs for GPUs, distributed processes, etc, etc), illustrating with examples from the rapidly moving Haskell community, and identifying some of the challenges we need to tackle.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Journey To Systemic Improvement Lean Exchange Dec 2009 David J
1. A Journey to Systemic
Improvement
David Joyce
BBC Worldwide
1
2. Kanban
Kanban is a transparent, work-limited,
value pulling system.
Eric Willeke - Kanbandev Yahoo! group
2
3. Start with what you do now.
Modify it slightly to implement
pull
Use a transparent method for
viewing work, and organising the
team
Limit WIP and pull work when
the team has capacity.
Evolve from there by recognising
Stop Starting - Start Finishing! bottlenecks, waste and variability
that affect performance
David Anderson
3
4. Kanban began
in one product
team in mid 2008
Continually evolving...
4
5. Kanban began
in one product
team in mid 2008
Continually evolving...
4
10. Kanban began
in one product
team in mid 2008
Batched Releases
Continually evolving...
5
11. Kanban began
MMFs in one product
team in mid 2008
Continually evolving...
5
12. Kanban began
in one product
team in mid 2008
Ideation Board
Continually evolving...
5
13. Kanban began
in one product
team in mid 2008
Goals & Objectives
Continually evolving...
5
14. Kanban began
in one product
team in mid 2008
Express Lane
Continually evolving...
5
15. Kanban began
in one product
team in mid 2008
Hidden Work
Continually evolving...
5
16. Kanban began
in one product
team in mid 2008
Dependencies
Continually evolving...
5
17. Kanban began
in one product
team in mid 2008
Systest Constraint
Continually evolving...
5
18. The Kanban “flu”
soon spreads to
other teams
Application Support
6
19. The Kanban “flu”
soon spreads to
Classes of service
other teams
Application Support
6
20. The Kanban “flu”
soon spreads to
Estimation
other teams
Application Support
6
21. The Kanban “flu”
soon spreads to
other teams
Application Support
T-Shirt Sizing
6
22. Standard Work The Kanban “flu”
soon spreads to
other teams
Application Support
6
23. The Kanban “flu”
soon spreads to
other teams
Application Support
Order point
6
24. The Kanban “flu”
soon spreads to
other teams
Large Standup
Application Support
6
25. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
7
26. The Kanban “flu”
soon spreads to
other teams
2nd Product Team
Application Support
Pro duct Teams
7
27. The Kanban “flu”
soon spreads to
other teams
Application Support
MMF Breakdown Pro duct Teams
7
28. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
MMF Queue
7
29. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Reduced Board Size
7
30. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
8
31. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
Design Board 1
8
32. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
Design Board 2
8
33. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
Design Board 3
8
34. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
CO TS Team
9
35. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
CO TS Team
COTS Main Board
9
36. The Kanban “flu”
soon spreads to
other teams
Application Support
Pro duct Teams
Design Team
CO TS Team
3rd Party Board
9
37. Now entering new
territory
Had looked at Agile before
small team sizes didn’t
fit
specialisation
constant mix of new
development & support
irregular release
cadence
10
38. Now entering new
territory
Excel Board
Had looked at Agile before
small team sizes didn’t
fit
specialisation
constant mix of new
development & support
irregular release
cadence
10
39. Now entering new
territory
First Board
Had looked at Agile before
small team sizes didn’t
fit
specialisation
constant mix of new
development & support
irregular release
cadence
10
45. No Single Solution Recipe for success
Focus on Quality
Based on a set of Reduce WIP, Deliver
principles Often
Better practice NOT Balance Demand against
best practice Throughput
Prioritise
Coupled with sound Reduce variability
engineering practices
and a team willing to Let the data tel
l yo u,
reflect, adapt and what to do w ith
the data
improve
Control
Statistical
David Anderson
12
46. Mean reduced from 22 to 14 days (33%)
Lead Time 50% drop in the spread in variation.
Each of the outliers were proved to be special cause.
Data split at financial year end and in July
13
47. Mean reduced from 9 to 3 days (67%)
77% drop in the spread in variation.
Development Time The major reduction factor has been to limit work in
process.
Data split at financial year end and in July
14
48. Reduction in lead and cycle times, and increase in
throughput are not at the expense of quality.
# Live Defects Number of live bugs is within statistical control, and
seeing a reduction since July.
Data split at end and in July
15
49. Mean reduced from 25 to 5 days (81%)
Large drop in the spread in variation.
# Days Blocked The outliers was proved to be special cause, waiting
for a 3rd party. # blockers actually increased.
Data split at financial year end and in July
16
50. Scrum to Kanban
Data split at end and in July
Mean reduced from 10 to 4 days (60%)
Engineering Time 64% drop in the spread in variation.
17
51. Systems Thinking
The means to obtain knowledge, and
act with prediction and confidence of
improvement.
John Seddon - Freedom from Command & Control
18
52. Kanban encourages a whole
Are we just building
“system” view rather than a
he wrong th ing righter?
t locally optimised IT view
Often IT develop
solutions based on
sub optimised status quo
are
Softw
t
Projec
Projects often focus on the
needs of a single business unit
If we build an IT system around
a wasteful process, then we are
locking in that process for longer
David Anderson & Dr. Peter Middleton
19
53. Sales
Marketing
Finance
HR
Upper Management
IT
20
54. Sales
Marketing
Finance
HR
Upper Management
IT
20
56. Upper Management
.T.
S I
ED
Marketing
N E
Finance
Sales
HR
IT
Hidden costs
20
57. Upper Management
Flow
Marketing
Outside
Finance
Sales
HR
IT
in
Hidden costs
20
58. There is little merit in a well
Since IT “can” executed project that no one
sho uld it?
wants the output from.
Focus on customer needs, and the
organisation as a system
Many of the previous problems,
that apparently required
software projects, may well have
been ‘dissolved’
The improvement effort can be
targeted to where it has most benefit.
Dr. Peter Middleton
21
59. The thing that makes technology
work is not the technology
Does this mean the end of IT?
There is a better way to approach the
use of IT.
Understand and improve, then ask if IT
can further improve.
Larger gains can be achieved through better thinking
around the design and management of work.
Then pulling IT into the work as needed.
Tripp Babbitt
22
60. Un derstan d
Purpose - look outside in
Learn about
nature of demands (in customer terms)
response to demand
causes of failure demand
capability and predictability
flow - end to end
23
61. Impro ve
Improve performance without
using IT
If the current work uses IT then
leave it in place, work with it, or
treat it as a constraint Don’t do anything to change
the IT
Value demand Clean flow
Design System Set work clean
aro un d these
Failure demand Act on the system
Eliminate Causes conditions impeding flow
John Seddon
24
62. Can IT further impro ve
this process or system?
Now we can see potential
benefits, from a position of
knowledge, about the work.
We can therefore predict the The result is always less
investment in IT, and much more
benefits IT solutions will bring
value from it
IT is pulled into the work, rather
than dictating the way work
works
John Seddon
25
67. More information on Kanban
My blog http://leanandkanban.wordpress.com/
Kanban community site http://www.limitedwipsociety.org
Kanban for Software Engineering http://bit.ly/hz9Ju
Soon to be published academic paper on BBCW and Kanban case study
More information on Systems Thinking
Understanding variety of demand http://bit.ly/tnnmI
Freedom from Command and Control http://bit.ly/1OUCnS
Economies of Flow http://bit.ly/tGw3U
29
68. Any Questions ?
I must understand the system, improve the work, THEN pull IT
I must understand the system, improve the work, THEN pull IT
I must understand the system, improve the work, THEN pull IT
I must understand the system, improve the work, THEN pull IT
I must understand the system, improve the work, THEN pull IT
30