The Lessons Learned Handbook

The phrase “lessons learned is such a common one, yet people struggle with developing effective lessons learned approaches. The Lessons Learned Handbook is written for the project manager, quality manager or senior manager trying to put in place a system for learning from experience, or looking to improve the system they have. Based on experience of successful and unsuccessful systems, the author recognises the need to convert learning into action. For this to happen, there needs to be a series of key steps, which the book guides the reader through. The book provides practical guidance to learning from experience, illustrated with case histories from the author, and from contributors from industry and the public sector. The book is a practitioner-level guide to the design and the mechanics of lessons learned processes Takes a holistic approach, tracking lessons from identification to reapplication Makes the case for the assignment of actions for learning

Online instruction is rapidly expanding the way administrators and educators think about and plan instruction. In addition, due to a pandemic, online instructional practices and learning in a virtual environment are being implemented with very little training or support. Educators are learning new tools and strategies at a quick pace, and often on their own, even through resistance. It is important to explore lessons learned through the pandemic but also of importance is sharing the virtual classroom options and instruction that align to best practices when transitioning to online instruction. Sharing these will allow educators to understand and learn that virtual instruction can benefit all, even when not used out of need, and can enhance face-to-face courses in many ways. The Handbook of Research on Lessons Learned From Transitioning to Virtual Classrooms During a Pandemic is a critical reference that presents lessons instructors have learned throughout the COVID-19 pandemic including what programs and tools were found to be the most impactful and useful and how to effectively embed virtual teaching into face-to-face teaching. With difficult choices to be made and implemented, this topic and collection of writings demonstrates the learning curve in a state of survival and also lessons and resources learned that will be useful when moving back to face-to-face instruction as a tool to continue to use. Highlighted topics include the frustrations faced during the transition, lessons learned from a variety of viewpoints, resources found and used to support instruction, online learner perspectives and thoughts, online course content, and best practices in transitioning to online instruction. This book is ideal for teachers, principals, school leaders, instructional designers, curriculum developers, higher education professors, pre-service teachers, in-service teachers, practitioners, researchers, and anyone interested in developing more effective virtual and in-classroom teaching methods.

Softwaretests stellen eine kritische Phase in der Softwareentwicklung dar. Jetzt zeigt sich, ob das Programm die entsprechenden Anforderungen erfüllt und sich auch keine Programmierungsfehler eingeschlichen haben. Doch wie bei allen Phasen im Software-Entwicklungsprozess gibt es auch hier eine Reihe möglicher Fallstricke, die die Entdeckung von Programmfehlern vereiteln können. Deshalb brauchen Softwaretester ein Handbuch, das alle Tipps, Tricks und die häufigsten Fehlerquellen genau auflistet und erläutert, damit mögliche Testfehler von vornherein vermieden werden können. Ein solches Handbuch ersetzt gut und gerne jahr(zehnt)elange Erfahrung und erspart dem Tester frustrierende und langwierige Trial-und-Error-Prozeduren. Chem Kaner und James Bach sind zwei der international führenden Experten auf dem Gebiet des Software Testing. Sie schöpfen hier aus ihrer insgesamt 30-jährigen Erfahrung. Die einzelnen Lektionen sind nach Themenbereichen gegliedert, wie z.B. Testdesign, Test Management, Teststrategien und Fehleranalyse. Jede Lektion enthält eine Behauptung und eine Erklärung sowie ein Beispiel des entsprechenden Testproblems. "Lessons Learned in Software Testing" ist ein unverzichtbarer Begleiter für jeden Software Tester.

There are no losses in life just lessons learned. Every experience, trial, and pain teaches us something we never knew about ourselves. Author Jeevan Brown dives into the lives of 16 college students as they experience the trials and tribulations that ultimately made them the men and women they are today. Based on true events, these stories are raw, uncut, funny, nostalgic, and emotional. From near death experiences, sports, rape, drugs, racism, STD's, finances, fashion, relationships and more. Each story gives a detailed account of the pivotal aspects followed by advice, statistics and the lessons the main characters learned from each experience. This book may help somebody dealing with the same dynamic with hopes that they'll overcome the unfortunate circumstances that he or she is in.

This book is about lessons learned (both conferred and received) by a fictional protagonist, E. Randall Mann, who was a law teacher at a major law school for over fifty years. There are nine stories or chapters that comprise this book. The stories appear as written in the first person by Mann and a fictitious student, Billie Williams, who served as Mann's research assistant after he retired and ultimately wrote two of the stories in remembrance following Mann's death. Although the context for the lessons learned is law school and legal education, the lessons are intended to be transcendent. They explore the complex ingredients of life that often enrich us all: courage, resilience, survival, introspection, self-knowledge and self-awareness, death and loss, race, trust, friendship, love, and, above all, inspiration. Praise for Lessons Learned: "These stories are written by a mentor and colleague who taught law for 51 years and who provided a guiding influence to countless law school students, administrators, and deans. They serve as a wonderful supplement to One L by Scott Turow, as they go beyond the first year to offer perspectives throughout the law school experience, including lessons learned from colleagues, mentors, family, and above all students." -- Mike Spivey, Spivey Consulting Group There are a number of "lessons learned" contained in this book but there seem to be two prime lessons woven into the fabric of these stories of a teacher. The first lesson learned is stated in metaphorical terms in Chapter 3 and describes the best law school teacher as "a Socratic teacher who could lead and orchestrate an entire class much like the best of symphony conductors . . . but leaves the making of music to orchestral players." More direct are his descriptions of real teachers as those who earn the trust of their students, have a sense of humor and create an effective "classroom chemistry." ... As a colleague of Professor Becker's, Michael Waterstone, wrote, this book "ought to appear on every dean's recommended reading list for people considering law school, or about to enter law school, or about to begin as an entry level teacher in law school." To which I would add, "and every pre-law advisor."-- Gerald Wilson, Duke Universiy

For many years, the U.S. Army recognized the need to share information or lessons gained from training and actual combat operations. During World War II and the Korean War, the Army published "combat bulletins" in an attempt to share combat experiences with other Soldiers. During the Vietnam War, Army units published quarterly operational reports that made an effort to share lessons from combat operations. By doing this, units learned from the mistakes others made and were given an opportunity to avoid the same problems. Although these procedures were successful, the Army did not have a formal or permanent program in place to collect, analyze, and share lessons in both peacetime and wartime. As a result, the Army established the Center for Army Lessons Learned (CALL) in 1985. The Army had officially recognized the need to share lessons gained from training experiences and actual combat operations. Since the inception of CALL, the Army, as a learning organization, greatly evolved over time. CALL also evolved. Now, military communities, civilian governmental agencies, and the corporate world recognize the importance of sharing knowledge and learning from past experiences. In many ways, the U.S Army led this effort by allowing commanders to make honest mistakes in training, talk about those mistakes openly, and share what was done to correct those mistakes with other units about to undergo the same training experience. This is an essential precondition for having an effective lessons learned (LL) program: the ability to self-analyze and self-criticize in an atmosphere where there is no blame. The results were instrumental in changing the Army and creating a learning environment that won the Cold War, ensured victory in Desert Storm, and continues to support our Soldiers in Iraq and Afghanistan today.

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions