- Taschenbuch: 280 Seiten
- Verlag: The Pragmatic Programmers; Auflage: 1 (5. Oktober 2010)
- Sprache: Englisch
- ISBN-10: 1934356581
- ISBN-13: 978-1934356586
- Größe und/oder Gewicht: 19 x 2,2 x 23,5 cm
- Durchschnittliche Kundenbewertung: 3 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 58.042 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
The Agile Samurai: How Agile Masters Deliver Great Software (Pragmatic Programmers) (Englisch) Taschenbuch – 5. Oktober 2010
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
""This book is very well written. Rasmusson uses an entertaining writing style that makes it pleasant to read from beginning to end. What I like the most is the author experience. The way he presents the topics dealing with role assignation (chapter 2) and reality in agile planning (chapter 8) is simply remarkable.""--Computing Reviews
""The Agile Samurai is the book I wish I'd read before I started my last agile project. The chapters on agile project inception alone are worth the price of admission."" --Joshua Kerievsky, Founder and CEO, Industrial Logic, Inc.
""The Agile Samurai is exactly the book you and your team need to understand and deliver using the agile method. It makes the concepts tactile for everyone from the highest level of leadership to the people pushing forward on the front lines.""""
--Jessica Watson, Business Analyst, Shaw Communications
Über den Autor und weitere Mitwirkende
As an experienced entrepreneur and former agile coach for ThoughtWorks, Jonathan Rasmusson has consulted internationally, helping others find better ways to work and play together. When not coaching his sons' hockey teams or cycling to work in the throes of a Canadian winter, Jonathan can be found sharing his experiences with agile delivery methods at his blog, http: //agilewarrior.wordpress.com.
My favorit agile book!
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
"Agile is a way of developing software that reminds us that although computers run the code, it's people who create and maintain it."
Jonathan Rasmussen, the Other JR, has written a great, short, to-the-point book about how to move a project to agile. From the beginning "Deliver something of value every week" to the Agile Principles sprinkled throughout the book, such as "The best architectures, requirements, and designs emerge from self-organizing teams" to the conversations between the student and the Sensei, you can learn how to move your project from where it is to agile.
Some pieces I particularly like are:
1. All of Chapter 4, Seeing the Big Picture, where Jonathan suggests we need an elevator pitch for our project. I'm stealing this idea right away.
2. Chapter 8: Agile Planning, Dealing with Reality. After a humorous side trip with Murphy and his Law, Jonathan introduces us to burndown, burnup, and team velocity charts.
3. Chapter 15: Continuous Integration: Making it Production-Ready. What if you only had one hour to deploy your product. Could you? Jonathan walks you through what you need to do to make the code production ready.
Jonathan has great advice about how to know how agile you are:
"And don't forget. It's not about "being" agile. It's about building great products and delivering world class service to your customers."
This is a great book. If you are thinking of starting an agile journey, do yourself a favor and get this book. You will not be sorry.
The writing style is very informal; the author uses a conversational tone throughout the book. Almost every page contains illustrations, which makes it an easy and quick read. The style of the book is comparable to the Head First books. It left me with the the impression that I sat in an all-day meeting where someone said a lot of intelligent things to which everyone else agreed. Unfortunately, not many of these things seemed radically new or thought-provoking, so I fear I won't remember many of them next month. Of course, this may be entirely my own fault. I prefer a more formal, concise, old-school language. I also prefer dense and meaty text books with lots of diagrams, numbers and formulas. In return, I can dispense with stick figures, pictograms, and even with Master Sensei (a guru character used in the book). I feel that a lot of the deeper and more complex issues of agile project management have simply been left out.
To be fair, it must be mentioned that I probably do not fall into the target group for which this book was written. It is more appropriate as an introductory text for people who are new to agile project management, or even new to the entire business of project management. Think "trial lesson" and "starter course".
What this book is: a great and valuable source of reality connected simple facts that would allow you to re-evaluate how you build your software. Inception Deck is a great tool to kick off a project. Project planning and execution from agile point of view and with developers in mind are chapters that logically explain how to address everyday issues on traditional projects. This book is about achieving targets by going with simplicity.
The bookshelf now has claim to another great book that is written by someone that I once had the honour of working with. The Agile Samurai is a great book that comes straight from the trenches of working, refinining, and applying agile practices. Jonathan Rasmusson ("JR"), is a master programmer, iteration manager, and general jack of all software trades. I would be able to recommend the book alone just based on the content that is within the pages, but I can recommend it even stronger knowing that JR has condensed into its pages the dissemination of practices, war wounds, and nuggets that could only have been gleaned by someone who has proven each of the techniques on projects of all sizes.
I gave the following recommendation in the opening sections of the book:
This book was written with the insight and clarity that can only come from a person who has proved these techniques in the trenches. I have read many books on agile software development; this is by far the most engaging, easy to read, and just plain fun of them all. Get ready to sharpen that sword!
For fun, you may also want to check out the awesome Bruce Lee promotional video, that JR put together for the book (it is hilarious).
Enjoy sharpening the sword!!
Develop With Passion®
Several good concepts are discussed in this book and if you don't have experience in software development then they are very important to realize:
* Customer involvement is very important
* Change will happen so forget spending months planning
* Deliver working functionality quickly and regularly
* Put effort into creating and maintaining quality software and your efforts will be repaid as time goes on.
One oversight which concerns me is that the book gives a very negative view of documentation. I think what he means is excessive effort spent writing requirements documents. Well documented code and good explanatory documentation are still of paramount importance and shouldn't be skimped on by a frantic, fast paced agile approach.
The author repeatedly hammers the point that the only item you can be flexible on is scope. Budgets and time frames usually don't have much flexibility. Quality is always important. So the only thing left is scope. If the project goes well you can add scope, if problems are encountered then you have to cut out scope and drop some desired features.