The Agile Team Handbook 2nd Edition

Completely revised and expanded, The Agile Team Handbook, Second Edition, will help guide you, your Team, and your organization on your Agile journey using Scrum. Scrum is intentionally disruptive. It is socially disruptive and organizationally disruptive with a purpose - to help your team and your organization build the best possible products as effectively as possible. Working within the disruptive framework that is Scrum is both challenging and highly rewarding. This handbook provides a solid foundation for you and your team to overcome the challenges and reap the rewards.

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.

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.

Deliver Better Games Faster, On Budget—And Make Game Development Fun Again! Game development is in crisis—facing bloated budgets, impossible schedules, unmanageable complexity, and death march overtime. It’s no wonder so many development studios are struggling to survive. Fortunately, there is a solution. Scrum and Agile methods are already revolutionizing development outside the game industry. Now, long-time game developer Clinton Keith shows exactly how to successfully apply these methods to the unique challenges of game development. Keith has spent more than fifteen years developing games, seven of them with Scrum and agile methods. Drawing on this unparalleled expertise, he shows how teams can use Scrum to deliver games more efficiently, rapidly, and cost-effectively; craft games that offer more entertainment value; and make life more fulfilling for development teams at the same time. You’ll learn to form successful agile teams that incorporate programmers, producers, artists, testers, and designers—and promote effective collaboration within and beyond those teams, throughout the entire process. From long-range planning to progress tracking and continuous integration, Keith offers dozens of tips, tricks, and solutions—all based firmly in reality and hard-won experience. Coverage includes Understanding Scrum’s goals, roles, and practices in the context of game development Communicating and planning your game’s vision, features, and progress Using iterative techniques to put your game into a playable state every two to four weeks— even daily Helping all team participants succeed in their roles Restoring stability and predictability to the development process Managing ambiguous requirements in a fluid marketplace Scaling Scrum to large, geographically distributed development teams Getting started: overcoming inertia and integrating Scrum into your studio’s current processes Increasingly, game developers and managers are recognizing that things can’t go on the way they have in the past. Game development organizations need a far better way to work. Agile Game Development with Scrum gives them that—and brings the profitability, creativity, and fun back to game development.

Introduction to Disciplined Agile Delivery provides a quick overview of how agile software development works from beginning-to-end. It describes the Disciplined Agile Delivery (DAD) process decision framework and then works through a case study describing a typical agile team's experiences adopting a disciplined agile approach. The book describes how the team develops the first release of a mission-critical application while working in a legacy enterprise environment. It describes their experiences from beginning-to-end, starting with their initial team initiation efforts through construction and finally to deploying the solution into production. It also describes how the team stays together for future releases, overviewing their process improvement efforts from their Scrum-based beginnings through to a lean continuous delivery approach that fits in with their organization's evolving DevOps strategy.The DAD framework is a hybrid of existing methods such as Scrum, Kanban, Agile Modeling, SAFe, Extreme Programming, Agile Data, Unified Process and many others. DAD provides the flexibility to use various approaches and plugs the gaps not addressed by mainstream agile methods. In a nutshell, DAD is "pragmatic agile." DAD describes proven strategies to adapt and scale your agile initiatives to suit the unique realities of your enterprise without having to figure it all out by yourself.Here's an overview of what each chapter covers:* Chapter 1: Introduction. This chapter provides a quick overview of the book and a brief history of Disciplined Agile.* Chapter 2: Reality over Rhetoric. This chapter explores several common myths about DAD and more importantly disproves them.* Chapter 3: Disciplined Agile Delivery in a Nutshell. This chapter provides a brief yet comprehensive overview of the DAD framework. * Chapter 4: Introduction to the Case Study. This chapter introduces us to the team, describes the market opportunity that they hope to address, and describes the environment in which they're working.* Chapter 5: Inception. The team's initiation effort includes initial requirements modeling and planning with their stakeholders in a streamlined manner, initial architecture modeling, setting up their physical work environment, setting up the start of their tooling infrastructure, initial risk identification, and finally securing stakeholder support and funding for the rest of the first release.* Chapters 6 through 10: Construction. These chapters each describe a single Construction iteration, sharing the team's experiences during each of those two-week timeboxes. * Chapter 11: Transition. The two-week transition phase focuses on final testing and fixing, training the support/help-desk staff, finishing a few short end-user "how to" videos, and deploying the solution into production.* Chapter 12: Future Releases. This chapter overviews the team's improvement efforts over the next few releases, describing how they evolve from the agile Scrum-based lifecycle to a leaner approach and eventually to continuous delivery.* Chapter 13: Closing Thoughts. This chapter overviews the disciplined agile resources that are available to you.* Appendix: The Disciplined Agile IT Department. This short appendix overviews our ongoing work on the Disciplined Agile framework to address the full scope of an IT department. At 102 pages, you should find this book to be a quick, informative read.

