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.

    Unfortunately, change is extraordinarily difficult, and most attempts to initiate and sustain it fail. In It Starts with One, J. Stewart Black and Hal B Gregersen identify the core problem: changing individuals and the "mental maps" inside their heads must happen before you can change the organization. Just as actual maps guide people's footsteps, mental maps guide daily behavior. Successful strategic change for the organization is all about changing individual mental maps and behaviors first, because they are the organization.To change organizations, you must break through your own brain barrier -- and help those around you do the same. One step at a time, It Starts with One shows how to do that: how to create new destinations, and new, more inspiring effective paths to sustainable change. Black and Gregersen systematically identify the brain barriers that stand in your way: failure to see, failure to move, and failure to finish. Drawing on their extensive experience consulting with world-class organizations, they offer integrated tools, strategies, and solutions for overcoming each of these obstacles. This edition offers even more effective tools, more guidance on leading change in globalizing environments, and more insight into changing your own mental maps...liberating yourself to transform your entire organization.Seventy percent of organizations that seek strategic change fail. Organizations can't change because individuals don't change. Individuals don't change because powerful mental maps stand in their way. This book offers a powerful, start-to-finish strategy for helping people redraw their mental maps -- and unleash their power to deliver superior, sustained strategic change. Thoroughly updated with new techniques, case studies, and examples, this book offers even more valuable insights for today's leaders and managers.

    Three dots to represent Dallas, Houston, and San Antonio. Three arrows to show direct flights. Problem solved, and the picture made it easy to sell Southwest Airlines to investors and customers. Used properly, a simple drawing on a humble napkin is more powerful than Excel or PowerPoint. It can help crystallize ideas, think outside the box, and communicate in a way that people simply “get”. In this book Dan Roam argues that everyone is born with a talent for visual thinking, even those who swear they can’t draw. Drawing on twenty years of visual problem solving combined with the recent discoveries of vision science, this book shows anyone how to clarify a problem or sell an idea by visually breaking it down using a simple set of visual thinking tools – tools that take advantage of everyone’s innate ability to look, see, imagine, and show. THE BACK OF THE NAPKIN proves that thinking with pictures can help anyone discover and develop new ideas, solve problems in unexpected ways, and dramatically improve their ability to share their insights. This book will help readers literally see the world in a new way.

    As Senge makes clear, in the long run the only sustainable competitive advantage is your organization’s ability to learn faster than the competition. The leadership stories in the book demonstrate the many ways that the core ideas in The Fifth Discipline, many of which seemed radical when first published in 1990, have become deeply integrated into people’s ways of seeing the world and their managerial practices. In The Fifth Discipline, Senge describes how companies can rid themselves of the learning “disabilities” that threaten their productivity and success by adopting the strategies of learning organizations—ones in which new and expansive patterns of thinking are nurtured, collective aspiration is set free, and people are continually learning how to create results they truly desire. The updated and revised Currency edition of this business classic contains over one hundred pages of new material based on interviews with dozens of practitioners at companies like BP, Unilever, Intel, Ford, HP, Saudi Aramco, and organizations like Roca, Oxfam, and The World Bank. It features a new Foreword about the success Peter Senge has achieved with learning organizations since the book’s inception, as well as new chapters on Impetus (getting started), Strategies, Leaders’ New Work, Systems Citizens, and Frontiers for the Future. Mastering the disciplines Senge outlines in the book will:• Reignite the spark of genuine learning driven by people focused on what truly matters to them• Bridge teamwork into macro-creativity• Free you of confining assumptions and mindsets• Teach you to see the forest and the trees• End the struggle between work and personal time

    The book covers all roles, rules and the main principles underpinning Scrum, and is based on the Scrum Guide Edition 2013. A broader context to this fundamental description of Scrum is given by describing the past and the future of Scrum. The author, Gunther Verheyen, has created a concise, yet complete and passionate reference about Scrum. The book demonstrates his core view that Scrum is about a journey, a journey of discovery and fun. He designed the book to be a helpful guide on that journey. Ken Schwaber, Scrum co-creator says that this book currently is the best available description of Scrum around. The book combines some rare characteristics: It describes Scrum in its entirety, yet places it in a broader context (of past and future). The author focuses on the subject, Scrum, in a way that it truly supports the reader. The book has a language and style in line with the philosophy of Scrum. The book shows the playfulness of Scrum. David Starr and Ralph Jocham, Professional Scrum trainers and early agile adopters, say that this is the ultimate book to be advised as follow-up book to the students they teach Scrum to and to teams and managers of organizations that they coach Scrum to."

    It uses Lean concepts such as limiting work in progress to improve results. A Kanban system is a means of balancing the demand for work to be done with the available capacity to start new work. This book provides a distillation of Kanban: the "essence" of what it is and how it can be used. This brief overview introduces all the principal concepts and guidelines in Kanban and points you to where you can find out more. Essential Kanban Condensed is a great resource to get started or continue exploring ideas for evolutionary change and improvement in business agility.

    This long-awaited revision contains changes throughout the text. There are new implementations of most of the major programming systems in the book, including the interpreters and compilers, and the authors have incorporated many small changes that reflect their experience teaching the course at MIT since the first edition was published. A new theme has been introduced that emphasizes the central role played by different approaches to dealing with time in computational models: objects with state, concurrent programming, functional programming and lazy evaluation, and nondeterministic programming. There are new example sections on higher-order procedures in graphics and on applications of stream processing in numerical programming, and many new exercises. In addition, all the programs have been reworked to run in any Scheme implementation that adheres to the IEEE standard.

    Written by a usability engineer with a long and successful paper prototyping history, this book is a practical, how-to guide that will prepare you to create and test paper prototypes of all kinds of user interfaces. You'll see how to simulate various kinds of interface elements and interactions. You'll learn about the practical aspects of paper prototyping, such as deciding when the technique is appropriate, scheduling the activities, and handling the skepticism of others in your organization. Numerous case studies and images throughout the book show you real world examples of paper prototyping at work.Learn how to use this powerful technique to develop products that are more useful, intuitive, efficient, and pleasing:* Save time and money - solve key problems before implementation begins * Get user feedback early - use it to focus the development process * Communicate better - involve development team members from a variety of disciplines * Be more creative - experiment with many ideas before committing to one

    In this one-of-a-kind text, author V. Anton Spraul breaks down the ways that programmers solve problems and teaches you what other introductory books often ignore: how to Think Like a Programmer. Each chapter tackles a single programming concept, like classes, pointers, and recursion, and open-ended exercises throughout challenge you to apply your knowledge. You'll also learn how to:Split problems into discrete components to make them easier to solve Make the most of code reuse with functions, classes, and libraries Pick the perfect data structure for a particular job Master more advanced programming tools like recursion and dynamic memory Organize your thoughts and develop strategies to tackle particular types of problems Although the book's examples are written in C++, the creative problem-solving concepts they illustrate go beyond any particular language; in fact, they often reach outside the realm of computer science. As the most skillful programmers know, writing great code is a creative art—and the first step in creating your masterpiece is learning to Think Like a Programmer.

    From creating new data-driven products through to increasing operational efficiency, big data has the potential to makeyour organization both more competitive and more innovative.As this emerging field transitions from the bleeding edge to enterprise infrastructure, it's vital to understand not only the technologies involved, but the organizational and cultural demands of being data-driven.Written by O'Reilly Radar's experts on big data, this anthology describes:- The broad industry changes heralded by the big data era- What big data is, what it means to your business, and how to start solving data problems- The software that makes up the Hadoop big data stack, and the major enterprise vendors' Hadoop solutions- The landscape of NoSQL databases and their relative merits- How visualization plays an important part in data work

    Establishing and maintaining processes that greatly reduce the chances of project failure is paramount to achieving the competitive edge your company seeks."The Handbook of Program Management" gives program managers at all levels the techniques to put such processes in place as well as consistently integrate new technology and new people into these processes, thus producing superior products and services. Dr. James Brown, an internationally recognized authority in program and project management, explains how to strike a crucial balance between operations and project implementations-the precise point where you must nurture repeatable success.Outlining the differences between the roles of program and project managers, Dr. Brown provides proven principles for establishing a successful program management culture that is supported by enthusiastic personnel and stakeholders. He shows you how to develop the attributes of an effective program manager, from having a vision and strategy for long-term improvement to assessing people and building relationships to analyzing a myriad of means for accomplishing program objectives. You'll see how to Readily adapt to changing business conditions and turn chaos into clarity Mentor and coach project managers in terms of stakeholder management Make strategic program process decisions that positively impact your culture Build strong teams on multiple levels Plan an effective program execution Manage risk in an environment of uncertaintyYou'll also learn the keys to proper portfolio management and how to capitalize on positive program outcomes. Nowhere else will you find such comprehensive, authoritative information on meeting the new standards of program management--Dr. Brown's "The Handbook of Project Management" is the definitive resource.

    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

    By “reverse engineering the fastest growing company in the history of the world,” author Jeff Jarvis, proprietor of Buzzmachine.com, one of the Web’s most widely respected media blogs, offers indispensible strategies for solving the toughest new problems facing businesses today. With a new afterword from the author, What Would Google Do? is the business book that every leader or potential leader in every industry must read.

    Companies that embrace Agile Management learn to connect everyone and everything . . . all the time. They can deliver instant, intimate, frictionless value on a large scale.Agile began emerging many decades ago, but truly took off in the software development industry. Sparking dramatic improvements in quality, innovation, and speed-to-market, the Agile movement is now spreading quickly throughout all kinds of companies. It enables a team, a unit, or an enterprise to nimbly adapt and upgrade products and services to meet rapidly changing technology and customer needs. And the process is applicable anywhere — companies don’t need to be born Agile, like Spotify. Even centuries-old Barclays is making the transition and reaping rewards.Filled with examples from every sector, The Age of Agile helps readers:Master the three laws of Agile Management (team, customer, network) ● Embrace the new mindset ● Overcome constraints ● Employ meaningful metrics ● Make the entire organization Agile ● And moreWith this breakthrough approach, even global giants can learn to act entrepreneurially. Their future depends on it.