If you are skeptical about adopting Scrum, it may be time to give it another look. That’s what Harwinder of DeepFriedBrainProject.com did. Originally a skeptic, the blogger gave Scrum a second chance and came up with his version of the pros and cons to Scrum.
When Documentation Just Isn’t Enough
The big deal about Scrum is that it stresses work over documentation. Many people disagree with this tactic, as documentation is considered an important part of the project process. However, Harwinder concedes that Scrum isn’t about completely throwing documentation out the window. It’s about making sure that when you do document, the hours you spend doing so are worth more documenting than they are developing software. In other words, document when necessary, but not when it gets in the way of doing work.
But Where Does that Leave the Project Manager?
So what does this mean for the project manager? Well, there isn’t any project management in Scrum. There is a Scrum Master, though. This role is more as a facilitator than a decision maker, but it is an essential role nonetheless. In a lot of ways, Scrums can be considered a back to basics approach, one where priorities are reorganized and roles are redefined. It may not be the answer for everyone, but it might be worth a second look. Read the original article at DeepFriedBrainProject.com: http://www.deepfriedbrainproject.com/2012/04/scrum-from-skeptics-point-of-view.html