A Retrospective is a valuable way to improve how your team works together by reflecting on what has come before and using what you have learned to move ahead together. The authors present a structure with four simple questions to help you get started with using retrospectives in your team environment.
Last year Allan Kelly wrote an InfoQ article about a tool for retrospectives - Dialogue Sheets. A year and over 2000 downloads later he looks at how they are being used and ways they have been adapted in the wild.
DevOps@Nokia Entertainment is the first article of the “DevOps War Stories” series. Each month we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption.
Essential Scrum by Kenny Rubin is a book about getting more out of Scrum. It’s an introduction to Scrum and its values, principles and practices, and a source of inspiration on how to apply it.
In an Agile business annual performance reviews seem old fashioned. Why would we wait one year to get feedback? Ryan Hagan offers a manageable, individual approach to reviews. 2
Patrick Kua has recently published The Retrospective Handbook which provides practical advice on how to make retrospectives much more effective. 1
Certified Scrum Master training tells us we must conduct Reviews (aka Demo's) at the end of every Sprint. Rarely do we get guidance on how to have a great Sprint Review. 5
Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. Resulting in great levels of participation. 10
This paper tells the story of the adaption process of agile software development with a focus on one mechanism – retrospective – we employ to guide team members realize the needed change.
In this article, excerpted from the book Coaching Agile Teams, Lyssa Adkins shows you how to activate the journey toward high performance in an Agile team in both provocative and practical ways.
For developers and leaders only familiar with Scrum or XP, Lean may be a bit of a mystery. Here's an introduction to Lean Thinking and how it enhances software development. 7
Lean thinking aims to reduce waste (in Japanese: muda), overburden (muri) and unnecessary variation (mura). Roman Pichler proposes addressing overburden as the first step toward a leaner process. 8