10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Kurt Christensen on Nov 21, 2006
In his latest blog entry, Jeff Sutherland introduces an attractive and exceptionally concise introduction to the Scrum development process, titled "Scrum in Five Minutes." Created by Swedish consulting firm Softhouse, this 16-page PDF file gives a brief outline of the pieces and players of Scrum.

[excerpt from Scrum in Five Minutes by Softhouse]
For those who are new to Scrum, such executive summaries can serve as a useful introduction.
In addition, short summaries like this can facilitate comparisons between the various flavors of agile development. Some others available are visual roadmap of Extreme Programming and What does Lean Software Development Really Boil Down To?
Agile Development: A Manager's Roadmap for Success
A practical guide to choosing the right agile tools
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
I'm not a huge fan of "Scrum-only agile", so this paper gets it right. Scrum is best when paired with a lower level software development methodology like XP.
Furthermore, this paper clearly explains Scrum in as many words as should be required. This is pretty much all anyone needs to know and implement Scrum (preferrably with the help of an experienced Agile Coach).
Well done. Don't read the book. Read this PDF! :-)
This is really nice feedback, thanks!
If you want to know more about Softhouse and our agile team you are welcome to read my blog: IntelliJens.
/Jens
A very good overview of Scrum. However, I doubt if a software development method should claim that it can be universally applied with some adaptation.
See the following excerpt.
Is Scrum a method just for software development?
Not at all! The method can be adapted for all different types of
projects ? for instance newspaper production or medical engineering
development.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
3 comments
Watch Thread Reply