- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
The Software Project Manager's Bridge to Agility Paperback – May 19 2008
|New from||Used from|
There is a newer edition of this item:
Special Offers and Product Promotions
Frequently Bought Together
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
From the Back Cover
When software development teams move to agile methods, experienced project managers often struggle—doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not “command and control.
The authors begin by explaining how agile works: how it differs from traditional “plan-driven methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute's classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile--covering the emotional challenges, personal values, and key leadership traits you'll need to succeed.
- Relating thePMBOKRGuideideals to agile practices: similarities, overlaps, and differencesUnderstanding the role and value of agile techniques such as iteration/release planning and retrospectivesUsing agile techniques to systematically and continually reduce riskImplementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvementLearning to trust your teams and listen for their discoveriesProcuring, purchasing, and contracting for software in agile, collaborative environmentsAvoiding the common mistakes software teams make in transitioning to agileCoordinating with project management offices and non-agile teams“Selling agile within your teams and throughout your organization
For every project manager who wants to become more agile.
Part I An Agile Overview7
Chapter 1 What is "Agile"? 9
Chapter 2 Mapping from the PMBOKRGuide to Agile 25
Chapter 3 The Agile Project Lifecycle in Detail 37
Part II The Bridge: Relating PMBOKRGuide Practices to Agile Practices49
Chapter 4 Integration Management 51
Chapter 5 Scope Management 67
Chapter 6 Time Management 83
Chapter 7 Cost Management 111
Chapter 8 Quality Management 129
Chapter 9 Human Resources Management 143
Chapter 10 Communications Management 159
Chapter 11 Risk Management 177
Chapter 12 Procurement Management 197
Part III Crossing the Bridge to Agile215
Chapter 13 How Will My Responsibilities Change? 217
Chapter 14 How Will I Work with Other Teams Who Aren't Agile? 233
Chapter 15 How Can a Project Management Office Support Agile? 249
Chapter 16 Selling the Benefits of Agile 265
Chapter 17 Common Mistakes 285
Appendix A Agile Methodologies 295
Appendix B Agile Artifacts 301
About the Author
Michele Sliger has extensive experience in agile software development, having transitioned to Scrum and XP practices in 2000 after starting her career following the traditional waterfall approach. A self-described “bridge builder,” her passion lies in helping those in traditional software development environments cross the bridge to agility. Michele is the owner of Sliger Consulting Inc., where she consults with businesses ranging from small startups to Fortune 500 companies, helping teams with their agile adoption, and helping organizations prepare for the changes that agile adoption brings. A frequent conference speaker and regular contributor to software industry publications, Michele is a strong advocate of agile principles and value-driven development practices. She is a certified Project Management Professional (PMPR) and a Certified Scrum Trainer (CST). She has an undergraduate MIS degree and an MBA. When not working, Michele volunteers as a grief facilitator for teens at Judi’s House, a nonprofit dedicated to helping children learn how to cope with the loss of a loved one.
Stacia Broderick has worked as a project manager for fifteen years, the last eight in software development. She was fortunate to be helped across the bridge under the mentorship of Ken Schwaber while working for Primavera Systems in 2003 and ever since has helped hundreds of teams the world over embrace the principles of and transition to an agile way of creating products. Stacia founded her company, AgileEvolution, Inc., in 2006 based on the belief that agile practices present a humane, logical way for teams and companies to deliver products. Stacia is a Certified Scrum Trainer as well as a PMPR, a mix that proves valuable when assisting organizations’ transition from traditional to modern practices. Stacia enjoys running, playing classical violin, and spending time with her family.See all Product Description
Inside This Book(Learn More)
Most Helpful Customer Reviews on Amazon.com (beta)
As the title states, Sliger and Broderick sets out to bridge this divide and does a super job showing how agile management practices fit into the project management body of knowledge (PMBOK). They reinforce this message with extensive quotes from the PMBOK that explicitly address incremental and iterative development. I especially like their chapter summaries which compare and contrast project manager approaches to specific practices under a plan-driven and an agile project. One of their key messages is that project managers should allow the team to focus on the current iteration, allowing the project managers to focus on removing impediments to future work. This is sound advice no matter what development framework you are using.
Sliger and Broderick discussion on how agile is being extended to product and release planning and how it's adapting to interfacing with PMOs and non-agile teams is also very relevant. While agile purest reject such notions, these are issues that my clients are facing today. Sliger and Broderick succinctly summarize the current thinking on agile product and release planning and provide sound advice on adapting agile to meet these real-world needs.
One shortcoming in the book is that the authors imply that agile is the silver-bullet that should always be used. I wished they would have acknowledge that while agile methods are appropriate in many situations; plan-driven methods are the appropriate choice for other situations. (See Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner)
I highly recommend this book and will be adding to our seminars reference lists. It is especially useful to experienced project managers. As the product description (see above) states they often struggle while transitioning to agile. However, I don't think they are doubtful about the approach, but instead are confused by the hype they encounter. It will also be useful to agilest who starting to see through the hype in other books. Sliger and Broderick have cut through the hype and reinforce the point that effective project management principles still apply.
The first chapter already helped me forward and removed some of my skepticism. This book is really what is says it is. It's a bridge for the traditional PMI project manager to understand what the difference is between traditional projects and agile projects and it's written in the language of a traditional project manager, the language of PMBOK. From that perspective, I've come to see this as an smart and important book thatm hopefully, will help lots of trainer project managers to understand what agile development is trying to do and why.
The book start with an introduction by Stacia, who describes her experience moving from a traditional environment to an agile environment and the difficulty she faced of changing the way of working she was used to. An excellent introduction that sets the tone of the rest of the book.
The rest of the book consists of 3 parts (plus some appendixes). The first part is the "standard introduction" part in which Agile development gets introduced, in which the first mapping of Agile development to the PMBOK is made and ends with a chapter on a generic agile lifecycle model, which is a guideline for the rest of the book.
The second part is the main part of the book and is structured around the different chapters of the PMBOK. This part actually maps to the PMBOK even on sub-chapter level, done quite well. Within each of the PMBOK chapters, the authors explain the problems the PMBOK tries to solve and how Agile practices solve the same problems, but in a different way. It summarizes this in every chapter with a comparison between traditional practices and Agile practices.
All the chapters seem to cover all the major agile project management practices. It starts with integration management and discussing how all things integrate together and how changes are managed. From there it moves to scope control and explains the differences between traditional WBS task breakdowns and working in a more feature-based way. Time management is next, covering the different planning cycles in the generic agile lifecycle framework (they introduced in Chapter 3). Next is cost management, and quality management. Chapter 9 covers human resource management and was a really nice chapter in which the authors describe well the difference between traditional project resourcing and trying to work with fixed teams that can actually learn new skills when needed. By this time, I felt the major topics had been covered, but there still needed to be communications management and Risk Management to make the mapping of the PMBOK complete. Here I felt the authors started repeating things that were covered earlier, but thats the risk when copying a fixed structure. The last chapter in the PMBOK mapping is procurement management and this chapter was a disappointment to me. The authors are of opinion that there is not much difference in this area, while personally I would not agree with that. Anyways.
The third part covers "the rest" with the main chapter probably be 13 which discusses about the changes in responsibilities between a traditional project manager and an "agile project manager". It describes in fairly much detail the changes in behavior and even tries to cover how to get past this difficult change and why people would want to go through the change (whats in it for them). Also chapter 15 answers one important question: What to do with the PMO. The authors suggest transforming it into an agile supporting organization which they still call "Agile PMO".
Chapter 16 (Selling benefits of Agile) and Chapter 17 (Common Mistakes) are useful chapters for people who are driving the change. It helps them answer some of the common questions and deal with some of the resistance. These chapters conclude the book.
In many areas, I'm still skeptical and do not always agree with the authors. I don't know if it's a good idea to change peoples and organizations role and still keep the old name, like "agile project manager" and "agile PMO". Scrum has solved this by simply calling it different: when the behavior is different then also call it different. Hence the ScrumMaster. Also, the authors strongly stick to the "project thinking" and seem at assume that thats a good way of a managing work. Same with contracts, the authors don't seem to think there will be much change in that area. The book has not convinced me the PMBOK is a good idea either, instead just confirmed my earlier criticism.
All tht said. Realistically, I understand that much of these aspect will not change or not quickly. So, this book introduces new concepts in a familiar language. I do think this will be needed and the authors done a great (perhaps the best possible) job in explaining agile concepts in traditional terms without losing it's meaning. This was the purpose of the book and it certainly succeeded in that.
For project managers looking at agile development, this book is an absolute must.
For agilists, the book is still a good and useful read! (also to understand traditional thinking)
After three short chapters that introduce the general principles and activities of an agile software development project, the authors attack the meat of their subject. Each of the nine chapters of part two corresponds directly to one of the PMI's project management knowledge areas. Sliger and Broderick, each an experienced PMP, cover the changed responsibilities of the project manager transitioning to agile. A highlight of each chapter is the small table with columns for "I used to do this" and "Now I do this" that succinctly summarizes the often profound differences between traditional and agile project management.
This book is necessary reading for any project manager making the change to agile as well as for any ScrumMaster or agile coach working on a large projects. The book takes a giant stride toward dispelling the myth that the only role for project managers is to buy pizza and soda and get out of the way.
Taking the starting point in your existing knowledge as a Project Management Professional (or similar certification level), Michele Sliger and Stacia Viscardi explains in clear language the concepts and benefits of agile development. They are firm in their belief in agile but not religious, so a part of the book is dedicated to give examples on how agile can co-exsist with traditional minded organisations (who haven't seen the light yet). Another great chapter covers how to sell in agile into the different levels of the organization.
You will need to read other agile books as well on your agile journey - books that goes more into deep on the specific agile method you eventually choose to implement. However, this book is important and does exactly what the title claims: provide you with a bridge to agile development.
CSC, CST, PMP
Look for similar items by category
- Books > Business & Investing > Management & Leadership > Management
- Books > Business & Investing > Skills > Project Management
- Books > Computers & Technology > Computer Science > Software Engineering
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Quality Control
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Project Management > Agile
- Books > Computers & Technology > Project Management > PMP Exam
- Books > Computers & Technology > Software
- Books > Professional & Technical > Business Management > Management & Leadership > Management
- Books > Professional & Technical > Business Management > Management & Leadership > Project Management
- Books > Textbooks > Business & Finance > Management
- Books > Textbooks > Computer Science & Information Systems > Programming Languages
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering