Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$22.45$22.45
FREE delivery: Tuesday, March 19 on orders over $35.00 shipped by Amazon.
Ships from: Amazon.com Sold by: Amazon.com
Buy used: $7.33
Other Sellers on Amazon
+ $5.20 shipping
92% positive over last 12 months
FREE Shipping
98% positive over last 12 months
FREE Shipping
100% positive over last 12 months
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Agile Project Management with Scrum (Developer Best Practices) 1st Edition
Purchase options and add-ons
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 more valuable software faster.
Gain the foundation in Scrum theory―and practice―you need to:
- Rein in even the most complex, unwieldy projects
- Effectively manage unknown or changing product requirements
- Simplify the chain of command with self-managing development teams
- Receive clearer specifications―and feedback―from customers
- Greatly reduce project planning time and required tools
- Build―and release―products in 30-day cycles so clients get deliverables earlier
- Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects
- Support multiple teams working on a large-scale project from many geographic locations
- Maximize return on investment!
- ISBN-10073561993X
- ISBN-13978-0735619937
- Edition1st
- PublisherMicrosoft Press
- Publication dateFebruary 11, 2004
- LanguageEnglish
- Dimensions7.4 x 0.8 x 9 inches
- Print length192 pages
Frequently bought together

Similar items that may deliver to you quickly
From the Publisher
From the Mike Cohn Signature Series
The Addison-Wesley Signature Series: Mike Cohn
Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. He is the author of User Stories Applied for Agile Software Development and Agile Estimating and Planning, as well as books on Java and C++ programming. With more than 20 years of experience, Mike has previously been a technology executive in companies of various sizes, from startup to Fortune 40. A frequent magazine contributor and conference speaker, Mike is a founding member of the AgileAlliance, and serves on its board of directors.
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|
| Essential Scrum | The Scrum Field Guide | The Great ScrumMaster | Agile Project Management with Scrum | Succeeding with Agile | Driving Value with Sprint Goals | |
| A practical guide to the most popular agile process | Advice for your first year and beyond | Fast, focused, practical guide | Real-world lessons | Proven, practical guidance to making Scrum work in any organization | Critical Scrum and product management fundamentals through the lens of the Sprint Goal | |
| Kenneth Rubin | Mitch Lacey | Zuzana Sochova | Ken Schwaber | Mike Cohn | Maarten Dalmijn | |
| "This book serves as an indispensable guide, helping teams choose among the billions of possible ways of implementing Scrum and finding one that leads to success." — Mike Cohn, author of "Succeeding with Agile", Certified Scrum Trainer | "…I can definitely recommend Mitch’s book! I am confident that you will find my book and this book to be good compliments to one another, even (and especially) where the two differ on particular issues or approaches." -- Kenneth Rubin | "[Sochova] fills an important gap in providing practical advice and tools for ScrumMasters who wish to improve their craft. The book is full of powerful tips sure to help any ScrumMaster." — Mike Cohn | "This book is an excellent guide for anyone looking to improve how he or she delivers software, and I recommend it highly." — Mike Cohn, author of "Succeeding with Agile", Certified Scrum Trainer | "By reading this book, you will find that Mike brings up issues that you never thought of, offers advice on how you might handle situations, and helps you define new roles on your team." -- Tim Lister, Principal, The Atlantic Systems Guild, Inc | "'Sprint Goals are the beating heart of Scrum,'. Without them, Scrum falls apart. Maarten makes a powerful argument for why Scrum teams need Sprint Goals and offers invaluable anecdotes, practical tips and guidelines to get started right away." |
Editorial Reviews
About the Author
A 30-year veteran of the software development industry, Ken Schwaber is a leader of the agile process revolution and one of the developers of the Scrum process. A signatory of the Agile Manifesto in 2001, he subsequently founded the Agile Alliance and the Scrum Alliance. Ken authored Agile Project Management with Scrum and coauthored Agile Software Development with Scrum and has helped train more than 47,000 certified ScrumMasters.
Product details
- Publisher : Microsoft Press; 1st edition (February 11, 2004)
- Language : English
- Paperback : 192 pages
- ISBN-10 : 073561993X
- ISBN-13 : 978-0735619937
- Item Weight : 11.5 ounces
- Dimensions : 7.4 x 0.8 x 9 inches
- Best Sellers Rank: #106,357 in Books (See Top 100 in Books)
- #12 in Agile Project Management
- #37 in Software Testing
- #121 in Software Development (Books)
- Customer Reviews:
Important information
To report an issue with this product or seller, click here.
About the author

