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.

The Provocative and Practical Guide to Coaching Agile Teams As an agile coach, you can help project teams become outstanding at agile, creating products that make them proud and helping organizations reap the powerful benefits of teams that deliver both innovation and excellence. More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it’s a challenging role. It requires new skills—as well as a subtle understanding of when to step in and when to step back. Migrating from “command and control” to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You’ll gain a deep view into the role of the agile coach, discover what works and what doesn’t, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach’s roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you’re an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?

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.

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.

This pocket guide to Scrum is the one book for everyone who wants to learn or re-learn about Scrum. The book describes the framework as it was designed and intended, with a strong focus on the purpose to the rules and adding an historical perspective to Scrum and the Agile movement. Several elements that were described in the first edition of Scrum - A Pocket Guide (2013) were later added to the official Scrum Guide. The most noticeable ones are the Scrum Values (2016) and the description of the 3 questions of the Daily Scrum as a good, yet optional practice (2017). As the balance of society keeps shifting from industrial labor to digital work, complexity and unpredictability keep increasing. The need for agility through Scrum increases equally, in and beyond software and product development. This 2nd edition of Scrum - A Pocket Guide offers the clarity and insights on Scrum that many organizations need, today and in the foreseeable future. Scrum – A Pocket Guide is an extraordinarily competent book. It flows with insight, understanding, and perception. This should be the de facto standard handout for all looking for a complete, yet clear overview of Scrum without being bothered by irrelevancies. (Ken Schwaber, Scrum co-creator) The author, Gunther Verheyen, is a seasoned Scrum practitioner (2003). Throughout his standing career as a consultant, Gunther has employed Scrum in diverse circumstances. He was partner to Ken Schwaber and Director of the Professional Scrum series at Scrum.org. He is the founder of Ullizee-Inc and engages with people and organizations as an independent Scrum Caretaker.