IHS Webcast - Navigating Today’s Global Regulatory Environment Tevia Arnold
Regulatory experts from Tech-Clarity and IHS discuss recent research around the complexity of the global EHS compliance environment and provide best practices in navigating the ever-changing regulatory and product stewardship landscape.
Hothouse combines rapid prototyping with executive decision making to drive consensus on customer experience design.
Presented at ProductCamp DC Spring 2012 event on May 5.
Imaginea's Test engineering shares its process guideliness, best practices and recommedations for effective Product testing. Ensures software products behave the way they are supposed to.
New Product Development (NPD) is the overall process of strategy, organization, concept generation, product and marketing plan creation and evaluation, and commercialization of a new product. This Technology Multipliers webinar provides a complete overview of the NPD process, models, tools, and metrics to succeed with new product development for technology companies.
Our top 10 Metrics reveal the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
3 Keys to Great Customer Experience When Launching Web and Mobile ApplicationsCompuware APM
Designing a great application is only part of ensuring a great customer experience. Ensuring that the application meets business and user expectations in a way that attracts and keeps customers wanting more, yet protecting and increasing business interests is the key to a great customer experience.
Join guest speaker Margo Visitacion of Forrester Research Inc, and Mark Eshelby of Compuware for this webinar about Designing and Launching Web and Mobile Applications that delight your customers and are good business.
In this webinar learn how:
• Today’s teams must focus on a wider range of requirements to verify in complex environments
–how do web and mobile applications change the customer experience?
• Why application development professionals must use collaborative test design principles and approaches .
• How to approach testing your Web and Mobile Applications focusing on the end user experience.
Acquire the Necessary Support for DFSS Projects from Senior ManagementTom Judd
Abstract:
• Get success early, in order to gain support for DfSS beyond researchand development
• Make a strong business case to ensure the consistent allocation of resources
• Inform senior management so that they connect the dots and believe in the value of investing in products from the start
• Implement a strong management commitment not just at project level but at a total system program level
Presented by Tom Judd, Sr. Director, Prodcut Development Quality, Motorola, at the IQPC Annual DFSS Conference in April, 2008, in Chicago.
Spice up your agile retrospectives - LKFR14 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them?
Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.
The retrospective facilitator (often the scrum master) should have a toolbox of retrospective exercises, and be able to pick the most effective one.
This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. You will experience several exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives.
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.
How to Become a Better Scrum Master - Agile Tour Beirut 2016 - Ben LindersBen Linders
During this interactive presentation you will explore the Scrum master role and provide examples of how to do it in an effective way. Humor combined with valuable insights and ideas.
IHS Webcast - Navigating Today’s Global Regulatory Environment Tevia Arnold
Regulatory experts from Tech-Clarity and IHS discuss recent research around the complexity of the global EHS compliance environment and provide best practices in navigating the ever-changing regulatory and product stewardship landscape.
Hothouse combines rapid prototyping with executive decision making to drive consensus on customer experience design.
Presented at ProductCamp DC Spring 2012 event on May 5.
Imaginea's Test engineering shares its process guideliness, best practices and recommedations for effective Product testing. Ensures software products behave the way they are supposed to.
New Product Development (NPD) is the overall process of strategy, organization, concept generation, product and marketing plan creation and evaluation, and commercialization of a new product. This Technology Multipliers webinar provides a complete overview of the NPD process, models, tools, and metrics to succeed with new product development for technology companies.
Our top 10 Metrics reveal the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
3 Keys to Great Customer Experience When Launching Web and Mobile ApplicationsCompuware APM
Designing a great application is only part of ensuring a great customer experience. Ensuring that the application meets business and user expectations in a way that attracts and keeps customers wanting more, yet protecting and increasing business interests is the key to a great customer experience.
Join guest speaker Margo Visitacion of Forrester Research Inc, and Mark Eshelby of Compuware for this webinar about Designing and Launching Web and Mobile Applications that delight your customers and are good business.
In this webinar learn how:
• Today’s teams must focus on a wider range of requirements to verify in complex environments
–how do web and mobile applications change the customer experience?
• Why application development professionals must use collaborative test design principles and approaches .
• How to approach testing your Web and Mobile Applications focusing on the end user experience.
Acquire the Necessary Support for DFSS Projects from Senior ManagementTom Judd
Abstract:
• Get success early, in order to gain support for DfSS beyond researchand development
• Make a strong business case to ensure the consistent allocation of resources
• Inform senior management so that they connect the dots and believe in the value of investing in products from the start
• Implement a strong management commitment not just at project level but at a total system program level
Presented by Tom Judd, Sr. Director, Prodcut Development Quality, Motorola, at the IQPC Annual DFSS Conference in April, 2008, in Chicago.
Spice up your agile retrospectives - LKFR14 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them?
Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.
The retrospective facilitator (often the scrum master) should have a toolbox of retrospective exercises, and be able to pick the most effective one.
This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. You will experience several exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives.
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.
How to Become a Better Scrum Master - Agile Tour Beirut 2016 - Ben LindersBen Linders
During this interactive presentation you will explore the Scrum master role and provide examples of how to do it in an effective way. Humor combined with valuable insights and ideas.
Continuous Improvement, make it visible - ICSPI 2006 - Ben LindersBen Linders
Communication is an important factor in improvement programs. Communication pictures the goals and approach of an improvement program. It can motivate people to commit to change, by showing expected benefits and early results. But wrong or too much communication can also frustrate people, getting them to resist changing.
Many improvement programs are run by technical persons, in a technical environment. Often communication is undervalued and underestimated, and perceived as difficult. It is something that people are inexperienced in, which makes them feel uncomfortable. But if they get started, and take some hurdles, they can get better in it. This presentation provides hands-on information, and hint & tips.
This presentation will show how vital communication is for improvement programs. It supplies a set of tools and techniques to improve the visibility of targets and results, and will explain how this has been used to monitor and steer continuous improvement in an R&D organization. Views on continuous improvement from different stakeholders are included, to show their needs on communication.
Learning to Become Agile, with Retrospectives - QCon London 2015 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to become agile by deploying agile practices in an effective way and continuously learning and improve themselves.
This talk explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. Examples will be given of exercises that you can use to facilitate retrospectives, supported with advice for introducing and improving retrospectives. It is based on the successful book Getting Value out of Agile Retrospectives which is published on InfoQ, Amazon, Leanpub.
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to improve continuously and deliver more value to their customers.
Keynote Need for Continuous Improvement - Agile Tour Kaunas 2016 - Ben LindersBen Linders
Agile isn’t a silver bullet, and it’s not a one size fits all approach. Continuous improvement is what makes it work, it’s at the heart of agile. Ben will show why continuous improvement matters in agile and what you can do to help your teams and organization to be more agile.
Kr8tige software met Lean - RWS - Ben LindersBen Linders
Wat is Lean, en hoe kun je daarmee sneller software ontwikkelen, met hogere kwaliteit tegen lagere kosten? Een overzicht van de principes van Lean, en hoe je het toe kunt passen om verspilling te verminderen, kwaliteit te integreren en medewerkersbetrokkenheid te verbeteren.
Agile quality: Maximize results with a small quality team - PSQT 2005 - Ben L...Ben Linders
How could you maintain quality and organizational efficiency, when the quality staff is reduced? What can you do to optimize improvement effort, and contribute to organizational results? How do you keep up morale in difficult times?
This presentation will show a continuous process of keeping focus, involving people from line and projects, collaboration, and communication. The approach was driven by strong needs from management, and implemented based on values and key success factors of the company. The results are better control, increased performance, and meeting organizational targets.
Real Agile Value with Agile Retrospectives - The making of...Ben Linders
Ben Linders takes you on a journey about writing and self-publicing books. He talk about how the book Getting Value out of Agile Retrospectives started, explain how he works remotely with his co-author Luis Gonçalves and how the book has been translated to Dutch by a self-organized agile team of volunteers.
Spicing up Agile Retrospectives - Agile Tour London 2015 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben will also give a workshop on Valuable Agile Retrospectives on October 22.
Doing Valuable Agile Retrospectives -ATBru 2014 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. They help teams to deploy agile practices in an effective way and to continuously learn and improve themselves.But sometimes teams struggle to figure out what an agile retrospective is? And they wonder how they should do them? This presentation explains the “what” and “why” of retrospectives and the business value and benefits that they can bring. It shows several exercises from the book "Getting Value out of Agile Retrospectives" to help you to facilitate retrospectives, supported with advice for introducing and improving retrospectives. Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously.
The road to agility - AgileEE conference 2016 - Ben LindersBen Linders
Adopting agile often doesn’t go as smoothly as expected in an organization. The road to agility can be hard to travel: You can’t plan your journey up front and there will be surprises along the way. Becoming agile is a learning process which requires that you reflect regularly and adopt your way of working, finding better ways to travel.
Ben Linders will explore what teams, agile coaches, Scrum masters, and managers can do to be prepared for a journey to agility, what to pack and how to decide which road to follow along the way. This talk will help you to successfully deploy ideas and practices that you’ve learned at the conference.
Becoming agile in an agile way - ITMPI webinar by Ben LindersBen Linders
Software development organizations need to become more agile and lean, to deliver products and services that satisfy the needs of their customers. There are multiple ways to do this, which asks for an agile approach to you change your way of working in small directed steps. Retrospectives help you to inspect and adapt your agile journey, assuring that you will get results from your agile and lean transition.
For a writeup on this webinar topic see http://www.benlinders.com/2013/becoming-agile-in-an-agile-way/
Need for Continuous Improvement in Agile - 1stconf Melbourne 2016 - Ben LindersBen Linders
Agile isn't a silver bullet, and it’s not a one size fits all approach. Continuous improvement is what makes it work, it’s at the heart of agile. Ben will show why continuous improvement matters in agile and what you can do to help your teams and organization to be more agile.
Reaching Business Goals with Value Adding CMMI Assessments, Ben Linders, Euro...Ben Linders
This presentation will show how to apply the CMMI in a business focussed way, by doing frequent assessments. Goals are input to the planning of assessments, a matrix is used to assure both organisation and process area coverage, and the results of assessments integrate smoothly within operational targets of existing groups within the organisation.
Practical tools support the frequent assessments, and experience with the CMMI is used to optimize the assessment and improvement cycle, resulting in continuously improving the performance of the organisation towards its goals.
Agile Quality: maximize results with a small quality team, Ben Linders, Europ...Ben Linders
The Ericsson Operational Development & Quality team has managed to introduce a new Management System with a process baseline, rolled out measurements throughout the organization using a Balanced ScoreCard approach, and kept up a focused continuous improvement program. This presentation shows how (obstacles, KSF, results).
At all times, management has made clear that they need control of all aspects of the operation. With a collaborated approach of management and Operational Development (OD), the balanced scorecard was introduced. OD has streamlined target setting, monthly reporting, and quarterly management reviews. The monthly report has been enhanced from a figures only report to full analysis, action definition and forecasting per reported target, involving the line by means of feedback interviews.
A Management System was introduced, moulding and optimizing the existing organisation structure, authorities, and policies. With this management system, the set of processes was reduced, and process support was re-enforced.
A continuous improvement program was continued, with more focus on organizational targets. Existing tools like audits, root cause analysis, and improvement sessions were used to extract vital few actions together with line and project management; the resulting actions were tracked to completing by the OD team.
Key success factors have been the management commitment & active support, the drive of the OD & Quality team, and the build up of skills and knowledge that was needed to implement the changes. Cross-organizational co-operation was stimulated, and management was involved through the monthly reporting & feedback cycle. This presentation will give examples of this, and hints & tips on how to exploit these key success factors in your own organization.
The result is an efficient organization, capable of running projects and supporting activities in a largely quantitative managed way, meeting the required business results.
Spicing up Agile Retrospectives - Agile Practitioners 2016 - Ben LindersBen Linders
The agile manifesto proposes that a “team reflects on how to become more effective”. Agile retrospectives can be used to inspect and adapt the way of working. Retrospectives help teams to deploy agile practices in an effective way and to continuously learn and improve themselves. Ben Linders, co-author of Getting Value out of Agile Retrospectives, will talk about the why and how of agile retrospectives, with much practical tips, stories, and examples. Ben also gives full-day workshops on Valuable Agile Retrospectives.
Controlling Project during Development with a Defect Model, Ben Linders, ICST...Ben Linders
Wouldn’t it be nice if you could have more insight into the quality of a product, while it is developed, and not afterwards? Would you like to be able to estimate how many defects are inserted in the product in a certain phase, and how effective a (test) phase is in capturing these defects? To optimize your test phases regarding focus and effort in relation to how many defects they will find? This presentation will show a simple but very effective model that makes it possible: The Project Defect Model.
The aim of the Project Defect Model is to track product quality, take corrective actions and reduce quality risks. To get more insight into the quality of the product during development, it is needed to measure the software development processes with two views: Introduction and detection of defects. Introduction is done during the specification, design and coding phases; defects are either introduced into documents or into the actual product. Detection of defects is done via inspections and test during all the phases of the project.
A tool was developed using a spreadsheet. The purpose of the tool was to estimate the number of defects per phase, and to track all defects discovered in inspections and tests against these estimates. The tool supported analysis of the data with both calculated values and graphs comparing actuals to estimates in terms of current status and trends over time.
The Project Defect Model has been beneficial to projects. It has helped estimating, planning, and tracking quality during the project, including an estimate of the the number of defects left in the released product. The quality data has been used in the project together with time and cost data, to take better decisions on test, review and inspections, and design. Also it has identified quality risks at an early stage, helping the project take corrective actions and decisions on product release and maintenance capacity planning. Finally the model provided insight into the effectiveness of the verification activities, supporting effective process improvement.
Paper:
The presentation is on a defect planning/tracking tool and approach. Focus will be upon:
• Goals: What was the purpose of the model, why developed, what did we want to reach?
• How: Show the definition of the model and its implementation and application.
• Tools: The tool that was developed to implement the model, how it works, strengths.
• Results: How did the model and tool help the project? Did it live up to its purpose?
• Success factors: What were key issues that we have dealt successfully with?
• Future: How is this model used in future projects, what could further increase its benefits?
My presentation on Agile Vancouver conference in 2011
As the goal of Agile evangelists was to convince people to switch from long Waterfall projects, the main message was to think small – short iterations, no upfront design, and requirements that fit on a card. This presentation explores limitations and pitfalls of a purely iteration focused approach and discuss different ways to address them while still retaining the speed and flexibility of the Agile approach.
This is my latest presentation on "Scrum managing through complexity" given at Luxembourg Sacred Heart University Executive MBA Class (Jan. 17th 2012).
This is a part of the Operational Excellence Module.
Psychological Safety in Teams - FlowCon France 2024 - Ben LindersBen Linders
Psychological safety in teams is important; team members must feel safe and able to communicate and collaborate effectively to deliver value. It’s also necessary to build long-lasting teams since things will happen and relationships will be strained.
But, how safe is a team? How can we determine if there are any factors that make the team unsafe or have an impact on the team’s culture?
In this mini-workshop, we’ll play games for psychological safety and team culture utilizing a deck of coaching cards, The Psychological Safety Cards. We will learn how to use gamification to gain a better understanding of what’s going on in teams. Individuals share what they have learned from working in teams, what has impacted the team’s safety and culture, and what has led to positive change.
Different game formats will be played in groups in parallel. Examples are an ice-breaker to get people talking about psychological safety, a constellation where people take positions about aspects of psychological safety in their team or organization, and collaborative card games where people work together to create an environment that fosters psychological safety.
Why people hate working in Agile teams - QA Challenge Accepted 2023 - Ben Lin...Ben Linders
By now, many of us have been through one or more "agile transformations". We've been surrounded by agile coaches and Scrum masters who tried to help us adapt to agile, with managers who became servant leaders. Hopefully they weren't telling you what to do or how to do your work! A lot of people simply hate working in agile teams - Ben hears that all the time. And that is why he's here! In this talk, Ben will explore the difficulties of collaborating in teams and what we can do to make it beneficial and worthwhile for people to work in teams. Ben will delve into what teams really need, and what leaders should do and should not do to support them, including providing an environment and culture where teams can flourish and supporting teams in removing barriers. Through this talk, attendees will gain a better understanding of the reasons why people struggle to work in agile teams, and what leaders can do to create a positive and supportive environment for teams. The talk is intended for anyone working in a team or working with teams, from agile coaches and Scrum masters to managers and team members who are looking to improve their collaboration skills and create a more positive and productive work environment.
Improving Your Testing Skills and Practices with Gamification - Testing Unite...Ben Linders
So many challenges, so little time. As testers or quality engineers, we need to sharpen the saw, but how? Gamification can be a way to look at how you’re doing and find out where to improve. It’s a great way to have everyone engaged and get the best out of people.
In this presentation, Ben Linders will show how playing games (onsite or online) with the Agile Testing Coaching Cards and Agile Quality Coaching Cards help to explore your current quality and testing practice and decide as a team on what to improve or experiment with.
Start up distributed teams online - Mini XP days 2022 - Ben LindersBen Linders
How to start up a distributed team online with gamification
Remote first is becoming the norm, and this is also true for new teams. Where you would previously organize one or more onsite kick-off sessions to start a new team, a new distributed team would have to be working online together from day 1.
Techniques used for team chartering might still be useful, but they would need a different approach for online working. Gamification, incentifying people’s engagement by using game-style principles and practices, can help you to build strong teams.
In this session, we’ll look at several tools and playing formats that can be used to start up distributed teams and foster further development.
We’ll do the exercises in teams, and as we will be experimenting with both in-person and online exercises it’s good to bring your laptop or tablet too.
Mini XP Days
Instead of scaling up further, XP Days decided to “scale-out”: they rerun some of the favourite sessions of the previous year’s XP Days at the “Mini XP Day”, a one day conference with three tracks. Mini XP Day is ideal if you’ve missed XP Days or if you want to get a “taste” of what XP Days is.
Mini XP Days 2022 will be held on May 17 at the Van der Valk Hotel Beveren.
Increasing psychological safety in agile teams - Agile humans lean coffee 202...Ben Linders
Psychological safety in teams is important; it is necessary for the team to be able to communicate and collaborate effectively in order to deliver value. It's also necessary to build long-lasting teams since things will happen and relationships will be strained; team members must be informed of what's going on in the team and feel comfortable dealing with it. But, how safe is a team? How can we determine if there are any factors that make the team unsafe or have an impact on the team's culture?
In this mini-workshop, we'll play a game for psychological safety and team culture utilizing a deck of coaching cards. We will learn how to use gamification to gain a better understanding of what's going on in teams. Individuals can share what they have learned from working in teams, how it impacted the team's safety and culture, and what led to positive change.
We'll use a Jamboard for the game, so you will need a Google account to join the Jamboard. All participants will receive a code along with a discount for buying the cards.
Improving your quality and testing skills with gamification - Spring 2021 Onl...Ben Linders
For the first time, I’m doing a session at the Online Testing Conference. I’ll be playing games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards to help people explore how things are going and to improve their way of working.
Improving Your Quality and Testing Skills with Gamification
So many challenges, so little time. As testers we need to sharpen the saw, but how? Gamification can be a way to look at how you’re doing and find out where to improve. It’s a great way to have everyone involved and get the best out of people.
In this presentation, Ben Linders will play games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards to show how you can explore your current quality and testing practice and decide in your team on what to improve or experiment with.
Players can use the coaching cards to discuss quality and testing values, principles, and practices. In teams, people can use the cards to share their experiences and learnings.
Different game formats can be used to share experiences on testing and quality principles and practices and explore how they can be applied effectively.
Takeaways
Show how to use gamification to self-assess your current way of working.
Play games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards.
Explore how to facilitate games to enhance quality and testing in agile teams.
\
Online Testing Conference
OnlineTestConf was the first 100% online conference to provide all the advantages of attending professional QA related conferences: personal learning, networking etc. without the shortcomings of scheduling, expenses and travel. The conference has been running for the past 5 years on a semi-annual basis, long before COVID-19 forced all live events online.
Our next event will be our 10th OnlineTestConf! Conference attendees are from all parts of the world, we host well known speakers as well as young presenters, and discuss everything that relates to Testing and QA. Attendance is and will remain free of charge and we invite anyone who sees themselves involved in testing and the testing community to join.
How agile are you? - Agile New England 2021 - Ben LindersBen Linders
On April 1, 2021, (no joke) I did an Agile 101 for Agile New England where we played the Agile Self-assessment Game online.
The Agile Self-assessment Game: How Agile Are You? by Ben Linders
The Agile Self-assessment Game is an Agile ” compass & map” to find out where you are and inspire you with ideas and suggestions on where to go next on your agile journey. It’s a cooperative card game to discover how agile you are and what you can do to increase your agility to deliver more value to their customers and stakeholders.
In this session, Ben Linders explored how a game can enable people to pull in ideas for change and apply those in a way that best suits their collective needs. And we have played with the Agile self-assessment cards online.
Ben Linders is an Independent Consultant in Agile, Lean, Quality, and Continuous Improvement. As an adviser, trainer, and coach, he helps organizations with effectively deploying software development and management practices. He focuses on continuous improvement, collaboration and communication, and professional development, to deliver business value to customers. Ben is an active member of networks on Agile, Lean, and Quality, and a well-known speaker and author. Creator of many Agile Coaching Tools, for example, the Agile Self-assessment Game.
Mini workshop collaborative problem solving - OOP 2021 - Ben LindersBen Linders
Problem? What Problem? Practice Collaborative Problem-solving
Working in teams we face problems in our daily work. As a team, we should be able to solve problems collaboratively. Agile calls these problems impediments.
Impediments can be something in the way of working, processes, tools, or organizational rules or structures. They can also be something cultural or structural.
In this mini-workshop, we’ll practice solving an impediment as a team. Next, we’ll explore how we solved it, how we worked together. What hindered and helped us. We’ll learn what we can do to collaborate better.
Futurespective on Software Development in 2040 - Agile Tour Brussels 2020 - B...Ben Linders
Back to the Future – A Futurespective on Software Development in 2040
We start the futurespective by sketching the future. How is software developed in 2040? Is it people, AI, or a combination? Teams, large groups, or individual work? Programming and testing, or other approaches? Continuous delivery, chunks, iterations, push or pull? Distributed, dispersed, localized teams? There are no limits, let your imagination flow to visualize ideas about developing software products in 2040.
Next, we’ll discuss what got us there. How did these new ways of developing software come into existence? How did we discover them? What experiments led to this? What drove us or influenced us along the way?
Finally, we think about the steps that we can take in 2020 to reach the castle in the sky of software development. What can we do now to become better? What should we stop as it won’t exist in the future anymore?
Let’s find out how the future of software development looks, by doing a futurespective exercise in groups!
How agile are you - Agile Tour London 2020 - Ben LindersBen Linders
Let’s Play a Game to Self-assess Your Agility
Every team, every organization is less or more agile. But how agile are you, and how can you increase your agility? Methods or frameworks don’t tell you how to become agile or increase your agility.
The Agile Self-Assessment Game is an “agile map” with coaching cards for Scrum, DevOps, Kanban, and Business Agility.
Playing the game inspires you with ideas and suggestions on where to go next on your agile journey. Join this session to experience different playing formats in teams, learn how you can discover how agile you are, and get fresh ideas to increase your agility.
Mini workshop retrospecting your retrospectives - Experience Agile 2020 - Be...Ben Linders
The mini-workshop Retrospecting your Retrospectives at eXperience Agile 2020 provides you with ideas to debug your agile retrospectives, find out why they aren’t working and learn how to spice them up and bring the energy back in the team.
Are your retrospective meetings not helping teams to improve? Same actions coming up every retro? People skip the retro, or find them boring? A lack of energy in the room? Chit-chatting instead of discussing real issues? No need for that, let’s retrospect your retrospectives!
In this mini-workshop, you will experience how to use retrospective exercises to debug your retrospective meetings. People will work in teams to reflect on how their retrospectives are going and will learn what they can do to make them valuable again.
It’s a highly interactive session, learning by doing. I’ll bring in my experience from 20 years of doing agile retrospectives, and will set a culture where people will share their ideas and learn.
Agile retrospectives should help teams to reflect at the end of each iteration to learn and decide what to improve and take action in the next iteration. Valuable Agile Retrospectives provide the solution for a successful agile adoption at all levels in the organization. They help teams to reflect and learn how to apply agile practices effectively, and support managers with ideas to set conditions for their teams to grow and deliver more value.
But sometimes retrospectives don’t live up their expectation. Problems that can happen are:
The same questions (what went well, what to improve) are being asked
Similar actions keep coming up in every retrospective
Nothing happens after the meeting, actions are not done
People are postponing or skipping the retrospective meeting
Team members complain that retrospectives are boring and a waste of time
There’s a lack of energy in the room during the meeting, people are not engaged
People don’t feel safe to speak up and share their view
Discussions in the retrospective are not about the real problems (elephant in the room)
The retrospective facilitator is leading people towards a pre-defined answer/solution
In this session, teams will be doing 5 different exercises. In a time slot of two hours, teams rotate to do 2-3 of them.
Intended audience: Scrum masters, agile coaches, tech leads, developers, testers, operations, and anyone who facilitates retrospectives.
This session includes ideas published in my book Getting Value out of Agile Retrospectives, practices from the Retrospective Exercises Toolbox, and agile coaching tools available in my webshop. It’s partly based on things that I teach in one of my workshops: Increasing Organizational Agility with Retrospectives.
Learning Objectives:
Learn to use exercises to reflect on your current practice of retrospectives
See how to create a safe and productive environment to run retrospectives
Practice effective skills for facilitating retrospectives and getting people engaged
Webinar enhancing quality and testing in agile teams - PractiTest - Ben LindersBen Linders
It can be hard for agile teams to deal with quality and testing challenges and decide what to do to deliver high-quality products. There are many different approaches and solutions, which, depending on the context, the problem at hand, and how they are applied, can be more or less effective.
In this webinar, Ben Linders will show you how can use gamification to self-assess your current way of working and enhance quality and testing in agile teams. Playing games with the Agile Testing Coaching Cards and Agile Quality Coaching Cards make it possible to explore your current quality and testing practice and reach a consensus on what could be improved.
Players can use the coaching cards to discuss quality and testing values, principles, and practices. In teams, people can use the cards to share their experiences and learnings.
During the webinar, we’ll pick out cards from the coaching decks to go into detail on specific principles and practices and explore how they can be applied effectively.
Futurespective on software development in 2040 - Aginext - Ben LindersBen Linders
I just came back from 2040 to find out that we are still making software. But it’s not as we know it, Jim! Software development is done completely differently compared to the agile wave that we had at the start of the century. How different? Well, let’s futuresplore it together.
Leading for Self-organization - Stretch 2020 - Ben LindersBen Linders
Agile is something for teams, right? True, but teams don’t function in a vacuum. As a manager, you can set the stage and support teams who want to increase their agility. This presentation explores three topics that managers can work on to make teams succeed and increase the company’s agility: Leadership, Collaboration, and Culture.
Pecha Kucha How to screw up your agile retrospective big time - Ben Linders -...Ben Linders
Retrospectives are great, except when they are not. This tongue-in-cheek presentation explores how you can make agile retrospectives unsuccessful by screwing them, up. I gave this Pecha Kucha at OOP 2020.
Agile Retrospectives to the Next Level - Organizational Agility - OOP 2020 - ...Ben Linders
Agile Retrospectives can be used to deal with problems in teams, at a project or product level, or those related to the collaboration between the team and stakeholders. But you need a different approach compared to team level retrospectives to do organizational-wide improvement.
This session shows how to use agile retrospectives to reveal and solve systemic organizational problems and to increase the company’s agility It explores different approaches, formats, and techniques for agile retrospectives that are done beyond the development team.
Extended Abstract
Nowadays many agile teams are doing retrospectives regularly. They are investing their time to reflect, learn, and take action to improve their way of working and deal with problems that they are facing in a structural way.
Organizations are seeing the benefits from this: teams that are becoming empowered, being able to deliver more value to customers and stakeholders, happy employees, and fewer people leaving the organization. It’s time to take retrospectives to a higher level, and use them to reveal and solve systemic organizational problems. Agile Retrospectives can be used to do that, but you need a different approach.
In this session, I will show how we can use retrospectives to improve the agility of organizations.
Note: Some might call the above approach scaling retrospectives. If that goes towards imposing how teams do retrospectives with some kind of framework, then I believe it doesn’t work. Increasing agility with retrospectives is about creating an environment where teams not only focus on their own improvement needs but also on the company as a whole, and get support from management when improvements go over their team borders or outside their autonomy.
Learning at Scale - FlowCon France 2019 - Ben LindersBen Linders
Where we are seeing more and more individual and team level learning and continuous improvement in organizations, improvements at the higher levels still tend to pose significant challenges. We learn as a team and learn how to be a team, but when we reach the borders of our team and have to deal with more complex systems involving people from our ecosystem and even sometimes from people outside our ecosystem, many improvement practices break down and don’t lead to sustainable results. At the same time, the bigger and more complex our solutions become, the more we need to be able to secure improvement at all levels in the organization.
In this talk, Ben Linders will explore what we can do to increase our understanding of systematic problems at higher levels in organizations, and how to use that to improve the performance and agility of organizations. He will show how we can apply techniques like system/multi-team retrospectives and systems thinking to get improvement going at a level of two higher than the team, and present the benefits that this can bring to teams and organizations as a whole.
Organizational agility: Taking retrospectives to the next level - DevOpsCon M...Ben Linders
Nowadays, many agile teams are doing retrospectives regularly. They are investing time to reflect, learn, and take action to improve their way of working and deal with problems that they are facing in a structural way. Organizations are seeing the benefits from this: teams that are becoming empowered, being able to deliver more value, happy employees, and fewer people leaving the organization. It’s time to take retrospectives to a higher level, and use them to reveal and solve systematic organizational problems. Problems that exist at a project or product level are related to the collaboration between teams and their stakeholders. Agile retrospectives can be used to do that, but you need a different approach. In this session, Ben Linders will show how we can use retrospectives to improve the agility of organizations.
Dealing effectively with impediments - Agile Management Congress 2019 - Ben L...Ben Linders
If your organization wants to become agile and lean, teams need to be able to handle impediments quickly and effectively.
Playing the Impediment Board Game, you will practice how to recognize and analyze impediments, understand how they hinder teams, and decide what to do by deploying agile and lean principles and good practices. You’ll learn to become more effective by recognizing impediments early and get rid of them before they become a major issue.
The impediment game teaches you the five steps for handling impediments effectively:
– recognize and analyze impediments
– find out how they hinder the team
– find effective solutions to deal with them
– decide what to do and who can do it
– learn how to become more effective in dealing with impediments
Agile coaches use the Impediment Board Game in agile transformations to coach teams and help them to become self-organized and empowered to solve any impediments that they might face on their agile journey.
Come play the impediment board game!
Teams what is in it for me - Agile Portugal 2019 - Ben LindersBen Linders
Agile talks a lot about self-organized teams, where developers and testers work together to deliver software. But what can you do to make teams succeed? This talk explores why people would like to work in teams, what managers can do to enable a team structure and culture, and how to (not) manage agile teams.
3. Agile
or
Waterfall?
Nee Type 2 Projects Type 4 Projects
Product Development ag &
Research
ile
Methods well defined
Changemanagement
Type 1 Projects Type 3 Projects
Engineering
waterfall Software Development
Ja
Ja Nee
Goals well defined 3
6. Agile Manifesto
MoreAgile
Manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
by Geert Bossuyt
Through this work we have come to value:
Individuals and interactions over processes and tools
Teamwork & responsibility over Individuals and Interaction
WorkingDeliver Value over Working software documentation
software over comprehensive
Partnership elaboration over Customer collaboration
Customer collaboration over contract negotiation
Embrace change over Respond to Change
Responding to change over Agile Manifesto,plan
While we value the following a
we state that MoreAgile is more Agile.
That is, while there is value in the items on
the right, we value the items on the left more.
6
11. Change owner
• Define the content of the change
• Decide on release date and content
• Be responsible for the “profitability” of the
change (ROI)
• Prioritize features according to (market) value
• Adjust features and priority every iteration, as
needed
• Accept or reject work results
11
13. Release Planning
Product Vision
1 2 3 4 5 6 7 8
User
Change User User User
Story Story Story User stories are the
Story
Epic
Agile way of documenting
User User User User
Story Story Story requirements. Epic
Story
As a <user role> Epic Epic
User User User User User
Story Story Story I want <something>
Story Story
So I can achieve <value>
User User User User User User
Story Story Story Story Story Story
13
14. Rough Estimation
High Medium Low
User
User User
User User
User
User
User
Story User
Story User
Story
Story User
Story
User
Story Story
Story
Story
Story User User
User User
Story
Story User
User
User
Story
User User
Story
Story Story
User Story
Story
User
Story
Story Story
User
Story
User User
Story
User
User Story
Story
User
Story
Story
Story
Story
14
15. Rough Estimation
High
User
User
User
User
Story
Story
Story
Story
User
Story
15
16. Rough Estimation
High Medium Low
User User User User User User User User
Story Story Story Story Story Story Story Story
User User User User User User User
Story Story Story Story Story Story Story
User User User
User
Story Story Story
Story
User User 1 Story
Story Story Point
16
17. Vertical Slicing
Software Development Change Management
Presentation Layer Coaching
Business Layer Training
Database Layer Process Artefacts
17
18. Definition of Done
in Software Development
• Tested & bugfree • Refactoring
• Deployed to test server, • Code reviewed when
so PO can test needed
• All user actions • Remember to check
• All supported browsers the Style_guideline
• IE7/8 • Maintain wiki page
• Chrome • Maintain ERD document
• Firefox • Versions of components
• Safari on Mac • License overview
• Comments in code • Check the constraints
18
19. Definition of Done
in Change Management
• Ownership transfered
• New methods defined • First round of
• Employees trained improvement suggestions
• Change initiated in at processed
least 1 pilot project • Plan defined for further
• Positive feedback of improvements
users • “Regression-test” (after
care) on previous sprints
19
21. Ben Linders Advies
Agile Process Improvement
Expected benefits:
• Collaboration PI team
and stakeholders
• Deployment (over
defining) processes
• Adopt to changes
• Incrementaly, ROI
• Learn to work Agile
3
22. Ben Linders Advies
Golden Rules for PI
• Dare to share, early and frequently
• Result depends on team, not individuals
• The one who checks out a task is not
necessarily the one who has to finish it
• The one’s working on a task are the right
people
• You may critique anything,
but never criticize anyone
BenLinders.com/GoldenRules
4
23. Ben Linders Advies
Case: Making agile fit!
• SW product development, project based org.
• Started Agile some months ago with 3 teams
• Teams signal impediments with the
– Product owners
– Project leader
– Line Managers
Change needed, but the “agile” show must go on!
5
24. Create
a
Roadmap 1
• Change
steps
(User
Stories)
– break
up
the
project
in
10-‐20
concrete
steps
(each
having
value)
– 15
minutes
• Defini<on
of
Done?
(Value/DoD)
– 10
minutes
•
Es<mates
– business
value
– story
points
• Release
Planning
– Assign
stories
to
sprints