The Agile Self Assessment Game

The Agile Self-Assessment Game is used by teams and organizations to self-assess their agility. Playing the game enables teams to reflect on their own team interworking, discover how agile they are and decide what they can do to increase their agility to deliver more value to their customers and stakeholders. This is the first book specifically about Agile Self-assessments. In this book, Ben Linders explains what self-assessments are and why you would do them, and explores how to do them using the Agile Self-assessment Game. He's also sharing experience stories from people who played the game. This book is based on his experience as a developer, tester, team leader, project manager, quality manager, process manager, consultant, coach, trainer, and adviser in Agile, Lean, Quality and Continuous Improvement. It takes a deep dive into self-assessments, viewing them from different perspectives and provides ideas, suggestions, practices, and experiences that will help you to do effective agile self-assessments with your teams. The book is aimed at Scrum masters, agile coaches, consultants leading agile transformations, developers and testers, project managers, line managers, and CxOs; basically for anyone who is looking for an effective way to help their agile teams improve and to increase the agility of their organization. With plenty of ideas, suggestions, and practical cases on Agile Self-assessments, this book will help you to apply assessments and help teams to improve. Note: The agile coaching cards needed to play the games described in the book can be downloaded for a nominal fee at benlinders.com/downloads.

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.

In many organizations, management is the biggest obstacle to successful Agile development. Unfortunately, reliable guidance on Agile management has been scarce indeed. Now, leading Agile manager Jurgen Appelo fills that gap, introducing a realistic approach to leading, managing, and growing your Agile team or organization. Writing for current managers and developers moving into management, Appelo shares insights that are grounded in modern complex systems theory, reflecting the intense complexity of modern software development. Appelo's Management 3.0 model recognizes that today's organizations are living, networked systems; and that management is primarily about people and relationships. Management 3.0 doesn't offer mere checklists or prescriptions to follow slavishly; rather, it deepens your understanding of how organizations and Agile teams work and gives you tools to solve your own problems. Drawing on his extensive experience as an Agile manager, the author identifies the most important practices of Agile management and helps you improve each of them. Coverage includes • Getting beyond “Management 1.0” control and “Management 2.0” fads • Understanding how complexity affects your organization • Keeping your people active, creative, innovative, and motivated • Giving teams the care and authority they need to grow on their own • Defining boundaries so teams can succeed in alignment with business goals • Sowing the seeds for a culture of software craftsmanship • Crafting an organizational network that promotes success • Implementing continuous improvement that actually works Thoroughly pragmatic–and never trendy–Jurgen Appelo's Management 3.0 helps you bring greater agility to any software organization, team, or project.

With plenty of ideas, suggestions, and practical cases on software quality, this book will help you to improve the quality of your software and to deliver high-quality products to your users and satisfy the needs of your customers and stakeholders. Many methods for product quality improvement start by investigating the problems, and then work their way back to the point where the problem started. For instance audits and root cause analysis work this way. But what if you could prevent problems from happening, by building an understanding what drives quality, thus enabling to take action before problems actually occur? What Drives Quality explores how quality plays a role in all of the software development activities. It takes a deep dive into quality by listing the relevant factors of development and management activities that drive the quality of software products. It provides a lean approach to quality by analyzing the full development chain from customer requests to delivering products to users. I'm aiming this book at software developers and testers, architects, product owners and managers, agile coaches, Scrum masters, project managers, and operational and senior managers who consider quality to be important. A book on quality should be practical. It should help you, the reader of this book, to improve the quality of your software and deliver better products. It should inspire you and give you energy to persevere on your quality journey. What drives quality tries to do just that, and more. This book is based on my experience as a developer, tester, team leader, project manager, quality manager, process manager, consultant, coach, trainer, and adviser in Agile, Lean, Quality and Continuous Improvement. It takes a deep dive into quality with views from different perspectives and provides ideas, suggestions, practices, and experiences that will help you to improve quality of the products that your organization is delivering. This book views software quality from an engineering, management, and social perspective. It explores the interaction between all involved in delivering high-quality software to users and provides ideas to do it quicker and at lower costs.

