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.

    Beautiful Evidence is about how seeing turns into showing, how data and evidence turn into explanation. The book identifies excellent and effective methods for showing nearly every kind of information, suggests many new designs (including sparklines), and provides analytical tools for assessing the credibility of evidence presentations (which are seen from both sides: how to produce and how to consume presentations). For alert consumers of presentations, there are chapters on diagnosing evidence corruption and PowerPoint pitches. Beautiful Evidence concludes with two chapters that leave the world of pixel and paper flatland representations - and move onto seeing and thinking in space land, the real-land of three-space and time.

    According to the August Forrester Report, 56 percent of IT managers interviewed at Global 2,500 companies are already using some type of open source software in their infrastructure and another 6 percent will install it in the next two years. This revolutionary model for collaborative software development is being embraced and studied by many of the biggest players in the high-tech industry, from Sun Microsystems to IBM to Intel.The Cathedral & the Bazaar is a must for anyone who cares about the future of the computer industry or the dynamics of the information economy. Already, billions of dollars have been made and lost based on the ideas in this book. Its conclusions will be studied, debated, and implemented for years to come. According to Bob Young, "This is Eric Raymond's great contribution to the success of the open source revolution, to the adoption of Linux-based operating systems, and to the success of open source users and the companies that supply them."The interest in open source software development has grown enormously in the past year. This revised and expanded paperback edition includes new material on open source developments in 1999 and 2000. Raymond's clear and effective writing style accurately describing the benefits of open source software has been key to its success. With major vendors creating acceptance for open source within companies, independent vendors will become the open source story in 2001.

    Dominic Frisby has written a great account. Read it and glimpse into the future'—Sir Richard Branson In 2008, while the world was busy panicking about the global financial crisis, a computer programmer called Satoshi Nakamoto posted a message on an out-of-the-way mailing list. ‘I’ve been working on a new electronic cash system,’ he said. ‘It might make sense to get some just in case it catches on.’ Nobody seemed to care. But what he had programmed would become the world’s most famous alternative currency: Bitcoin. Economists, anarchists, speculators, computer coders, libertarians, criminals and entrepreneurs were inspired across the world. Early adopters would make a return two million times larger than their investment. Now it seems that Bitcoin will do to banking and finance what email did to the postal service and what the internet did to publishing: destroy old monopolies and create opportunities for the masses. Some even suggest that the technology behind Bitcoin will usurp our Western systems of representative democracy. In this gripping book, Dominic Frisby sets out to solve the mystery surrounding the identity of Bitcoin’s secretive creator, Satoshi Nakamoto. He shows how Bitcoin will change the world. And, perhaps most importantly of all, he does something nobody else has hitherto been able to do: he explains in layman’s language exactly how it works. 'The book’s outstanding, but the story it tells is even better.’ —Matt Ridley, The Times ‘In this highly readable yet technically accomplished book, Dominic Frisby makes crypto currencies crystal clear. Read it, or fail to understand possibly the most important financial innovation of our time.' —Liam Halligan, Sunday Telegraph 'Despite having an MSc in Computer Science and spending over ten years studying monetary theory, I ignored Bitcoin as hype for too long. You shouldn’t. Read Dominic’s thrilling book and discover the next big thing.’ —Steve Baker, MP

    By presenting actual experiences and analyzing them as they are described, the author conveys the developmental thought processes employed and shows a style of thinking that leads to successful results is something that can be learned. Along with spectacular successes, the author also conveys how failures contributed to shaping the thought processes. Provides the reader with a style of thinking that will enhance a person's ability to function as a problem-solver of complex technical issues. Consists of a collection of stories about the author's participation in significant discoveries, relating how those discoveries came about and, most importantly, provides analysis about the thought processes and reasoning that took place as the author and his associates progressed through engineering problems.

    Should the blame fall on Wall Street, Main Street, or Pennsylvania Avenue? On greedy traders, misguided regulators, sleazy subprime companies, cowardly legislators, or clueless home buyers?According to Bethany McLean and Joe Nocera, two of America's most acclaimed business journalists, the real answer is all of the above-and more. Many devils helped bring hell to the economy. And the full story, in all of its complexity and detail, is like the legend of the blind men and the elephant. Almost everyone has missed the big picture. Almost no one has put all the pieces together.All the Devils Are Here goes back several decades to weave the hidden history of the financial crisis in a way no previous book has done. It explores the motivations of everyone from famous CEOs, cabinet secretaries, and politicians to anonymous lenders, borrowers, analysts, and Wall Street traders. It delves into the powerful American mythology of homeownership. And it proves that the crisis ultimately wasn't about finance at all; it was about human nature.Among the devils you'll meet in vivid detail:• Angelo Mozilo, the CEO of Countrywide, who dreamed of spreading homeownership to the masses, only to succumb to the peer pressure-and the outsized profits-of the sleaziest subprime lending.• Roland Arnall, a respected philanthropist and diplomat, who made his fortune building Ameriquest, a subprime lending empire that relied on blatantly deceptive lending practices.• Hank Greenberg, who built AIG into a Rube Goldberg contraption with an undeserved triple-A rating, and who ran it so tightly that he was the only one who knew where all the bodies were buried.• Stan O'Neal of Merrill Lynch, aloof and suspicious, who suffered from "Goldman envy" and drove a proud old firm into the ground by promoting cronies and pushing out his smartest lieutenants.• Lloyd Blankfein, who helped turn Goldman Sachs from a culture that famously put clients first to one that made clients secondary to its own bottom line.• Franklin Raines of Fannie Mae, who (like his predecessors) bullied regulators into submission and let his firm drift away from its original, noble mission.• Brian Clarkson of Moody's, who aggressively pushed to increase his rating agency's market share and stock price, at the cost of its integrity.• Alan Greenspan, the legendary maestro of the Federal Reserve, who ignored the evidence of a growing housing bubble and turned a blind eye to the lending practices that ultimately brought down Wall Street-and inflicted enormous pain on the country.Just as McLean's The Smartest Guys in the Room was hailed as the best Enron book on a crowded shelf, so will All the Devils Are Here be remembered for finally making sense of the meltdown and its consequences.

    In Russell Brunson's experience, after working with thousands of businesses, he has found that’s rarely the case. Low traffic and weak conversion numbers are just symptoms of a much greater problem, a problem that’s a little harder to see (that’s the bad news), but a lot easier to fix (that’s the good news). DotComSecrets will give you the marketing funnels and the sales scripts you need to be able to turn on a flood of new leads into your business.

    He invented such things as "the highly confident letter" (I'm highly confident that I can raise the money you need to buy company X) and "the blind pool" (Here's a billion dollars: let us help you buy a company), and he financed the biggest corporate raiders--men like Carl Icahn and Ronald Perelman.And then, on September 7, 1988, things changed. The Securities and Exchange Commission charged Milken and Drexel Burnham Lambert with insider trading and stock fraud. Waiting in the wings was the US District Attorney, who wanted to file criminal and racketeering charges. What motivated Milken in his drive for power and money? Did Drexel Burnham Lambert condone the breaking of laws? The Predators' Ball dramatically captures American business history in the making, uncovering the philosophy of greed that has dominated Wall Street in the 1980s.

    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.

    It took the open source world by storm since its inception in 2005, and is used by small development shops and giants like Google, Red Hat, and IBM, and of course many open source projects.A book by Git experts to turn you into a Git expert. Introduces the world of distributed version control Shows how to build a Git development workflow.

    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

    With this practical, hands-on book, you’ll learn how to do it faster and smarter using Lean UX techniques. UX expert Laura Klein shows you what it takes to gather valuable input from customers, build something they’ll truly love, and reduce the time it takes to get your product to market.No prior experience in UX or design is necessary to get started. If you’re an entrepreneur or an innovator, this book puts you right to work with proven tips and tools for researching, identifying, and designing an intuitive, easy-to-use product.Determine whether people will buy your product before you build itListen to your customers throughout the product’s lifecycleUnderstand why you should design a test before you design a productGet nine tools that are critical to designing your productDiscern the difference between necessary features and nice-to-havesLearn how a Minimum Viable Product affects your UX decisionsUse A/B testing in conjunction with good UX practicesSpeed up your product development process without sacrificing quality

    Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.

    Adam Neumann, an immigrant determined to make his fortune in the United States, landed on the idea of repurposing surplus New York office space for the burgeoning freelance class. Over the course of ten years, WeWork attracted billions of dollars from some of the most sought-after investors in the world, while spending it to build a global real estate empire that he insisted was much more than that: an organization that aspired to nothing less than "elevating the world's consciousness."Moving between New York real estate, Silicon Valley venture capital, and the very specific force field of spirituality and ambition erected by Adam Neumann himself, Billion Dollar Loser lays bare the internal drama inside WeWork. Based on more than two hundred interviews, this book chronicles the breakneck speed at which WeWork’s CEO built and grew his company along with Neumann’s relationship to a world of investors, including Masayoshi Son of Softbank, who fueled its chaotic expansion into everything from apartment buildings to elementary schools.Culminating in a day-by-day account of the five weeks leading up to WeWork’s botched IPO and Neumann’s dramatic ouster, Wiedeman exposes the story of the company’s desperate attempt to secure the funding it needed in the final moments of a decade defined by excess. Billion Dollar Loser is the first book to indelibly capture the highly leveraged, all-blue-sky world of American business in President Trump’s first term, and also offers a sober reckoning with its fallout as a new era begins.

    If you're one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You'll learn how to gain "quick wins" that build support, and then use the flexibility of Scrum to maximize value creation across the entire process. In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn't) be modified. Coverage includes Getting teams on board, and bringing new team members aboard after you've started Creating a "definition of done" for the team and organization Implementing the strong technical practices that are indispensable for agile success Balancing predictability and adaptability in release planning Keeping defects in check Running productive daily standup meetings Keeping people engaged with pair programming Managing culture clashes on Scrum teams Performing "emergency procedures" to get sprints back on track Establishing a pace your team can truly sustain Accurately costing projects, and measuring the value they deliver Documenting Scrum projects effectively Prioritizing and estimating large backlogs Integrating outsourced and offshored components Packed with real-world examples from Lacey's own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.