Download Free Project Retrospectives Book in PDF and EPUB Free Download. You can read online Project Retrospectives and write the review.

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.
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.
Failure to learn from past mistakes and successes has consistently been a major obstacle to improving IT project management. This monograph addresses this shortcoming by integrating, updating, and extending the research findings from four previous studies on IT project retrospectives. The result is a "meta-retrospective" of 264 IT projects.
Improve Every Retrospective! Real Solutions for Every Team Leader, Facilitator, and Participant “. . . Aino has shared a robust, curated list of antipatterns and how to avoid them. . . . And she has shared so much more than tips and techniques. You will find a gold mine--with precious nuggets, including her personal experiences, effective facilitation resources, and pointers for extracting yourself and your team when you're stuck.” --From the Foreword by Diana Larsen, co-author, Agile Retrospectives: Making Good Teams Great Retrospectives are indispensable for continuous learning and improvement in Lean, Agile, DevOps, and other contexts, but most of us have suffered through at least one retrospective that was a waste of time, or worse. Now, leading agile coach Aino Vonge Corry identifies 24 reasons that retrospectives fail and shows how to overcome each of them. Using the familiar “patterns” approach, Retrospectives Antipatterns introduces antipatterns related to structure, planning, people, distributed teams, and more. Corry shares traps she's encountered and mistakes she's made over more than a decade of leading retrospectives and then presents proven solutions. With her insights and guidance, you can run enjoyable retrospectives that deliver concrete improvements and real value--or at the very least recognize when you are making the same mistake as the author! Create a common language, actionable solutions, and proven plans for solving the retrospective problems you'll encounter most often Recognize symptoms, assess tradeoffs, and refactor your current situation into something better Plan more effectively: decide who should attend and facilitate, when to schedule your retrospective, and how much time to set aside Handle “people” problems: deal with negativity, silence, distrust, disillusionment, loudmouths, and cultural differences Facilitate better “virtual” retrospectives, with tips for online retrospectives included in each antipattern Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.
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
This new edition gives project managers practical methods and tools to make the right decisions while juggling multiple objectives, risks and uncertainties, and stakeholders. Project management requires you to navigate a maze of multiple and complex decisions that are an everyday part of the job. To be effective, you must know how to make rational choices with your projects, what processes can help to improve these choices, and what tools are available to help you with decision-making. An entertaining and easy-to-read guide to a structured project decision-making process, Project Decisions will help you identify risks and perform basic quantitative and qualitative risk and decision analyses. Lev Virine and Michael Trumper use their understanding of basic human psychology to show you how to use event chain methodology, establish creative business environments, and estimate project time and costs. Each phase of the process is described in detail, including a review of both its psychological aspects and quantitative methods.
This is the digital version of the printed book (Copyright © 2005). Take Control of Your Project in the Final Stage of Software Development In software development, projects are won or lost during the project endgame-that final stage of software development between release for testing and release to customers. Software Endgames: Eliminating Defects, Controlling Change, and the Countdown to On-Time Delivery presents the core strategies for delivering working software to your customers. Focusing solely on the endgame, the book provides hard-won, hands-on strategies and practices for delivering real value. In the endgame, effective management and repair of defects is crucial. Experienced project manager and consultant Robert Galen shows readers how to conduct effective defect triage -- analyzing, understanding, and categorizing defects-in preparation for scheduling repairs. Readers will learn how to transform the endgame from a time of rampant defects and utter chaos into a time of focused repairs, effective teamwork, and change management. You'll set release criteria, establish endgame release plans, and utilize a variety of change reduction and endgame management techniques. Topics include developing various forms of release criteria and leveraging them to guide your teams' efforts strategies for reducing the rate of change change control and triage techniques that lead to efficient and effective defect repair decisions alternative methods of defect repair for decision-making flexibility setting up a defect-tracking system, managing defects and gathering standard metrics for endgame defect trending techniques for repair planning and efficiency agile extensions -- how to apply these techniques to agile projects how to "mine" your endgames for overall software development improvements.
Who Says Large Teams Can't Handle Agile Software Development? Agile or "lightweight" processes have revolutionized the software development industry. They're faster and more efficient than traditional software development processes. They enable developers to embrace requirement changes during the project deliver working software in frequent iterations focus on the human factor in software development Unfortunately, most agile processes are designed for small or mid-sized software development projects-bad news for large teams that have to deal with rapid changes to requirements. That means all large teams! With Agile Software Development in the Large, Jutta Eckstein-a leading speaker and consultant in the agile community-shows how to scale agile processes to teams of up to 200. The same techniques are also relevant to teams of as few as 10 developers, especially within large organizations. Topics include the agile value system as used in large teams the impact of a switch to agile processes the agile coordination of several sub-teams the way project size and team size influence the underlying architecture Stop getting frustrated with inflexible processes that cripple your large projects! Use this book to harness the efficiency and adaptability of agile software development. Stop getting frustrated with inflexible processes that cripple your large projects! Use this book to harness the efficiency and adaptability of agile software development.
For those considering Extreme Programming, this book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience. While plenty of books address the what and why of agile development, very few offer the information users can apply directly.
Thousands of IT professionals are being asked to make Scrum succeed in their organizations-including many who weren't involved in the decision to adopt it. If you're one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You'll learn how to gain "quick wins" that build support, and then use the flexibility of Scrum to maximize value creation across the entire process. In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn't) be modified. Coverage includes Getting teams on board, and bringing new team members aboard after you've started Creating a "definition of done" for the team and organization Implementing the strong technical practices that are indispensable for agile success Balancing predictability and adaptability in release planning Keeping defects in check Running productive daily standup meetings Keeping people engaged with pair programming Managing culture clashes on Scrum teams Performing "emergency procedures" to get sprints back on track Establishing a pace your team can truly sustain Accurately costing projects, and measuring the value they deliver Documenting Scrum projects effectively Prioritizing and estimating large backlogs Integrating outsourced and offshored components Packed with real-world examples from Lacey's own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.