The findings will surprise many readers and, quite frankly, upset others.The ChallengeBuilt to Last, the defining management study of the nineties, showed how great companies triumph over time and how long-term sustained performance can be engineered into the DNA of an enterprise from the very beginning. But what about the company that is not born with great DNA? How can good companies, mediocre companies, even bad companies achieve enduring greatness? The StudyFor years, this question preyed on the mind of Jim Collins. Are there companies that defy gravity and convert long-term mediocrity or worse into long-term superiority? And if so, what are the universal distinguishing characteristics that cause a company to go from good to great?The StandardsUsing tough benchmarks, Collins and his research team identified a set of elite companies that made the leap to great results and sustained those results for at least fifteen years. How great? After the leap, the good-to-great companies generated cumulative stock returns that beat the general stock market by an average of seven times in fifteen years, better than twice the results delivered by a composite index of the world's greatest companies, including Coca-Cola, Intel, General Electric, and Merck. The ComparisonsThe research team contrasted the good-to-great companies with a carefully selected set of comparison companies that failed to make the leap from good to great. What was different? Why did one set of companies become truly great performers while the other set remained only good? The FindingsThe findings of the Good to Great study will surprise many readers and shed light on virtually every area of management strategy and practice. The findings include:Level 5 Leaders: The research team was shocked to discover the type of leadership required to achieve greatness.The Hedgehog Concept (Simplicity within the Three Circles): To go from good to great requires transcending the curse of competence.A Culture of Discipline: When you combine a culture of discipline with an ethic of entrepreneurship, you get the magical alchemy of great results. Technology Accelerators: Good-to-great companies think differently about the role of technology.The Flywheel and the Doom Loop: Those who launch radical change programs and wrenching restructurings will almost certainly fail to make the leap.

    It is based on the Toyota (lean) model, which combines operational excellence with value-based strategies to produce steady growth through a wide range of economic conditions. In contrast with the crash-and-burn performance of companies trumpeted by business gurus in the 1990s, the firms profiled in Lean Thinking -- from tiny Lantech to midsized Wiremold to niche producer Porsche to gigantic Pratt & Whitney -- have kept on keeping on, largely unnoticed, along a steady upward path through the market turbulence and crushed dreams of the early twenty-first century. Meanwhile, the leader in lean thinking -- Toyota -- has set its sights on leadership of the global motor vehicle industry in this decade. Instead of constantly reinventing business models, lean thinkers go back to basics by asking what the customer really perceives as value. (It's often not at all what existing organizations and assets would suggest.) The next step is to line up value-creating activities for a specific product along a value stream while eliminating activities (usually the majority) that don't add value. Then the lean thinker creates a flow condition in which the design and the product advance smoothly and rapidly at the pull of the customer (rather than the push of the producer). Finally, as flow and pull are implemented, the lean thinker speeds up the cycle of improvement in pursuit of perfection. The first part of this book describes each of these concepts and makes them come alive with striking examples. Lean Thinking clearly demonstrates that these simple ideas can breathe new life into any company in any industry in any country. But most managers need guidance on how to make the lean leap in their firm. Part II provides a step-by-step action plan, based on in-depth studies of more than fifty lean companies in a wide range of industries across the world. Even those readers who believe they have embraced lean thinking will discover in Part III that another dramatic leap is possible by creating an extended lean enterprise for each of their product families that tightly links value-creating activities from raw materials to customer. In Part IV, an epilogue to the original edition, the story of lean thinking is brought up-to-date with an enhanced action plan based on the experiences of a range of lean firms since the original publication of Lean Thinking. Lean Thinking does not provide a new management "program" for the one-minute manager. Instead, it offers a new method of thinking, of being, and, above all, of doing for the serious long-term manager -- a method that is changing the world.

    He explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. He shows why these queues form and how they undermine the speed, quality, and efficiency in product development.

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    If you are seriously interested in understanding how you and your team can start down the path of improvement with XP, you must read this book."-- Francesco Cirillo, Chief Executive Officer, XPLabs S.R.L. "The first edition of this book told us what XP was--it changed the way many of us think about software development. This second edition takes it farther and gives us a lot more of the 'why' of XP, the motivations and the principles behind the practices. This is great stuff. Armed with the 'what' and the 'why, ' we can now all set out to confidently work on the 'how' how to run our projects better, and how to get agile techniques adopted in our organizations."-- Dave Thomas, The Pragmatic Programmers LLC "This book is dynamite! It was revolutionary when it first appeared a few years ago, and this new edition is equally profound. For those who insist on cookbook checklists, there's an excellent chapter on 'primary practices, ' but I urge you to begin by truly contemplating the meaning of the opening sentence in the first chapter of Kent Beck's book: 'XP is about social change.' You should do whatever it takes to ensure that every IT professional and every IT manager--all the way up to the CIO--has a copy of Extreme Programming Explained on his or her desk."-- Ed Yourdon, author and consultant "XP is a powerful set of concepts for simplifying the process of software design, development, and testing. It is about minimalism and incrementalism, which are especially useful principles when tackling complex problems that require a balance of creativity and discipline."-- Michael A. Cusumano, Professor, MIT Sloan School of Management, and author of The Business of Software " Extreme Programming Explained is the work of a talented and passionate craftsman. Kent Beck has brought together a compelling collection of ideas about programming and management that deserves your full attention. My only beef is that our profession has gotten to a point where such common-sense ideas are labeled 'extreme.'..."-- Lou Mazzucchelli, Fellow, Cutter Business Technology Council "If your organization is ready for a change in the way it develops software, there's the slow incremental approach, fixing things one by one, or the fast track, jumping feet first into Extreme Programming. Do not be frightened by the name, it is not that extreme at all. It is mostly good old recipes and common sense, nicely integrated together, getting rid of all the fat that has accumulated over the years."-- Philippe Kruchten, UBC, Vancouver, British Columbia "Sometimes revolutionaries get left behind as the movement they started takes on a life of its own. In this book, Kent Beck shows that he remains ahead of the curve, leading XP to its next level. Incorporating five years of feedback, this book takes a fresh look at what it takes to develop better software in less time and for less money. There are no silver bullets here, just a set of practical principles that, when used wisely, can lead to dramatic improvements in software development productivity."-- Mary Poppendieck, author of Lean Software Development: An Agile Toolkit "Kent Beck has revised his classic book based on five more years of applying and teaching XP. He shows how the path to XP is both

    But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.

    These people are celebrities now. What was it like when they were just a couple friends with an idea? Founders like Steve Wozniak (Apple), Caterina Fake (Flickr), Mitch Kapor (Lotus), Max Levchin (PayPal), and Sabeer Bhatia (Hotmail) tell you in their own words about their surprising and often very funny discoveries as they learned how to build a company.Where did they get the ideas that made them rich? How did they convince investors to back them? What went wrong, and how did they recover?Nearly all technical people have thought of one day starting or working for a startup. For them, this book is the closest you can come to being a fly on the wall at a successful startup, to learn how it's done.But ultimately these interviews are required reading for anyone who wants to understand business, because startups are business reduced to its essence. The reason their founders become rich is that startups do what businesses do--create value--more intensively than almost any other part of the economy. How? What are the secrets that make successful startups so insanely productive? Read this book, and let the founders themselves tell you.

     Drawing on years of experience training more than 10,000 busy managers from around the globe in practical, everyday coaching skills, Bungay Stanier reveals how to unlock your peoples' potential. He unpacks seven essential coaching questions to demonstrate how--by saying less and asking more--you can develop coaching methods that produce great results. – Get straight to the point in any conversation with The Kickstart Question – Stay on track during any interaction with The Awe Question – Save hours of time for yourself with The Lazy Question – and hours of time for others with The Strategic Question – Get to the heart of any interpersonal or external challenge with The Focus Question – and The Foundation Question – Ensure others find your coaching as beneficial as you do with The Learning Question A fresh innovative take on the traditional how-to manual, the book combines insider information with research based in neuroscience and behavioural economics, together with interactive training tools to turn practical advice into practiced habits. Witty and conversational, The Coaching Habit takes your work--and your workplace--from good to great. "Coaching is an art and it's far easier said than done. It takes courage to ask a question rather than offer up advice, provide and answer, or unleash a solution. giving another person the opportunity to find their own way, make their own mistakes, and create their own wisdom is both brave and vulnerable. In this practical and inspiring book, Michael shares seven transformative questions that can make a difference in how we lead and support. And he guides us through the tricky part - how to take this new information and turn it into habits and a daily practice. --Brené Brown, author of Rising Strong and Daring Greatly

    The consensus is clear: MBA programs are a waste of time and money. Even the elite schools offer outdated assembly-line educations about profit-and-loss statements and PowerPoint presentations. After two years poring over sanitized case studies, students are shuffled off into middle management to find out how business really works.Josh Kaufman has made a business out of distilling the core principles of business and delivering them quickly and concisely to people at all stages of their careers. His blog has introduced hundreds of thousands of readers to the best business books and most powerful business concepts of all time. In The Personal MBA, he shares the essentials of sales, marketing, negotiation, strategy, and much more.True leaders aren't made by business schools-they make themselves, seeking out the knowledge, skills, and experiences they need to succeed. Read this book and in one week you will learn the principles it takes most people a lifetime to master.

    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.

    As the words "at work" suggest, Peter Seibel focuses on how his interviewees tackle the day–to–day work of programming, while revealing much more, like how they became great programmers, how they recognize programming talent in others, and what kinds of problems they find most interesting. Hundreds of people have suggested names of programmers to interview on the Coders at Work web site: http://www.codersatwork.com. The complete list was 284 names. Having digested everyone’s feedback, we selected 16 folks who’ve been kind enough to agree to be interviewed:- Frances Allen: Pioneer in optimizing compilers, first woman to win the Turing Award (2006) and first female IBM fellow- Joe Armstrong: Inventor of Erlang- Joshua Bloch: Author of the Java collections framework, now at Google- Bernie Cosell: One of the main software guys behind the original ARPANET IMPs and a master debugger- Douglas Crockford: JSON founder, JavaScript architect at Yahoo!- L. Peter Deutsch: Author of Ghostscript, implementer of Smalltalk-80 at Xerox PARC and Lisp 1.5 on PDP-1- Brendan Eich: Inventor of JavaScript, CTO of the Mozilla Corporation - Brad Fitzpatrick: Writer of LiveJournal, OpenID, memcached, and Perlbal - Dan Ingalls: Smalltalk implementor and designer- Simon Peyton Jones: Coinventor of Haskell and lead designer of Glasgow Haskell Compiler- Donald Knuth: Author of The Art of Computer Programming and creator of TeX- Peter Norvig: Director of Research at Google and author of the standard text on AI- Guy Steele: Coinventor of Scheme and part of the Common Lisp Gang of Five, currently working on Fortress- Ken Thompson: Inventor of UNIX- Jamie Zawinski: Author of XEmacs and early Netscape/Mozilla hackerWhat you’ll learn:How the best programmers in the world do their jobWho is this book for?Programmers interested in the point of view of leaders in the field. Programmers looking for approaches that work for some of these outstanding programmers.

    Christensen says outstanding companies can do everything right and still lose their market leadership -- or worse, disappear completely. And he not only proves what he says, he tells others how to avoid a similar fate.Focusing on "disruptive technology" -- the Honda Super Cub, Intel's 8088 processor, or the hydraulic excavator, for example -- Christensen shows why most companies miss "the next great wave." Whether in electronics or retailing, a successful company with established products will get pushed aside unless managers know when to abandon traditional business practices. Using the lessons of successes and failures from leading companies, "The Innovator's Dilemma" presents a set of rules for capitalizing on the phenomenon of disruptive innovation.

    But when he took the helm in 2004, America was losing that war badly: despite vastly inferior resources and technology, Al Qaeda was outmaneuvering America’s most elite warriors. McChrystal came to realize that today’s faster, more interdependent world had overwhelmed the conventional, top-down hierarchy of the US military. Al Qaeda had seen the future: a decentralized network that could move quickly and strike ruthlessly. To defeat such an enemy, JSOC would have to discard a century of management wisdom, and pivot from a pursuit of mechanical efficiency to organic adaptability. Under McChrystal’s leadership, JSOC remade itself, in the midst of a grueling war, into something entirely new: a network that combined robust centralized communication with decentralized managerial authority. As a result, they beat back Al Qaeda. In this book, McChrystal shows not only how the military made that transition, but also how similar shifts are possible in all organizations, from large companies to startups to charities to governments. In a turbulent world, the best organizations think and act like a team of teams, embracing small groups that combine the freedom to experiment with a relentless drive to share what they’ve learned. Drawing on a wealth of evidence from his military career, the private sector, and sources as diverse as hospital emergency rooms and NASA’s space program, McChrystal frames the existential challenge facing today’s organizations, and presents a compelling, effective solution.

    Companies that live and die by outputs often fall into the "build trap," cranking out features to meet their schedule rather than the customer’s needs. In this book, Melissa Perri explains how laying the foundation for great product management can help companies solve real customer problems while achieving business goals. By understanding how to communicate and collaborate within a company structure, you can create a product culture that benefits both the business and the customer. You’ll learn product management principles that can be applied to any organization, big or small. In five parts, this book explores: Why organizations ship features rather than cultivate the value those features represent How to set up a product organization that scales How product strategy connects a company’s vision and economic outcomes back to the product activities How to identify and pursue the right opportunities for producing value through an iterative product framework How to build a culture focused on successful outcomes over outputs

    Crossing the Chasm has become the bible for bringing cutting-edge products to progressively larger markets. This edition provides new insights into the realities of high-tech marketing, with special emphasis on the Internet. It's essential reading for anyone with a stake in the world's most exciting marketplace.