Spark the Change is about an organisation’s ability to be responsive, innovative and harness the energy of its employees. It brings together leaders from across the business to explore how they can work together to create lasting and total change. will cover this conference for InfoQ.
In this guest blog post on BenLinders.com Andrew Mawson from Advanced Workplace Associates talks about their ongoing research on cognition. The aim of that research is to provide guidelines that help knowledge workers do the right things to maximise their cognitive performance.
I have submitted several talks and workshops to the XP Days Benelux 2016 conference. This conference, which will be held November 24 – 25 in Heeze, the Netherlands, is looking for presenters that want to facilitate highly interactive sessions where everyone participates and learns from each other.
In Agile retrospectives gebruik je oefeningen waarmee je als team kunt verbeteren. Het boek Waardevolle Agile Retrospectives bevat 13 oefeningen die je in retrospectives kunt toepassen. Deze blog post beschrijft een nieuwe retrospective oefening die gebruikt kan worden om de kwaliteiten van (Scrum) teams zichtbaar te maken, ze te bespreken en vervolgens te kijken hoe je ze kunt benutten.
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.
In this workshop you will learn different exercises that you can use to facilitate retrospectives, supported with the “what” and “why” of retrospectives, the business value and benefits that they can bring you.
In the previous posts in the series on handling impediments I explored why agile teams need to be able to deal with impediments, how you can recognize problems and what you can do to get a shared understanding of a problem in the team. This post will explain how you can find effective solution for solving impediments.
In this third post in the series on handling impediments I'll explore what you can do to understand the impediment and underlying the problems that the team is trying to deal with. Previous posts explained why impediments matter and how you can recognize the problem.
Via twitter kwam in contact met Johan Roels. In zijn boek Cruciale Dialogen herken ik veel dingen vanuit mijn ervaring met continue verbetering in organisaties. Het vlindermodel wat Johan heeft gedefinieerd in zijn boek verbindt communicatie met waardering om oplossingen voor problemen te zoeken en die vervolgens effectief te implementeren.
In February 2016 I will be giving three workshops in Melbourne Australia, one on continuous improvement and two on agile retrospectives. The workshop are organized by Elabor8 who invited me to come to Australia: We are extremely excited to have Ben Linders over from Europe for a series of workshops in February. Ben is the co-author of "Getting Value out of Agile Retrospectives"and is a regular keynote conference speaker (including Agile Greece Summit 2015 and QCon Beijing 2015). I will give the following workshops: Getting More out of Agile and Lean on Tuesday February 16 Valuable Agile Retrospectives (beginners) on Thursday February 18 Valuable Agile Retrospectives (advanced) on Friday February 19 The workshops are held in the Elabor8 offices at 455 Bourke Street. Level 7 , Melbourne, VIC 3000 AU, Australia. Ticket sale has started, you can register yourself at the Elabor8 Eventbrite events page.
We can learn from failures, from our mistakes; that is something we all know. But we can also learn from things that go well. Here's an example of a team that explored how they succeeded in delivering their project on time against their expectation and used their learnings to improve, and a couple of techniques and exercises that you can use in retrospectives to learn from things that go well.
Agile retrospectives help teams to learn from how they are doing and find ways to improve themselves. In stead of learning from what went wrong, from problems, mistakes or failures, teams can also learn from things that went well, by asking strength-based questions in their retrospectives. Such questions will help them to use their existing skills and experience to become great in doing things that they are already good at.