You know the Agile and Lean development buzzwords, you've read the books. But when systems need a serious overhaul, you need to see how it works in real life, with real situations and people. Lean from the Trenches is all about actual practice. Every key point is illustrated with a photo or diagram, and anecdotes bring you inside the project as you discover why and how one organization modernized its workplace in record time. Lean from the Trenches is all about actual practice. 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.

This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time. Covering: Practical tips and tricks for most Scrum and XP practices. Typical pitfalls and how they were addressed. Diagrams and photos illustrating day-to-day work. Testing and test-driven development. Scaling and coordinating multiple teams. Dealing with resistance from inside and outside the team. Planning and time estimation techniques

Your team is stressed; priorities are unclear. You're not sure what your teammates are working on, and management isn't helping. If your team is struggling with any of these symptoms, these four case studies will guide you to project success. See how Kanban was used to significantly improve time to market and to create a shared focus across marketing, IT, and operations. Each case study comes with illustrations of the Kanban board and diagrams and graphs to help you see behind the scenes. Learn a Lean approach by seeing how Kanban made a difference in four real-world situations. You'll explore how four different teams used Kanban to make paradigm-changing improvements in software development. These teams were struggling with overwork, unclear priorities, and lack of direction. As you discover what worked for them, you'll understand how to make significant changes in real situations. The four case studies in this book explain how to: Improve the full value chain by using Enterprise Kanban Boost engagement, teamwork, and flow in change management and operations Save a derailing project with Kanban Help an office team outside IT keep up with growth using Kanban What seems easy in theory can become tangled in practice. Discover why "improving IT" can make you miss your biggest improvement opportunities, and why you should focus on fixing quality and front-end operations before IT. Discover how to keep long-term focus and improve across department borders while dealing with everyday challenges. Find out what happened when using Kanban to find better ways to do work in a well-established company, including running multi-team development without a project office. You'll inspire your team and engage management to make it easier to develop better products. What You Need: This is a case study book, so there are no software requirements. The book covers the relevant bits of theory before presenting the case studies.

The Lean UX approach to interaction design is tailor-made for today’s web-driven reality. In this insightful book, leading advocate Jeff Gothelf teaches you valuable Lean UX principles, tactics, and techniques from the ground up—how to rapidly experiment with design ideas, validate them with real users, and continually adjust your design based on what you learn. Inspired by Lean and Agile development theories, Lean UX lets you focus on the actual experience being designed, rather than deliverables. This book shows you how to collaborate closely with other members of the product team, and gather feedback early and often. You’ll learn how to drive the design in short, iterative cycles to assess what works best for the business and the user. Lean UX shows you how to make this change—for the better. Frame a vision of the problem you’re solving and focus your team on the right outcomes Bring the designers’ toolkit to the rest of your product team Share your insights with your team much earlier in the process Create Minimum Viable Products to determine which ideas are valid Incorporate the voice of the customer throughout the project cycle Make your team more productive: combine Lean UX with Agile’s Scrum framework Understand the organizational shifts necessary to integrate Lean UX Lean UX received the 2013 Jolt Award from Dr. Dobb's Journal as the best book of the year. The publication's panel of judges chose five notable books, published during a 12-month period ending June 30, that every serious programmer should read.

Printed in full color. Faced with a software project of epic proportions? Tired of over-committing and under-delivering? Enter the dojo of the agile samurai, where agile expert Jonathan Rasmusson shows you how to kick-start, execute, and deliver your agile projects. Combining cutting-edge tools with classic agile practices, The Agile Samurai gives you everything you need to deliver something of value every week and make rolling your software into production a non-event. Get ready to kick some software project butt. By learning the ways of the agile samurai you will discover: how to create plans and schedules your customer and your team can believe in what characteristics make a good agile team and how to form your own how to gather requirements in a fraction of the time using agile user stories what to do when you discover your schedule is wrong, and how to look like a pro correcting it how to execute fiercely by leveraging the power of agile software engineering practices By the end of this book you will know everything you need to set up, execute, and successfully deliver agile projects, and have fun along the way. If you're a project lead, this book gives you the tools to set up and lead your agile project from start to finish. If you are an analyst, programmer, tester, usability designer, or project manager, this book gives you the insight and foundation necessary to become a valuable agile team member. The Agile Samurai slices away the fluff and theory that make other books less-than-agile. It's packed with best practices, war stories, plenty of humor and hands-on tutorial exercises that will get you doing the right things, the right way. This book will make a difference.

In 2002 the agile manifesto was published. Since then thousands of people have been trained in scrum & other agile ways of working. The first sentence of the agile manifesto says: We are uncovering better ways of developing software by doing it and helping others do it. This book is about helping others and contains tips Yves collected from people in the trenches, eg people who are doing it. agile working improves with more diversity, this book contains tips from 89 different people, living in 28 countries and with 28 (different) nationalities. With tips from: Sander Hoogendoorn Ivan Darmawan Naresh Jain Diana Larsen Michael Sahota Mike Cohn Shane Hastie Ben Linders Katrina Clokie Henrik Kniberg Christopher Avery Johanna Rothman Karthik Kamal B Ardita Karaj Jutta Eckstein Yassal Sundman Aino Corry Clare Sudbery Rashina Hoda Lisette Sutherland Samantha Laing Karen Graeves Judy Rees Allison Pollard Linda Rising Mina Boström Nakicenovic Michele Sliger Jenni & Ole Jepsen Emilie Franchomme George Dinwiddie Siddharta Govindaraj Woody Zuill Nicole Belilos Vasco Duarte Angela Riggs Chris Matts Bart Vermijlen Lisa Crispin Zuzi Sochova Corey Ladas Rini Van Solingen Dana Pylayeva Stacey Ackerman Tim Ottinger Ivo Peksens Tom Perry Tobias Fors Hina Popal Terry Harmer Olaf Lewitz Joanne Perold Stacia Viscardi Emily Webber Tobias Anderberg Heidi Helfand Ravi Kumar Cesario Ramos Corinna Baldauf Jeff Patton Ron Jeffries Tom Cagley Oana Juncu Nele Van Beveren Jimmy Janlén Irene Kuhn Michael (Mike) Hill Ilan Kirschenbaum Jürgen De Smet Lanette Creamer Daria Bagina Phil Gadzinski Tony Ponton Roman Pichler Madhavi Ledalla Brenda Bao Tze Chin Tang Selena Delesie Molood Ceccarelli Nadezhda Belousova Anke Maerz Daniel Terhorst-North Deepti Jain Karen Catlin Tsutomu Yasui Kanatcha Sakdiset Kevlin Henney

“We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader.