Jan 28, 2021
3 min read
Table of Contents
- Foreword
- Preface
- Who This Book Is For
- How to Read This Book
- New to Agile or Lean?
- Disclaimer
- Acknowledgments
- How We Work
- About the Project
- Timeline
- How We Sliced the Elephant
- How We Involved the Customer
- Structuring the Teams
- Attending the Daily Cocktail Party
- First Tier: Feature Team Daily Stand-up
- Second Tier: Sync Meetings per Specialty
- Third Tier: Project Sync Meeting
- The Project Board
- Our Cadences
- How We Handle Urgent Issues and Impediments
- Scaling the Kanban Boards
- Tracking the High-Level Goal
- Defining Ready and Done
- Ready for Development
- Ready for System Test
- How This Improved Collaboration
- Handling Tech Stories
- Example 1: System Test Bottleneck
- Example 2: Day Before the Release
- Example 3: The 7-Meter Class
- Handling Bugs
- Continuous System Test
- Fix the Bugs Immediately!
- Why We Limit the Number of Bugs in the Bug Tracker
- Visualizing Bugs
- Preventing Recurring Bugs
- Continuously Improving the Process
- Team Retrospectives
- Process Improvement Workshops
- Managing the Rate of Change
- Managing Work in Progress
- Using WIP Limits
- Why WIP Limits Apply Only to Features
- Capturing and Using Process Metrics
- Velocity (Features per Week)
- Why We Don’t Use Story Points
- Cycle Time (Weeks per Feature)
- Cumulative Flow
- Process Cycle Efficiency
- Planning the Sprint and Release
- Backlog Grooming
- Selecting the Top Ten Features
- Why We Moved Backlog Grooming Out of the Sprint Planning Meeting
- Planning the Release
- How We Do Version Control
- No Junk on the Trunk
- Team Branches
- System Test Branch
- Why We Use Only Physical Kanban Boards
- What We Learned
- Know Your Goal
- Experiment
- Embrace Failure
- Solve Real Problems
- Have Dedicated Change Agents
- Involve People
- A Closer Look at the Techniques
- Agile and Lean in a Nutshell
- Agile in a Nutshell
- Lean in a Nutshell
- Scrum in a Nutshell
- XP in a Nutshell
- Kanban in a Nutshell
- Reducing the Test Automation Backlog
- What to Do About It
- How to Improve Test Coverage a Little Bit Each Iteration
- Step 1: List Your Test Cases
- Step 2: Classify Each Test
- Step 3: Sort the List in Priority Order
- Step 4: Automate a Few Tests Each Iteration
- Does This Solve the Problem?
- Sizing the Backlog with Planning Poker
- Estimating Without Planning Poker
- Estimating with Planning Poker
- Special Cards
- Cause-Effect Diagrams
- Solve Problems, Not Symptoms
- The Lean Problem-Solving Approach: A3 Thinking
- How to Use Cause-Effect Diagrams
- Example 1: Long Release Cycle
- Example 2: Defects Released to Production
- Example 3: Lack of Pair Programming
- Example 4: Lots of Problems
- Practical Issues: How to Create and Maintain the Diagrams
- Pitfalls
- Why Use Cause-Effect Diagrams?
- Final Words
- Glossary: How We Avoid Buzzword Bingo
Copyright © 2011, The Pragmatic Bookshelf.
TOC | What Readers Are Saying About Lean from the Trenches 👉
Lean from the Trenches by Henrik Kniberg can be purchased in other book formats directly from The Pragmatic Programmers. If you notice a code error or formatting mistake, please let us know here so that we can fix it.
