| ||||||||||||
 Trade In this Item for up to £11.70
Trade in Agile Software Development with SCRUM for an Amazon.co.uk gift card of up to £11.70, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Authors
Discover books, learn about writers, and more.
Product Description
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
Product Description
eXtreme Programming is an ideal many software shops would love to reach, but with the constant pressures to produce software quickly, they cannot actually implement it. The Agile software process allows a company to implement eXtreme Programming quickly and immediately-and to begin producing software incrementally in as little as 30 days! Implementing eXtreme Programming is easier said than done. The process can be time consuming and actually slow down current software projects that are in process. This book shows readers how to use SCRUM, an Agile software development process, to quickly and seamlessly implement XP in their shop-while still producing actual software. Using SCRUM and the Agile process can virtually eliminate all downtime during an XP implementation.
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
Sell a Digital Version of This Book in the Kindle Store
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
26 of 26 people found the following review helpful:
4.0 out of 5 stars
A paradigm shift in software development,
By
This review is from: Agile Software Development with SCRUM (Paperback)
5 stars to the writers, less of them to the publisher (you don't get to see graphics that bad these days). I read 'Extreme Programming Explained' almost two years ago, enjoyed it, and changed some of my views on the development process; I adopted some practices, but the XP Planning Game did not fit in our process. I the read 'Agile Software Development Ecosystems', enjoyed it, and learned that XP was not the only alternative to the conventional software development process. Now, Scrum, and its well thought simplicity, has shown me a proven and understandable way to manage software projects, and deepened the changes that the XP book stared on me.The discussion on the "defined process control model" vs the "empirical process control model", in Chapter 2 and available on line, should be mandatory reading for any one involved with IT. Chapter 5 extends this discussion and is also outstanding. Chapter 6 provides several models/views to explain Scrum; having several models of the same thing is something that you do very often when doing software design and deepens your understanding of the system; I liked the use of this technique in prose and the very interesting models covered. Read it. You may not want to become a Scrum practitioner, but the book will probably change the way that you think about software development.
16 of 16 people found the following review helpful:
5.0 out of 5 stars
Ideas that work with new terminology,
By
This review is from: Agile Software Development with SCRUM (Paperback)
This book explains some very useful methods for delivering customer-focused solutions. Aside from a new set of terminology to get used to, the book cites the usefulness of: fast daily status meetings ("Scrums"), 'locked' 30-day iterations ("Sprints") that deliver working code at the end, small teams of 6-8 multi-skilled people, a prioritised book of work that is re-appraised every 30 days ("Backlog"), regular assessment of the work effort in the backlog rather than using a project plan, collective responsibility for delivery. I have seen people use these methods in successful projects within my company but they didn't know they were using Scrum, they were just doing things that they felt were right, have worked for them in the past and enabled them to focus on driving out a solution that would meet the real needs of the users.
9 of 9 people found the following review helpful:
2.0 out of 5 stars
Disappointed,
By Paolo (Italy) - See all my reviews
This review is from: Agile Software Development with SCRUM (Paperback)
This book has been disappointing and boring. You can find the most interesting parts also in Ken Schwaber's speech at Google Tech Talks (Scrum Et Al, September 5, 2006). Throughout the book, the authors try to sell Scrum. I wanted to learn how to use this methodology, but they kept focusing just on how cool it is for the company.
Scrum is great (i suppose!) but this book is definitely NOT worth buying. Note: I didn't consider in the vote the poor quality of the figures. The resolution sometimes is so low that you can't even read what is written on the diagrams.
Share your thoughts with other customers: Create your own review
Would you like to see more reviews about this item?
|
Most Recent Customer Reviews |
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
