« May 2007 | Main | July 2007 »
June 25, 2007
Why Scrum Works
Why does Scrum work? Why do any of the Agile methodologies work? How does Scrum help teams deliver value? How does it help high performance teams form?
This series of posts that will look at why Scrum works on three levels:
- Scrum delivers value to the business
- Scrum helps form high performing teams
- Scrum helps motivate and focus team members
Delivering value to the business
Scrum delivers value to the business through:
- Every iteration the product is ready to ship.
- Adapt to changing requirements: Short iterations mean that the Product Owner provides frequent feedback. As result there are frequent small course corrections as opposed to massive changes late in the project.
- Visibility of progress: delivering a working product at the end of every iteration means that the customer, executive sponsors and other interested parties can see the product take shape. They are not surprised six weeks before release.
- Accurate tracking of how much work is left before release: the combination of the product backlog and the team's velocity (aka Yesterday's weather in XP speak) means that you tell how much the team will get done by the release date.
- Lightweight requirements: Since the team is in frequent (preferably daily contact) with the Product Owner, she spends less time writing detailed requirements. Instead she is able focus on making decisions and answering questions from developers.
- Process improvement mechanism to meet business needs: As business needs change – SOX, FDA compliance, through the retrospective the Scrum process can be improved and adapted to meet goals and needs in changing environments.
In short, Scrum provides a way for the business to maximize its ROI by using iterative development to rapidly create working software. It ensures that the team is always working to deliver the highest priority features.
The next post in this series will cover how the elements of Scrum create the right environment for the formation of high performance teams. This post will be hosted in my own blog: Notes From a Tool User
This article written by Mark Levison.
Posted by Guest at 02:54 PM | |
June 19, 2007
Derth of Articles
I apologize to everyone for the lack of articles over the last few months. I've been traveling like crazy including India, England, the US and China! I _think_ life is settling down a little so I plan to start writing again.
Thanks for your patience!
Posted by Mishkin Berteig at 02:38 PM | |
June 04, 2007
The Culture of Time
Thanks to Deborah Hartmann who pointed out these links:
Perception of Time
Timeless Time
Personally, I'm strongly on the side of "polychronic"... and I'm being strongly encouraged to move to a more "monochronic" approach to time management. All my life I have struggled with calendars, PDAs etc. We'll see how it goes!
Posted by Mishkin Berteig at 10:00 PM | |