The Kindle title is not currently available for purchase

You've subscribed to ! We will preorder your items within 24 hours of when they become available. When new books are released, we'll charge your default payment method for the lowest price available during the pre-order period.

Update your device or payment method, cancel individual pre-orders or your subscription at
Your Memberships & Subscriptions

There was an error. We were unable to process your subscription due to an error. Please refresh and try again.

Follow the author

Ken Schwaber

Follow

Agile Project Management with Scrum (Developer Best Practices) 1st Edition, Kindle Edition

by Ken Schwaber (Author) Format: Kindle Edition

4.4 385 ratings

Part of: Developer Best Practices (23 books)

See all formats and editions

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-13

978-0735619937
Edition

1st
Sticky notes

Not Enabled
Publisher

Microsoft Press
Publication date

February 11, 2004
Part of series

Developer Best Practices
Language

English
File size

970 KB
See all details

Report an issue with this product or seller

Read with the free Kindle apps (available on iOS, Android, PC & Mac), Kindle E-readers and on Fire Tablet devices. See all supported devices

Next 5 for you in this series See full series

Total Price: $108.36

By clicking on the above button, you agree to Amazon's Kindle Store Terms of Use

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

ASIN ‏ : ‎ B004OR1XHY
Publisher ‏ : ‎ Microsoft Press; 1st edition (February 11, 2004)
Publication date ‏ : ‎ February 11, 2004
Language ‏ : ‎ English
File size ‏ : ‎ 970 KB
Simultaneous device usage ‏ : ‎ Unlimited
Text-to-Speech ‏ : ‎ Enabled
Enhanced typesetting ‏ : ‎ Not Enabled
X-Ray ‏ : ‎ Not Enabled
Word Wise ‏ : ‎ Not Enabled
Sticky notes ‏ : ‎ Not Enabled
Print length ‏ : ‎ 277 pages

Customer Reviews:
4.4 385 ratings

Brief content visible, double tap to read full content.

Full content visible, double tap to read brief content.

Videos

Help others learn more about this product by uploading a video!

Upload your video

About the author

Follow authors to get new release updates, plus improved recommendations.

Ken Schwaber

Brief content visible, double tap to read full content.

Full content visible, double tap to read brief content.

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

4.4 out of 5

385 global ratings

How customer reviews and ratings work

Sort reviews by

Top reviews from the United States

There was a problem filtering reviews right now. Please try again later.

Amazon customer

Thinking outside of the cubical -- reducing complexity and the art of the possible

Reviewed in the United States on August 25, 2010

Verified Purchase

I came at this book from several perspectives based on my background in Solutions Sales, Project Management (traditional -- PMP certified), Contract/Vendor Management, and SQA Management.

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.

One person found this helpful

Helpful

wiredweird

Credible, but I'll have to see for myself.

Reviewed in the United States on October 17, 2006

Verified Purchase

The Scrum principle is simple. It starts with some common observations: that projects generally succeed when someone sidesteps the formal process and gets the job done anyway, and that big teams spend more time tripping over each other than typing code. Scrum starts with the radical idea of announcing that we're going to do what we were going to anyway, then mixing in big handfuls of eXtreme Programming.

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

3 people found this helpful

Helpful

Jim Holmes

Concise read on the value of Scrum -- and how to implement it

Reviewed in the United States on January 30, 2007

Verified Purchase

I bought this after hearing Scott Hansleman talk about it on his scrum podcast at [...]. I figure Scott seems to have had great success with Scrum at his place of work ([...]so any book he recommended on the topic ought to be solid. Indeed it is!

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.

4 people found this helpful

Helpful

Top reviews from other countries

Translate all reviews to English

Jessica Veridiana

Nice!

Reviewed in Brazil on July 23, 2023

Verified Purchase

Schwabber shares a lot of experience in this book.

Kornelia Küster

Gutes Buch

Reviewed in Germany on October 30, 2023

Verified Purchase

Ein gutes Buch zur Prüfungsvorbereitung

Translate review to English

Andrea, Jole, Giugiu e Lilli

Scorrevole e molto incisivo

Reviewed in Italy on November 28, 2021

Verified Purchase

Un'eccellente scorrevole testo che spiega come adottare Scrum nei vari contesti progettuali.

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.

One person found this helpful

Translate review to English

Heather

Great Resource & Reference information for Scrum leaders.

Reviewed in Canada on September 20, 2018

Verified Purchase

I purchased this as a gift for my spouse. He's most pleased with the breadth and depth of the contents in this book. My spouse teaches how to develop & implement computer games. Our son, uses "Scrum" format during his team meetings. He's perused this book and feels it would be valuable for everyone needing project management skills. Keeping teams on task & on track is an art that can be learned with the aid of this publication.

N. Murali Mohan

A must read for all Scrum Masters

Reviewed in India on March 18, 2018

Verified Purchase

The author presents around 25 different scenarios / challenges that he faced and how he resolved those. The book is still relevant even after two decades of its publication!!!

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.