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âŚ
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.
While this book was still in the writing, Crispin and Gregory published draft chapters on the internet.
At the time, I read them, and managed to introduce many of the great insights into my own work. Even though I was working in a more traditional environment, the ideas from the two ladies inspired me on my journey to the agile methodologies.
I even managed to contribute some of my own real-world examples from my own experiences to their writings â and they decided to include some of them.
Te>Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.âŚ
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.
âGood agile testing is good context-driven testing applied in an agile context.â
I recall reading through the authorsâ lessons on software testing at about the same time I dived into more agile topics. Lessons Learned in Software Testing helped me keep the connection towards more traditional contexts â more so since I was still working in a more traditional context.
With their more than 100 lessons some of them applied to me, others did not. I am sure, other readers will find the same in their context.
Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.
In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. LearnâŚ
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.
Gerald M. â Jerry â Weinberg is my most-often quoted author.
Having spent more than 50 years in the software world, Jerry was able to write in a timeless manner about the lessons he learned. Over the years, he collected more and more stories he survived from, including all aspects that brings software from an idea to a product that everyone can use.
In this first volume in his Quality Software Management series, he will extend your perspective with Causal-Loop Diagrams and thereby introduce you to the world of Thinking in Systems.
The takeaways from his stories are fostered in easy-to-remember laws and principles that he gives you as a free takeaway summary in the end as well. Extend your perspective on managing for quality rather than staying oblivious.
In this first volume of the Quality Software Management series, Gerald M. Weinberg tackles the first requirement for developing quality software: learning to think correctly -- about problems, solutions, and quality itself.
Guidelines on management are introduced to stimulate the kind of thinking needed.
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âŚ
Defining and managing the requirements for a software system is hard! Iâve been interested in improving how projects handle their requirements for more than 35 years. I realized how important this was when I saw how many projectsâincluding my ownâstruggled and failed when they neglected to build a solid foundation of well-understood and clearly communicated requirements. Iâve personally used nearly all of the techniques described in my book Software Requirements, and I got always better results when I applied those techniques. My books, articles, training courses, presentations, and videos on requirements have been helpful to thousands of business analysts worldwide for many years.
Suzanne and James Robertson have been writing insightful books on software requirements for many years. This book covers all the important topics, including understanding the real problem, different techniques for exploring solutions, and numerous ways to communicate requirements effectively. I especially like their treatment of quality attribute requirements and defining âfit criteriaâ to judge whether a solution adequately addresses them.
The book includes a comprehensive requirements specification template to guide writing a rigorous and complete specification on projects for which that is valuable. I also appreciate their use of visual models both to communicate with the reader and to guide the reader in communicating requirements to project stakeholders. I do prefer my book Software Requirements, but this is an excellent choice as well by two authorities in the field.
"If the purpose is to create one of the best books on requirements yet written, the authors have succeeded."
-Capers Jones
Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed.
Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and thatâŚ
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âŚ
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âŚ
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,âŚ
