Mastering large-scale software delivery will define the economic landscape of the 21st century, just as mass production defined the landscape in the 20th. Unfortunately, business and technology leaders outside of the tech giants are woefully ill-equipped to solve the problems posed by digital transformation. A new approach is needed.In Project to Product, value stream network pioneer and technology leader Dr. Mik Kersten introduces the Flow Framework. This new way of building an infrastructure for innovation will change the way enterprises think about software delivery, enabling every organization the opportunity to win a portion of the $18.5 trillion (IDC) that will be created annually through better software delivery.Project to Product provides leaders the missing framework needed to create the technology equivalent of an advanced manufacturing line, across thousands of IT professionals, and enables optimizing value creation across the entire organization. This book is ideal for C-suite leadership and IT management at every level.

    Aging computer systems present complex technical challenges for organizations both large and small, and Kill It with Fire provides sound strategies for spearheading modernization efforts.Kill It with Fire examines aging computer systems, the evolution of technology over time, and how organizations can modernize, maintain, and future-proof their current systems.In playful and engaging prose, Marianne Bellotti uses real-world case studies to illustrate the technical challenges of modernizing complex legacy systems, as well as the organizational challenges of time-intensive maintenance efforts. The book explains how to evaluate existing architecture, create upgrade plans, and handle communication structures. Team exercises and historical analyses of complex computer systems make this a valuable resource for those in both older and newer companies, and will help readers restore or create systems built to evolve as time goes on.

    This-is-Lean

    With wisdom and a healthy dose of wit, Denning introduces a cast of furry characters who together learn the fine art of change through storytelling in their quest to overcome obstacles, generate enthusiasm and teamwork, share knowledge, and ultimately lead their company into a new era of success and significance. Through the stories of Squirrel Inc., readers will learn that the ability to tell the right story at the right time can determine the outcome of any major change effort. In each chapter Denning's squirrels learn to use storytelling to address leadership challenges: How to bring about change How to communicate who you are How to transmit values How to foster collaboration How to stop rumors How to share knowledge How to lead your organization into the future

    It’s not about to-do lists and accountability charts. It’s about creating a framework for regular check-ins, key results, and most of all, the beauty of a good fail – and how to take a temporary disaster and turn it into a future success. In this book, Wodtke takes you through the fictional case study of Hanna and Jack, who are struggling to survive in their own startup. They fight shiny object syndrome, losing focus, and dealing with communication issues. After hard lessons, they learn the practical steps they need to do what must be done. The second half of the book demonstrates how to use Objectives and Key Results (OKRs) to help teams realize big goals in a methodical way, leaving nothing to chance. Laid out in a practical but compelling way, she makes the lessons of Hanna and Jack’s story clear and actionable. Ready to move your team in the right direction? Read this, and learn the system of creating your focus – and finding success. "Busy grinding without purpose is the secret death of too many startups. In this memorable story, Christina gives us a glimpse of a more satisfying kind of startup--still hard and chaotic but full of purpose and the chance to build something great." James Cham, Founder, Bloomberg Beta "This book is useful, actionable, and actually fun to read! If you want to get your team aligned around real, measurable goals, Radical Focus will teach you how to do it quickly and clearly." -Laura Klein, Principal, Users Know "Someone once told me that 'problems are just opportunities that haven’t presented themselves'. Since I was introduced to OKRs, they've been an invaluable tool for me, and our company. Christina's ideas have been instrumental, allowing me to better navigate the often ambiguous approach to goal setting and along the way creating a more open and accountable team and a clearer path for myself professionally. I personally can't thank her enough for the guidance." Scott Baldwin, Director of Services, Yellow Pencil "Radical Focus illustrates how to implement OKRs in an engaging, compact, realistic story. Best of all, Wodtke proves OKRs can be fun!" Ben Lamorte, OKRs.com

    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

    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.

    We’re building more products than ever before, but most of them fail—not because we can’t complete what we set out to build, but because we waste time, money, and effort building the wrong product.What we need is a systematic process for quickly vetting product ideas and raising our odds of success. That’s the promise of Running Lean.In this inspiring book, Ash Maurya takes you through an exacting strategy for achieving a "product/market fit" for your fledgling venture, based on his own experience in building a wide array of products from high-tech to no-tech. Throughout, he builds on the ideas and concepts of several innovative methodologies, including the Lean Startup, Customer Development, and bootstrapping.Running Lean is an ideal tool for business managers, CEOs, small business owners, developers and programmers, and anyone who’s interested in starting a business project.Find a problem worth solving, then define a solutionEngage your customers throughout the development cycleContinually test your product with smaller, faster iterationsBuild a feature, measure customer response, and verify/refute the ideaKnow when to "pivot" by changing your plan’s courseMaximize your efforts for speed, learning, and focusLearn the ideal time to raise your "big round" of fundingGet on track with The Lean Series Presented by Eric Ries—bestselling author of The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses—The Lean Series gives you solid footing in a proven methodology that will help your business succeed.

    Adopting Lean will take time and commitment, but it’s vital for harnessing the cultural and technical forces that are accelerating the rate of innovation.* Discover how Lean focuses on people and teamwork at every level, in contrast to traditional management practices* Approach problem-solving experimentally, by exploring solutions, testing assumptions, and getting feedback from real users* Lead and manage large-scale programs in a way that empowers employees, increases the speed and quality of delivery, and lowers costs* Learn how to implement ideas from the DevOps and Lean Startup movements even in complex, regulated environments

    Product Mastery explores the traits of the best product owners offering an insight into the difference between good and great product ownership and explaining how the best product owners are DRIVEN to be successful.In a follow up to the hugely successful Scrum Mastery, Geoff Watts shares more enlightening case studies on how to be:Decisive with incomplete information.Ruthless about maximizing value and minimizing risk.Informed about your product’s domain.Versatile in your leadership style.Empowering of project stakeholders.Negotiable while you pursue your vision.This is essential reading for anyone involved in an agile product development effort.Geoff Watts has been a thought leader in the agile development space for many years and his books, training and coaching have helped thousands of teams across the world deliver better products more effectively.Geoff is the author of Scrum Mastery: From Good to Great Servant-Leadership and The Coach’s Casebook: Mastering The Twelve Traits That Trap Us, a winner of the 2016 International Book Awards."Product Mastery is a great book to read if you want to understand how a great Product Owner works. Whether you are hiring a Product Owner or want to be a great Product Owner, the insights that Geoff Watts shares in this book should be your guide."--Jeff Sutherland, Co-Creator of Scrum and author of Scrum: The Art of Doing Twice The Work in Half the Time“Geoff has done a great job at distilling the soft skills product owners need to succeed. His new book is packed with practical advice to advance your skills and become a truly great product owner.”– Roman Pichler, Author of Strategize and Agile Product Management with Scrum.

    A pocket-sized overview of roles, artifacts and the sprint cycle, adapted from the bestseller The Elements of Scrum by Chris Sims & Hillary Louise Johnson

    His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant—or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a colleague from student days—Jonah—to help him break out of conventional ways of thinking to see what needs to be done.The story of Alex's fight to save his plant is more than compulsive reading. It contains a serious message for all managers in industry and explains the ideas which underline the Theory of Constraints (TOC) developed by Eli Goldratt.

    But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.

    The result: greater productivity, quality, and profits achieved with minimal cost, time, and effort invested.