Book Review - Agile Project Management with Scrum

I've just finished reading Ken Schwaber's - Agile project management with Scrum.
Well worth the read, although a little pricey as is always expected from Microsoft's Press.
It was my first thorough read/investigation into Scrum, although I have done some reading into its basic premise on earlier occasions.
I've got to admit I was quite excited about what Scrum proposes, it was much more in line with my own beliefs on project management than many other methodologies I've read about.
I'm not going use this post to discuss Scrum and its benefits, I'll save that for another day. Instead this is a quick review of the book itself.
For those of you that know Scrum, you'll be aware that with Scrum it's relatively easy to explain the components of the methodology. It's the application of those simple components and rules that are significant.
With this in mind Schwaber doesn't go into great detail about all of the components involved in Scrum. Instead he describes an overview of the roles and delivery process in one of the initial chapters - Backdrop -The Science of Scrum; then leaves descriptive details to apply them to real life scenarios to all further explanations.
Considering the theory behind Scrum, this makes perfect sense. Scrums self organising units, empowering teams of individuals to complete projects through self managed plans of delivery.
Taking the book into real world examples enables Schwaber to detail some of the issues you may encounter when trying to implement Scrum.
To this end he goes on to describe each role within the process and issues he's encountered when trying to assist companies with their adoption of Scrum into their project teams.
He focuses on a selection of about 5 different clients that his worked with to illustrate the various elements and possible issues that you may encountered.
This allows him also to illustrate how flexibility is a core requisite of any Scrum implementation and the benefits this can bring.
It also allows him to deal with possible issues you may encounter when attempting to change management cultures that revolve around project delivery by more traditional structured approaches, such as Prince2.
Real life examples allow Schwaber to illustrate some innovative approaches that he's had to adopt in order to get management to accept Scrum as a valid delivery approach.
The book finishes with a number of appendices which detail all of the roles and related documentation that you can expect to produce during a typical Scrum life cycle or Sprint.
This is a more than adequate way of imparting these details rather than wasting time in the core body of the book.
I particularly liked the chapter that dealt with the Scrum Master role in the implementation of Scrum. It detailed a number of real life examples of which I've experienced very similar scenarios to in my career. The scenarios illustrate the mistakes made by the Scrum Master and what was required to resolve the situation.
There are also a number of notes that followed the publication of the book that cover how to implement Scrum with specific requirements; such as meeting Capability Maturity Model requirements.
All in all I thought the book an excellent read and it has certainly inspired me to adopt some of the ideas of Scrum to my day to day work.
Scrum would have worked well with a number of previous projects I've worked on within an enterprise infrastructure environment. It seems harder or less appropriate to implement with smaller projects within a web environment that may be completed within less than 30 days.
If I were to have any gripes about the book they would only be the price, a little sharp but always expected with anything from the Microsoft Press.
Perhaps also the editing of the book, I noticed a few editorial mistakes with repeated names in the wrong places and other very minor issues. Which when you're paying top dollar you would hope wouldn't appear.
Other than that, I would highly recommend the book to anyone thinking about Scrum implementations within their organisation; or for curious project managers that might just want to add another string to their bow of methodology knowledge.
Related reading:
Digital Project Management - Episode One - Introduction - Digital Signals http://www.digital-constructions.com/blog/2008/12/digital-project-management-episode-1.html
Digital Project Management - Episode Two - Project Acquisition - Digital Signals http://www.digital-constructions.com/blog/2009/02/digital-project-management-episode-2.html
Digital Project Management - Episode Three - Planning, Pitching & Acceptance - Digital Signals http://www.digital-constructions.com/blog/2009/06/digital-project-management-episode-3.html
Digital Project Management - The Communication Brief - Digital Signals http://www.digital-constructions.com/blog/2009/05/communication-brief-initial-project.html
Labels: agile, agile with scrum, digital project management, project management, scrum
blog comments powered by Disqus








