What’s an Agile Retrospective and Why Would You Do It?
Agile retrospectives can be used by teams to inspect and adapt the way of working. Here's an introduction to agile retrospectives, to help you to get started with them.
Asking why?
Another technique for Getting Value out of Agile Retrospectives is "Asking Why?". "Why" is one of the most valuable question that I use in retrospectives. It gives insight in peoples behavior and their feelings and motives that drive them, helps to find root causes of problems, and reveal the strengths that people have. And helps teams to see common goals, and find ways to collaboratively reach them.
Peopleware Summary in 15 Tweets
The book Peopleware by Tom DeMarco and Tim Lister has been released in a 3rd edition, and the topics addressed in it are still very important. Software development is about people: when, how and where they can work together. If you truly are concerned with people, and looking for ways to improve how you collaboratively develop and deliver software, then this book is a must read.
Improving Collaboration in Agile Projects with the Retrospective of Retrospectives
What can agile projects do to improve collaboration between teams, and increase their contributions in the project? Doing retrospectives of retrospectives is a way to share learnings across a project, and to solve problems that a project is facing.
Using Solution Focused in a Strengths Based Retrospective
How can you become an excellent team that is able to deliver and exceed customer expectations? By continuously becoming better in the things that you are doing great, using a strengths based retrospective. This technique helps teams to improve themselves by focusing on their personal and team strengths.
Retrospective Benefits: Power to the Team
The 2nd blog in the series "Retrospective Benefits" explains how team benefit from retrospectives by finding those improvement actions that matter to them, and help them to do their work better. Agile retrospectives give the power to the team, where it belongs!
Getting to the Root Causes of Problems in a Retrospective: five times why exercise
When you have problems that keep coming back in your sprints, you can try the five times why technique. It helps you to get to the root causes of the problems, and to define effective actions that prevent them from happening in future sprints. This is one of the retrospective technique that will be included in the Pocket Book on Agile Retrospectives, your feedback can help us to improve it!
Coming up: A Pocket Book on Agile Retrospectives
Together with Luis Gonçalves I am writing a pocket book about "Getting Value out of Agile Retrospectives".We value your feedback, so please let us know what you think of our initiative, our previously published blogs and which topics you would like to have covered in the pocket book?
Feelings Matter in Agile Retrospectives: one-word exercise
A 1 word retrospective is a technique that helps if a team is struggling with the way they collaborate, or if there are issues which are not dealt with. All team members state in 1 word how they feel about the sprint, and a discussion is facilitated. It is an effective way for the team to discuss what is hampering them, and agree on how to deal with it and get it out of the way.
Retrospective Benefits: Actions by the Team
Retrospectives bring benefits to Agile teams, they help them to improve and deliver value to their customers and the company. This first article in the series Retrospective Benefits explores how you can benefit from retrospectives, by getting improvement actions that will be done by the agile team.
The Clean Coder: A Book on Professionalism and Attitude
The book The Clean Coder by Robert C. Martin is about attitude and discipline in software development. Robert explores how soft skills matter in IT, how people communicate and collaborate and develop their skills to become a professional programmer.
How I Started with Agile Retrospectives
At the start of the 21th century I did my first agile retrospectives. I started with retrospectives to help a project to improve along the way, so that we could reap the benefits during the project, and benefits. My aim then and now: To enable teams and the whole organization to improve continuously.
- Go to the previous page
- 1
- …
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- …
- 44
- Go to the next page