Sign in with Facebook
Loading...
64th out of 85 books
—
30 voters
Agile Software Development with Scrum
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...more
Paperback, 158 pages
Published
October 11th 2001
by Prentice Hall
Friend Reviews
To see what your friends thought of this book,
please sign up.
Community Reviews
(showing
1-30
of
595)
Having been involved in attempts at Agile/Scrum in three companies now, I can say that the method--I refuse to call it a methodology as it is not the study of methods--has things to recommend it.
This book, however, is overlong and burdened with sales pitches. If one were to glean the wheat from the chaff, the page count might drop to 50 pages or fewer. Not one but two introductory chapters (following two forewords and a preface) stand in one's way before chapter 3, which is the first to get down...more
This book, however, is overlong and burdened with sales pitches. If one were to glean the wheat from the chaff, the page count might drop to 50 pages or fewer. Not one but two introductory chapters (following two forewords and a preface) stand in one's way before chapter 3, which is the first to get down...more
3 likes · like · see review
view all 5 comments
Can the authors be any more full of themselves?
When I went to such and such company "I" implemented this, "I" established that. I thought agile software development was about the team, not lauding individual accomplishments. An irony the authors seemed to have overlooked.
BTW, have you ever been to a company where agile development just plain failed? Just flat out sucked. I've worked at two companies in the last year where they brought in expensive consultants/analysts to help implement agile dev...more
When I went to such and such company "I" implemented this, "I" established that. I thought agile software development was about the team, not lauding individual accomplishments. An irony the authors seemed to have overlooked.
BTW, have you ever been to a company where agile development just plain failed? Just flat out sucked. I've worked at two companies in the last year where they brought in expensive consultants/analysts to help implement agile dev...more
2 likes · like · see review
This isn't the best book out there about Agile or Scrum. (I'm not sure which book is the best, but it's definitely not this one.)
If you're interested less in how to apply Scrum and more in the authors' personal experiences in discovering Scrum and why they think it's a good idea, then this could be an okay book. If they had any experiences where Scrum didn't work spectacularly, though, those aren't included here.
It's particularly intriguing that in the Introduction chapter, when discussing intro...more
If you're interested less in how to apply Scrum and more in the authors' personal experiences in discovering Scrum and why they think it's a good idea, then this could be an okay book. If they had any experiences where Scrum didn't work spectacularly, though, those aren't included here.
It's particularly intriguing that in the Introduction chapter, when discussing intro...more
(4.0) Overall nice and concise, fair bit of proselytizing though
As with many methodology books, there's plenty of "really, this works!" and "I saved so many projects that were in the toilet," so just try to skim through those (or omit entirely). The rest is pretty good. You should read chapters 2 (intro--quickly), 3 (how-to), 4 (how-to), 6 (why it works), 7 (multi-team projects) and 9 (core values of scrum).
The core elements to scrum:
* remove distractions and let team focus on demonstratable fea...more
As with many methodology books, there's plenty of "really, this works!" and "I saved so many projects that were in the toilet," so just try to skim through those (or omit entirely). The rest is pretty good. You should read chapters 2 (intro--quickly), 3 (how-to), 4 (how-to), 6 (why it works), 7 (multi-team projects) and 9 (core values of scrum).
The core elements to scrum:
* remove distractions and let team focus on demonstratable fea...more
Perhaps I shouldn't have read this while sick with the flu.
If you're working in an organization that already uses Scrum, or some flavor thereof, then chapters 3–5 offer some useful background. Had I been coming to this book cold, however, it would have been a real slog to learn from. The text is slathered in business jargon and mumbo-jumbo, like this example from page 12:
If you're working in an organization that already uses Scrum, or some flavor thereof, then chapters 3–5 offer some useful background. Had I been coming to this book cold, however, it would have been a real slog to learn from. The text is slathered in business jargon and mumbo-jumbo, like this example from page 12:
A fully integrated component design environment leads to rapid evolution of a software system with emergent, adaptive propert...more
2 likes · like · see review
Like most of the people I know who've read this book, I skimmed a good deal of it. It gives a lot of insight into why Scrum is such an attractive method of development (especially for startups), and explains the things that need to be cultivated to allow this process to succeed. In that sense, the book was pretty interesting. However, it wasn't very well written. It seemed like the two authors wrote slightly differently-worded versions of the same ideas, and since this was written in 2004 when v...more
1 like · like · see review
SCRUM is a process I had heard a lot about but I hadn't ever really learned about. I'm glad I did learn about it, how it works and how it came about.
The main idea is to enable development teams to focus on development without distractions or interruptions from management or anywhere else.
The most helpful part was the section on empirical process control and how such an approach is the only way to deal with creative development. The defined process approach can never work; despite what they may...more
The main idea is to enable development teams to focus on development without distractions or interruptions from management or anywhere else.
The most helpful part was the section on empirical process control and how such an approach is the only way to deal with creative development. The defined process approach can never work; despite what they may...more
Good book on formal Scrum - nice refresher on the "how" and "why" behind Scrum methodology. Would be lying if I said I didn't skim some of it. After a few "case studies" around what's wrong with traditional waterfall methodologies, you get the point. I'm guessing these parts were more interesting when the book initially came out and the whole concept of Scrum was a bit more revolutionary. It's been 12 years since the publish date- which is a long time in technology. (For example, they strongly r...more
1 like · like · see review
Putting together software is hard. This book outlines a method, called Scrum, of organizing the people involved in a software project. The authors argue that creating software is a process that operates in an incompletely defined environment: target markets change, old technologies are supplanted or redefined by the new, new target platforms arise, etc. Management by careful prediction based on initial conditions is thwarted by the nonlinear dynamics that permeate the development environment; or...more
web application
***************
Aparajayah Technologies is a leading web development company in India an application development and outsourcing company situated in Madurai. Services include software development, web development and Search engine optimization.
http://www.aparajayah.com/mobileappli...
***************
Aparajayah Technologies is a leading web development company in India an application development and outsourcing company situated in Madurai. Services include software development, web development and Search engine optimization.
http://www.aparajayah.com/mobileappli...
Not a bad place to start when learning about scrum, though not too practical for all types of projects. You will be better off learning from one of the more modern books, then going for this to get some fundamentals and see where scrum comes from.
This book provides a great introduction to the Agile development process which is really Getting Things Done for business. It has changed the way I want to structure organizations around me and has amazing strategies. I highly recommend this book.
Excellent book for understanding scrum - learn where it came from, learn how the author and others have used it to solve their management problems and get the basics of scrum from the guys that started it.
This is the book that changed my whole attitude to software development. The ideas were similar to my own thinking, but it was pleasing to find all the ideas summed up and put into a working framework.
I suppose it is one of the first books about Scrum and mandatory for anyone doing Scrum. Especially since the author Ken Schwaber is one of the most prominent figures up there in the Scrum Olymp.
Personally I think that regarding info and writing there are better books. He does explains the ideas, values and principles of Scrum and gives examples. But still, I much preferred reading "Scrum from the Trenches" fror example or any of the books by Mike Cohn.
I'll also try out Boris Gloger Scrum handbo...more
Personally I think that regarding info and writing there are better books. He does explains the ideas, values and principles of Scrum and gives examples. But still, I much preferred reading "Scrum from the Trenches" fror example or any of the books by Mike Cohn.
I'll also try out Boris Gloger Scrum handbo...more
Most of what you need to know is in the first few chapters. The book reads like the material came from a bunch of presentations or atricles/case studies that were tied together but at 154 pages it's not too painful. I enjoyed reading the Agile Product Management with Scrum book better, not necessarily for the content but for the ease of reading. They are short books and worth reading.
This is our 'basic text' for our use of Scrum. It explains why it delivers the benefits we are trying to attain. All of the managers have a copy.
I thought it was an interesting approach to project management. I would recommend several chapters in it to any new team.
The "No B.S." book on Scrum. What Scrum is all about, and nothing else. Simple, short, valuable book.
Feb 10, 2010
Ben Haley
marked it as to-read
Another from the Art of Project Management which will be useful for the type of development we do at PERTS.
A should-read book on product development for knowledge workers and entrepreneurs.
This book describes Scrum, but is no longer entirely accurate according to the commonly accepted formula. It is also full of rhetoric and marketing that make it an extremely tedious read.
More suited for a project manager than from a developer's perspective.
Could be at least two times shorter telling exactly the same information.
A quick read, Agile Software Development with SCRUM provides a practical introduction to the methodology, emphasizing the value delivered by the ideology while explaining scrum process mechanics. This is the first book I give to folks I'm bringing into the process.
Yes, the initial book on Scrum so it's 5/5 for the thinking, the ideas, the change it started. The book itself, is not an easy read, is not very consistent and some of the thinking have now moved on, better to read software in 30 days these days methinks.
The "de facto" scrum book, a good quick read on the basics of scrum and how to implement it.
Bloated with useless acronyms, unnecessary graphs, and cumbersome sentences. Poorly organized and poorly written. Where the hell was the editor?
Scrum's a useful software development methodology, but it's not well presented here.
Scrum's a useful software development methodology, but it's not well presented here.
One of the seminal books on scrum, however this is getting dated. Quite a bit of the advice in the book does not match contemporary leading practices or definitions of Scrum.
There are no discussion topics on this book yet.
Be the first to start one »
