Agile Project Management with Scrum: A Practical Guide for Scrum Teams in the Real World

This book is a valuable, practical, no-nonsense addition to the agile literature. Co-authors Andrew and Phuong-Van quickly get down to brass tacks in covering a very broad software development and management landscape. In valuable detail, they cover: agile foundations, finance, management buy-in, agile requirements, architecture vision, product owner role, focused testing, teamwork, agile management, how to adapt Scrum without destroying it; and top it off with a readiness assessment tool. There are two groups of people who will find this book really useful: those coming from a more traditional plan-driven mindset and those coming from a newer agile mindset. The strength of this tome is that it is practical without being dogmatic, and therefore provides a bridge to the others' thinking for people in both these groups. For those of you coming from a traditional, plan-driven background, there are several wonderful sections of information.
The material on visioning Architecture, creating smart requirements for the Scrum Product Backlog, being an effective Product Owner in true agile, servant leader mode, focusing on automated, regression and integration tests, being an enthusiastic and productive team member, and adapting Scrum without killing its agile core will serve two purposes. On one hand, it should provide warmth and comfort if your heart has been chilled by myths that agile teams are lacking in essential software development disciplines. On the other, it will expose you to some of the really critical soft stuff: the wonderful people, team and leadership elements of Scrum that have made it so popular with the rank and file and enlightened managers alike. For those of you coming from a newer agile mindset, especially if you may not have been exposed to more traditional rigor, the material that covers considering Earned Value in particular and finance in general, creating an Architecture Vision and applying it to the Scrum Product Backlog; and performing criteria-based estimation as an addition to planning poker should help expand your thinking without raising your hackles.
The treatment of traditional rigor here is quite sensible and appropriate, and you should have no issues with finding a way to immediately apply some of these proven traditional techniques almost immediately on your projects. If you're a project manager, developer, tester, product manager, business analyst, or in fact anyone involved with software development: you will find that this book helps you understand the nitty-gritty of work on Scrum teams with a very focused practicality. It is a comprehensive work that I believe you will enjoy, no matter where your starting point. What you'll learn * How to use Scrum as you undertake agile management of software and the teams involved in this * How to understand the financial context * How to secure top management support while you obtain middle management buy-in * How to make the story point estimate comparable for Scrum Enterprise-wide implementation * How architectural vision influences team velocity and software quality * How to guade and use the importance of automated, regression and integration tests * How to adapt Scrum without destroying its agile foundations * How to assess and tap Scrum project readiness and much much more...Who this book is for This book is for two major groups of people who will find this book really useful: those coming from a more traditional plan-driven mindset and those coming from a newer agile mindset.