As contrary as it sounds, "planning" -- as we traditionally understand the term--can be the worst thing a company can do. Consider that volatile weather events disrupt trusted supply chains, markets, and promised delivery schedules. Ever-shifting geo-political tensions, as well as internal political upheaval within U.S. and global governments, derail long-planned new ventures. Technology failures block opportunities. Competitors suddenly change their product or release date; your team cannot meet the pace of innovations in your market niche, leaving you sidelined. There are myriad ways in the current business environment for a company's well-considered business plans to go awry. Most business schools continue to prepare managers to be effective in stable and predictable environments, conditions that, if they ever existed at all, are long gone. The Agility Shift shows business leaders exactly how to make the radical mindset and strategy shift necessary to create an agile, entrepreneurial organization that can innovate and thrive in complex, ever-changing contexts. As author Pamela Meyer explains, there is much more involved than a reconfiguration of the org chart and job descriptions. It requires relinquishing the illusion of control at the very foundation of most management training and business practice. Despite most leaders' approaches, "Agility is not simply accelerated planning." Unlike many agility books on the market, The Agility Shift provides specific, actionable strategies and tactics for leaders at all levels of the organization to put into practice immediately to improve agility and achieve results.

The profession of Agile Coaching is, in a word, confusing. That's because of a number of factors, including:?It gets conflated with Professional Coaching and it's so much more than that;?There isn't a standard or generally accepted model for what it is and isn't;?Clients don't understand it, so shared accountability is unbalanced with their coaches;?There is specialized nuance around the skills of coaching at the Team, Enterprise or Organizational, Technical, and Leadership levels.This confusion has created a space where nearly anyone can claim to be an Agile Coach with little experience and narrow skills. Resulting largely in mediocrity and negative impacts for our clients, who by the way, are counting on and paying us for help.Bob Galen has written Extraordinarily Badass Agile Coaching to help alleviate the confusion. The book centers on the Agile Coaching Growth Wheel as the competency and skill maturity model to baseline your agile coaching skills against. Its core goal is to "raise the bar" as to what true excellence looks like and to help you establish a personal development and growth plan.Bob intentionally uses the term Badass to create a vision of professionalism, craft, passion, accountability, and expertise that you need to bring to bear in service of your clients if you represent yourself as an "agile coach".Being an Extraordinarily Badass Agile Coach isn't easy, quick, or for the faint of heart. It takes lots of hard work and dedication. It also requires a map to point you in the right direction. Consider this book that map to coaching badassery, personal growth, and client service.

Learning agility is not a new concept, but it took years of research to prove that it really does exist, and can be quantified on an individual level. Out of that research came the introduction of the Burke Learning Agility Inventory¿ (Burke LAI) as the first reliable, theoretically grounded way to measure learning agility. This book explains how learning agility is measured, and explores the ways that this information can be developed and applied by individuals and organizations.

Agile emphasizes to establish teams and give them whatever they need to do their work. This book on impediments explores how teams can effectively deal with the problems that will happen in their daily work. In agile these problems are called impediments: anything that slows down a team and needs to be dealt with. Agile teams need to be able to handle impediments. This is the first book specifically about dealing with impediments using agile thinking with problem-solving practices. In this book, I explain why dealing with impediments matters. The book also provides approaches for you to effectively handle impediments in teams and beyond the teams. I'm also sharing experience stories from my practice. I based this book on my experience as a developer, tester, team leader, project manager, quality manager, process manager, consultant, coach, trainer, and adviser in Agile, Lean, Quality, and Continuous Improvement. This book dives into problem solving and impediments, viewing them from different perspectives and provides ideas, suggestions, practices, and experiences that will help you to become more effective in dealing with impediments. This book is for agile teams, Scrum masters, tech leads, agile coaches, consultants, developers and testers, project managers, line managers, and CxOs; basically, anyone who is looking for an effective way to handle impediments or support people in doing that. With plenty of ideas, suggestions, examples, and practical cases on impediments, this book will help you to become more effective in dealing with impediments.