For over a decade I helped people develop their skills and expand their leaderful-ness in Agile Coaching and I kept hearing the same blocker: “This is great and all, but my leaders don’t get it. They are the impediment.” After working with many thousands of Agilists I decided to go into the “belly of the beast” and personally coach leadership teams. What I found were not beasts or even garden variety egomaniacs. Instead, I found well-meaning people who are genuinely confounded by the complexity of today’s business landscape and who struggle with performance-killing team dynamics. Good news: the human technology to “solve” these issues is widely available. We know how.
This book gives the philosophical underpinning for why creating a leadership development culture in all parts of your organization is essential for working in our VUCA (volatile, uncertain, complex, ambiguous) business landscape. And, it shows you how to do it with specific practices and new-mindset concepts. It is geared toward organizations with Agile ways of working in the environment, but is also useful if Agile is not present. I especially enjoy the way several theories of adult development are interwoven in this book which makes using them to guide leadership development strategies (your own and others) simpler and more immediately applicable.
Organizations around the globe are struggling to adapt to an increasingly complex and turbulent social, economic, technological, and business environment—whether they be banks, product development companies, or city councils. Many are responding by embracing agility as a way of working—some with a primary orientation around operational agility (Agile software development methods such as Scrum and SAFe), others focusing on customer development agility (e.g., Lean Startup), while others are embracing a broader business agility. In almost all of these cases, the prevailing notion of agility is concerned primarily with processes and practices, with systems and structures—a form of outer agility. But,…
I’ve managed projects and programs for over forty years. I’ve seen the effects of both good and bad systems on the people who try to do their best work. These books help managers and teams see their systems. How long does a team need to deliver work that fulfills a good objective? Are there systemic blockages that prevent people from doing a good job? These books represent my philosophy: People want to do a good job. When they have clear objectives and know the principles of flow, they can succeed. That’s how I’ve succeeded in my career. You can, too.
When I read the very first page, I had an “aha!” moment. Singh explains that scaling flow, the flow of work through the teams, is the single most important idea in “scaling” agility. That means each team optimizes for their challenges, not a specific process.
I loved this book because Singh makes the principles of flow easy to understand and apply. That’s the “secret” to scaling agility.
If you are a large organization that has seen the benefits of Agile approaches on teams, you have either attempted to or talked about scaling Agile. Scaling has become synonymous with overburdened and cumbersome frameworks that create more problems than they solve. We need a simpler solution to the problem of scaling Agile. We need to break this problem down to its basic tenet - Optimizing the flow of value to customers. The strategy of Kanban can be applied to do exactly that. In doing so, we can discard the practices proposed by common Agile scaling frameworks and go to…
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
The second book from Gregory and Crispin brought me up-to-date on the different trends in the Agile world, ten years after having delved into their first book.
How do you share the quality mindset in a DevOps culture? What about Design Thinking? With many more examples from the industry, the two authors made me curious about some of the things that I had ignored until I read their book.
Janet Gregory and Lisa Crispin pioneered the agile testing discipline with their previous work, Agile Testing. Now, in More Agile Testing, they reflect on all they've learned since. They address crucial emerging issues, share evolved agile practices, and cover key issues agile testers have asked to learn more about.
Packed with new examples from real teams, this insightful guide offers detailed information about adapting agile testing for your environment; learning from experience and continually improving your test processes; scaling agile testing across teams; and overcoming the pitfalls of automated testing. You'll find brand-new coverage of agile testing for the enterprise,…
On Jan 30, 2013, I was sacked for "insubordination." No notice, no severance. My bosses threatened the other employees with dismissal if they talked to me. I'd been at the company for decades, rising from entry level to the executive team; after years of striving, it was a devastating blow. Once I picked myself up, I realized I’d leaned in so far, I’d toppled over. So I set off on a new path. Today, I have a master’s degree in Eastern classics, four leadership books, and one historical novel, and I’m committed to helping high achievers—women, especially—find their own paths to happy success: paths beyond “lean in.”
It may seem strange to include a jobseeker’s guide in a list of leadership books, but Agile Unemployment is the resource for anyone faced with the hardest leadership task of all: leading yourself through a time of trial.
Sabina Sulat has been there—on both sides of the HR desk for “that conversation”—and she offers her well-earned wisdom with deep candor, much-needed encouragement, and straight-shooting practicality. In my early career days, I always found the “What color is your parachute” genre pretty useless, not to mention incredibly depressing. I wish I’d had Sulat’s sound guidance back then; it would have helped me lean in, out, up, down, and sideways with far more grace and optimism.
Lost your job? Struggling to figure the future out?
Agile Unemployment is the book for you. Losing your job can be harrowing, but it is a temporary state and does not define you. Cast aside your doubts and develop a new mindset to carry you through those down moments and rebuild your life how YOU see fit. Agile Unemployment is your guide to working through the job searching process and learning how to pivot your mindset to build resilience as you develop confidence and find the job of your dreams.
Turn losing your job into a moment of opportunity. Agile…
There are many creative professions where the performers practice their skills more often compared to the actual time they do the actual work.
Software development is widely considered as a creative profession. Unfortunately, it doesn’t fall into the category of professions where its practitioners hone their skills. This book discusses a coaching strategy where software teams can periodically practice and improve their technical practices.
“Samman” is the Swedish word for “together”. Organisations that invest in technical coaching increase their business success. This book is a real eye-opener for anyone who likes to improve their approach to team coaching. It lays out the groundwork for improving the technical practices of software teams.
Samman Technical Coaching is an approach to Agile training that focuses on technical questions concerning how code is written. It is a highly effective way of increasing agility in your software development organization. The first part of the Samman method involves the coach working in an ensemble with development teams, programming in their production codebase. This hands-on mentoring is accompanied by daily “learning hour” sessions for mastering particular techniques. In this book you will discover how to put Samman into practice, improve your coding procedures and how you collaborate. It is a practical guide for aspiring and experienced coaches looking…
I keep coming back to this book for the past 20 years now. The first and second edition are two completely different books.
By reading them both, you as the reader can get a good feel about the origins and evolution of Extreme Programming during those early years. For me, both books provide the much needed foundation for a human approach towards software development.
The ideas in this book advocate for social change, while breaking with the habits of the prevalent Waterfall approach, which unfortunately is still very much alive and kicking. This book, both the first and the second edition, are very important reads.
"In this second edition of Extreme Programming Explained, Kent Beck organizes and presents five years' worth of experiences, growth, and change revolving around XP. If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book."
- Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L. "The first edition of this book told us what XP was-it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the 'why' of XP, the motivations and the…
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
“Good agile testing is good context-driven testing applied in an agile context.”
The authors of this book summarize their decades of experience in software testing in over 100 lessons they learned. Follow them along different aspects of the tester’s job, as they re-tell various stories collected over the years with some clear guidance to surviving and testing project.
These software testing industry leaders have some timely contextual advice in here – whether you work as a tester on an agile team or in a more traditional fashion.
Decades of software testing experience condensed into the most important lessons learned.
The world's leading software testing experts lend you their wisdom and years of experience to help you avoid the most common mistakes in testing software. Each lesson is an assertion related to software testing, followed by an explanation or example that shows you the how, when, and why of the testing lesson. More than just tips, tricks, and pitfalls to avoid, Lessons Learned in Software Testing speeds you through the critical testing phase of the software development project without the extensive trial and error it normally takes to…
Being able to understand and change reality through our knowledge and skill is literal magic. We’re building systems with so many exciting and unexpected properties that can be exploited and repurposed for both good and evil. I want to keep some of that magic and help people engineer – build great systems that make people’s lives better. I’ve been securing (and breaking) systems, from operating rooms to spaceships, from banks to self-driving cars for over 25 years. The biggest lesson I’ve learned is that if security is not infused from the start, we’re forced to rely on what ought to be our last lines of defense. This list helps you infuse security into your systems.
When I worked in application security at Microsoft, we still had products that shipped every few years. I learned to scale application security in that world, but many people live in a different world now. AAS helped me understand which of our approaches translated well, which had to be transformed, and which needed to be discarded or replaced. I regularly refer back to it, even a few years later.
Agile continues to be the most adopted software development methodology among organizations worldwide, but it generally hasn't integrated well with traditional security management techniques. And most security professionals aren't up to speed in their understanding and experience of agile development. To help bridge the divide between these two worlds, this practical guide introduces several security tools and techniques adapted specifically to integrate with agile development.
Written by security experts and agile veterans, this book begins by introducing security principles to agile practitioners, and agile principles to security practitioners. The authors also reveal problems they encountered in their own experiences with…
I have been designing user interfaces since graduate school at Stanford, where I studied psychology and computer science. Over the five decades since then, I have designed many digital products and services, learning a lot about how to make them usable and useful. Two decades ago, I turned more towards sharing my knowledge and experience through writing (articles and books) and teaching (professionals and students). I’ve taught at Stanford University, Mills College, the University of Canterbury (New Zealand), the University of San Francisco, and at professional conferences and companies. Google invited me twice to speak in their Authors @ Google series, and ACM and SIGCHI have given me several awards.
This book is the software industry’s “bible” on how to start software development projects.
It explains how to conduct up-front user research, before design, prototyping, and coding start. User research, followed by analysis of your findings, is how you determine requirements and figure out what features or improvements are needed and which are most important.
This book presents a collection of methods for doing that. You probably won’t need every method described this book on every project, but having Holtzblatt and Beyer’s toolkit of user-research and analysis methods available when needed is valuable.
I read it several times, and now several of its methods are baked into my normal design process.
Contextual Design: Design for Life, Second Edition, describes the core techniques needed to deliberately produce a compelling user experience. Contextual design was first invented in 1988 to drive a deep understanding of the user into the design process. It has been used in a wide variety of industries and taught in universities all over the world. Until now, the basic CD approach has needed little revision, but with the wide adoption of handheld devices, especially smartphones, the way technology is integrated into people's lives has fundamentally changed. Contextual Design V2.0 introduces both the classic CD techniques and the new techniques…
I love to expand my knowledge and learn not just about new technologies, but how things work. I find it fascinating to dig deep into computer programming, technology concepts, and really geek out on things. That’s why I love software development or programming books that aren’t just about some technology and how to do something, but rather books that really make you think and teach you not just programming skills but critical thinking about problem-solving skills. As a software developer for over 15 years and a person who teaches software developers, I have learned that if someone isn’t entertained, they aren’t learning. That’s why I put together a list of fun, entertaining and useful books.
I love writing good clean code. There is something refreshing about writing or reading code that reads more like a book than some obscure instructions to a machine. This book goes into the details of how to write “clean code” and what makes it clean.
I felt like I learned so much about writing good code from reading this book about things that you are never really taught in school or on the job as a software developer.
I found so much of the book so interesting because I could use what I was learning right away to become a better programmer.
If you want to become a better programmer and are looking for a book that will entertain you and be fun along the way, I highly recommend Clean Code.
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way.
Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a…
