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

    You will learn the techniques successful leaders use to make their strategic decisions and you will be given the tools to ensure that your team is in alignment to achieving common goals. Leading Quality is the first book that teaches why quality is important and how to incorporate it within the workspace. Praise for Leading Quality:   “A quality mindset remains key to differentiating your product and your company. Leading Quality offers key lessons to develop this mindset.” - Michael Lopp, author of Managing Humans and VP of Product Engineering at Slack “Leading Quality communicates just how important a focus on quality is within your company and is one of the few titles that actually teaches how to lead quality in a clear yet captivating manner.”  - Shesh Patel, Engineering Manager at The New York Times “Three elements define any successful product: quality, quality, and quality. Leading Quality is a comprehensive and practical guide to embedding quality into the DNA of any product organization.” - Nick Caldwell, CPO at Looker and former VP of Engineering at Reddit

    It is written in a conversational tone, doesn't take itself too seriously, and avoids extraneous fluff."- Eric Ries, Author & Creator of the Lean Startup methodology"Get the CustDev book to dive deep into customer interviews and understand how your product can be developed to meet your customers' needs."- Dan Martell, Founder of Flowtown, angel investorCustomer Development is a four-step framework for helping startups discover and validate their customers, product, and go-to-market strategy, developed by Steve Blank and an integral part of Eric Ries' Lean Startup methodology. Focused on the Customer Discovery step, The Entrepreneur's Guide to Customer Development is an easy to follow guide for finding early adopters, building a Minimum Viable Product, finding Product-Market fit, and establishing a sales and marketing roadmap.Deemed a "must-read" by Steve Blank and Eric Ries, inside you will find detailed customer development and lean startup concept definitions, a step-by-step approach to best practices, a business model analysis guide, case studies, rich graphics, as well as worksheets and exercises. No matter the stage of your business, you will return often to this guide to learn how to build a product people want;"get out of the building;" foster strong customer relationships; test business model risk; reach out to early adopters; conduct startup marketing; create a customer funnel based on buyers' process; and prepare your startup to scale up.The Entrepreneur's Guide to Customer Development: A Cheat Sheet to The Four Steps to the Epiphany, affectionately known as the "CustDev book," serves as course text for classes at Stanford University, University of Chicago, Boston University, DePaul University, University of Minnesota and University of Norway."Our UCL (University College London) students love The Entrepreneur's Guide to Customer Development. Thanks to Brant & Patrick for writing this helpful book. "- Dave Chapman, Deputy Head of the Department of Management Science and Innovation at UCL (University College London)"Love it! Required reading for all NYU entrepreneurs."- Frank Rimalovski, Managing Director of NYU Innovation Venture FundThis book is both an introduction for those unfamiliar with lean concepts and highly actionable for lean practitioners. It is a user friendly guide, written to be accessible to marketing professionals, Engineers startup founders and entrepreneurs, VCs, angels, and anyone else involved in building scalable startups.Existing companies will benefit to from applying Customer Development principles described in detail herein: for example, startups struggling to achieve market traction, or well established companies seeking to spark new innovation.This is a business book for startups like no other. No fluff, but rather sound principles and concrete steps to take to build your business. Get up to speed on Customer Development now.

    In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies.Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile.Using the techniques in Agile Estimating and Planning , you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include:Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days--and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.

    Time has not diminished the progressiveness of his business philosophy, or his profound influence on worldwide industry. The modern printing of Today and Tomorrow features an introduction by James J. Padilla, Group Vice President, Ford North America. It also includes an enhanced selection of photos illustrating the processes and facilities Ford covers in the text. Taiichi Ohno acknowledged that a key stimulus to JIT was his close reading of this book. Today, these same ideas are re-emerging to revitalize American industry in new ways."I, for one, am in awe of Ford's greatness. I believe Ford was a born rationalist -- and I feel more so every time I read his writings. He had a deliberate and scientific way of thinking about industry in America. For example, on the issues of standardization and the nature of waste in business, Ford's perception of things was orthodox and universal."- Taiichi Ohno

    It has made countless new businesses possible and presents a massive opportunity for large enterprises to innovate like startups and retire decades of technical debt. But making the most of the cloud requires much more from enterprises than just a technology change. Stephen Orban led Dow Jones’s journey toward digital agility as their CIO and now leads AWS’s Enterprise Strategy function, where he helps leaders from the largest companies in the world transform their businesses. As he demonstrates in this book, enterprises must re-train their people, evolve their processes, and transform their cultures as they move to the cloud. By bringing together his experiences and those of a number of business leaders, Orban shines a light on what works, what doesn’t, and how enterprises can transform themselves using the cloud.

    Forget the dashing swashbuckler, effective leadership is typically understated. It's the myriad small things that make the big things possible. In Do Lead, Les McKeown demolishes the myths that have paralysed leadership in our modern era, then provides newt tools for the job. You'll discover that we can all lead. And what's more, we should. Because effective leadership is goal- not people-oriented. It's about the person with the right skills putting themselves forward. Find out:• The mindset required• The basic leadership toolkit• Techniques for dealing with the (inevitable) failuresWhether you are new to the game or reigniting a dormant passion, start leading from where you are, right now. And start to make a difference. You can lead. Yes, you.

    He explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. He shows why these queues form and how they undermine the speed, quality, and efficiency in product development.

    It will allow you to avoid some likely pitfalls and it will guide you to asking, yourself and your clients, the right questions. Though many people focus on the visualization techniques in Kanban the true value only emerges when you, as a kanban system manager, are apt at noticing the anti-patterns that occur on the kanban board and are able to take appropriate actions. David generously shares his vast experience in this field, with plenty real case scenarios, to the benefit of the reader. After reading this book I toyed with the idea: Would I've changed my approach to coaching my previous clients, in their adoption of agile values and practices, had I read this at the time? Well, I certainly would have, for all of them, and I'm sure it would have meant a smoother change process for the agilely challenged organizations. David provides a comprehensive guide to implementing Kanban in a software development/maintenance environment. Covering the mechanics, dynamics, principles and rationale behind why Kanban is a so promising framework for managing the work of a variety of teams and groups and being an evolutionary-based change management driver. Kanban is the practical approach to implement Lean Software Development, and this book is the practical guide for how to start using Kanban, and how to adapt the system for advanced needs. The book is clear and flowing, even though it covers some quite technical material. I would recommend it to Development managers, Project/Program managers, Agile Coaches/Consultants. It addresses concerns/needs of Novice as well as those already familiar with Kanban and looking for advanced answers. Even if you don't intend to implement a kanban system, there are a lot of techniques and ideas that are easily applicable to any product development/maintenance environment, agile or not. Bottom line, highly recommended.

    Strategic planning is essential. People's competencies should be measured and their weaknesses shored up. People crave feedback.These may sound like basic truths of our work lives today. But actually, they're lies. As strengths guru and bestselling author Marcus Buckingham and Cisco Leadership and Team Intelligence head Ashley Goodall show in this provocative, inspiring book, there are some big lies--distortions, faulty assumptions, wrong thinking--running through our organizational lives. Nine lies, to be exact. They cause dysfunction and frustration and ultimately result in a strange feeling of unreality that pervades our workplaces.But there are those who can get past the lies and discover what's real. These are freethinking leaders who recognize the power and beauty of our individual uniqueness, who know that emergent patterns are more valuable than received wisdom, and that evidence is more powerful than dogma. With engaging stories and incisive analysis, the authors reveal the essential truths that such freethinking leaders will recognize immediately: that it is the strength and cohesiveness of your team, not your company's culture, that matters most; that we need less focus on top-down planning and more on giving our people reliable, real-time intelligence; that rather than trying to align people's goals we should strive to align people's sense of purpose and meaning; that people don't want constant feedback, they want helpful attention. This is the real world of work.If you embrace each person's uniqueness and see this as key for all healthy organizations; if you reject dogma and engage with the real world; if you seek out emergent patterns and put your faith in evidence, not philosophy; if you thrill to the power of teams--if you do all of these, then you are a freethinking leader, and this book is for you.

    Eighteen short months later, Nissan was back in the black, and within several more years it had become the most profitable large automobile company in the world. In SHIFT, Ghosn describes how he went about accomplishing the seemingly impossible, transforming Nissan once again into a powerful global automotive manufacturer. The Brazilian-born, French-educated son of Lebanese parents, Ghosn first learned the management principles and practices that would shape his decisions at Nissan while rising through the ranks at Michelin and Renault. Upon his arrival at Nissan, Ghosn began his new position by embarking on a three-month intensive examination of every aspect of the business. By October 1999 he was ready to announce his strategy to turn the company around with the Nissan Revival Plan. In the plan, he consistently challenged the tradition-bound thinking and practices of Japanese business when they inhibited Nissan’s effectiveness. Ghosn closed plants, laid off workers, broke up long-standing supply networks, and sold off marginal assets to focus on the company’s core business. But slashing costs was just the first step in Nissan’s recovery. In fact, Ghosn introduced changes in every corner of the company, from manufacturing and engineering to marketing and sales. He updated Nissan’s car and truck lineup, took risks on dynamic new designs, and demanded improvements in quality—strategies that quickly burnished Nissan’s image in the marketplace, and re-established the company in the minds of consumers as a leader in innovation and engineering.Like the best-selling memoirs of Jack Welch, Lou Gerstner, and Larry Bossidy, SHIFT is a fascinating behind-the-scenes look at what it takes to transform and re-create a world-class company. Written by one of the world’s most successful and acclaimed CEOs, SHIFT is an invaluable guide for business readers everywhere.

    Lean Analytics steers you in the right direction.This book shows you how to validate your initial idea, find the right customers, decide what to build, how to monetize your business, and how to spread the word. Packed with more than thirty case studies and insights from over a hundred business experts, Lean Analytics provides you with hard-won, real-world information no entrepreneur can afford to go without.Understand Lean Startup, analytics fundamentals, and the data-driven mindsetLook at six sample business models and how they map to new ventures of all sizesFind the One Metric That Matters to youLearn how to draw a line in the sand, so you’ll know it’s time to move forwardApply Lean Analytics principles to large enterprises and established products

    From lean and project management to statistics and data analysis, the DMAIC process is explained in a clear and insightful manner. Figures, tables, references, useful appendices, and a full sample test only add to this book's comprehensiveness.

     With a foreword by Larry Page, and contributions from Bono and Bill Gates. Measure What Matters is about using Objectives and Key Results (OKRs), a revolutionary approach to goal-setting, to make tough choices in business. In 1999, legendary venture capitalist John Doerr invested nearly $12 million in a startup that had amazing technology, entrepreneurial energy and sky-high ambitions, but no real business plan. Doerr introduced the founders to OKRs and with them at the foundation of their management, the startup grew from forty employees to more than 70,000 with a market cap exceeding $600 billion. The startup was Google. Since then Doerr has introduced OKRs to more than fifty companies, helping tech giants and charities exceed all expectations. In the OKR model objectives define what we seek to achieve and key results are how those top­ priority goals will be attained. OKRs focus effort, foster coordination and enhance workplace satisfaction. They surface an organization's most important work as everyone's goals from entry-level to CEO are transparent to the entire institution. In Measure What Matters, Doerr shares a broad range of first-person, behind-the-scenes case studies, with narrators including Bono and Bill Gates, to demonstrate the focus, agility, and explosive growth that OKRs have spurred at so many great organizations. This book will show you how to collect timely, relevant data to track progress - to measure what matters. It will help any organization or team aim high, move fast, and excel.

    Gerard, PhD, its chief learning officer, candidly describe the triumphs and stumbles of a seven-year journey to lean healthcare, an effort that continues today and that has slashed medical errors, improved patient outcomes, raised staff morale, and saved $27 million dollars in costs without layoffs. Find out:> How lean techniques of value-stream-mapping and rapid improvement events cut the average “door-to-balloon” time for heart attack patients at two hospitals from 90 minutes to 37.> What ThedaCare leaders did to replace medicine’s “shame and blame” culture with a lean culture based on continuous improvement and respect for people.> How the lean principle of “building in quality at the source” broke down divisions among medical specialties allowing teams to develop patient care plans faster.> Why traditional modern management is the single biggest impediment to lean healthcare.> How the plan-do-study-act cycle coupled with rapid improvement events cut the wait time at a robotic radiosurgery unit from 26 days to six.> How the lean concept of “one piece flow” saved time in treating ischemic stroke patients, increasing the number of patients receiving a CT scan within 25 minutes from 51% to 89%.> How senior leaders at other healthcare organizations can begin their own lean transformations using a nine-step action plan based on what ThedaCare did — and what it would do differently.Toussaint and Gerard prove that lean healthcare does not mean less care. On the Mend shows that when care is truly re-designed around patients, waste and errors are eliminated, quality improves, costs come down, and healthcare professionals have more time to spend with patients, who get even better care.