Dear Scrum community, Boris Gloger has published a brand new website where Scrum Masters, Scrum team members and Product Owners can search for Scrum jobs offered by companies using Scrum. Check out scrumjobs.com at http://scrumjobs.com/

Once upon in time, a Scrum Master was asked by a large company to help introduce Scrum in one of their most important and strategic projects. The Scrum Master asked for the company’s motivation to use Scrum and was told that a project which was kicked-off 6 months ago wasn’t showing much progress and that the bosses wanted to see results and that the deadline was already looming. So the project sponsors decided to adapt to a more promising approach about which they have heard good things – Scrum. If …

“Scrum does not work and I won’t even give it a try!”
— anonymous ignorant
This collection of all the ignorant statements I have come across since I have been using Scrum should help you reply to similar statements in case you will ever be confronted with them:

“Scrum does not work because it is not fault-tolerant”
“Sprint reviews are a waste of time! Let’s skip them!”
“Daily Scrums are micro-management! Let’s not do this!”
“Scrum is waterfall because you are working on stories consecutively!”

In this post, you can find a list of  books about and related to Scrum. This post itself is highly incremental so I will add more recommendations as well as some reviews every now and then.

Agile Software Development with Scrum, Ken Schwaber, Mike Beedle
Scrum and XP from the Trenches, Henrik Kniberg (free download here)
User Stories Applied: For Agile Software Development, Mike Cohn
Agile Estimating and Planning, Mike Cohn
Agile Retrospectives: Making Good Teams Great
The Enterprise and Scrum, Ken Schwaber
Managing the Design Factory, Donald Reinertsen

Happy reading! In case you would like to discuss any …

At the time I was working on my CSP application, I found this terrific book written by Henrik Kniberg about his experience and lessons learned using Scrum and XP. You can download a free version of “Scrum and XP from the trenches” from InfoQueue.

“Scrum is waterfall because you are working on stories consecutively!”
– anonymous ignorant

Of all the ignorant statements I’ve heard so far, this is my new favorite one. Obviously this one is dead wrong because for each story, you complete analysis, design, implementation, testing, and documentation (see figure 1) before you move on to the next story whereas in waterfall, you first complete the analysis for all requirements, then design for all requirements, then implementation, and so on and so forth (see figure 2). So the big difference between Scrum and …