We can view situations in our work as opportunities from which to learn how to better handle similar situations in future, by looking back and asking “How will I deal with future situations like this to improve my results?” PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements.
Schools use Scrum to help students to learn more effectively and develop themselves in an enjoyable way. The self-organized student teams work in sprints to learn subjects and evolve the learning process. Results from the agile way of working are improved quality of education, higher grades and motivated students. InfoQ interviewed people from several schools involved in teaching with Scrum.
Enterprises want early and frequent customer feedback to be able to understand their needs and be able to deliver products that create value for them. Brian Murray explains how Yammer uses Minimum Viable Products to test their business customer hypotheses, and why they focus so much attention on the architecture of their products.
The essence of software engineering introduces the Software Engineering Method and Theory (SEMAT) initiative which self-organizing teams can use to adopt agile and lean software development practices. 1
A Retrospective is a great way to encourage your team or group to reflect on what has happened and plan for what’s ahead, constantly improving how you work together. This article provides some ideas. 1
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 in the wild.
This article is part of the "DevOps War Stories" series.Each month we hear what DevOps brings to a different organisation, what worked and what didn’t and 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