Articles
From Information Week: Government, Feb 2012. A coming together of technologies and IT management philosophies at the federal level---including agile development and shared services--is cause for guarded optimism.
This is a paper from my colleague Ade Miller at Microsoft. It is about Distributed Agile Development at Microsoft patterns & practices. It's a good read.
The fourth question in Scrum is used for helping identify early risks in new teams that may not surface through more traditional approaches.
A May 30, 2012 article in the Wall Street Journal illustrating how General Electric is starting to use Scrum and agile methods and principles.
From Information Week: Government, Feb 2012: DHS plans a big push toward more agile development, where software is developed over a series of one- or two-week sprints.
"Are you done yet?"
The answer to this question may sink your career, your team and your project. If you respond with a "yes," you may be forced to take on additional work. If you say "no," you may be branded as someone who can't get things done.
We put a lot of emphasis on being Renaissance workers, able to step comfortably from one job role to the next. But, as Mitch Lacey describes here, not all roles play nicely with each other, and trying to combine them may lead to disaster.
January 2012, MSDN. In this article, Mitch Lacey explains the importance of a product backlog, describes what makes a good backlog, and provides some best practices for creating and maintaining your backlog.
January 2012, MSDN. Mitch Lacey discusses the difficulty surrounding software project estimation, and provides tips and tricks for using two agile software estimation techniques when estimating projects.
January 2012, MSDN. In this article, Mitch Lacey discusses three methods that have proven very beneficial for many Agile teams: the Kano Model of Customer Satisfaction, a series of Innovation Games by Luke Hohmann, and Karl Weigers’ Relative Weighting model. Any of these can help you move from rough prioritization of your backlog to a precise ordering that satisfactorily weighs risk, importance, and customer satisfaction.
