The Software Project Manager's Bridge to Agility (Agile Software Development Series) / Edition 1

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $9.81
Usually ships in 1-2 business days
(Save 80%)
Other sellers (Paperback)
  • All (14) from $9.81   
  • New (5) from $36.49   
  • Used (9) from $9.81   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$36.49
Seller since 2009

Feedback rating:

(10666)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
New Book. Shipped from UK within 10 to 14 business days. Established seller since 2000.

Ships from: Secaucus, NJ

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$39.25
Seller since 2008

Feedback rating:

(17874)

Condition: New
Brand New, Perfect Condition, Please allow 4-14 business days for delivery. 100% Money Back Guarantee, Over 1,000,000 customers served.

Ships from: Westminster, MD

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
$39.26
Seller since 2007

Feedback rating:

(23585)

Condition: New
BRAND NEW

Ships from: Avenel, NJ

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
$55.24
Seller since 2010

Feedback rating:

(10)

Condition: New
7-24-08 other 1 BRAND NEW! ONLY Expedited orders are shipped with tracking number! *WE DO NOT SHIP TO PO BOX* Please allow up to 14 days delivery for order with standard ... shipping. SHIPPED FROM MULTIPLE LOCATIONS. Read more Show Less

Ships from: San Jose, CA

Usually ships in 1-2 business days

  • Canadian
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
$66.96
Seller since 2014

Feedback rating:

(6)

Condition: New
New

Ships from: Idyllwild, CA

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Page 1 of 1
Showing All
Close
Sort by

Overview

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.

Coverage includes

  • Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences
  • Understanding the role and value of agile techniques such as iteration/release planning and retrospectives
  • Using agile techniques to systematically and continually reduce risk
  • Implementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvement
  • Learning to trust your teams and listen for their discoveries
  • Procuring, purchasing, and contracting for software in agile, collaborative environments
  • Avoiding the common mistakes software teams make in transitioning to agile
  • Coordinating 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 Overview 7

Chapter 1 What is "Agile"? 9

Chapter 2 Mapping from the PMBOKR Guide to Agile 25

Chapter 3 The Agile Project Lifecycle in Detail 37

Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49

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 Agile 215

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

Glossary 321

Bibliography 327

Index 333

Read More Show Less

Product Details

  • ISBN-13: 9780321502759
  • Publisher: Addison-Wesley
  • Publication date: 6/4/2008
  • Series: Agile Software Development Series
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 353
  • Product dimensions: 7.30 (w) x 9.10 (h) x 1.00 (d)

Meet 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.

Read More Show Less

Read an Excerpt

PrefacePreface

We are dedicated to the use of Agile practices in software development (a.k.a. Agilists), but we didn't start out that way. We began as Project Management Professionals (PMP®)1 who used more traditional methods in the development of software.Why We Wrote This Book

We followed the approaches outlined in the Project Management Institute's A Guide to the Project Management Body of Knowledge—Third Edition (PMBOK® Guide) for much of our careers, and in moving to Agile approaches we became more aware of the misconceptions out there surrounding the subject matter of this book—incorrect ideas that we once believed as well. Now as Agile consultants, we continue to hear our clients say that they believe (incorrectly) that if they are to keep their PMP certification and follow the practices outlined in the PMBOK® Guide that they must use a waterfall-like methodology. We also hear the mistaken belief that Agile approaches lack discipline and rigor. And we see the fear and dismay of those who believe that their investment in the Project Management Institute (PMI) may be for naught if they follow the path to agility.

It is our goal to dispel these myths in our book and show that the Third Edition of the PMBOK® Guide does in fact support Agile software development methods and that the investment that project managers have made in the PMI and in the practices outlined in the PMBOK® Guide are still solid and appropriate to pursue. It is clear to us that the PMBOK® Guide is methodology-neutral and supports good project management practices regardless of theapproach chosen. Although many are already aware of this fact, we find that there are still many who are not. As PMPs who are now Agile enthusiasts, we feel it is important to also dispel the mistaken notion in the Agile community that PMPs cannot be good Agile project managers. We would like to build a bridge between the two, thus the need for this book.Structure and Content of the Book

