The Agile Samurai

Book Notes - The Agile Samurai

Started Apr 10, 2022

Quotes

Deliver something of value every week
Look to the master, follow the master, walk with the master, see through the master, become the master.
Agile Principle - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Sure, you need documentation. Sure, you need plans. But they are in support of only one thing—working software.
The engine for getting stuff done on an agile project is the iteration—a one- to two-week period where you take your customers’ most important stories and transform them into running, tested software.
when reality disagrees with your plan, you’ll change your plan. Adaptive planning is a cornerstone of agile delivery.
If it cannot be potentially shipped, it is not done
Agile principle - Working software is the primary measure of success
Three simple truths
- It is impossible to gather all the requirements at the beginning of the project
- Whatever requirements you gather are guaranteed to change
- There will always be more to do than time and and money will allow.
For one, roles really blur on agile projects. When it’s done right, joining an agile team is a lot like working in a mini-startup. People pitch in and do whatever it takes to make the project successful—regardless of title or role.
Agile Principles: The best architectures, requirements, and designs emerge from self-organizing teams.

Notes

Thoughts

References

Resources

Agile Masters

Reviewers

Noel Rappin, Alan Francis, Kevin Gisi, Jessica Watson, Tomas Gendron, Dave Klein, Michael Sikorsky, Dan North, Janet Gregory, Sanjay Manchiganti, Wendy Lindemann, James Avery, Robin Dymond, Tom Poppendieck, Alice Toth, Ian Dees, Meghan Armstrong, Ram Swaminathan, Heather Karp, Chad Fournier, Matt Hughes, Michael Menard, Tony Semana, Kim Shrier, and Ryheul Kristof