Rating:
Author: James Shore
ISBN : B00F8QCK0E
New from $17.99
Format: PDF
Download file now Free The Art of Agile Development from 4shared, mediafire, hotfile, and mirror link
The Art of Agile Development contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.
This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers.
The Art of Agile Development gives you clear answers to questions such as:
- How can we adopt agile development?
- Do we really need to pair program?
- What metrics should we report?
- What if I can't get my customer to participate?
- How much documentation should we write?
- When do we design and architect?
- As a non-developer, how should I work with my agile team?
- Where is my product roadmap?
- How does QA fit in?
The book teaches you how to adopt XP practices, describes each practice in detail, then discusses principles that will allow you to modify XP and create your own agile method. In particular, this book tackles the difficult aspects of agile development: the need for cooperation and trust among team members.
Whether you're currently part of an agile team, working with an agile team, or interested in agile development, this book provides the practical tips you need to start practicing agile development. As your experience grows, the book will grow with you, providing exercises and information that will teach you first to understand the rules of agile development, break them, and ultimately abandon rules altogether as you master the art of agile development.
"Jim Shore and Shane Warden expertly explain the practices and benefits of Extreme Programming. They offer advice from their real-world experiences in leading teams. They answer questions about the practices and show contraindications - ways that a practice may be mis-applied. They offer alternatives you can try if there are impediments to applying a practice, such as the lack of an on-site customer.
--Ken Pugh, Author of Jolt Award Winner, Prefactoring
"I will leave a copy of this book with every team I visit."
--Brian Marick, Exampler Consulting
Download latest books on mediafire and other links compilation Free The Art of Agile Development
- File Size: 1667 KB
- Print Length: 440 pages
- Simultaneous Device Usage: Unlimited
- Publisher: O'Reilly Media; 1 edition (July 14, 2008)
- Sold by: Amazon Digital Services, Inc.
- Language: English
- ASIN: B00F8QCK0E
- Text-to-Speech: Enabled
X-Ray:
- Lending: Not Enabled
- Amazon Best Sellers Rank: #204,360 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #37
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Project Management
- #37
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Project Management
Free The Art of Agile Development
This book is very well-timed. Now that agile development practices are "crossing the chasm" towards professionally accepted standards, this book reminds us that "agile" is neither a narrow, prescriptive set of standardized practices, nor a free-for-all smorgasbord of every possible practice.
This book will give teams and their management the information necessary to make informed decisions about the make-up of a software product team, and how it operates. The Art of Agile Development is intelligent, thoughtful, professional, and realistic. It is based on years of varied experiences, and it reveals a well-tested set of recommendations.
Part I
The book starts out with high-altitude answers to "Why?" and "How?" and a satisfying definition of "success." This is followed by a story of a hypothetical XP team. The story is full of dialog revealing the day-to-day functioning of a well-running team as a new hire joins the team. That dialog may seem contrived, but it's likely more of a composite of things heard on various teams. Yes, agile teams do enjoy their work, and people who enjoy their work talk about it as portrayed. I think this portrayal brings forth an important decision for the reader: Do you suspect that your development teams could truly run more smoothly, or are you merely looking for a way to dismiss this weird new "agile movement" and get on with your agonizing career? (Either way, keep reading!)
Part II
The second section of the book is a detailed exploration of the development practices recommended by the authors. There are a number of practices recognizable from XP, with some additional thoughtful practices, some realistic alterations, and some notable replacements.
I just can't stand reading this book. Being an SCM manager I am familiar with the good ideas and the problems of agile development. I am also familiar with the managers who like to use catch phrases to motivate and fix every issue with development.
This book is great training if you want to just spit out a bunch of buzzwords in agile programming but not really understand them. The first 200 pages of the book are literally a maelstrom of agile "buzzwords" broken up into recommendations of XP (extreme programming).
One thing that is repeated for every single XP practice is the following "THIS_PRACTICE is a prerequisite for agile (or XP) but if you can not THIS_PRACTICE you can still be effective... and here are alternatives... contraindications.." Ok, first off, if you have an idea or set of practices to improve programming, stick to you guns. With all the alternatives and wishy washy commitment in the writing of this book, I would conclude that the idea of XP is not that good in the first place.
The structure of the book is painfully chopped up into small pieces and the exact same concepts, practices and advice are repeated over, and over, and over!!!! Its maddening. Each chapter is also padded with all of the "if you can't do this..." sub-chapters which like most of the book just repeats the same conceits. There are many good points in the book but its simply not interesting to read. It reads more like a huge power point presentation. Touching on hundreds of ideas and highlighting them. The treatement of each individual practice is simply too shallow to be thought provoking or entertaining in any way. I know programming practice is not sexy but it can certainly be engaging.