Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as “post-mortems”) are only held at the end of the project—too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today. Now Esther and Diana show you the tools, tricks and tips you need to fix the problems you face on a software development project on an on-going basis. You’ll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes and how to scale these techniques up. You’ll learn how to deal with problems, and implement solutions effectively throughout the project—not just at the end. This book will help you: Design and run effective retrospectives Learn how to find and fix problems Find and reinforce team strengths Address people issues as well as technological Use tools and recipes proven in the real world With regular tune-ups, your team will hum like a precise, world-class orchestra.

Getting Value out of Agile Retrospectives helps you and your teams to do retrospectives effectively and efficiently. It's a toolbox with many exercises for facilitating retrospectives, supported with the "what" and "why" of retrospectives, the business value and benefits that they bring, and advice for introducing and improving retrospectives. If you are a Scrum master, agile coach, project manager, product manager or facilitator then this book helps you to discover and apply new ways to do Valuable Agile Retrospectives with your teams. With plenty of exercises you can develop your own personal Retrospectives Toolbox to become more proficient in doing retrospectives and get more out of them.

Learning Agile is a comprehensive guide to the most popular agile methods, written in a light and engaging style that makes it easy for you to learn. Agile has revolutionized the way teams approach software development, but with dozens of agile methodologies to choose from, the decision to "go agile" can be tricky. This practical book helps you sort it out, first by grounding you in agile’s underlying principles, then by describing four specific—and well-used—agile methods: Scrum, extreme programming (XP), Lean, and Kanban. Each method focuses on a different area of development, but they all aim to change your team’s mindset—from individuals who simply follow a plan to a cohesive group that makes decisions together. Whether you’re considering agile for the first time, or trying it again, you’ll learn how to choose a method that best fits your team and your company. Understand the purpose behind agile’s core values and principles Learn Scrum’s emphasis on project management, self-organization, and collective commitment Focus on software design and architecture with XP practices such as test-first and pair programming Use Lean thinking to empower your team, eliminate waste, and deliver software fast Learn how Kanban’s practices help you deliver great software by managing flow Adopt agile practices and principles with an agile coach

What others in the trenches say about The Pragmatic Programmer... “The cool thing about this book is that it’s great for keeping the programming process fresh. The book helps you to continue to grow and clearly comes from people who have been there.” — Kent Beck, author of Extreme Programming Explained: Embrace Change “I found this book to be a great mix of solid advice and wonderful analogies!” — Martin Fowler, author of Refactoring and UML Distilled “I would buy a copy, read it twice, then tell all my colleagues to run out and grab a copy. This is a book I would never loan because I would worry about it being lost.” — Kevin Ruland, Management Science, MSG-Logistics “The wisdom and practical experience of the authors is obvious. The topics presented are relevant and useful.... By far its greatest strength for me has been the outstanding analogies—tracer bullets, broken windows, and the fabulous helicopter-based explanation of the need for orthogonality, especially in a crisis situation. I have little doubt that this book will eventually become an excellent source of useful information for journeymen programmers and expert mentors alike.” — John Lakos, author of Large-Scale C++ Software Design “This is the sort of book I will buy a dozen copies of when it comes out so I can give it to my clients.” — Eric Vought, Software Engineer “Most modern books on software development fail to cover the basics of what makes a great software developer, instead spending their time on syntax or technology where in reality the greatest leverage possible for any software team is in having talented developers who really know their craft well. An excellent book.” — Pete McBreen, Independent Consultant “Since reading this book, I have implemented many of the practical suggestions and tips it contains. Across the board, they have saved my company time and money while helping me get my job done quicker! This should be a desktop reference for everyone who works with code for a living.” — Jared Richardson, Senior Software Developer, iRenaissance, Inc. “I would like to see this issued to every new employee at my company....” — Chris Cleeland, Senior Software Engineer, Object Computing, Inc. “If I’m putting together a project, it’s the authors of this book that I want. . . . And failing that I’d settle for people who’ve read their book.” — Ward Cunningham Straight from the programming trenches, The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process--taking a requirement and producing working, maintainable code that delights its users. It covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Read this book, and you'll learn how to Fight software rot; Avoid the trap of duplicating knowledge; Write flexible, dynamic, and adaptable code; Avoid programming by coincidence; Bullet-proof your code with contracts, assertions, and exceptions; Capture real requirements; Test ruthlessly and effectively; Delight your users; Build teams of pragmatic programmers; and Make your developments more precise with automation. Written as a series of self-contained sections and filled with entertaining anecdotes, thoughtful examples, and interesting analogies, The Pragmatic Programmer illustrates the best practices and major pitfalls of many different aspects of software development. Whether you're a new coder, an experienced programmer, or a manager responsible for software projects, use these lessons daily, and you'll quickly see improvements in personal productivity, accuracy, and job satisfaction. You'll learn skills and develop habits and attitudes that form the foundation for long-term success in your career. You'll become a Pragmatic Programmer.

