Holiday Season and travel is giving me an opportunity to catch up with some books I always wanted
to read. As I gear up to lead large scale agile transformation initiative, it is only natural that such books are dominating.
On Writing Well: Re-read. So many authors that I regularly read (continue to) recommend this book, as one of the best in non-fiction writing. It teaches brevity, simplicity and core essentials of writing well - an email, an article, a blog post or even a book.
Clean Architecture: Martin’s (Uncle Bob) Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. This book talks about:
- Learn what software architects need to achieve–and core disciplines and practices for achieving it
- Master essential software design principles for addressing function, component separation, and data management
- See how programming paradigms impose discipline by restricting what developers can do
- Understand what’s critically important and what’s merely a “detail”
- Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications
- Define appropriate boundaries and layers, and organize components and services
- See why designs and architectures go wrong, and how to prevent (or fix) these failures
Toyota Kata gets to the essence of how Toyota manages continuous improvement and human ingenuity, through its improvement kata and coaching kata. Mike Rother explains why typical companies fail to understand the core of lean and make limited progress―and what it takes to make it a real part of your culture.
Lean Enterprise: How High Performance Organizations Innovate at Scale: How well does your organization respond to changing market conditions, customer needsand emerging technologies when building software-based products? This practical guide presents Lean and Agile principles and patterns to help you move fast at scale—and demonstrates why and how to apply these methodologies throughout your organization, rather than with just one department or team.