The low hanging fruit of correlation and largesample sizes is fast running out. Focusing on the job, understanding truecausality, is going to be the only way to get people to switch and use yourproduct.

    In a rare look into Toyota's ability to consistently achieve breakthroughs that outperform the competition, The Elegant Solution explains what Toyota associates have know all along: its not about the cars. Rather, Toyota's astounding success is just the visible result of a hidden creative process that begins with a seven-digit number. One million. That's how many new ideas that Toyota organization implements every year. These ideas come from every level of the organization- from the factory floors to the corporate suites. And organizations all over the world want to learn how it's done. Now senior University of Toyota advisor Matthew May show how any company can achieve an environment of everyday innovation and discover the kinds of elegant solutions that hold the power to change the game forever. World-class benchmarks like Lexus, Prius, Scion- even Toyota's vaunted production system- are simply shining examples of elegant solutions.

    Their rules of thumb and coaching advice are great blueprints for new and experienced software engineering managers alike." --Tom Conrad, CTO, Pandora "I wish I'd had this material available years ago. I see lots and lots of 'meat' in here that I'll use over and over again as I try to become a better manager. The writing style is right on, and I love the personal anecdotes." --Steve Johnson, VP, Custom Solutions, DigitalFish All too often, software development is deemed unmanageable. The news is filled with stories of projects that have run catastrophically over schedule and budget. Although adding some formal discipline to the development process has improved the situation, it has by no means solved the problem. How can it be, with so much time and money spent to get software development under control, that it remains so unmanageable? In Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams , Mickey W. Mantle and Ron Lichty answer that persistent question with a simple observation: You first must make programmers and software teams manageable. That is, you need to begin by understanding your people--how to hire them, motivate them, and lead them to develop and deliver great products. Drawing on their combined seventy years of software development and management experience, and highlighting the insights and wisdom of other successful managers, Mantle and Lichty provide the guidance you need to manage people and teams in order to deliver software successfully. Whether you are new to software management, or have already been working in that role, you will appreciate the real-world knowledge and practical tools packed into this guide.

    Strategy deployment, called hoshin kanri by Toyota, has proven to be the most effective process for meeting this ongoing challenge. In his new book Getting the Right Things Done, author and LEI faculty member Pascal Dennis outlines the nuts and bolts of strategy deployment, answering two tough questions that ultimately can make or break a company's lean transformation: * What kind of planning system is required to inspire meaningful company-wide continuous improvement? * How might we change existing mental models that do not support a culture of continuous improvement? Getting the Right Things Done demonstrates how strategy deployment can help leaders harness the full power of Lean. Organization leaders at all levels and the management teams who are responsible for strategy deployment will find this book especially insightful. It tells the story of a fictional (yet very real) midsized company, Atlas Industries that needs to dramatically improve to compete with emerging rivals and meet new customer demands. Getting the Right Things Done chronicles the journey of the company and its President/COO, an experienced lean leader who was hired five years ago to steer Atlas in the right direction. While Atlas had already applied some basic lean principles, it had not really connected the people and business processes so that the company could dramatically improve. Atlas' challenge: "Something was missing: a way of focusing and aligning the efforts of good people, and a delivery system, something that would direct the tools to the right places." Enter strategy deployment. The book is designed to provide readers with a framework for understanding the key components of strategy deployment: agreeing on the company's "True North," working within the PDCA cycle, getting conse

    Product Mastery explores the traits of the best product owners offering an insight into the difference between good and great product ownership and explaining how the best product owners are DRIVEN to be successful.In a follow up to the hugely successful Scrum Mastery, Geoff Watts shares more enlightening case studies on how to be:Decisive with incomplete information.Ruthless about maximizing value and minimizing risk.Informed about your product’s domain.Versatile in your leadership style.Empowering of project stakeholders.Negotiable while you pursue your vision.This is essential reading for anyone involved in an agile product development effort.Geoff Watts has been a thought leader in the agile development space for many years and his books, training and coaching have helped thousands of teams across the world deliver better products more effectively.Geoff is the author of Scrum Mastery: From Good to Great Servant-Leadership and The Coach’s Casebook: Mastering The Twelve Traits That Trap Us, a winner of the 2016 International Book Awards."Product Mastery is a great book to read if you want to understand how a great Product Owner works. Whether you are hiring a Product Owner or want to be a great Product Owner, the insights that Geoff Watts shares in this book should be your guide."--Jeff Sutherland, Co-Creator of Scrum and author of Scrum: The Art of Doing Twice The Work in Half the Time“Geoff has done a great job at distilling the soft skills product owners need to succeed. His new book is packed with practical advice to advance your skills and become a truly great product owner.”– Roman Pichler, Author of Strategize and Agile Product Management with Scrum.

    

    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."

    More than 250 examples from technological leaders including IBM, Compaq, and Apple--plus a new focus on growth strategies and on Internet businesses--define how high-tech companies can use product strategy and product platform strategy for competitiveness, profitability, and growth in the Internet age.

    Rose Randall is the archetypical reluctant project manager. Following a painful project failure years ago, Rose s life is cast into chaos when she is once again thrown into the role against her wishes. Faced with a struggling project, help comes from an unexpected source guiding Rose in the direction of Real Options.When you have read Commitment , you:* understand what the Real Options model is;* can apply the Real Options model to manage project risks successfully;* understand why much of your life involves options that you currently are treating as commitments;* see the world through a different filter opening up many new possibilities;* understand the difference between Commitments and Options.Because the book will:* provide specific examples of how a project can manage its risks using the Real Options model;* outline a simple technique for making decisions;* make you aware of all the decisions you make every day;* build your confidence in your ability to decide when to commit and when to leave options open.In short, this book is indispensable for new and experienced project managers plus anyone else who is interested in knowing more about managing large projects.

    Step-by-step instruction and practical case studies show you how to use these tools effectively to achieve better outcomes of projects at hand. Plus, the book provides full coverage on managing continuous process improvement, procurement management, managing distressed projects, and managing multiple team projects. The companion Web site includes exercises and solutions that accompany the project management instruction in the book.

    At 3M, teams are critical to meeting the company's goal of producing half of each year's revenues from the previous five years' innovations. Kodak's Zebra Team proved the worth of black-and-white film manufacturing in a world where color is king.But many companies overtook the potential of teams in turning around tagging profits, entering new markets, and making exciting innovations happen -- because they don't know how to utilize teams successfully. Authors Jon R. Katzenbach and Douglas K. Smith talked with hundreds of people in more than thirty companies to find out where and how teams work best and how to enhance their effectiveness. They reveal:The most important element in team successWho excels at team leadership ... and why they are rarely the most senior peopleWhy companywide change depends on teams ... and moreComprehensive and proven effective, The Wisdom of Teams is the classic primer on making teams a powerful tool for success in today's global marketplace.

    Yet they can't always articulate their ideas clearly enough for you to turn them into code. The Cucumber Book dives straight into the core of the problem: communication between people. Cucumber saves the day; it's a testing, communication, and requirements tool - all rolled into one. We'll show you how to express your customers' wild ideas as a set of clear, executable specifications that everyone on the team can read. You'll learn how to feed those examples into Cucumber and let it guide your development. You'll build just the right code to keep your customers happy, and not a line more. The first part of the book teaches you how to use the core features of Cucumber. You'll learn how to use Cucumber's Gherkin DSL to describe-- in plain language - the behavior your customers want from the system. You'll learn how to write Ruby code that interprets those plain language specifications and checks them against your application. In Part 2, you'll consolidate the knowledge you just gained with a worked example. Although it was born in the Ruby community, you can use Cucumber to test almost any system, from a simple shell script or a Perl script, to enterprise PHP or a Java web application. In Part 3, you'll find a selection of recipes for some of the most common situations you'll encounter using Cucumber in the wild. You'll learn how to test Ajax-heavy web applications with Capybara and Selenium, REST web services, Ruby on Rails applications, command-line applications, legacy applications and lots more! Written by the creator of Cucumber and one of its most experienced users and contributors, The Cucumber Book is an authoritative guide that will give you and your team all the knowledge you need to start using Cucumber with confidence. What You Need: Windows, Mac OS X (with XCode) or Linux Ruby 1.9.2 and upwards

    As Guy Kawasaki puts it, If the two most popular words in your company are "partner" and "strategic," and "partner" has become a verb, and "strategic" is used to describe decisions and activities that don t make sense . . . it s time for a reality check. For nearly three decades, Kawasaki has earned a stellar reputation as an entrepreneur, venture capitalist, and irreverent pundit. His 2004 bestseller, "The Art of the Start," has become the most acclaimed bible for small business. And his blog is consistently one of the fifty most popular in the world. Now, Kawasaki has compiled his best wit, wisdom, and contrarian opinions in handy book form. From competition to customer service, innovation to marketing, he shows readers how to ignore fads and foolishness while sticking to commonsense practices. He explains, for instance: How to get a standing ovation The art of schmoozing How to create a community The top ten lies of entrepreneurs Everything you wanted to know about getting a job in Silicon Valley but didn t know who to ask Provocative, useful, and very funny, this no bull shiitake book will show you why readers around the world love Guy Kawasaki."

    He explains how managers can inspire their people and manage the daily workflow for maximum productivity and includes exercises and activities at the end of each chapter to help managers start implementing new ideas immediately.

    They don't make us feel happier or richer. Why are they not designed as well as the products we love to use such as an Apple iPod or a BMW? The 'developed' world has moved beyond the industrial mindset of products and the majority of 'products' that we encounter are actually parts of a larger service network. These services comprise people, technology, places, time and objects that form the entire service experience. In most cases some of the touchpoints are designed, but in many situations the service as a complete ecology just "happens" and is not consciously designed at all, which is why they don't feel like iPods or BMWs. One of the goals of service design is to redress this imbalance and to design services that have the same appeal and experience as the products we love, whether it is buying insurance, going on holiday, filling in a tax return, or having a heart transplant. Another important aspect of service design is its potential for design innovation and intervention in the big issues facing us, such as transport, sustainability, government, finance, communications and healthcare. Given that we live in a service and information age, a practical, thoughtful book about how to design better services is urgently needed.