People need to be effective.Productivity books focus on doing more, Jim and Tonianne want you to focus on doing better. Personal Kanban is about choosing the right work at the right time. Recognizing why we do the things we do. Understanding the impact of our actions. Creating value - not just product. For ourselves, our families, our friends, our co-workers. For our legacy.Personal Kanban takes the same Lean principles from manufacturing that led the Japanese auto industry to become a global leader in quality, and applies them to individual and team work. Personal Kanban asks only that we visualize our work and limit our work-in-progress. Visualizing work allows us to transform our conceptual and threatening workload into an actionable, context-sensitive flow. Limiting our work-in-progress helps us complete what we start and understand the value of our choices. Combined, these two simple acts encourage us to improve the way we work and the way we make choices to balance our personal, professional, and social lives.Neither a prescription nor a plan, Personal Kanban provides a light, actionable, achievable framework for understanding our work and its context. This book describes why students, parents, business leaders, major corporations, and world governments all see immediate results with Personal Kanban.

    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.

    In 1999, Tony introduced Clayton Christensen to the idea that “people have underlying needs or processes in their lives, that they are addressing in some way right now”—an insight that was to become Jobs-to-be-Done Theory. For 25 years, Ulwick and his company, Strategyn, have helped over 400 companies, applying Jobs-to-be-Done Theory in practice with a success rate of 86%—a 5-fold improvement. “Ulwick has taken the guesswork out of innovation,” says the ‘father of modern marketing,’ Philip Kotler, S. C. Johnson Distinguished Professor of International Marketing at the Kellogg School of Management, Northwestern University. “He has done this by introducing us to Jobs-to-be-Done theory, and converting it to practice using his rigorous innovation process known as Outcome-Driven Innovation. I call him the Deming of Innovation because, more than anyone else, Tony has turned innovation into a science,” adds Kotler. LEARN - Why companies fail at innovation and how to avoid critical mistakes. - How to employ the Jobs-to-be-Done Theory Needs Framework to categorize, define, capture, and prioritize customer needs. - A Jobs-to-be-Done Growth Strategy Matrix to categorize, understand, and employ the 5 strategies that drive growth. - Outcome-Based Segmentation: how does it create new opportunities? - The details of the innovation process known as Outcome-Driven Innovation. It ties customer-defined metrics to the customer’s Job-to-be-Done, transforming every aspect of opportunity discovery, marketing and innovation. - The Language of Job-to-be-Done – the syntax and lexicon of innovation.

    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 outcomesBring the designers’ toolkit to the rest of your product teamShare your insights with your team much earlier in the processCreate Minimum Viable Products to determine which ideas are validIncorporate the voice of the customer throughout the project cycleMake your team more productive: combine Lean UX with Agile’s Scrum frameworkUnderstand the organizational shifts necessary to integrate Lean UXLean 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.

    Scaling Up: How a Few Companies Make It...and Why the Rest Don't is the first major revision of this business classic. In Scaling Up, Harnish and his team share practical tools and techniques for building an industry-dominating business. These approaches have been honed from over three decades of advising tens of thousands of CEOs and executives and helping them navigate the increasing complexities (and weight) that come with scaling up a venture. This book is written so everyone -- from frontline employees to senior executives -- can get aligned in contributing to the growth of a firm. There's no reason to do it alone, yet many top leaders feel like they are the ones dragging the rest of the organization up the S-curve of growth. The goal of this book is to help you turn what feels like an anchor into wind at your back -- creating a company where the team is engaged; the customers are doing your marketing; and everyone is making money. To accomplish this, Scaling Up focuses on the four major decision areas every company must get right: People, Strategy, Execution, and Cash. The book includes a series of new one-page tools including the updated One-Page Strategic Plan and the Rockefeller Habits ChecklistTM, which more than 40,000 firms around the globe have used to scale their companies successfully -- many to $1 billion and beyond. Running a business is ultimately about freedom. Scaling Up shows business leaders how to get their organizations moving in sync to create something significant and enjoy the ride.

    As newly appointed captain of the USS Santa Fe, a nuclear-powered submarine, he was responsible for more than a hundred sailors, deep in the sea. In this high-stress environment, where there is no margin for error, it was crucial his men did their job and did it well.But the ship was dogged by poor morale, poor performance, and the worst retention in the fleet. Marquet acted like any other captain until, one day, he unknowingly gave an impossible order, and his crew tried to follow it anyway. When he asked why the order wasn't challenged, the answer was "Because you told me to." Marquet realized he was leading in a culture of followers, and they were all in danger unless they fundamentally changed the way they did things. That's when Marquet took matters into his own hands and pushed for leadership at every level. Turn the Ship Around! is the true story of how the Santa Fe skyrocketed from worst to first in the fleet by challenging the U.S. Navy's traditional leader-follower approach. Struggling against his own instincts to take control, he instead achieved the vastly more powerful model of giving control. Before long, each member of Marquet's crew became a leader and assumed responsibility for everything he did, from clerical tasks to crucial combat decisions. The crew became fully engaged, contributing their full intellectual capacity every day, and the Santa Fe started winning awards and promoting a highly disproportionate number of officers to submarine command.No matter your business or position, you can apply Marquet's radical guidelines to turn your own ship around. The payoff: a workplace where everyone around you is taking responsibility for their actions, where people are healthier and happier, where everyone is a leader.

    In the next ten years, change will happen even faster. As Hillary Clinton's Senior Advisor for Innovation, Alec Ross travelled nearly a million miles to forty-one countries, the equivalent of two round-trips to the moon. From refugee camps in the Congo and Syrian war zones, to visiting the world's most powerful people in business and government, Ross's travels amounted to a four-year masterclass in the changing nature of innovation. In The Industries of the Future, Ross distils his observations on the forces that are changing the world. He highlights the best opportunities for progress and explains how countries thrive or sputter. Ross examines the specific fields that will most shape our economic future over the next ten years, including robotics, artificial intelligence, the commercialization of genomics, cybercrime and the impact of digital technology. Blending storytelling and economic analysis, he answers questions on how we will need to adapt. Ross gives readers a vivid and informed perspective on how sweeping global trends are affecting the ways we live, now and tomorrow.

    From the transistor to the laser, it s hard to find an aspect of modern life that hasn t been touched by Bell Labs. Why did so many transformative ideas come from Bell Labs? In "The Idea Factory," Jon Gertner traces the origins of some of the twentieth century s most important inventions and delivers a riveting and heretofore untold chapter of American history. At its heart this is a story about the life and work of a small group of brilliant and eccentric men Mervin Kelly, Bill Shockley, Claude Shannon, John Pierce, and Bill Baker who spent their careers at Bell Labs. Their job was to research and develop the future of communications. Small-town boys, childhood hobbyists, oddballs: they give the lie to the idea that Bell Labs was a grim cathedral of top-down command and control.Gertner brings to life the powerful alchemy of the forces at work behind Bell Labs inventions, teasing out the intersections between science, business, and society. He distills the lessons that abide: how to recruit and nurture young talent; how to organize and lead fractious employees; how to find solutions to the most stubbornly vexing problems; how to transform a scientific discovery into a marketable product, then make it even better, cheaper, or both. Today, when the drive to invent has become a mantra, Bell Labs offers us a way to enrich our understanding of the challenges and solutions to technological innovation. Here, after all, was where the foundational ideas on the management of innovation were born. "The Idea Factory" is the story of the origins of modern communications and the beginnings of the information age a deeply human story of extraordinary men who were given extraordinary means time, space, funds, and access to one another and edged the world into a new dimension."

    How has Google done it? Veteran technology reporter Steven Levy was granted unprecedented access to the company, and in this revelatory book he takes readers inside Google headquarters—the Googleplex—to show how Google works.While they were still students at Stanford, Google cofounders Larry Page and Sergey Brin revolutionized Internet search. They followed this brilliant innovation with another, as two of Google’s earliest employees found a way to do what no one else had: make billions of dollars from Internet advertising. With this cash cow, Google was able to expand dramatically and take on other transformative projects: more efficient data centers, open-source cell phones, free Internet video (YouTube), cloud computing, digitizing books, and much more.The key to Google’s success in all these businesses, Levy reveals, is its engineering mind-set and adoption of such Internet values as speed, openness, experimentation, and risk taking. After its unapologetically elitist approach to hiring, Google pampers its engineers—free food and dry cleaning, on-site doctors and masseuses—and gives them all the resources they need to succeed. Even today, with a workforce of more than 23,000, Larry Page signs off on every hire.But has Google lost its innovative edge? With its newest initiative, social networking, Google is chasing a successful competitor for the first time. Some employees are leaving the company for smaller, nimbler start-ups. Can the company that famously decided not to be evil still compete?No other book has ever turned Google inside out as Levy does with In the Plex.

    Conventional wisdom says most startups need to be in Silicon Valley, started by young engineers around a sexy new idea, and backed by VC funding. But as Mikkel Svane reveals in Startupland, the story of founding Zendesk was anything but conventional.Founded in a Copenhagen loft by three thirty-something friends looking to break free from corporate doldrums, Zendesk Inc. is now one of the hottest enterprise software companies, still rapidly growing with customers in 150 countries. But its success was anything but predestined. With revealing stories both funny and frank, Mikkel shares how he and his friends bravely left secure jobs to start something on their own, how he almost went broke several times, how they picked up themselves and their families to travel across the world to California and the unknown, and how the three friends were miraculously still together for Zendesk's IPO and (still growing) success.Much like Zendesk's mission itself--to remove friction, barriers, and mystery in order to make customer service easier and more approachable--Startupland removes some of the myths about startups and startup founders. Mikkel's advice, hard-won through experience, often bucks conventional wisdom and entrepreneurial tropes. He shares why failure (whether fast or slow) is awful, why a seemingly boring product or idea can be the most exciting, why giving back to the community is as important as the bottom line. From how to hire right (look for people who are not offended by swearing) to which personas generate the highest response rates, Mikkel answers the most pressing questions from the perspective of someone still in the trenches and willing to share the hard truth, warts and all.While there are books by consultants who tell you how to build businesses, or by entrepreneurs now running billion-dollar businesses, there are few books from people still in the trenches who acutely remember the difficult daily decisions, the thrill (and fears) of the early days, the problems that scale with growing a business, and the reason why they all went on the adventure in the first place. Startupland is indispensable reading for all entrepreneurs who want to make their ideas the next big thing. The book will inspire and empower you to follow your own dream and create your own story.

    Questioning—deeply, imaginatively, "beautifully"—can help us identify and solve problems, come up with game-changing ideas, and pursue fresh opportunities. So why are we often reluctant to ask "Why?"Berger's surprising findings reveal that even though children start out asking hundreds of questions a day, questioning "falls off a cliff" as kids enter school. In an education and business culture devised to reward rote answers over challenging inquiry, questioning isn't encouraged—and, in fact, is sometimes barely tolerated.And yet, as Berger shows, the most creative, successful people tend to be expert questioners. They've mastered the art of inquiry, raising questions no one else is asking—and finding powerful answers. The author takes us inside red-hot businesses like Google, Netflix, IDEO, and Airbnb to show how questioning is baked into their organizational DNA. He also shares inspiring stories of artists, teachers, entrepreneurs, basement tinkerers, and social activists who changed their lives and the world around them—by starting with a "beautiful question."Berger explores important questions, such as:- Why aren't we nurturing kids' natural ability to question—and what can parents and schools do about that?- Since questioning is a starting point for innovation, how might companies and business leaders begin to encourage and exploit it?- And most important, how can each of us re-ignite that questioning spark—and use inquiry as a powerful means to rethink and reinvent our lives?A More Beautiful Question outlines a practical Why / What If / How system of inquiry that can guide you through the process of innovative questioning—helping you find imaginative, powerful answers to your own "beautiful questions."

    Combining his candid insights with a rigorous analysis of Toyota's attempts at Lean production, Ohno's book explains how Lean principles can improve any production endeavor. A historical and philosophical description of just-in-time and Lean manufacturing, this work is a must read for all students of human progress. On a more practical level, it continues to provide inspiration and instruction for those seeking to improve efficiency through the elimination of waste.

    In fact, this one document can steer an entire organization when it comes to delivering on company strategy. This practical guide teaches you how to create an effective product roadmap, and demonstrates how to use the roadmap to align stakeholders and prioritize ideas and requests. With it, you’ll learn to communicate how your products will make your customers and organization successful. Whether you're a product manager, product owner, business analyst, program manager, project manager, scrum master, lead developer, designer, development manager, entrepreneur, or business owner, this book will show you how to: Articulate an inspiring vision and goals for your product Prioritize ruthlessly and scientifically Protect against pursuing seemingly good ideas without evaluation and prioritization Ensure alignment with stakeholders Inspire loyalty and over­-delivery from your team Get your sales team working with you instead of against you Bring a user­ and buyer-­centric approach to planning and decision-making Anticipate opportunities and stay ahead of the game Publish a comprehensive roadmap without over­committing

    Forget short-term symptoms like Donald Trump and Brexit, it is innovation itself that explains them and that will itself shape the 21st century for good and ill. Yet innovation remains a mysterious process, poorly understood by policy makers and businessmen, hard to summon into existence to order, yet inevitable and inexorable when it does happen.Matt Ridley argues in this book that we need to change the way we think about innovation, to see it as an incremental, bottom-up, fortuitous process that happens to society as a direct result of the human habit of exchange, rather than an orderly, top-down process developing according to a plan. Innovation is crucially different from invention, because it is the turning of inventions into things of practical and affordable use to people. It speeds up in some sectors and slows down in others. It is always a collective, collaborative phenomenon, not a matter of lonely genius. It is gradual, serendipitous, recombinant, inexorable, contagious, experimental and unpredictable. It happens mainly in just a few parts of the world at any one time. It still cannot be modelled properly by economists, but it can easily be discouraged by politicians. Far from there being too much innovation, we may be on the brink of an innovation famine.Ridley derives these and other lessons, not with abstract argument, but from telling the lively stories of scores of innovations, how they started and why they succeeded or in some cases failed. He goes back millions of years and leaps forward into the near future. Some of the innovation stories he tells are about steam engines, jet engines, search engines, airships, coffee, potatoes, vaping, vaccines, cuisine, antibiotics, mosquito nets, turbines, propellers, fertiliser, zero, computers, dogs, farming, fire, genetic engineering, gene editing, container shipping, railways, cars, safety rules, wheeled suitcases, mobile phones, corrugated iron, powered flight, chlorinated water, toilets, vacuum cleaners, shale gas, the telegraph, radio, social media, block chain, the sharing economy, artificial intelligence, fake bomb detectors, phantom games consoles, fraudulent blood tests, faddish diets, hyperloop tubes, herbicides, copyright and even – a biological innovation -- life itself.

    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