[[ READ E-PUB ]] ⇲ The Agile Samurai: How Agile Masters Deliver Great Software ↞ PDF eBook or Kindle ePUB free

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 quite a good resource for seeing where many of themodern practic 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 quite a good resource for seeing where many of themodern practices evolved from and how the old folk used to work That s not to say that there aren t anyproblems 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 upoften 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 usedoften, 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 improvements.The main issue I have with Agile and evenmodern 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 techniques to make actual software development easier, efficient orproductive There are some practices that try to improve on software quality, but they re either overly optimistic about their benefits, like TDD was, or get quickly 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 lotbeneficial in getting the most out of delivering great software [[ READ E-PUB ]] ↶ The Agile Samurai: How Agile Masters Deliver Great Software ↡ 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 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 every 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 Really enjoyed the simplicity of the explanations of what needs to be done to be agile, and why.One mostly knows these things, but there are key points that was spot on.Things like When you say work is done, it is done Tested Ready for production You take ownership of your own work Writing tests to avoid things breaking, and to know that your change isn t breaking anything else Continuous integration Deployment Work must be Production ready at any point in time Engage Communicate w Really enjoyed the simplicity of the explanations of what needs to be done to be agile, and why.One mostly knows these things, but there are key points that was spot on.Things like When you say work is done, it is done Tested Ready for production You take ownership of your own work Writing tests to avoid things breaking, and to know that your change isn t breaking anything else Continuous integration Deployment Work must be Production ready at any point in time Engage Communicate with Customer Engage with peers Work with your neighbours in your neighbourhood If something cannot be delivered in a week, then it is not scoped small enoughDon t do things because of the methodology, do things because they add value.This book is a recommended read for everyone in the development pipeline Developer, Tester, BA, Manager, Ops, IT I went through this book as a professional development effort to obtain a greater understanding of Agile I myself am not in an Agile environment thankfully , but I do have counterparts that I work with who are As such, I wanted to give this a go to learnabout it I really have mixed feelings about the Agile development process One thing this book does is absolutely highlight the fact that Agile was created for software development Which perplexes me as to why so many organizations tha I went through this book as a professional development effort to obtain a greater understanding of Agile I myself am not in an Agile environment thankfully , but I do have counterparts that I work with who are As such, I wanted to give this a go to learnabout it I really have mixed feelings about the Agile development process One thing this book does is absolutely highlight the fact that Agile was created for software development Which perplexes me as to why so many organizations that do not develop software, have adopted this as the one size fits all methodology for best business practices I feel like Agile is kind of like a 2nd Lieutenant LT O 1 in the Army fresh out of ROTC OCS The LT has been through training, has read through numerous field manuals FMs and can tell you all about how through his experience things should be done but when it comes down to it, he lacks the irreplaceable in person experience of actual combat Then, when his soldier s try to push back and say, No Sir, that is not going to work The LT is absolutely confused because he read it in a manual, or was trained that way at West Point, or it looks so perfect on paper how could it not be nothing but absolute truth Aside from that personal opinion and analogy above about what I think of Agile, I have heard numerous feedback comments from individuals who live Agile every day and it s not pretty Things like We were actuallyefficient using Waterfall The point system is broken, it breeds laziness, as you can just accept not meeting deadlines and it is okay to just push things off to the next iteration thus, things just keep getting thrown over the fence over and over again Too many meetings Agile was designed for software development why are we using it for our mission which has absolutely nothing to do with software dev So on and so forth I don t understand the appeal of a string of buzzwords and constant short daily meetings throughout the day that interrupt workflow A point system that is easily broken by pop ups And why so many organizations are trying to make a software development methodology be a one size fits all solution for everything I will try my best to be open minded, and if I am ever directly part of an Agile working environment, to not come in with a sour attitude I quite enjoyed this It gave me some background to Agile processes that I haven t had before.The master student thing was really cheesy, but I managed to look past that. One of the best books on Agile software development that I have read Its beauty lies in its simplicity clear, down to earth guide through the Agile principles, planning, estimating, analysis, development, communication with clients, and testing Some overall principles like honest communication with clients as early as possible, just in time and just enough analysis, visualising your project and your pace of development are covered well throughout the book.The book is also well illustrated gr One of the best books on Agile software development that I have read Its beauty lies in its simplicity clear, down to earth guide through the Agile principles, planning, estimating, analysis, development, communication with clients, and testing Some overall principles like honest communication with clients as early as possible, just in time and just enough analysis, visualising your project and your pace of development are covered well throughout the book.The book is also well illustrated graphs and cartoons are helpful and make the point of the author even clearer.The general story wrapper of the book that a novice student is learning the Agile principles from a Samurai was not very insightful, yet not disturbing It could by and large just be ignored 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 l 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 technique I can see the value from some of the agile methodologies The continual focus on the customer is a necessary component of any product development and is vital to ensuring you don t get stuck in solving irrelevant problems land unit tests are great and save a lot of time preventing problems and with identification when things go wrong A couple of the things I m not so sure about Fluidity of roles It seems to leave a lot up in the air, if everyone on the project is an expert in their field, I can see the value from some of the agile methodologies The continual focus on the customer is a necessary component of any product development and is vital to ensuring you don t get stuck in solving irrelevant problems land unit tests are great and save a lot of time preventing problems and with identification when things go wrong A couple of the things I m not so sure about Fluidity of roles It seems to leave a lot up in the air, if everyone on the project is an expert in their field, leaving the final decisions of testing and whatnot up to whoever seems nice Having worked on a variety of projects with a wide variety of teams, I know it to be a lot messier than that A lot comes down to feelings and vague motivations I m still skeptical of the effectiveness of this Also, there seems to be quite a bit of Jedi hand waving for problem solving in Agile Maybe it s specific to this book I m just exploring this concept But Go solve whatever needs to be solved works well until it doesn t lots of interesting tidbits as somebody using agile it was interesting to see how it should be implemented and which things aren t really part of it but my teams may have made up It seemed mainly geared towards though who go through shorter project lifecycles How to apply agile to consulting. Super Valuable Fun With Agile Samurai you can have a really fun precious introduction on Agile and also, really nice resources to exploreWhat I really enjoyed was the cool writing, technical books don t need to be boring serious to be valuable, and the super useful tips.Thanks Jonathan, for the tips and all the dialogues between Master and Student Super Valuable Fun With Agile Samurai you can have a really fun precious introduction on Agile and also, really nice resources to exploreWhat I really enjoyed was the cool writing, technical books don t need to be boring serious to be valuable, and the super useful tips.Thanks Jonathan, for the tips and all the dialogues between Master and Student