Ken Schwaber is president of Advanced Development Methods (ADM), a company dedicated to improving the software development practice. He is an experienced software developer, product manager, and industry consultant. Schwaber initiated the process management product revolution of the early 1990's and also worked with Jeff Sutherland to formulate the initial versions of the Scrum development process.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
I'll briefly explain how SCRUM has helped me consider new possibilities on each of the above mentioned areas. In addition, I'll start off with a general perception of this book.
If asked to sum up my thoughts in one word on Agile Project Management with SCRUM, it would be "REVOLUTIONARY"!
Even though the text is focused on software development as the domain where SCRUM is applied, it's easy to see how SCRUM can be applicable to any project.
SCRUM is based on a well defined set of rules and a set of roles which include a ScrumMaster, a Product Owner, and a team(s). I found it revolutionary as it works exceptionally well in complex, chaotic project situations, and it empowers a team in new ways, and forges new optimized partnering between those delivering (the team) and those consuming (the customers). SCRUM also focuses on ROI and regular prioritized delivery of business value.
The Solution Sales view:
SCRUM offers a new approach to bid on complex, fixed-price, fixed-date RFPs. To do this, a bidding firm would have to collaborate with the client up front, to explain the differences between between a traditional waterfall-based approach and the SCRUM approach. An enlightened client will see the opportunity for partnering in new ways with a supplier, and how SCRUM minimizes risk and increases flexibility while keeping the spotlight on business value as defined by customer's prioritized needs. Communication is based on business value, not technical jargon, which also leads to increased customer satisfaction.
The Project Management view (traditional):
When I studied to become Project Management Professional (PMP) certified, I learned many formalized methods for managing, controlling, reporting, and delivering on a project. SCRUM is a complete paradigm shift, but it rapidly starts to feel good. The author illustrates through numerous case studies how a project manager, now a ScrumMaster, contributes and can still meet management's requirements for information reporting and results. The text also highlights CMM KPA's and how SCRUM still ensures compliance.
The Contract/Vendor Management view:
Having taken a formal program in contract management and having been both on the vendor and vendor management sides of the fence, I began thinking early into the book how SCRUM would impact these areas. My thinking here ties into my earlier thoughts on the Solution Sales view -- SCRUM provides a new model of Supply Chain Management (SCM) and partnering that can reduce costs and improve results. A side effect that leaped out at me is that I believe that SCRUM could have a dramatic effect on minimizing the need to offshore delivery. By having a resident local team using SCRUM, results look so positive based on the case studies I read, that SCRUM could increase onshoring due to its rapid results (achieved within a 30 day Sprint), team/customer cohesion, and more. Offshore delivery would still be very possible using SCRUM and improve results, however, I can imagine the value of the shared space partnership between a local team and local customers at its positive macroeconomic impact as well.
The SQA view:
I've been a QA engineer and manager. QA adds necessary value, however, it is often seen as a policeman role, or an afterthought where quality is "tested" in. The identification of last minute defects causes angst, anger, increased costs, and customer dissatisfaction. The latter often being due to great pressure to ship anyway or solutions that can't be fully tested in time which lead to customer identified defects (and costs), or bug-fix delays impact client schedules/needs.
SCRUM makes testing a component of "doneness" -- embedded in a concept which SCRUM calls "sashimi" after the Japanese delicacy. In a nutshell, testing becomes everyone's job and the team partners to produce a complete result as committed to at the beginning of the Sprint. No more policeman. Instead, a committed team that works together in an optimized manner.
In summary, SCRUM provides much to think about for Sales, Project Management, Software Development, Contract Management, and QA professionals. It is an exciting process that has undeniable value.
This is a good second book. It attends less to the basics of running the team and working with the customers and corporate surroundings, although Schwaber does present all those basics. Instead, the focus is on case studies, especially ones that look like bad matches to Scrum management style. I like that emphasis: typical methodology books assume perfect compliance with fragile or rare prerequisite assumptions, then wash their hands of any circumstance that doesn't meet their delicate needs. This is a good bit more realistic - it's about the whole concept of cut-and-fit to get the most out of Scrum despite unfavorable situations and stakeholders.
Late in the book, Schwaber makes the point that people will do whatever they're rewarded for. However obvious this sounds, it's an ongoing source of corporate inanity. Suppose that percent of the code covered in testing is a major goal: programmers will dutifully eliminate handling of exceptional conditions or invalid preconditions for which tests are hard to generate (NOT an improvement). Suppose reduced development time is rewarded: watch testing time plummet and bug counts soar. I agree that progress must be measurable, and agree at the top of my lungs that the wrong measurements are worse than none at all.
Still, one theme comes through again and again: that, when the going gets weird, typical practitioners will rapidly find themselves in way over their heads. He, with more experience than any other Scrumster around, exerts the limits of his creativity to get past problems of fairly ordinary kinds (like intrasigent management). It's certainly a good recommendation for his consulting services. It's just not a message that a novice wants to hear. I have the strongest reservations about his fondness for bullpen office environments, as well.
There's good to be had here, I'm sure, but I'd have to see Scrum in action before I could really internalize the way it's meant to work.
//wiredweird
PS: It's just an amusing typo, not a deliberate act that "the ... team was going to use Scum [sic]," p.64
The book's laid out in a series of stories which illustrate responsibilities and typical problems to overcome for the Scrum roles of Product Owner, ScrumMaster, and Team. The stories are short, concise, and followed up by Lessons Learned which cover salient highlights for the various points made in the section. Throughout the book runs Schwaber's theme of how one can use Scrum to solve any number of problems and increase the productivity of their development work.
What's really nice about the book is that there are stories of failures as well as successes. Software development is rarely all roses, so it's nice to see a couple examples where things didn't work -- and a solid analysis of what went wrong in those cases.
On the flipside, I'd have liked a bit more detail on constructing the sprint and product backlogs. I realize that traipses somewhat over into the realm of software estimation, but more fleshing out would have been helpful. However, there's a great example of scaling Scrum and rolling up numerous product backlogs from lower levels in to a larger backlog for a major system, so that's quite beneficial.
The book's terrifically well-written, is an easy read, and is formatted such that you're able to quickly pick up the important bits of Scrum. It's a terrific read for anyone looking to bring some sensible, tailorable processes to their software development efforts.
Top reviews from other countries
Solo il Capitolo 1 è dedicato alla teoria di Scrum: il resto del libro rispecchia l'opinione dell'autore secondo cui Scrum non può essere appreso studiando la teoria ma piuttosto un team deve applicarla a una situazione pratica per poter davvero gestire il framework.
Schwaber passa poi rapidamente a diversi casi di studio, mostrando come Scrum è stato applicato in varie situazioni complesse.
Scrum Masters would benefit from the various scenarios presented. They would get guidance on how to proceed if they face similar situations. The learning section at the end of each scenario instills the concepts.
I would recommend it for all new Scrum Masters.







