Agile Software Development with Scrum (Series in Agile Software Development) 1st Edition
|
Ken Schwaber
(Author)
Find all the books, read about the author, and more.
See search results for this author
Are you an author?
Learn about Author Central
|
|
Mike Beedle
(Author)
Find all the books, read about the author, and more.
See search results for this author
Are you an author?
Learn about Author Central
|
Use the Amazon App to scan ISBNs and compare prices.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
-
Apple
-
Android
-
Windows Phone
-
Android
|
Download to your computer
|
Kindle Cloud Reader
|
Frequently bought together
Customers who viewed this item also viewed
Agile Project Management with Scrum (Developer Best Practices)Paperback
Scrum: The Art of Doing Twice the Work in Half the TimePaperback
Agile Estimating and PlanningPaperback
The Professional Product Owner: Leveraging Scrum as a Competitive AdvantagePaperback
User Stories Applied: For Agile Software DevelopmentPaperback
Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, and Leave Competitors in the DustPaperback
More items to explore
User Stories Applied: For Agile Software DevelopmentPaperback
Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn))Kenneth RubinPaperback
The Professional Product Owner: Leveraging Scrum as a Competitive AdvantagePaperback
Agile Retrospectives: Making Good Teams GreatPaperback
Clean Code: A Handbook of Agile Software CraftsmanshipPaperback
Refactoring: Improving the Design of Existing Code (2nd Edition) (Addison-Wesley Signature Series (Fowler))Hardcover
Editorial Reviews
Review
"Agile development methods are key to the future of flexible software systems. Scrum is one of the vanguards of the new way to buy and manage software development when business conditions are changing. This book distills both the theory and practice and is essential reading for anyone who needs to cope with software in a volatile world." ― Martin Fowler, industry consultant and CTO, ThoughtWorks
"Most executives today are not happy with their organization's ability to deliver systems at reasonable cost and timeframes. Yet, if pressed, they will admit that they don't think their software developers are not competent. If it's not the engineers, then what is it that prevents fast development at reasonable cost? Scrum gives the answer to the question and the solution to the problem. ― Alan Buffington, industry consultant, former Present, Fidelity Systems Company
From the Back Cover
Arguably the most important book about managing technology and systems development efforts, this book describes building systems using the deceptively simple process, Scrum. Readers will come to understand a new approach to systems development projects that cuts through the complexity and ambiguity of complex, emergent requirements and unstable technology to iteratively and quickly produce quality software.
BENEFITS- Learn how to immediately start producing software incrementally regardless of existing engineering practices or methodologies
- Learn how to simplify the implementation of Agile processes
- Learn how to simplify XP implementation through a Scrum wrapper
- Learn why Agile processes work and how to manage them
- Understand the theoretical underpinnings of Agile processes
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.
Mike Beedle, an experienced software development practitioner, is the founder and CEO of e-Architects, Inc., a management and technical consulting company that helps its clients develop software in record time. Beedle has contributed to thousands of software projects for the last 20 years, and has used, recommended, and guided others to implement Scrum since 1995.
Excerpt. © Reprinted by permission. All rights reserved.
This book was written for several audiences. Our first audience is application development managers that need to deliver software to production in short development cycles while mitigating the inherent risks of software development. Our second audience is the software development community at large. To them, this book sends a profound message: Scrum represents a new, more accurate way of doing software development that Is based on the assumption that software is a new product every time that it is written or composed. Once this assumption is understood and accepted, it is easy to arrive at the conclusion that software requires a great deal of research and creativity, and the therefore it is better served by a new set of practices that generate a self-organizing structure while simultaneously reducing risk and uncertainty.
Finally, we have also written this book for a general audience that includes everyone involved in a project where there is constant change and unpredictable events. For this audience Scrum provides a general-purpose project management system that delivers, while it thrives on change and adapts to unpredictable events.
Software as "new product" as presented in this book, is radically different from software as "manufactured product", the standard model made for software development throughout the last 20 years. Manufacture-like software methods assume that predictability comes from defined and repeatable processes, organizations, and development roles; while Scrum assumes the process, the organization, and the development roles are emergent but statistically predictable, and that they arise from applying simple practices, patterns and rules. Scrum is in fact much more predictable and effective than manufacturing-like processes, because when the Scrum practices, patterns and rules are applied diligently, the outcome is always; 1) higher productivity, 2) higher adaptability, 3) less risk and uncertainty, and 4) greater human comfort.
The case studies we provide in this book will show that Scrum doesn't provide marginal productivity gains like process improvements that yield 5-25% efficiencies. When we say Scrum provides higher productivity, we often mean several orders of magnitude higher i.e. several 100 percents higher. When we say higher adaptability, we mean coping with radical change. In some case studies, we present cases where software projects morphed from simple applications in a single domain to complex applications across multiple domains: Scrum still managed while providing greater human comfort to everyone involved. Finally, we show through case studies that Scrum reduces risk and uncertainty by making everything visible early and often to all the people involved and by allowing adjustments to be made as early as possible.
Throughout this book we provide 3 basic things: 1) an understanding of why this new thinking of software as new product development is necessary, 2) a thorough description of the Scrum practices that match this new way of thinking with plenty of examples, and 3) a large amount of end-to-end case studies that show how a wide range of people and projects have been successful using Scrum for the last 6 years.
This last point is our most compelling argument: The success of Scrum is overwhelming. Scrum has produced by now billions of dollars in operating software in domains as varied as finance, trading, banking, telecommunications, benefits management, healthcare, insurance, e-commerce, manufacturing and even scientific environments.
It is our hope that you, the reader of this book, will also enjoy the benefits of Scrum, whether as a development staff member wishing to work in a more predictable, more comforting, and higher producing environment, or as a manager desiring to finally bring certainty to software development in your organization.
Mike Beedle, Chicago
Ken Schwaber, Boston
I'd like to read this book on Kindle
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product details
- Publisher : Pearson; 1st edition (October 11, 2001)
- Language : English
- Paperback : 176 pages
- ISBN-10 : 0130676349
- ISBN-13 : 978-0130676344
- Item Weight : 10.2 ounces
- Dimensions : 6.02 x 0.47 x 9.02 inches
-
Best Sellers Rank:
#105,672 in Books (See Top 100 in Books)
- #76 in Software Design & Engineering
- #200 in Software Development (Books)
- #362 in Computer Software (Books)
- Customer Reviews:
Customer reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Scrum is more then just morning meetings or backlog lists. It is a process control system and every part of it is essential. Saying you "do Scrum": but only have morning meetings or backlogs is like saying you have a foundry control system with no feedback sensors. If you don't crash and burn, its just luck that is saving you.
Here's a radical proposal: why don't we just say that we're going to do (and then do) what we were going to do anyway? That's Scrum. It's built around short time-scales, a month or so, the kind where forecasting has a chance to work. It counts on simple plans with unambiguous goals, to be completed within those timeframes. It demands that people just go ahead and do what needs to be done, even if a few rules get bent, things that people would have done anyway. The difference lies in doing them with head held high, not as midnight missions intended to sneak success into fundamentally broken plans, in spite of counter-productive rules.
The consequences of the approach are far-reaching. For one, it outlaws the plus-one disease, or mission creep, or feature-itis, or whatever you call it. This plain-spoken approach makes promises and works to keep them - having the content of the promise changed by fiat, halfway through, is outlawed. There's a time and a place new commitements to be made, and that is not in the heat of the development moment. "Scrum" uses many sports analogies, and moving the goalposts (or having them moved) is not part of its game.
There's a lot more too it, of course, and that's why describing Scrum takes a whole book. It has a lot to like, including an emphasis on personal responsibility and even bravery - things that many work environments punish brutally. I don't go along with the authors' revival tent true-believerism. Despite that, there's enough good sense in this book to soften even doubts as solidified as mine.
//wiredweird
Schwaber is the "Godfather of Scrum" and essentially invented the techniques; Beedle was one of the first converts to Scrum and together they definitely know their stuff.
The book covers everything from the theoretical basis for Scrum to how to organize your teams, conduct daily Scrum meetings to keep things moving along, to planning your Scrum project, to tracking the "backlog" of items that need to be completed to finish a project.
Scrum is not a rehash of another methodology. As the authors say, "Scrum is different." Some of the things you'll learn in this book will seem counterintuitive but they work and the authors do a great job of laying out enough information to, if not fully convince you, then at least persuade you to give Scrum a try. (And once you've done that, you'll be convinced!)
I think this book is especially important for anyone reading any of the XP books that have come out over the past two years. Scrum provides an excellent management wrapper around the techniques of XP.
This book is great because it's only 150 pages but everything is succinct and clear--very different from some other books on project management techniques that are needlessly long.
After reading this book you will know everything needed to get started with a Scrum project--and most likely that project will be more successful with Scrum than with whatever process you're using currently.
Highly recommend this book!!
Thanks, Ken!!
My big complaint is the physical quality of the pages. First, the text is very light. The pages are so thin, you can see text from the flip side through it obscuring what you're reading. The figures and tables are amateurish at best. Very hard to physically reads this book.
Top reviews from other countries
Explore similar books
- Great ScrumMaster, The: #ScrumMasterWay (Addison-Wesley Signature Series (Cohn))
Paperback$32.99$32.99




