Accordingly, we've put much of the detail concerning this bridging in Part II, where we map the PMBOK® Guide's practices to Agile practices. It is our intent to show project managers that in moving to an Agile methodology, they do not move away from implementing PMI-recommended practices—they simply implement the practices in a different way, making sure that the intent behind these practices remains true. In some chapters you'll find a clear mapping, whereas in others the mapping is more imprecise. This book is intended to be a guide, a way to take the lexicon you are already familiar with and relate it to a new way of developing software. This book will not replace any of the more specific Agile practice books in the market today, and we encourage you to supplement this reading with other books on particular Agile methods (Scrum, XP, Lean, Crystal, and so on).

The next several sections provide a quick preview of the book.Part I: An Agile Overview

Part I introduces you to the basic terms and concepts of Agile software development. We begin in the first chapter ("What is Agile?") with a look back at the emergence of agile ideas in the history of software development. You may be surprised to learn that even Winston Royce's paper on the waterfall approach recommended an iterative cycle and the involvement of the end user in the whole of the project! From this history we move forward and review the concepts behind the Agile Manifesto and its associated principles, which are the basis of all agile software development frameworks.

In Chapter 2, "Mapping from the PMBOK® Guide to Agile," we look at the history of the PMI and its most famous contribution to the practice of project management, the PMBOK® Guide. We'll examine how the PMBOK® Guide project lifecycle phases and project management process groups can be related to the Agile Fractal. And we'll reiterate again that you can be agile and be in keeping with the recommendations outlined in the PMBOK® Guide.

Chapter 3, "The Agile Project Lifecycle," describes the agile project lifecycle—from release planning to iteration planning to daily planning—and how demos, reviews, and retrospectives at the end of each iteration allow the team to continually improve. This chapter begins the use of terminology and concepts that we expand on throughout the rest of the book.Part II: The Bridge: Relating PMBOK® Guide Practices to Agile Practices

This is the part of the book where we review each of the PMBOK® Guide knowledge areas and discuss what you used to do as a traditional project manager, and what you should consider doing instead as an agile project manager. As the title implies, we are trying to build an explicit bridge between the traditional and the agile, and provide you with guidance on what tasks and activities you should substitute—or keep.

As it is in the PMBOK® Guide, the knowledge areas are not in any type of chronological order. In both traditional and agile project management settings, you will find yourself doing most of these activities in parallel.

Because there is some overlap in the knowledge areas, you may find some ideas and concepts repeated. We did this intentionally, because we expect many of you to use this part of the book as a reference guide, and may therefore start with any of these chapters in any order. However, to keep the repetition to a minimum, we do use references to other chapters rather than rewrite large sections.

The chapters in Part II include the following:

  • Chapter 4: "Integration Management"

  • Chapter 5: "Scope Management"

  • Chapter 6: "Time Management"

  • Chapter 7: "Cost Management"

  • Chapter 8: "Quality Management"

  • Chapter 9: "Human Resources Management"

  • Chapter 10: "Communications Management"

  • Chapter 11: "Risk Management"

  • Chapter 12: "Procurement Management"

Part III: Crossing the Bridge to Agile

Whereas Part II covers the specific practical activity changes, Part III covers the softer skills of being an agent of change and what this change means for you personally and professionally. Having answered much of the "what" you need to do in Part II, we turn our focus to "how" to make these changes in Part III. From how your role changes, to how you'll work with others who aren't agile, to what to watch out for, we respond to the commonly asked questions of those who are about to cross the bridge. The chapters in Part III complete the main body of the book:

  • Chapter 13: "How Will My Role as a Project Manager Change?"

  • Chapter 14: "How Will I Work with Other Teams Who Aren't Agile?"

  • Chapter 15: "How Can a Project Management Office Support Agile? "

  • Chapter 16: "Selling the Benefits of Agile"

  • Chapter 17: "Common Mistakes"

Appendixes

We've included two appendixes we hope you will find useful. Appendix A, "Agile Methodologies," runs down a number of the software development methodologies that fall under the Agile umbrella. Appendix B, "Typical Agile Artifacts," includes a look at the typical Agile project "artifacts."Who This Book Is For