This is the digital copy of the printed booik (Copyright © 2001). With detailed scenarios, imaginative illustrations, and step-by-step instructions, consultant and speaker Norman L. Kerth guides readers through productive, empowering retrospectives of project performance. Whether your shop calls them postmortems or postpartums or something else, project retrospectives offer organizations a formal method for preserving the valuable lessons learned from the successes and failures of every project. These lessons and the changes identified by the community will foster stronger teams and savings on subsequent efforts. For a retrospective to be effective and successful, though, it needs to be safe. Kerth shows facilitators and participants how to defeat the fear of retribution and establish an air of mutual trust. One tool is Kerth's Prime Directive: Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand. Applying years of experience as a project retrospective facilitator for software organizations, Kerth reveals his secrets for managing the sensitive, often emotionally charged issues that arise as teams relive and learn from each project.

Agile retrospectives help you get to the root of your real problems, so you can solve them quickly and effectively. They're the cornerstone of a successful continuous improvement process, and one of your best tools for triggering positive cultural change. In Improving Agile Retrospectives, leading agile coach/trainer Marc Loeffler combines practical guidance, proven practices, and innovative approaches for maximizing the value of retrospectives for your team--and your entire organization. You can apply his powerful techniques in any project, agile or otherwise. These techniques offer exceptional value wherever continuous improvement is needed: from "lessons-learned" workshops in traditional project management to enterprise-wide change management. Loeffler's detailed, results-focused examples help you recognize and overcome common pitfalls, adapt retrospectives to your unique needs, and consistently achieve tangible results. Throughout, he integrates breakthrough concepts, such as using experimentation and learning from system thinking. He presents small ideas that make a big difference--because they're deeply grounded in real experience. * Learn from failures and successes, and make good things even better * Master facilitation techniques that help you achieve your goals (and have fun doing it) * Prepare your retrospective so it runs smoothly * Practice techniques for generating actionable insights * Keep your retrospectives fresh and interesting * Perform retrospectives that address the entire system, not just your team * Focus on your "better future" with solution-focused retrospectives * Learn how to avoid typical pitfalls when facilitating retrospectives * Lead retrospectives across multiple distributed teams * Use retrospectives to support large-scale change

In this book, Jutta Eckstein examines how retrospectives –originally a kind of a facilitated workshop for gaining feedback– can be applied conceptually to initiate and implement organizational change. Technically, retrospectives were an instrument for a group to examine a past joint period of time and learn from that. The participants of a Retrospective for Organizational Change do not share a joint past, yet they learn from their different individual experiences and use this as a basis to form a shared future. The main strength is to leverage the experiences of a diverse group. Especially if the change is dynamic, which means the approach toward the goal is unclear or if it is complex, where the goal itself is indeterminate, Retrospectives for Organizational Change can provide a way to support the change.This book covers the conceptual idea of using Retrospectives for Organizational Change and additionally reports on the feedback and experiences of its practical application.