Free eBook Agile Project Management with Scrum (Microsoft Professional) By Ken Schwaber –

An excellent, readable, brief introduction to Scrum Only Chapter 1 is devoted to the theory of Scrum the rest of the book respects the author s strong view that Scrum can t be learned by studying the theory a team must apply it to a practical situation in order to truly get a handle on Scrum Schwaber accepts the limitations of the book format by turning quickly to case studies, showing how Scrum has been applied in various complex situations, including how Scrum has been mangled in its application and what lessons can be learned from those manglings. The Rules And Practices For Scrum A Simple Process For Managing Complex Projects Are Few, Straightforward, And Easy To Learn But Scrum S Simplicity Itself Its Lack Of Prescription Can Be Disarming, And New Practitioners Often Find Themselves Reverting To Old Project Management Habits And Tools And Yielding Lesser Results In This Illuminating Series Of Case Studies, Scrum Co Creator And Evangelist Ken Schwaber Identifies The Real World Lessons The Successes And Failures Culled From His Years Of Experience Coaching Companies In Agile Project Management Through Them, You Ll Understand How To Use Scrum To Solve Complex Problems And Drive Better Results Delivering Valuable Software FasterGain The Foundation In Scrum Theory And Practice You Need To Rein In Even The Most Complex, Unwieldy ProjectsEffectively Manage Unknown Or Changing Product RequirementsSimplify The Chain Of Command With Self Managing Development TeamsReceive Clearer Specifications And Feedback From CustomersGreatly Reduce Project Planning Time And Required ToolsBuild And Release Products In Day Cycles So Clients Get Deliverables EarlierAvoid Missteps By Regularly Inspecting, Reporting On, And Fine Tuning ProjectsSupport Multiple Teams Working On A Large Scale Project From Many Geographic LocationsMaximize Return On Investment Would have preferred less bad situation Scrum good situation type rah rah anecdotes Common pitfalls, a deeper discussion of tensions in applying the framework to different types of organizations and situations, and an exploration of different methodologies that still fit within the Scrum framework would have been preferred. One of the best books I have read on general project management.I like that it has many examples that make the theory pragmatic and feel the general Scrum techniques could help many projects delivering in general.I wrote project management instead of scrum because I think good project management in general works a lot like it is described here, not just if you want to work by agile paradigms So a lot to learn for everybody, clear structure that makes a read though and just picking your pieces valuable and a praxis oriented foundation What s not to like I read the book This was purely because my previous project followed agile The book is a collection of events, is it the best way to start Not sure There are other Scrum Books which can give you the grasp of Scrum and then may be read this book for understanding how or what can happen At that point, this is a good book Start of with other Agile Scrum books cards and then come to this. May be a bit dated now, but still some great stories to describe how people live in the Scrum framework. I found a few things interesting so far Sprint planning meetings time boxed at 8 hours, even with a 30 day sprint We are drastically different at ISC, and take a whole week on the PSC side to get a sprint planned and committed to I think we can reduce that two a day and gain a whole bunch of dev time back Help documentation counts towards the definition of done in a sprint Scrum is much than the framework, it s about the philosophy Self organization, ownership, empirical process control visibility, inspection, adaptation You can modify the mechanics in line with that philosophy to adapt to challenging situations, such as distributed teams, multiple scrums scrum of scrums , interdependent portfolio, etc Ideas for sprint review meetings trade show format use as opportunity to report out to leadership vs emails and other meetings invite customers knowledge sharing with other scrum teams. Probably the most important takeaway for me was that this book took me back to the starting point of the entire Agile movement and helped me clearly understand where Agile stems from i.e 1 software development is unbelievably complex, and 2 Agile was born to address that complexity by the deceptively simple process of Inspect Adapt This is important because too many Agile practitioners focus on the how s rather than the why s of what they do and get easily lost in the technicalities of their practices Retrospectively, all of this seems pretty obvious and straightforward However, we quite often forget what is pretty obvious and straightforward, don t we This book from one of the original founders of Agile brings us back to where it all started Yes, it is true that this book sometimes sounds like an advertisement, but, hey, when you re a lone voice in a wilderness, you re bound to raise your voice quite a bit and try to sound like a prophet. The book presents set of case studies from companies projects that were adopting SCRUM I liked how stories are organised and that there are always Lessons learned However, some of the case studies I found a bit boring superficial I also noticed, the author sees scrum master as a person conducting daily scrum person enforcing order of asking questions, to whom people are reporting which is a practice rather avoided nowadays Just something worth being aware of while reading. I would agree with other reviewers in saying the book is a bit dated by now But I still would say that many of the case studies presented in the book are still valid nowadays I would recommend this book to any ScrumMaster wanting to learn about the practicalities of a Scrum implementation in different circumstances.A worth read, with concise and straightforward language.