The Team Handbook Second Edition is a best-selling comprehensive resource book that organizations around the world use to teach people how to be effective team members. In addition, it contains tools and methods that teams use in their work. The Team Handbook Second Edition provides everything you need to create high performing teams. Topics include team roles, responsibilities, and dynamics; problem solving; process improvement strategies and tools; meeting skills; conflict resolution; decision-making methods; sponsor and management responsibilities; and team-building exercises and warms-up. This practical book helps master black belts, and all team members understand how to build effective and efficient teams within an organization. It is especially helpful to individuals who are responsible for creating teams and providing training for the people who are team members, as well as supporters of teams within the organization.

"Hundreds of organizations around the world have already benefited from Disciplined Agile Delivery (DAD). Disciplined Agile (DA) is the only comprehensive tool kit available for guidance on building high-performance agile teams and optimizing your way of working (WoW). As a hybrid of all the leading agile and lean approaches, it provides hundreds of strategies to help you make better decisions within your agile teams, balancing self-organization with the realities and constraints of your unique enterprise context. The highlights of this handbook include: #1. As the official source of knowledge on DAD, it includes greatly improved and enhanced strategies with a revised set of goal diagrams based upon learnings from applying DAD in the field. #2 It is an essential handbook to help coaches and teams make better decisions in their daily work, providing a wealth of ideas for experimenting with agile and lean techniques while providing specific guidance and trade-offs for those "it depends" questions. #3 It makes a perfect study guide for Disciplined Agile certification. Why "fail fast" (as our industry likes to recommend) when you can learn quickly on your journey to high performance? With this handbook, you can make better decisions based upon proven, context-based strategies, leading to earlier success and better outcomes"--

In an uncertain and complex world, learning is more important than ever before. In fact, it can be a competitive advantage. Teams and organizations that learn rapidly deliver greater customer value faster and more reliably. Furthermore, those teams are more engaged, more productive, and more satisfied. The most effective way to enable teams to learn is by holding regular retrospectives. Unfortunately, many teams only get shallow results from their retrospectives. This book is filled with practical advice, techniques, and real-life examples that will take retrospectives to the next level--whether your team is co-located, hybrid, or remote. This book will help team leads, scrum masters, and coaches engage their teams to learn, improve, and deliver greater results. For nearly two decades, scrum masters, team leads, and coaches have relied on the first edition of Agile Retrospectivesas an essential resource to facilitate better retrospectives. This edition builds on recent research, reflects the authors' experiences over two decades, and shares wisdom gleaned from the global retrospective community. Find practical advice to level up retrospective skills. Address the challenges of remote and hybrid retrospectives head on. Take advantage of expanded guidance on designing and facilitating retrospectives--based on the questions and concerns of practitioners worldwide. Gain insight into choosing a broad or narrow focus for retrospectives. Explore how to use both objective and subjective data to enable more effective conversations. Learn how to make decisions that stick. Understand the importance of psychological safety and how to foster it in retrospectives. Elevate issues and engage managers in systemic change. Learn from many real-life stories that demonstrate how our advice has impacted retrospectives at organizations around the globe. Finally, find a set of recommended flows that reveal the authors' thought process in designing retrospectives for scenarios teams faced in real life.