Although this book is targeted at software project managers who are members of the PMI, anyone who is doing traditional software project management will benefit from seeing agility presented in terminology to which they are accustomed. We will refer to these long-established methodologies as "waterfall," "plan-driven," or "traditional," all of which refer to sequential, phased, noniterative approaches to software development.Final Thoughts

We should also make it clear that we are not sanctioned by PMI or any of its representatives. This book is the result of our research, interpretation, and experience. Although we used the Third Edition of the PMBOK® Guide in our studies, we expect that as the PMBOK® Guide goes through further revisions, you will still find the concepts presented here to be relevant.Endnotes

1. "PMP," "PMI," and "PMBOK Guide" are registered marks of Project Management Institute, Inc.

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Table of Contents

Preface xvii

Acknowledgments xxiii

About the Authors xxv

Introduction 1

Part I An Agile Overview 7

Chapter 1 What is "Agile"? 9

Chapter 2 Mapping from the PMBOKR Guide to Agile 25

Chapter 3 The Agile Project Lifecycle in Detail 37

Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49

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 Agile 215

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

Glossary 321

Bibliography 327

Index 333

Read More Show Less

Preface

Preface

We are dedicated to the use of Agile practices in software development (a.k.a. Agilists), but we didn't start out that way. We began as Project Management Professionals (PMP®) 1 who used more traditional methods in the development of software.

Why We Wrote This Book

We followed the approaches outlined in the Project Management Institute's A Guide to the Project Management Body of Knowledge—Third Edition (PMBOK® Guide) for much of our careers, and in moving to Agile approaches we became more aware of the misconceptions out there surrounding the subject matter of this book—incorrect ideas that we once believed as well. Now as Agile consultants, we continue to hear our clients say that they believe (incorrectly) that if they are to keep their PMP certification and follow the practices outlined in the PMBOK® Guide that they must use a waterfall-like methodology. We also hear the mistaken belief that Agile approaches lack discipline and rigor. And we see the fear and dismay of those who believe that their investment in the Project Management Institute (PMI) may be for naught if they follow the path to agility.

It is our goal to dispel these myths in our book and show that the Third Edition of the PMBOK® Guide does in fact support Agile software development methods and that the investment that project managers have made in the PMI and in the practices outlined in the PMBOK® Guide are still solid and appropriate to pursue. It is clear to us that the PMBOK® Guide is methodology-neutral and supports good project management practices regardless of the approach chosen. Although many are already aware of this fact, we find that there are still many who are not. As PMPs who are now Agile enthusiasts, we feel it is important to also dispel the mistaken notion in the Agile community that PMPs cannot be good Agile project managers. We would like to build a bridge between the two, thus the need for this book.

Structure and Content of the Book

Accordingly, we've put much of the detail concerning this bridging in Part II, where we map the PMBOK® Guide's practices to Agile practices. It is our intent to show project managers that in moving to an Agile methodology, they do not move away from implementing PMI-recommended practices—they simply implement the practices in a different way, making sure that the intent behind these practices remains true. In some chapters you'll find a clear mapping, whereas in others the mapping is more imprecise. This book is intended to be a guide, a way to take the lexicon you are already familiar with and relate it to a new way of developing software. This book will not replace any of the more specific Agile practice books in the market today, and we encourage you to supplement this reading with other books on particular Agile methods (Scrum, XP, Lean, Crystal, and so on).

The next several sections provide a quick preview of the book.

Part I: An Agile Overview

Part I introduces you to the basic terms and concepts of Agile software development. We begin in the first chapter ("What is Agile?") with a look back at the emergence of agile ideas in the history of software development. You may be surprised to learn that even Winston Royce's paper on the waterfall approach recommended an iterative cycle and the involvement of the end user in the whole of the project! From this history we move forward and review the concepts behind the Agile Manifesto and its associated principles, which are the basis of all agile software development frameworks.

In Chapter 2, "Mapping from the PMBOK® Guide to Agile," we look at the history of the PMI and its most famous contribution to the practice of project management, the PMBOK® Guide. We'll examine how the PMBOK® Guide project lifecycle phases and project management process groups can be related to the Agile Fractal. And we'll reiterate again that you can be agile and be in keeping with the recommendations outlined in the PMBOK® Guide.

