0%

Book Description

Highly touted methodologies, such as Agile, Lean, and Design Thinking, leave many organizations bamboozled by an unprecedented array of processes, tools, and methods for digital product development. Many teams meet their peril trying to make sense of these options. How do the methods fit together to achieve the right outcome? What’s the best approach for your circumstances?

In this insightful report, Jonny Schneider from ThoughtWorks shows you how to diagnose your situation, understand where you need more insight to move forward, and then choose from a range of tactics that can move your team closer to clarity.

Blindly applying any model, framework, or method seldom delivers the desired result. Agile began as a better answer for delivering software. Lean focuses on product success. And Design Thinking is an approach for exploring opportunities and problems to solve. This report shows you how to evaluate your situation before committing to one, two, or all three of these techniques.

  • Understand how design thinking, the lean movement, and agile software development can make a difference
  • Define your beliefs and assumptions as well as your strategy
  • Diagnose the current condition and explore possible futures
  • Decide what to learn, and how to learn it, through fast research and experimentation
  • Decentralize decisions with purpose-driven, collaborative teams
  • Prioritize and measure value by responding to customer demand

Table of Contents

  1. 1. Introduction
    1. What Design Thinking Is
      1. Elements of Design Thinking
      2. Divergence, Emergence, and Convergence
      3. Design Thinking Is for All
    2. What Lean Thinking Is
      1. From Scientific Management to Lean Management
      2. Values and Principles of Lean Thinking
    3. What Agile Is
      1. Commonalities of Lean and Agile
      2. How Lean and Agile Are Different
    4. All Together Now
  2. 2. Actionable Strategy
    1. The Problem with Complexity
    2. Vision and Strategy
    3. Defining Actionable Strategy
      1. Step 1: Diagnose the Current Condition
      2. Step 2: Explore Possible Futures
      3. Step 3: Set a Course
      4. Step 4: Take Action and Adjust
    4. Conclusion
  3. 3. Act to Learn
    1. Defining Your Beliefs and Assumptions
    2. Decide What to Learn and How to Learn It
    3. Research and Experiments for Learning
    4. Problem Validation
      1. Customer Problems
      2. Solution Evaluation
      3. Demand Validation
      4. The Cost of Experiments
    5. Conclusion
  4. 4. Leading Teams to Win
    1. Purpose-Driven Autonomy
    2. Mission Command
    3. All Together Now
    4. Techniques for Communicating Purpose and Progress
      1. Visual Management
    5. Techniques for Prioritizing Value
      1. Dimensions of Success
      2. Making Success Measurable
      3. Value-Based Prioritization
    6. Conclusion
  5. 5. Delivery Is Still an Experiment
    1. DevOps and CD
      1. Making It Small and Often
      2. Freedom to Decide When and How Much to Release
    2. Evolutionary Architecture and Emergent Design
      1. Small, Modular, and Service-Oriented
    3. Conclusion
    4. Closing Thoughts on Design Thinking, Lean, and Agile
  6. Acknowledgments