People often ask me what to do to prevent that teams get bored when doing agile retrospectives for a longer period. The short answer is: Make sure that you are getting value from doing your retrospectives. 5 practical tips that will assure that you keep getting value from your agile retrospectives.
I will be doing two more workshops in Sydney during my Australian tour in February: Workshop Increasing Organisational Agility with Retrospectives on February 11 Workshop Getting More out of Agile and Lean on February 12 Next to Sydney I'm also visiting Melbourne on my Australian tour. I will give a keynote at 1stConf about The Need for Continuous Improvement in Agile and three workshops in Melbourne: Workshop Getting more out of Agile and Lean on February 16 Workshop Valuable Agile Retrospectives for Teams on February 18 Workshop Increasing Organisational Agility with Retrospectives on February 19 The workshops are done in collaboration with Elabor8. You can enter “thinksharp” at checkout to receive a discount on my workshops :-). Your can register yourself for the 1stConf and sign up for the workshops on eventbrite. If you want to know more about this workshop or any other workshops or training sessions, feel free to contact me. +31 6 2901 3863 [email protected] Ben Linders
In this workshop you will learn how to scale agile retrospectives, doing them with multiple teams from a project, product or organization, practice facilitation skills with different retrospective exercises, and learn how you can introduce and improve retrospectives. You will also learn to do agile self-assessments and readiness checks and to design and facilitate retrospectives that help organizations to increase their agility.
Are you interested in learning practices for teams and their stakeholders to develop the right products, deliver faster, increase quality, and create happy high performing teams? Come to my workshop Getting more out of Agile & Lean in Sydney, Australia.
A chapter about Sustainable Pace has been added to my new book Continuous Improvement – Doing whatever helps to become better and thus more valuable: Agile promotes that teams work in a sustainable pace to deliver value to their customers. When teams are working under too much pressure, technical debt will increase and velocity of teams will go down. Under such circumstances it will be almost impossible to do any improvement. A sustainable pace is an essential condition to enable team to improve continuously. This book is about increasing the awareness of continuous improvement and about how to improve in a sustainable way. It explores how improvement is engrained in agile, and provides suggestions that you can use in your daily work to improve continuously and increase your agility. Continuous Improvement is my third book. Earlier I published the books What Drives Quality and Getting Value out of Agile Retrospectives. All of my books are available on Ben Linders’…
2016 has started, my wish for everybody is to make it a great year. So let’s focus on doing real improvement to make it happen!
Several workshops on agile retrospectives and increasing agile value have been planned in 2016. (more…)
Bij een Kanban veranderaanpak gaat je uit van wat er is en start je bij de medewerkers. Je werkt bottom up om in kleine stapjes effectief te veranderen.
QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. I will be covering the QCon London conference for InfoQ with video interviews and news.
Ben je op zoek naar een goed praktische boek over agile software ontwikkeling met b.v. Scrum, Kanban of Lean? Of naar een bruikbaar boek over leiderschap of verandermanagement? Op benlinders.com/boeken vindt je mijn boek aanbevelingen. (more…)
Do you want to know how agile you are? What you can do to increase your agility? The agile and lean tool Agile Self-assessments provides 50+ checklists, tools and articles that you can use to self-assess your agility. (more…)
This is the first blog post of a series on handling impediments in agile teams. It explores why being able to deal with impediments matters for agile teams and provides a basic "process" for effectively dealing with them.