Technology companies make up seven of the world's ten largest firms by market capitalization. And the key to their success is the key to all modern organizations. Jonathan Smart, business agility practitioner, thought leader, and coach, reveals the patterns and antipatterns that will help organizations from every industry deliver better value sooner, safer, and happier through high levels of engagement, inclusion, and empowerment. Through his decades of experience in the technology world, Smart provides business leaders with a blueprint for creating a world-class organization of the future. Through Agile and Lean ways of working, business leaders can empower teams to improve production, grow together, and create better services for their customers. These better ways of working have overflowed from the IT department to every corner of successful organizations, taking root in every industry from aerospace to accounting, insurance to shipping. This book is not about software development. It is not a book about the computer industry. This book is about applying agility across the entire organization. It's a book that will put you at the front of change and ahead of the competition.

    Martin ("Uncle Bob") reintroduces agile values and principles for a new generation of software developers. In this eagerly-awaited book, the best-selling author of The Clean Coder shows how to bring unprecedented levels of professionalism and discipline to agile development -- and thereby write far more effective, successful software. As with his other books, Martin's Clean Agile: Back to Basics doesn't merely present multiple choices and options, and say "use your best judgment": it tells you what choices to make, and why those choices are critical to your success. Writing in the agile context, Martin offers direct, no-nonsense answers to crucial questions like:How and why did Agile begin? What are the costs and benefits of Agile? What are the most effective practices of Agile Development? How should an Agile team be organized? What roles do programmers, testers, and managers play in an Agile team? What is the role of the Agile Coach? What about Agile for large projects? What kinds of projects benefit from Agile? Clean Agile: Back to Basics is essential reading for programmers, managers, testers, project managers and every software professional called upon to lead or participate in an agile project.

     Drawing on years of experience training more than 10,000 busy managers from around the globe in practical, everyday coaching skills, Bungay Stanier reveals how to unlock your peoples' potential. He unpacks seven essential coaching questions to demonstrate how--by saying less and asking more--you can develop coaching methods that produce great results. – Get straight to the point in any conversation with The Kickstart Question – Stay on track during any interaction with The Awe Question – Save hours of time for yourself with The Lazy Question – and hours of time for others with The Strategic Question – Get to the heart of any interpersonal or external challenge with The Focus Question – and The Foundation Question – Ensure others find your coaching as beneficial as you do with The Learning Question A fresh innovative take on the traditional how-to manual, the book combines insider information with research based in neuroscience and behavioural economics, together with interactive training tools to turn practical advice into practiced habits. Witty and conversational, The Coaching Habit takes your work--and your workplace--from good to great. "Coaching is an art and it's far easier said than done. It takes courage to ask a question rather than offer up advice, provide and answer, or unleash a solution. giving another person the opportunity to find their own way, make their own mistakes, and create their own wisdom is both brave and vulnerable. In this practical and inspiring book, Michael shares seven transformative questions that can make a difference in how we lead and support. And he guides us through the tricky part - how to take this new information and turn it into habits and a daily practice. --Brené Brown, author of Rising Strong and Daring Greatly

    This book will help you get better outcomes from retrospectives and from any continuous improvement initiative. It will help you consider how best to prepare for retrospectives, generate innovative insights, achieve valuable outcomes, improve facilitation techniques, keep things fresh and maybe even how to have a bit of fun whilst doing it. This book is for anyone who undertakes continuous improvement of any sort, especially those looking to get better outcomes from retrospectives, either as a participant, facilitator, coach or manager of teams. We include ideas for people with varying levels of experience. So, whether you are just getting started with Scrum and retrospectives, or a veteran of continuous improvement looking to fine-tune or get new ideas, or if your retrospectives have become a bit stale and need re-invigorating, there are ideas in here to support you.

     Leading-edge companies like Amazon and Google are applying DevOps and Agile principles to deliver large software projects faster than anyone thought possible. But most executives don’t understand how to transform their current legacy systems and processes to scale these principles across their organizations. Leading the Transformation is an executive guide, providing a clear framework for improving development and delivery. Instead of the traditional Agile and DevOps approaches that focus on improving the effectiveness of teams, this book targets the coordination of work across teams in large organizations—an improvement that executives are uniquely positioned to lead.

    It uses Lean concepts such as limiting work in progress to improve results. A Kanban system is a means of balancing the demand for work to be done with the available capacity to start new work. This book provides a distillation of Kanban: the "essence" of what it is and how it can be used. This brief overview introduces all the principal concepts and guidelines in Kanban and points you to where you can find out more. Essential Kanban Condensed is a great resource to get started or continue exploring ideas for evolutionary change and improvement in business agility.

    

    With so much riding on innovation, creativity, and spark, it is essential to attract and retain quality talent--but what good does this talent do if no one is able to speak their mind? The traditional culture of "fitting in" and "going along" spells doom in the knowledge economy. Success requires a continuous influx of new ideas, new challenges, and critical thought, and the interpersonal climate must not suppress, silence, ridicule or intimidate. Not every idea is good, and yes there are stupid questions, and yes dissent can slow things down, but talking through these things is an essential part of the creative process. People must be allowed to voice half-finished thoughts, ask questions from left field, and brainstorm out loud; it creates a culture in which a minor flub or momentary lapse is no big deal, and where actual mistakes are owned and corrected, and where the next left-field idea could be the next big thing.This book explores this culture of psychological safety, and provides a blueprint for bringing it to life. The road is sometimes bumpy, but succinct and informative scenario-based explanations provide a clear path forward to constant learning and healthy innovation.* Explore the link between psychological safety and high performance * Create a culture where it's "safe" to express ideas, ask questions, and admit mistakes * Nurture the level of engagement and candor required in today's knowledge economy* Follow a step-by-step framework for establishing psychological safety in your team or organization Shed the "yes-men" approach and step into real performance. Fertilize creativity, clarify goals, achieve accountability, redefine leadership, and much more. The Fearless Organization helps you bring about this most critical transformation.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    An essential book that unlocks the secrets of highly successful groups and provides readers with a toolkit for building a cohesive, innovative culture, from the New York Times bestselling author of The Talent Code

    If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book."-- Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L. "The first edition of this book told us what XP was--it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the 'why' of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the 'what' and the 'why, ' we can now all set out to confidently work on the 'how' how to run our projects better, and how to get agile techniques adopted in our organizations."-- Dave Thomas, The Pragmatic Programmers LLC "This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there's an excellent chapter on 'primary practices, ' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change.' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk."-- Ed Yourdon, author and consultant "XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline."-- Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software " Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled 'extreme.'..."-- Lou Mazzucchelli, Fellow, Cutter Business Technology Council "If your organization is ready for a change in the way it develops software, there's the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years."-- Philippe Kruchten, UBC, Vancouver, British Columbia "Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity."-- Mary Poppendieck, author of Lean Software Development: An Agile Toolkit "Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both

    Now, they build on their message with a bold, iconoclastic strategy for creating the ideal company culture—what they call "the calm company." Their approach directly attack the chaos, anxiety, and stress that plagues millions of workplaces and hampers billions of workers every day.Long hours, an excessive workload, and a lack of sleep have become a badge of honor for modern professionals. But it should be a mark of stupidity, the authors argue. Sadly, this isn’t just a problem for large organizations—individuals, contractors, and solopreneurs are burning themselves out the same way. The answer to better productivity isn’t more hours—it’s less waste and fewer things that induce distraction and persistent stress.It’s time to stop celebrating Crazy, and start celebrating Calm, Fried and Hansson assert.Fried and Hansson have the proof to back up their argument. "Calm" has been the cornerstone of their company’s culture since Basecamp began twenty years ago. Destined to become the management guide for the next generation, It Doesn't Have to Be Crazy at Work is a practical and inspiring distillation of their insights and experiences. It isn’t a book telling you what to do. It’s a book showing you what they’ve done—and how any manager or executive no matter the industry or size of the company, can do it too.

    Rose Randall is the archetypical reluctant project manager. Following a painful project failure years ago, Rose s life is cast into chaos when she is once again thrown into the role against her wishes. Faced with a struggling project, help comes from an unexpected source guiding Rose in the direction of Real Options.When you have read Commitment , you:* understand what the Real Options model is;* can apply the Real Options model to manage project risks successfully;* understand why much of your life involves options that you currently are treating as commitments;* see the world through a different filter opening up many new possibilities;* understand the difference between Commitments and Options.Because the book will:* provide specific examples of how a project can manage its risks using the Real Options model;* outline a simple technique for making decisions;* make you aware of all the decisions you make every day;* build your confidence in your ability to decide when to commit and when to leave options open.In short, this book is indispensable for new and experienced project managers plus anyone else who is interested in knowing more about managing large projects.

    In Overcoming the Five Dysfunctions of a Team, Lencioni offers more specific, practical guidance for overcoming the Five Dysfunctions--using tools, exercises, assessments, and real-world examples. He examines questions that all teams must ask themselves: Are we really a team? How are we currently performing? Are we prepared to invest the time and energy required to be a great team? Written concisely and to the point, this guide gives leaders, line managers, and consultants alike the tools they need to get their teams up and running quickly and effectively.

    Rituals are powerful tools: they reinforce good habits, motivate personal and professional achievement, create a common bond between co-workers and build shared values; they can transform an organization's culture and provide a foundation to achieve common goals. Focusing on real-world examples, this book takes a practical approach to the power and benefits of workplace rituals. This insightful guide presents 50 creative rituals, from business and management to design and personal development. Specific case studies highlight the use of rituals and their positive impact to real-world organizations, while vivid visuals allow us to feel their energy and emotion.A ritual is only effective when its purpose is clearly defined. This book goes beyond simple analysis to provide actual recipes for individual rituals designed to promote specific habits, change negative behaviors, and instill values. Each ritual can be adapted to achieve a multitude of goals and tailored to fit your organization or team's specific needs.● Change behaviors, form positive habits, and assign meaning to shared goals● Build shared values, foster innovation, and encourage strong teamwork● Deal with conflicts effectively and engage others to work on resolutions● Learn the fundamental concepts of ritual-building and share your knowledge with your teamAn informative and inspirational resource for executives, managers, team leaders, and employees of every level, Rituals for Work provides a blueprint for building a culture of engagement, innovation, and shared purpose for organizations of all sizes, across industries.