Chapter 3, "The Agile Project Lifecycle," describes the agile project lifecycle—from release planning to iteration planning to daily planning—and how demos, reviews, and retrospectives at the end of each iteration allow the team to continually improve. This chapter begins the use of terminology and concepts that we expand on throughout the rest of the book.

Part II: The Bridge: Relating PMBOK® Guide Practices to Agile Practices

This is the part of the book where we review each of the PMBOK® Guide knowledge areas and discuss what you used to do as a traditional project manager, and what you should consider doing instead as an agile project manager. As the title implies, we are trying to build an explicit bridge between the traditional and the agile, and provide you with guidance on what tasks and activities you should substitute—or keep.

As it is in the PMBOK® Guide, the knowledge areas are not in any type of chronological order. In both traditional and agile project management settings, you will find yourself doing most of these activities in parallel.

Because there is some overlap in the knowledge areas, you may find some ideas and concepts repeated. We did this intentionally, because we expect many of you to use this part of the book as a reference guide, and may therefore start with any of these chapters in any order. However, to keep the repetition to a minimum, we do use references to other chapters rather than rewrite large sections.

The chapters in Part II include the following:

  • Chapter 4: "Integration Management"
  • Chapter 5: "Scope Management"
  • Chapter 6: "Time Management"
  • Chapter 7: "Cost Management"
  • Chapter 8: "Quality Management"
  • Chapter 9: "Human Resources Management"
  • Chapter 10: "Communications Management"
  • Chapter 11: "Risk Management"
  • Chapter 12: "Procurement Management"

Part III: Crossing the Bridge to Agile

Whereas Part II covers the specific practical activity changes, Part III covers the softer skills of being an agent of change and what this change means for you personally and professionally. Having answered much of the "what" you need to do in Part II, we turn our focus to "how" to make these changes in Part III. From how your role changes, to how you'll work with others who aren't agile, to what to watch out for, we respond to the commonly asked questions of those who are about to cross the bridge. The chapters in Part III complete the main body of the book:

  • Chapter 13: "How Will My Role as a Project Manager Change?"
  • Chapter 14: "How Will I Work with Other Teams Who Aren't Agile?"
  • Chapter 15: "How Can a Project Management Office Support Agile? "
  • Chapter 16: "Selling the Benefits of Agile"
  • Chapter 17: "Common Mistakes"

Appendixes

We've included two appendixes we hope you will find useful. Appendix A, "Agile Methodologies," runs down a number of the software development methodologies that fall under the Agile umbrella. Appendix B, "Typical Agile Artifacts," includes a look at the typical Agile project "artifacts."

Who This Book Is For

Although this book is targeted at software project managers who are members of the PMI, anyone who is doing traditional software project management will benefit from seeing agility presented in terminology to which they are accustomed. We will refer to these long-established methodologies as "waterfall," "plan-driven," or "traditional," all of which refer to sequential, phased, noniterative approaches to software development.

Final Thoughts

We should also make it clear that we are not sanctioned by PMI or any of its representatives. This book is the result of our research, interpretation, and experience. Although we used the Third Edition of the PMBOK® Guide in our studies, we expect that as the PMBOK® Guide goes through further revisions, you will still find the concepts presented here to be relevant.

Endnotes

1. "PMP," "PMI," and "PMBOK Guide" are registered marks of Project Management Institute, Inc.

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Customer Reviews

Average Rating 3
( 5 )
Rating Distribution

5 Star

(2)

4 Star

(0)

3 Star

(1)

2 Star

(1)

1 Star

(1)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 5 Customer Reviews
  • Anonymous

    Posted April 11, 2010

    Highly recommended book for beginners (PMPs)!!!

    Highly recommended book for those who has good understanding of PMBOK and wants to move to Agility. Very good comparison of how we do things in traditional project management and how we will do it in Agile project management.

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted June 17, 2008

    Excellent advice for project managers making the change to agile

    This excellent book is targeted directly at Project Management Professionals (PMPs) but will be extremely beneficial to any project manager who is interested in agile development. 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.

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted May 12, 2013

    No text was provided for this review.

  • Anonymous

    Posted August 16, 2009

    No text was provided for this review.

  • Anonymous

    Posted March 9, 2013

    No text was provided for this review.

Sort by: Showing all of 5 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)