Edited by the Sustainability Institute’s Diana Wright, this essential primer brings systems thinking out of the realm of computers and equations and into the tangible world, showing readers how to develop the systems-thinking skills that thought leaders across the globe consider critical for 21st-century life.Some of the biggest problems facing the world—war, hunger, poverty, and environmental degradation—are essentially system failures. They cannot be solved by fixing one piece in isolation from the others, because even seemingly minor details have enormous power to undermine the best efforts of too-narrow thinking.While readers will learn the conceptual tools and methods of systems thinking, the heart of the book is grander than methodology. Donella Meadows was known as much for nurturing positive outcomes as she was for delving into the science behind global dilemmas. She reminds readers to pay attention to what is important, not just what is quantifiable, to stay humble, and to stay a learner.In a world growing ever more complicated, crowded, and interdependent, Thinking in Systems helps readers avoid confusion and helplessness, the first step toward finding proactive and effective solutions.

    How can we originate new ideas, policies, and practices without risking it all?   Using surprising studies and stories spanning business, politics, sports, and entertainment, Grant explores how to recognize a good idea, speak up without getting silenced, build a coalition of allies, choose the right time to act, and manage fear and doubt; how parents and teachers can nurture originality in children; and how leaders can build cultures that welcome dissent. Learn from an entrepreneur who pitches his start-ups by highlighting the reasons not to invest, a woman at Apple who challenged Steve Jobs from three levels below, an analyst who overturned the rule of secrecy at the CIA, a billionaire financial wizard who fires employees for failing to criticize him, and a TV executive who didn’t even work in comedy but saved Seinfeld from the cutting-room floor. The payoff is a set of groundbreaking insights about rejecting conformity and improving the status quo.

    Along the way, they introduce 22 thinking tools that can help you customize the right agile practices for any environment.Better, cheaper, faster software development. You can have all three-if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development.Iterating towards excellence: software development as an exercise in discovery Managing uncertainty: decide as late as possible by building change into the system. Compressing the value stream: rapid development, feedback, and improvement Empowering teams and individuals without compromising coordination Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability How to see the whole-even when your developers are scattered across multiple locations and contractors Simply put, Lean Software Development helps you refocus development on value, flow, and people-so you can achieve breakthrough quality, savings, speed, and business alignment.

    You'll discover the power of storytelling and the way to make data a pivotal point in your story. The lessons in this illuminative text are grounded in theory, but made accessible through numerous real-world examples--ready for immediate application to your next graph or presentation.Storytelling is not an inherent skill, especially when it comes to data visualization, and the tools at our disposal don't make it any easier. This book demonstrates how to go beyond conventional tools to reach the root of your data, and how to use your data to create an engaging, informative, compelling story. Specifically, you'll learn how to:Understand the importance of context and audience Determine the appropriate type of graph for your situation Recognize and eliminate the clutter clouding your information Direct your audience's attention to the most important parts of your data Think like a designer and utilize concepts of design in data visualization Leverage the power of storytelling to help your message resonate with your audience Together, the lessons in this book will help you turn your data into high impact visual stories that stick with your audience. Rid your world of ineffective graphs, one exploding 3D pie chart at a time. There is a story in your data--Storytelling with Data will give you the skills and power to tell it!

    Not only do the authors reveal why the world is so completely screwed up, but they provide proven techniques for creative control of personal, social, and business problems. They analyze the reasons for human failure and tell how to achieve a state of well-being by avoiding that unwanted, ultimate promotion.Students of Freud, Potter, and Parkinson will be fascinated by this satirical examination of man's tendency to escalate himself to oblivion at his level of incompetence.

    Mountains of print have been written about culture. Loonshots identifies the small shifts in structure that control this transition, the same way that temperature controls the change from water to ice.Using examples that range from the spread of fires in forests to the hunt for terrorists online, and stories of thieves and geniuses and kings, Bahcall shows how this new kind of science helps us understand the behavior of companies and the fate of empires. Loonshots distills these insights into lessons for creatives, entrepreneurs, and visionaries everywhere.

    It could forever change how you experience and interact with your physical surroundings, open your eyes to the perversity of bad design and the desirability of good design, and raise your expectations about how things should be designed.B & W photographs and illustrations throughout.

    It holds nothing back while detailing the highest highs and lowest lows of what it's really like to run a startup.  Cliff Lerner's online dating startup, Snap Interactive, was running out of money when he bet the company's fortunes on a then-unknown platform called Facebook. The app suddenly began to acquire 100,000 new users daily for free, and soon after the stock price skyrocketed 2,000 percent, setting off an extraordinary chain of events filled with sudden success and painful lessons.You will learn how to:    * IGNITE EXPLOSIVE GROWTH by creating a remarkable product    * Identify the ONLY 3 METRICS THAT MATTER    * Explore valuable VIRAL GROWTH strategies to grow rapidly    * Execute the GENIUS MEDIA HACKS that helped us acquire 100 million users    * Create a thriving culture of PASSIONATE EMPLOYEES and CONSTANT INNOVATIONPRAISE:"A must read for founders and CEOs who want to achieve rapid growth while also building a great product and company." -Payal Kadakia, Founder & Executive Chairman of ClassPass"Explosive Growth is without question one of the most useful and entertaining business books I have ever read. Cliff gives you a roadmap to massively grow your startup with specific tactical lessons made memorable through engaging stories. This book is a must-read." -David Perry, Digital Sales & Business Development Expert at Google, Adobe, Amazon, Startup Advisor"Want to know how to grow your startup to 100 million users? Then this is the book for you. Explosive Growth gives step-by-step instructions, case studies and proven tactics on how to explode your growth." -Entrepreneur Magazine by Syed Balkhi"Lessons for startups and CEOs on growth hacking, marketing, and innovation from one of the smartest founders I know." -Andrew Weinreich, Inventor of Social Networking

    An essential book that unlocks the secrets of highly successful groups and provides readers with a toolkit for building a cohesive, innovative culture, from the New York Times bestselling author of The Talent Code

    With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 45 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."

    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

    In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle.You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing.User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other proxies Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

    Bill Bryson’s A Walk in the Woods is one example. Richard Feynman’s “Surely You’re Joking, Mr. Feynman!” is another. Now comes Youngme Moon’s Different, a book for “people who don’t read business books.” Actually, it’s more like a personal conversation with a friend who has thought deeply about how the world works … and who gets you to see that world in a completely new light.  If there is one strain of conventional wisdom pervading every company in every industry, it’s the absolute importance of “competing like crazy.” Youngme Moon’s message is simply “Get off this treadmill that’s taking you nowhere. Going tit for tat and adding features, augmentations, and gimmicks to beat the competition has the perverse result of making you like everyone else.” Different provides a highly original perspective on what it means to offer something that is meaningfully different—different in a manner that is both fundamental and comprehensive.  Youngme Moon identifies the outliers, the mavericks, the iconoclasts—the players who have thoughtfully rejected orthodoxy in favor of an approach that is more adventurous. Some are even “hostile,” almost daring you to buy what they are selling. The MINI Cooper was launched with fearless abandon: “Worried that this car is too small? Look here. It’s even smaller than you think.”  These are players that strike a genuine chord with even the most jaded consumers. In fact, almost every success story of the past two decades has been an exception to the rule. Simply go to your computer and compare AOL and Yahoo! with Google. The former pile on feature upon feature to their home pages, while Google is like an austere boutique, dominating a category filled with “extras.” Different shows how to succeed in a world where conformity reigns…but exceptions rule.

    Infrastructure engineers use a software version of this “chaos monkey” to test online services’ robustness—their ability to survive random failure and correct mistakes before they actually occur. Tech entrepreneurs are society’s chaos monkeys, disruptors testing and transforming every aspect of our lives, from transportation (Uber) and lodging (AirBnB) to television (Netflix) and dating (Tinder). One of Silicon Valley’s most audacious chaos monkeys is Antonio García Martínez.After stints on Wall Street and as CEO of his own startup, García Martínez joined Facebook’s nascent advertising team, turning its users’ data into profit for COO Sheryl Sandberg and chairman and CEO Mark “Zuck” Zuckerberg. Forced out in the wake of an internal product war over the future of the company’s monetization strategy, García Martínez eventually landed at rival Twitter. He also fathered two children with a woman he barely knew, committed lewd acts and brewed illegal beer on the Facebook campus (accidentally flooding Zuckerberg's desk), lived on a sailboat, raced sport cars on the 101, and enthusiastically pursued the life of an overpaid Silicon Valley wastrel.Now, this gleeful contrarian unravels the chaotic evolution of social media and online marketing and reveals how it is invading our lives and shaping our future. Weighing in on everything from startups and credit derivatives to Big Brother and data tracking, social media monetization and digital “privacy,” García Martínez shares his scathing observations and outrageous antics, taking us on a humorous, subversive tour of the fascinatingly insular tech industry. Chaos Monkeys lays bare the hijinks, trade secrets, and power plays of the visionaries, grunts, sociopaths, opportunists, accidental tourists, and money cowboys who are revolutionizing our world. The question is, will we survive?

    The Lean Startup movement is very promising, but for many teams it ends up translating into an important question: ”Yeah, but what to build ?” “In ThoughtWorks, our response has been a process called an inception. We gather together a good sample of the people who will be affected by the product and have an intensive session to set an initial direction, using a series of exercises focusing on collaboration and the capture of broad goals. We don't attempt a detailed specification, as that is exactly the kind of thing that becomes out of date as soon as code hits production. But we do want to understand what kind of outcomes we are hoping for, the features that we think will drive these outcomes, and how to assess the effectiveness of our product. With The Lean Inception, Paulo has captured his experience in running these inceptions over the last decade. In particular it's focused on his work to boil the inception down to its essence, concentrating the activity on a single, if very intensive, week of work. Paulo shares how he makes this work, through writing a product vision, capturing personas, understanding the user journeys, and developing high-level features. The result isn't a detailed plan of work, which we find quickly rots into irrelevance. It is a guiding set of goals to set us off in the right direction. It doesn't plan out a final product, with all the features that our users will need, instead it focuses on an initial product that we can release and learn from - the Minimum Viable Product. “ – Martin Fowler, Chief Cientist at ThoughtWorks