Agile is becoming a dirty word because of the way it is being marketed, implemented, over-simplified and misrepresented. Step by step guides and quick fix recipes are of limited use. It is better to free yourself and your projects by learning how to connect the underlying principles to what you want to achieve. Knowing what projects need and why Agile works will help you understand where and how to apply these principles and what to expect. This book explains why Agile was introduced and how the underlying principles and ideas are still relevant. It reviews Agile methods and advises how to take a pragmatic approach to them as a programmer, a project manager and a business stakeholder. If you want to know what Agile really is and how to understand its capabilities - from someone who has implemented and used Agile successfully as a programmer, manager and coach in both small and very large companies - then read this book.
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Books Trade-In Store for more details. Learn more. |
Book Description
Frequently Bought Together
Product details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, and more.
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
2 of 2 people found the following review helpful
5.0 out of 5 stars
Excellent overview of Agile in software development, and the different methods
3 Feb 2012
By N. WISE
Format:Paperback|Amazon Verified Purchase
Barry's extensive experience and knowledge of the Agile software development process really shows in this book. He covers off the reasons why Agile (XP) was created in the first place, why it should be used, and most importantly, how it's been derailed and bastardized by all the agile hangers-on.
The book covers a lot of the history if agile, mostly focusing on eXtreme Programming, being that's where it all started, and to a lesser extent, why things like Pair Programming, Test First Development (and Test Driven - not the same), Continuous Integration and Customer Collaboration are not just desirable things in software, but a requirement if you are "doing agile".
Later in the book, he looks at a lot of different "styles" and rates them with out useful, or not, they are. Included in this (in my experience, correct) critique are User Stores, Lean, Scrim, XP, PRINCE2, DSDM and Kanban.
I think he's correct on all of them, and he's not at all pulling punches. Possibly, the "review" of XP is a little flourishing, but it is still honest - it just shows his knowledge and passion on the topic.
The book rounds out with observations on the whole software development practice, from an agile perspective.
All up, I enjoyed this book. It was a fairly easy read, tho a little slow to get started (esp the first chapter). But once into it, it's excellent advice for anyone running or participating in an Agile team, or anyone thinking about "doing agile" and wondering what it is, and more importantly, what Agile is NOT.
(side note: I think most people will find what they are doing is NOT agile, and not even "Agile". It's just "random". Possibly still better than waterfall, tho!)
The book covers a lot of the history if agile, mostly focusing on eXtreme Programming, being that's where it all started, and to a lesser extent, why things like Pair Programming, Test First Development (and Test Driven - not the same), Continuous Integration and Customer Collaboration are not just desirable things in software, but a requirement if you are "doing agile".
Later in the book, he looks at a lot of different "styles" and rates them with out useful, or not, they are. Included in this (in my experience, correct) critique are User Stores, Lean, Scrim, XP, PRINCE2, DSDM and Kanban.
I think he's correct on all of them, and he's not at all pulling punches. Possibly, the "review" of XP is a little flourishing, but it is still honest - it just shows his knowledge and passion on the topic.
The book rounds out with observations on the whole software development practice, from an agile perspective.
All up, I enjoyed this book. It was a fairly easy read, tho a little slow to get started (esp the first chapter). But once into it, it's excellent advice for anyone running or participating in an Agile team, or anyone thinking about "doing agile" and wondering what it is, and more importantly, what Agile is NOT.
(side note: I think most people will find what they are doing is NOT agile, and not even "Agile". It's just "random". Possibly still better than waterfall, tho!)
Format:Paperback|Amazon Verified Purchase
If your team uses a methodology like scrum or lean, or if you're considering moving to an agile methodology, you should buy this book. If you're feeling generous then buy a copy for every member of your team--the price is low enough to warrant it.
It's an easy read and could be read cover-to-cover in one sitting. As I see it, the author's intention is for you to become "enlightened" with an understanding that being agile is not about management process but about programming practices such as test-first development, pair programming and refactoring.
The book sets out with a history of agile ideas and then picks apart the various facets of those ideas, discussing why each makes sense. For example, the author offers an excellent theory of "scope" and how it is traditionally thought of versus how an agile practitioner might think of it. This advice in particular was an "aha!" moment for me; it succinctly described a team issue I'd previously encountered but could never manage to resolve.
At the end of the book is a dissection of various methodologies and techniques such as user stories, scrum, kanban and XP. The scathing review of scrum will resonate with anyone ever involved on a team that's been "agilized" by a consultant drafted in to improve the team's under-performance. The point is that scrum can be imposed but the team is still left decidedly un-agile.
The author helpfully mentions numerous websites and books that you can explore as you progress on your journey towards enlightenment; that's important because this book tells you the why, but not the how. It won't give you strategies for pair programming, for example. But it will start you in the right direction--or correct your direction if you've started off on the wrong path.
It's an easy read and could be read cover-to-cover in one sitting. As I see it, the author's intention is for you to become "enlightened" with an understanding that being agile is not about management process but about programming practices such as test-first development, pair programming and refactoring.
The book sets out with a history of agile ideas and then picks apart the various facets of those ideas, discussing why each makes sense. For example, the author offers an excellent theory of "scope" and how it is traditionally thought of versus how an agile practitioner might think of it. This advice in particular was an "aha!" moment for me; it succinctly described a team issue I'd previously encountered but could never manage to resolve.
At the end of the book is a dissection of various methodologies and techniques such as user stories, scrum, kanban and XP. The scathing review of scrum will resonate with anyone ever involved on a team that's been "agilized" by a consultant drafted in to improve the team's under-performance. The point is that scrum can be imposed but the team is still left decidedly un-agile.
The author helpfully mentions numerous websites and books that you can explore as you progress on your journey towards enlightenment; that's important because this book tells you the why, but not the how. It won't give you strategies for pair programming, for example. But it will start you in the right direction--or correct your direction if you've started off on the wrong path.
Listmania!
|
|
Look for similar items by category
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.
|
