Many teams who are already using Scrum would like to know what benefits they can get by moving to Kanban. Dropping the Sprint timebox can seem quite scary but on the other hand spending less time planning and estimating seems attractive to many developers.
An old friend of mine, Henrik Kniberg (he's a big innovator in Scrum + Kanban integration), posted a great video on Agile Product Ownership. This is basically a 1 day product ownership course compressed into 15 minute animated presentation.
The Mikado Method is a simple straight forward methodology for large scale refactoring. It's a way to peel the layers of complexity away from any system. Systematically attack refactoring, in the knowledge that every change you make will be for the better of the system, rather than hoping it will be.
Epics have just been introduced in Atlassian's GreenHopper 6.1 agile management tool. It's a new feature for Scrum teams that enables them to organise a growing backlog. Epics represent big feature areas that the team will break down into stories and complete over a number of sprints.
Over the past 30 years, Marty Cagan has defined and built products for some of the most successful companies in the world, including Hewlett-Packard, Netscape Communications, America Online, and eBay. He shared his top 10 secrets to creating products customers love.
The Skills Matrix is something out of the Toyota Talent book that is used to help conduct agile performance evaluations for yourself and team members. Get the overview sheet and the awesome template to try it out. They're attached to the article.
Robert Holler, the CEO of VersionOne, and his colleagues got together earlier this year and discussed the lessons they had learned through ten years of insight into agile software development. "Hopefully we've learned more than just ten lessons," Holler told me humorously. Here were the insights he gave...
The method wars are over and Agile has won. But just like any war, peace time comes with its own set of problems and issues. As Agile becomes the de-facto way teams build software the impact on the other processes and systems become widespread.