The document provides an overview of Kanban concepts and practices for managing workflow. It includes definitions of core Kanban terms like work in progress limits, visualization of workflow, and continuous improvement. Examples are given showing how teams can use cumulative flow diagrams to understand and optimize their process, including reducing bottlenecks and variability. The overall message is that limiting work in process and focusing on continuous flow of work provides benefits like shorter lead times.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Cross-department Kanban Systems - 3 dimensions of scaling #llkd15Andy Carmichael
Describes Clearvision's journey of adopting Kanban, not just in the software development team but in Marketing and other departments. Uses 3 dimensions of scaling - Width (before and after); Height (different sizes, timescales, decision-making); Depth (interdependent services at the same level)
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Cross-department Kanban Systems - 3 dimensions of scaling #llkd15Andy Carmichael
Describes Clearvision's journey of adopting Kanban, not just in the software development team but in Marketing and other departments. Uses 3 dimensions of scaling - Width (before and after); Height (different sizes, timescales, decision-making); Depth (interdependent services at the same level)
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Lean Kanban India 2018 | Leveraging Lean and Kanban to implement Continuous ...LeanKanbanIndia
Session Overview :
How can continuous improvement culture and mindset be "transformed" with Lean and Kanban? What can corporate culture derive from and expand on cultures that still exist in Lean Manufacturing movement that began with TPS (Toyota Product System)? How can we leverage our knowledge of Lean and Kanban to transform organization's fitness for purpose? This is a workshop about a pictorial case study that shows how to apply Lean Manufacturing values, principles & best practices for continuous improvement in today's fast-paced IT landscape.
A survey of Kanban, a software development practice, its history, why people are using it, how to start using it, why it works, criticisms of it, advanced techniques, some general advice and a selected set of references,
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.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Kanban is an Lean practice that focuses on completing work. Used alone Kanban provides an evolutionary approach to agile development and better fits many SW development teams (like maintenance or sysadmin) that don't have an iterative cadence. Used in combination with agile processes like Scrum or Extreme Programming, Kanban practices like WIP limits and Service Level swim lanes solve issues real teams and companies encounter every day. Project managers should pay special attention to Kanban Lead Time metric.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
I decided to help all the freshmen and share the basic Kanban principles with them.
Good luck!
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Lean Kanban India 2018 | Leveraging Lean and Kanban to implement Continuous ...LeanKanbanIndia
Session Overview :
How can continuous improvement culture and mindset be "transformed" with Lean and Kanban? What can corporate culture derive from and expand on cultures that still exist in Lean Manufacturing movement that began with TPS (Toyota Product System)? How can we leverage our knowledge of Lean and Kanban to transform organization's fitness for purpose? This is a workshop about a pictorial case study that shows how to apply Lean Manufacturing values, principles & best practices for continuous improvement in today's fast-paced IT landscape.
A survey of Kanban, a software development practice, its history, why people are using it, how to start using it, why it works, criticisms of it, advanced techniques, some general advice and a selected set of references,
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.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Kanban is an Lean practice that focuses on completing work. Used alone Kanban provides an evolutionary approach to agile development and better fits many SW development teams (like maintenance or sysadmin) that don't have an iterative cadence. Used in combination with agile processes like Scrum or Extreme Programming, Kanban practices like WIP limits and Service Level swim lanes solve issues real teams and companies encounter every day. Project managers should pay special attention to Kanban Lead Time metric.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
I decided to help all the freshmen and share the basic Kanban principles with them.
Good luck!
An Exploration of Cross-product App ExperiencesAtlassian
Atlassian has been building out the Teamwork platform, bringing cross-product experiences like the rich-text editor to all of our products. Extending the Teamwork platform presents a new opportunity for developers.
In this talk, we'll share more on what the Teamwork platform is, where is it available, and explore how we’re thinking app developers might extend the platform. Learn more about the future vision of building cross-product apps, consider what new opportunities it might present for your team, and give early feedback for how you’d like to see it evolve.
There is much hype about Kanban since it was used by supermarkets and then perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach.
As project managers and software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar.
In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will dive into concepts such as limiting work in progress, Minimum Viable Product and Minimum Marketable Feature and see how these concepts can make our lives easier.
During this session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
Scrum and Kanban - Getting the Most from EachMichael Sahota
Scrum is the most popular Agile methodology with Kanban a growing second choice. Learn about the core parts of each one as well as how they differ so that you can find the best fit for your team or organizational context. For example, Scrum is great when you want to shake up the status quo and transform the way you work. Kanban is great when small changes are a better fit for the environment. Learn how they work and how you can use them in your environment.
Scrum with Kanban. Small adjustments, big improvements.Johann Arispe
Scrum with Kanban; small adjustments, big improvements (Paulo Caroli and Johann Arispe)
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...MARRIS Consulting
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
Are we there yet?
Opening keynote, London Lean Kanban Day #llkd15
What is Kanban, where does it take us, and how will we know we’ve arrived?
Updated July 2015 for
Live Agile Workshop & Forum Group, Singapore
BCS Nottingham & Derby
Getting to Ready Unhiding Work with a Backlog Refinement BoardMark Grove
Borrowing lessons from the Kanban method, we look how to visualize a team’s backlog refinement process using a backlog refinement board – ultimately allowing a team to make work more visible to better meet its Definition of Ready.
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
Agile Agency Scrum: An Introduction to Flexible Project Management for Produc...Tim Hamilton
Scrum works because the product owner gets to drive. Discover the process of successful agile scrum for agencies, from methodology and project management, to timeline and budget.
Scaling Scrum with UX in the EnterpriseCaleb Jenkins
Scrum is the most popular Agile framework in the world for effective team collaboration on complex projects. Scrum provides a small set of rules that create just enough structure for teams to be able to focus their innovation. Scrum is optimized for teams for teams of 5 to 9 people. Making Scrum work with larger teams or in large enterprise environments brings its own set of challenges. This talk presents 3 patterns used on enterprise teams to scale Scrum effectively with global teams.
This presentation was given at the 2014 Tulsa Tech Fest in Tulsa, OK - http://developingux.com/TulsaTech2014/
Using the Scrum Spirit to Unlock Empiricism and Agility in OKRs - Agile Bosto...Yuval Yeret
Objectives and Key Results (OKRs) are considered a “Modern operating system” by many companies and investors. But the typical implementation doesn’t deal well with the uncertainty and complexity involved in achieving the typical strategic objective whether it requires building a product, innovating a business model, or creating a new cross-functional company capability. In this talk, we will look at common anti-patterns involved in the typical OKR implementation and how the Scrum spirit can help OKR practitioners bring empiricism, empowerment, and continuous improvement to their OKR operating system. This talk is especially relevant to Scrum and Agile practitioners who are looking for creative ways to bring Scrum’s goodness we are so grateful for to the wider organization.
Fixing Your OKRs With Agility – Agile HartfordYuval Yeret
Presentation by Yuval Yeret, 'OKRs & Agile Sitting in a Tree' at the Agile Hartford Meetup Group - September 2023
Struggling to create a healthy synergy between OKRs and Agile/Scrum/SAFe? You're not alone. In this session, we provide a high-level overview of OKRs, identify some common OKR usage issues/anti-patterns, and suggest improvements leveraging Lean/Agile principles and practices. You will learn how to organize around value through an OKR lens. We will understand the connection between OKRs, KPIs, Products / Value Streams, and what that means for leveraging OKRs in the different Scrum/SAFe elements. We will discuss how Evidence-based Management (EBM) can amp up OKR empiricism. By the end of this session, you will understand the relationship between OKRs, Agile, Scrum, SAFe, and EBM and have concrete ideas for how to help your organization leverage them in synergy.
Who should attend? Agile Leaders, Coaches, Scrum Masters, team members, and anyone else who cares about sharing Agile mindset and practices to improve the way their organization works.
Fixing Your OKRs With Agility – Agile Indy 2023Yuval Yeret
Struggling to create a healthy synergy between OKRs and Agile/Scrum? You're not alone. OKRs (Objectives and Key Results) have become the latest management framework to suffer the fate of becoming popular too quickly, to the point where in many organizations, OKRs are a theater/charade with little valuable substance or benefits. That’s a shame because OKRs have enormous potential if used effectively. This talk will teach you how to leverage agility principles to fix your OKRs or implement OKRs in an agile way from day 1.
What's new in the Scaled Agile Framework (SAFe) 6.0 - Agile Indy May 10th MeetupYuval Yeret
SAFe 6.0, a significant version of the Scaled Agile Framework, was released earlier this Spring. Join us for a deep dive into the newly released SAFe 6.0, where we'll explore the latest updates and improvements to the framework.
In this session, we'll cover the following topics:
Strengthening the Foundation for Business Agility -
Foundational changes in SAFe
Empowering Teams and Clarifying Responsibilities
Accelerating Value Flow
Enhancing Business Agility with SAFe across the business
Delivering Better Outcomes with Measure and Grow and OKRs
This session will provide valuable insights into the latest release and how it can help you and your organization improve business agility and deliver value to customers faster. Join us for an informative and engaging session with our expert speaker, SAFe Fellow/SPCT, and Scrum.org PST Yuval Yeret, who has extensive experience in implementing SAFe at scale. Yuval loves to answer questions, so review the “What’s new in SAFe 6.0” article and come up with concrete questions you want him to answer.
OKRs and Agile Sitting on a Tree - Agile Austin.pdfYuval Yeret
Struggling to create a healthy synergy between OKRs and Agile/Scrum/SAFe? You're not alone. In this session, we provide a high-level overview of OKRs, identify some common OKR usage issues/anti-patterns, and suggest improvements leveraging Lean/Agile principles and practices. You will learn how to organize around value through an OKR lens. We will understand the connection between OKRs, KPIs, Products / Value Streams, and what that means for leveraging OKRs in the different Scrum/SAFe elements. We will discuss how Evidence-based Management (EBM) can amp up OKR empiricism. By the end of this session, you will understand the relationship between OKRs, Agile, Scrum, SAFe, and EBM and have concrete ideas for how to help your organization leverage them in synergy.
OKRs and Scrum - SMs of the Universe Webinar.pdfYuval Yeret
Struggling to create a healthy synergy between OKRs and Agile/Scrum? You're not alone. In this session, we provide a high-level overview of OKRs, identify some common OKR usage issues/anti-patterns, and suggest some improvements leveraging Lean/Agile principles and practices.
You will learn how to organize around value through an OKR lens. We will understand the connection between OKRs, KPIs, Products / Value Streams, and what that means for leveraging OKRs in the different Scrum elements. We will discuss how Evidence-based Management (EBM) can amp up OKR empiricism.
By the end of this session, you will understand the relationship between OKRs, Agile, Scrum, and EBM and have concrete ideas for how to help your organization leverage them in synergy.
Using OKRs in the SAFe Enterprise - Align and Focus on outcomes and enable bu...Yuval Yeret
Struggling to create a healthy synergy between OKRs and Agile/SAFe? You're not alone. In this session, we will identify some OKR anti-patterns and suggest alternative approaches more aligned with SAFe Lean/Agile principles. You will learn how to organize around value through an OKR lens as well as how to improve portfolio focus through economic prioritization and flow management of OKRs. We will understand the connection between OKRs, KPIs, Operational and Development Value Streams, and what that means for leveraging OKRs in the different SAFe elements. By the end of this session, you will have an understanding of the relationship between OKRs and SAFe and concrete ideas for how to help your organization leverage them in synergy.
OKRs for SAFe Summit 2022 - 20220705.pdfYuval Yeret
Struggling to create a healthy synergy between OKRs and Agile/SAFe? You're not alone. In this session, we will identify some OKR anti-patterns and suggest alternative approaches that are more aligned with SAFe Lean/Agile principles. You will learn how to organize around value through an OKR lens as well as how to improve portfolio focus through economic prioritization and flow management of OKRs. We will understand the connection between OKRs, KPIs, Operational and Development Value Streams, and what that means for leveraging OKRs in the different SAFe elements. By the end of this session, you will have an understanding of the relationship between OKRs and SAFe and concrete ideas for how to help your organization leverage them in synergy.
In this session, you will learn to:
Understand the relationship between OVS/DVS through KPIs and OKRs and using it to reorganize around value through the OKR lens
Focusing at the strategic level by combining OKRs, Epics, WSJF and the Portfolio Kanban
Using SAFe's PIP PI Objectives approach to set more aligned and realistic OKRs. Using OKRs thinking in PIP to move from output to outcomes on the DVS/ART
Are you a leader in an organization that’s leveraging Scrum? In this webinar, Professional Scrum Trainer Yuval Yeret, co-author of the Scrum Guide Companion for Leaders, looks at the different elements of Scrum and reflects on an effective way for leaders to engage with them. Throughout the session, Yuval explores topics in this new guide, shares stories from the trenches and discusses:
-What Scrum means for you as a leader
-How to create the conditions in which Scrum can thrive
-How leaders can support the Scrum accountabilities, artifacts and events
-How leaders can leverage Scrum to help them lead their teams
The Best A Man Can Get - Improving Agility in the World’s Shaving Headquarter...Yuval Yeret
In this session, I shared how Gillette is using Scrum applied at Scale to improve agility in a CPG non-software context. We had to make some bold choices that might make classic agile practitioners cringe but we believe are appropriate and support the Scrum spirit. We will talk about our experience using Scaled Scrum inspired by Nexus to design technical and commercial Increments of the Gillette Labs Exfoliating Razor and how it helped us achieve value creation goals in an aggressive timeline. We will share how we use Scrum principles and practices to accelerate innovation and team empowerment in the non-agile-native CPG world.
Validating Delivered Business Value – Going Beyond “Actual Business Value”Yuval Yeret
Actual is a relative term when it comes to business value delivered by a SAFe PI Objective. In this talk we will explore techniques for validating the actual value delivered by SAFe Teams and ARTs based on real-world outcomes that can be evaluated post-release. RTEs, Product Management and Lean/Agile Leaders will be able to assess their current ability to validate value and learn specific practices they could add to their artifacts and events. Finally, we will take a deeper look at optionality and hypothesis-driven thinking in SAFe and challenge the comfort zone on how to properly use some of SAFe’s essential elements in this context.
Learning Objectives:
Assess their competency level of their ART/Program when it comes to ability to validate value
Evolve their Inspect and Adapt events to enable validation value based on real outcomes
Extend their Program and Portfolio Kanbans to help manage the flow of learning and validation.
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019Yuval Yeret
Should you use Scrum or Kanban? 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 how DevOps fits into this picture.
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.
Scaled Agile Framework (SAFe) in the TrenchesYuval Yeret
eBook by AgileSparks - curated blog posts, guidance articles, implementation approaches - all based on AgileSparks and specifically Yuval Yeret's experience implementing SAFe in the trenches.
SAFe for Marketing – Extending Towards Real Business Agility - Global SAFe Su...Yuval Yeret
SAFe’s home turf is product/systems/applications development. Let’s talk about challenging this comfort zone by applying it in one of the core business functions – Marketing. Why? Because the marketing operating system is being disrupted and the larger the marketing organization the more it struggles to maintain relevancy and impact. More and more marketing organizations are seeing the impact of Agile and want to benefit as well. How should an organization using SAFe in R&D/IT look at Agile in Marketing? Is SAFe the right choice? Does it work “as is”? Are there any changes needed to support this new context? What are some lessons learned from trying this in the field?
Learning Objectives and Key Takeaways:
At some point in your enterprise transformation you should consider applying SAFe outside of Product Development/IT. Marketing is a great candidate for a next Value Stream to implement SAFe in.
Agile Marketing is possible not just for small nimble companies but also for large organizations with hundreds of marketers and several legacy silos. SAFe provides a blueprint for how to achieve this.
Understand the differences in applying SAFe outside of Product Development/IT and how to adjust the Big Picture / Implementation Roadmap to accommodate these differences.
The ideal “Business Agility” state is actually to bring together Marketing, Product Management/Development, Sales into one Value Stream.
This talk was delivered in the global SAFe Summit in DC in October 2018
Building Quality In in SAFe – The Testing Organization’s Perspective Yuval Yeret
SAFe emphasizes Building Quality In. We will take a deep dive into how this looks from a testing organization’s perspective and what does a SAFe implementation mean for Testing/QA professionals. We will map SAFe’s approach to best practices in the “”Agile Testing”” world. We will look at examples from the real world of how traditional testing organizations shift left and evolve towards continuous testing.
Learning Objectives and Key Takeaways:
Understand how best practices from the “”Agile Testing”” world map to SAFe’s context
Learn ideas and patterns for evolving Testing/QA’s role during a SAFe implementation
Understand how Test-Driven looks like and how techniques like Acceptance-Test-Driven-Design/Behavior-Driven
Development can empower testers as well as improve the flow on SAFe agile teams.
See how SAFe’s principles can be used to guide the evolution towards a lean/agile testing organization
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.
Abstract:
More and more organizations are realizing that in order to achieve business agility they need to go beyond implementing agile in specific teams/projects. Real agility requires scaling agile to the program/portfolio/enterprise level. In this session we will explore the options organizations have when looking to scale agile, with an emphasis on SAFe(tm) - the Scaled Agile Framework - one of the most popular options these days.
Learning Objectives:
• When does it make sense to Scale Agile
• What are the leading scaling approaches
• An introduction to SAFe's Big Picture and implementation configurations
• How to implement SAFe - The Implementation Roadmap
• Typical Results of implementing SAFe
• Key risks/red flags to be aware of when implementing SAFe
Scrum, Kanban, and DevOps Sitting in a Tree… - Big Apple Scrum Day 2018Yuval Yeret
Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.
10 Essential SAFe(tm) patterns you should focus on when scaling AgileYuval Yeret
Scaling agile can be overwhelming. In this tutorial, Yuval will provide an overview of the ten essential SAFe patterns, and highlight the diagnostic symptoms that appear when the patterns aren’t in place. Attendees will develop a personal “flash assessment” of their current work context and will be able to identify to “inspect and adapt” areas for improvement. They will also learn how to use this sort of assessment/patterns during their scaled agile journey.
(This includes the Essential SAFe assessment toolkit provided by ScaledAgile)
Scrum 4 marketing - Give Thanks to Scrum 2017Yuval Yeret
Scrum in Marketing
What does Scrum in Marketing look like? Why are more and more marketers using Scrum? How is it different than Scrum in software development? What are some challenges that marketers are facing when using Scrum – Are those Scrum deficiencies? Does Scrum mean giving up on the marketer artsy creative spirit? Where/how to start? This talk is based on Yuval’s work with real-world marketing teams/organizations.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
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.
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.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
5. Kanban in your wallet Henrik Kniberg Darn. Forgot to limit.
6. Kanban @ Toyota Supplier Buyer Henrik Kniberg Receive Consume Detach Ship Allocate Manufacture Taiichi Ohno Father of the Toyota Production System The tool used to operate the [Toyota Production] system is kanban. Adapted from Kiro Harada’s slide
9. “ People with different skills have to work together to deliver product features. Don’t build features that nobody needs right now. Don’t write more specs than you can code. Don’t write more code than you can test. Don’t test more code than you can deploy.” Corey Ladas Why pull? Why kanban?
13. ” One day in Kanban land” Henrik Kniberg http://blog.crisp.se/henrikkniberg/tags/kanban/
14. Scenario 1 – one piece flow Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing
15. Scenario 1 – one piece flow Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing
16. Scenario 1 – one piece flow Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing
17. Scenario 1 – one piece flow Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing
18. Scenario 1 – one piece flow. Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing
19. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing PO
20. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing PO
21. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing PO
22. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing PO
23. Scenario 2 – Deployment problem Henrik Kniberg B C A D F G H I J L K M !? E Next Dev Done Backlog 3 2 In production :o) Ongoing PO
24. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M !? Next Dev Done Backlog 3 2 In production :o) Ongoing PO
25. Scenario 2 – Deployment problem Henrik Kniberg B C A D E F G H I J L K M Next Dev Done Backlog 3 2 In production :o) Ongoing PO
26. Scenario 2 – Deployment problem Henrik Kniberg B A D E F G H I J L K M C Next Dev Done Backlog 3 2 In production :o) Ongoing PO
27. Scenario 2 – Deployment problem Henrik Kniberg B A D E F G H I J L K M C Next Dev Done Backlog 3 2 In production :o) Ongoing PO
28. The K anban Change Machine Performance Time Revolution (Scrum) Evolution ( K anban) (kanban the tool)
29. The K anban change machine Designed by David Anderson http://plixi.com/p/61319629
30.
31.
32.
33.
34.
35.
36.
37. Pop Quiz Full story at http ://yuvalyeret.com/2010/08/03/finding-the-right-dev-to-test-ratio-when-working-in-kanban / A lot of WIP in Test Empty Test Done Empty downstream (Bubble) Dev Done almost Full
38. How to deal with a test bottleneck How can I help current stories? Help us with Blocker Fix open defects on our Stories Help us automate tests for this story WIP Limit! Can’t start new DEV work!
39. How to deal with a test bottleneck How can I help you be more efficient? Help us do ATDD so you can develop based on our test expectations, and also offload some automation effort from us Automate Setups and Test Data Improve Dev Done quality! – less retesting for us Half of our work is not core test work. Maybe you can take some of it, or help us reduce waste there Come pair with us, you’ll probably see things from our perspective and have some ideas how to help! Creating more Blue Light - TOC
48. What can teams learn from Cumulative Flow? Work in Process (WIP) Average Cycle Time Real Done Burnup Total Scope Dev Burnup Done Burnup
49.
50. What we learn here Despite agile iterations, still cliff at the end Big gap between Dev and QA How much work is queued vs QA WIP? No visibility We want to iterate in a sustainable pace all the way to DONE DONE, not just to Done
51. Release Tracking using CFD total scope trend - assuming freeze from today Trend of “Done” Needed done rate to meet timeline/scope goal Note scope target is also from a specific lane (where all the scope for this timeline waits. Future scope is in earlier lanes)
Start with what you do now The Kanban Method does not ask you to change your process. It is based on the concept that you evolve your current process. There is no sweeping, engineered change to a new process definition or style of working. There is no such thing as the Kanban Software Development Process or the Kanban Project Management Method.
Agree to pursue incremental, evolutionary change The organization (or team) must agree that their current circumstances warrant a gentle, evolutionary approach to improvement. Perhaps a sweeping engineered change has recently failed due to resistance from team members, or perhaps the politics of the organization make it too risky for managers to propose and implement sweeping changes? Without agreement that a slow, gentle, evolutionary, incremental approach is the right way forward then there won’t be the right environment or management support for a Kanban initiative.
Empty after testing, development in done testing busy bottleneck in testing This is a classic bottleneck in an R&D team. Testing are at their work in progress limit, meaning they cannot take on more work. Acceptance has no work in progress, what we call a “bubble” Development are at their limit as well. Nothing from Testing is DONE waiting to be pulled, which explains why Acceptance has a bubble
Empty after testing, development in done testing busy bottleneck in testing This is a classic bottleneck in an R&D team. Testing are at their work in progress limit, meaning they cannot take on more work. Acceptance has no work in progress, what we call a “bubble” Development are at their limit as well. Nothing from Testing is DONE waiting to be pulled, which explains why Acceptance has a bubble
Automation – not just test automation! How can we help you spend more time actually testing (compared to setup, and other wastes) ( http://theoryofconstraints.blogspot.com/2007/06/toc-stories-2-blue-light-creating.html ) How often do we need to retest? Why? ATDD - drives better code into testing, as well as offload some testing work Agree on “READY for Testing” criteria for stories, setup relevant team rules and processes.
In traditinal first feature developed first and only when release ended move to QA So code is waiting for a long time until start testing The blue line – to ask what do u think it means at the end that move up – (regression)
From Dennis Stevens http://www.dennisstevens.com/2010/06/30/shorten-and-reduce-variability-in-lead-times-using-kanban/ : Wimbledon Okay, so there are some benefits to reducing variability and duration in lead time. But, how can you reduce lead time duration and variability without inhibiting the creativity required to do the work. Wimbledon provides some insight into this. At Wimbledon, the games take as long as they take. The number of games played is determined up front – they have to play all the games. There are Men’s and Women’s Singles, Men’s and Women’s Doubles, Mixed Double’s and many players participate in multiple events. Games can’t play in darkness (except on center court). Games can’t be played in the rain. Players can’t overlap doubles with mixed doubles or with singles play. Wimbledon has been played 142 times and the finals have been delivered late twice. That’s pretty amazing given the wide level of variation in the length of games and the other constraints that must be addressed. How does Wimbledon accomplish this? They have policies that impact the timing of the games – for the most part without impacting the way the game is played. For example: A tie breaker in the first four sets. This tie breaker is open ended as it requires a player to win by two points – only the final set requires winning by two games. Games can start earlier on a day if games are behind. The gap between games can be shortened to get in additional play each day. The tournament director may have players warm up on other courts to bring games closer together. Additional courts can be opened for play as long as it doesn’t create a conflict across events. They minimize the impact of rain by covering courts during rain delays. They have added lights and a roof over Center Court to allow games to run longer and during rain. Combined, these policies allow the games to take as long as they take – while allowing the tournament to deliver a fixed number of games in a fixed time.
Reduce Waiting How much time is a work item actually actively being worked on? If you pay careful attention to flow of work through your system you will likely find that a typical work item spends more time waiting to be worked on then being worked on. It is not unusual to find 5-10x wait time to work time. With wait time being a large portion of lead time, reducing wait time will have a significant impact on reducing lead time. Limiting WIP and pulling work are key techniques to reducing waiting. Rework: Or Failure Load Another big cost on lead time – and typically a huge impact on variability – is rework. Rework is the result of a defect that unintentionally escapes from one work queue and is identified in another. The result is that work moves backwards through the system – increasing lead time not just of the current work item, but of other work items. Leveraging techniques that minimize or eliminate rework are important to reducing variability and duration of lead time. Test driven development, automated test frameworks, continuous integration, and coding standards are methods of reducing or eliminating rework. Investing into reducing rework reduces lead time duration and variability. Making Work Ready One cause of variability and extended lead times is when work is pulled that isn’t ready to be worked on. This can happen when dependent work items aren’t prepared, required external resources aren’t standing by, or when the outcome (not the how) is not well understood. Making work ready requires understanding and aligning dependent work items. Minimizing dependencies during design helps reduce negative impact. Using scheduling methods like Kanban to schedule external (non-instantly available) performers helps coordination of external performers so work can continue to flow. Feature injection, where outcomes are defined during analysis and presented as testable examples is an excellent method of understanding and clearly communicating the expected outcome. Extra effort put into making work ready often results in reduced lead time. Relatively Small and Similar Size Work Large work items – or high variability in size and complexity of work items will result in higher variability and duration of work items. Breaking work into relative small and similar size work is a good method for reducing variability and duration of lead time. Breaking solutions down into small work can also result in improved design, higher testability, and more flexibility in the solution. This doesn’t mean that work should be broken down arbitrarily. Work should be broken down to the smallest level that is reasonable and no smaller. Swarming Swarming is when team members work together on work items to move them forward faster. Sometimes this is increasing the number of developers doing development – often it involves having generalists work in areas outside of their specialization. You will want to have the performers work on work items that are in risk of being late against their SLA.