If I ask people who facilitates their agile retrospective, most tell me that it's their Scrum master. Some even look surprised, as if their could be anybody else who leads their retrospectives? Yes there can be. In some situation it's even better if somebody else than the Scrum master facilitates the agile retrospective.
In my workshops I often play the impediment game with teams. In that game team members discuss impediments that happen during Scrum sprints or Kanban flows, and decide how to deal with them and who should solve the impediment. The "who" is most often "any team member". But in practice I see that teams struggle with impediments, and often expect the Scrum master or a manager to solve them. Let's explore what can be done to have impediments solved by Scrum team members.
The practices in the workshop Getting More out of Agile and Lean will help you to develop the right products for your business and customers, reduce your delivery time, increase the quality of your software, and create happy high performing teams.
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.
Ik zie regelmatig organisaties die besluiten dat ze agile en lean in willen voeren. Wat mij betreft een prima ontwikkeling, gezien de voordelen die een agile en lean werkwijze kan bieden. Waar het echter vaak mis gaat, is de manier waarop managers besluiten om agile en lean in te voeren: Top down, vooraf gepland, en met te weinig inbreng van de professionals. Dat moet en kan anders.
Over the years I've had some situations where I couldn't get a team to come together in a retrospective to meet and reflect on the sprint. I've seen two different kinds of reasons for this. One was that a team wasn't convinced that agile was suitable for them, so they questioned doing agile retrospectives. The other situation was that the team believed in agile and Scrum and wanted to do a retrospective, but was looking for an alternative solution where they would not have to meet physically. Something that also a dispersed team would consider when travelling isn't an option. Let's explore how you can recognize these situations and deal with them.
SwanseaCon is a technical event for Software Developers, Software Architects, Project Managers, Analysts and Consultants in Wales.
I recently received a question whether Product Owners should participate in agile retrospectives. An interesting discussion took off about how "it should be by the book" and "common sense" which I have summarized in the below blog post.
Who should be handling and solving impediments? Should it be the Scrum master? The team as a whole! Their agile coach? I prefer that team members recognize and solve impediments themselves. For most of them they don't need a Scrum master or coach. So if they see a problem, I expect team members to take action and solve it.
I'm honored to have been interviewed by Tom Cagley for his Software Process and Measurement Cast (SPaMCAST). Tom and I talked about the need for continuous improvement and how agile teams can develop skills and practices to recognize and deal with impediments.
Het Agile Manifesto beschrijft dat teams frequent reflecteren om hun effectiviteit te verbeteren. Je kunt Agile Retrospectives gebruiken om te leren van hoe dingen nu gaan en de manier van werken in Agile-teams aan te passen om continu te verbeteren. Dit eerste artikel van een serie over agile retrospectives geeft een introductie in retrospectives en beschrijft hoe je kunt zorgen voor veiligheid zodat mensen open en eerlijk kunnen zijn.
Working with remote teams is becoming a common thing. Where there are clear advantages to this it also has its challenges. One of them is building a relationship with people in remote teams, which is very important to make it work. Here are some ideas how you can do this.