Book õ The Agile Samurai How Agile Masters Deliver Great Software Ê 267 pages

Ebook The Agile Samurai How Agile Masters Deliver Great Software

Book õ The Agile Samurai How Agile Masters Deliver Great Software Ê 267 pages ¿ Faced with a software project of epic proportions? Tired of over committing and under delivering? Enter the dojo of the agile samurai where agile expert Jonathan Rasmusson shows you how to kick start execute and dVery week and make rolling software into production a non event You’ll see how agile software delivery really works and how to help your team get agile fast while having fun along the way With Agile methodology there's basically a template of ideas rather than a set process that has to be followed I do find Agile books are often a boring read or have deviated from the subject and I have to say this is the best one so far The content is good and it is presented in a fun easy to read style; I found myself whizzing through it I also found it refreshing that some of the examples were situations that didn't go well for the author rather than boasting about his achievements like authors often do I've never heard of an “Inception Deck” but I think there is great value in this techniue

Jonathan Rasmusson  The Agile Samurai How Agile Masters Deliver Great Software Mobi

Kick start execute and deliver your agile projects Combining tools core principles and plenty of humor The Agile Samurai gives you the tools and the attitude to deliver something of value e I uite enjoyed this It gave me some background to Agile processes that I haven't had beforeThe master student thing was really cheesy but I managed to look past that

Pdf ç The Agile Samurai How Agile Masters Deliver Great Software  Jonathan Rasmusson

The Agile Samurai How Agile Masters Deliver Great SoftwareFaced with a software project of epic proportions? Tired of over committing and under delivering? Enter the dojo of the agile samurai where agile expert Jonathan Rasmusson shows you how to For some context I'm writing this in 2017 This book was written at the height of the 'Agile' fad in 2010 Naturally a lot has changed since then and somewhat unsurprisingly this book hasn't aged that well Most people have either moved on or improved upon many of the practices described in this book If you've never worked in an 'Agile' environment before which is highly unlikely by now but still possible this book is uite a good resource for seeing where many of the modern practices evolved from and how the old folk used to work That's not to say that there aren't any problems in the way software development is handled that this book actually addresses Some issues like an overreliance on specification documents and treating estimates as anything other than a rough guess are still common frustrations that come up often than they should Even the way it suggests starting a new project with the use of an inception deck has some good ideas that I'm surprised aren't used often even if a lot of the steps themselves are unnecessary The book does mention that every team is different and should take and adjust the practices and ideas as they need to which is another thing I find managers tend to forget thinking implementing certain practices will result in overnight improvementsThe main issue I have with 'Agile' and even modern approaches to software development is that it treats it like menial labour which can be reasonably accurately estimated and has almost no mental fatigue cost So tools like velocity and burn down charts are a nice visual representation of how work has been progressing but using them to extrapolate future progress is naive and overly optimistic in most cases and is why I almost never hear of anyone using them any The one major thing that this book did remind me of is that 'Agile' is actually a project management tool and not techniues to make actual software development easier efficient or productive There are some practices that try to improve on software uality but they're either overly optimistic about their benefits like TDD was or get uickly sacrificed in favour of faster turnaround time like refactoring and to some extent unit testing Some other issues I had with the book were things like the amount of unnecessary admin it advocates for the lack of emphasis on team dynamics implying that these practices in themselves are enough to deliver good software and calling certain statements 'truths' when they're far from that This isn't a bad book by any means it's just outdated and maybe a tad too optimistic There's still a few things that one can gain from it but I suspect there are newer books out there that are a lot beneficial in getting the most out of delivering great software