A #1 Wall Street Journal bestseller with more than 500,000 copies sold, The Four Disciplines of Execution will radically change your business.Do you remember the last major initiative you watched die in your organization? Did it go down with a loud crash? Or was it slowly and quietly suffocated by other competing priorities? By the time it finally disappeared, it’s likely no one even noticed. What happened? Often, the answer is that the “whirlwind” of urgent activity required to keep things running day-to-day devoured all the time and energy you needed to invest in executing your strategy for tomorrow. The 4 Disciplines of Execution can change that forever. The 4 Disciplines of Execution (4DX) is a simple, repeatable, and proven formula for executing your most important strategic priorities in the midst of the whirlwind. By following the 4 Disciplines—Focus on the Wildly Important; Act on Lead Measures; Keep a Compelling Scoreboard; Create a Cadence of Accountability—leaders can produce breakthrough results, even when executing the strategy requires a significant change in behavior from their teams. 4DX is not theory. It is a proven set of practices that have been tested and refined by hundreds of organizations and thousands of teams over many years. When a company or an individual adheres to these disciplines, they achieve superb results, regardless of the goal. 4DX represents a new way to think and work that is essential to thriving in today’s competitive climate. The 4 Disciplines of Execution is one book that no business leader can afford to miss.

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    On the one hand, there are the more agile methods that focus on individual projects, and how to get them done fast--the camp represented by Beck and Cockburn. On the other hand, there are the more disciplined methods, focused on setting up organizational processes for getting projects done with predictable high quality--the camp best represented by the SEI, the CMMI, and Humphrey. Although these methods are often presented as mutually exclusive, they actually lie on a continuum. The authors of Balancing Agility and Discipline have worked out clear guidelines for determining where on that continuum a particular software development project is located--and therefore, how agile or disciplined a chosen methodology can or has to be.

    Readers new to Kanban will understand why and how it works, while those with experience will appreciate its fresh perspective and the connections it makes with a range of related models.

    This complexity and the emergence of networks is changing the practice of strategic management. Today's leaders need to understand how to design and guide complex collaborations to accelerate innovation and change--collaborations that cross boundaries both inside and outside organizations.Strategic Doing introduces you to the new disciplines of agile strategy and collaborative leadership. You'll learn how to design and guide complex collaborations by following a discipline of simple rules that you won't find anywhere else.- Unleash the power of true collaboration- Learn and master the 10 skills of agile leadership- Apply individual skills to targeted situations- Introduces a new discipline of leadership strategyFilled with compelling case studies, Strategic Doing outlines a new discipline of leadership strategy specifically designed for open, loosely-connected networks.

    

    If we can understand what makes these gatherings effective and memorable, then we can reframe and redirect them to benefit everyone, host and guest alike. Parker defines a gathering as three or more people who come together for a specific purpose. When we understand why we gather, she says -- to acknowledge, to learn, to challenge, to change -- we learn how to organize gatherings that are relevant and memorable: from an effective business meeting to a thought-provoking conference; from a joyful wedding to a unifying family dinner. Drawing on her experience as a strategic facilitator who's worked with such organizations as the World Economic Forum, the Museum of Modern Art, and the retail company Fresh, Parker explains how ordinary people can create remarkable occasions, large and small. In dozens of fascinating examples, she breaks down the alchemy of these experiences to show what goes into the good ones and demonstrates how we can learn to incorporate those elements into all of our gatherings. The result is a book that's both journey and guide, full of big ideas with real-world applications that will change the way you look at a business meeting, a parent-teacher conference, and a backyard barbecue.

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    Meetings are a crucial part of all our lives, but too often they go nowhere and waste valuable time. In Six Thinking Hats, Edward de Bono shows how meetings can be transformed to produce quick, decisive results every time. The Six Hats method is a devastatingly simple technique based on the brain's different modes of thinking. The intelligence, experience and information of everyone is harnessed to reach the right conclusions quickly. These principles fundamentally change the way you work and interact. They have been adopted by businesses and governments around the world to end conflict and confusion in favour of harmony and productivity. 'An inspiring man with brilliant ideas. De Bono never ceases to amaze with his clarity of thought' Richard Branson.Edward de Bono invented the concept of lateral thinking. A world-renowned writer and philosopher, he is the leading authority in the field of creative thinking and the direct teaching of thinking as a skill. Dr de Bono has written more than 60 books, in 40 languages, with people now teaching his methods worldwide. He has chaired a special summit of Nobel Prize laureates, and been hailed as one of the 250 people who have contributed most to mankind

    With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners.Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time.You'll learn:Fundamental differences between software engineering and programmingHow an organization effectively manages a living codebase and efficiently responds to inevitable changeWhy culture (and recognizing it) is important, and how processes, practices, and tools come into play

    We put out fires. We deal with emergencies. We stay downstream, handling one problem after another, but we never make our way upstream to fix the systems that caused the problems ... [This book] probes the psychological forces that push us downstream--including 'problem blindness,' which can leave us oblivious to serious problems in our midst. And Heath introduces us to the thinkers who have overcome these obstacles and scored ... victories by switching to an upstream mindset.

    Management is a key part of any organization, yet the discipline is often self-taught and unstructured. Getting to the good solutions of complex management challenges can make the difference between fulfillment and frustration for teams, and, ultimately, the success or failure of companies. Will Larson's An Elegant Puzzle orients around the particular challenges of engineering management--from sizing teams to technical debt to succession planning--and provides a path to the good solutions. Drawing from his experience at Digg, Uber, and Stripe, Will Larson has developed a thoughtful approach to engineering management that leaders of all levels at companies of all sizes can apply. An Elegant Puzzle balances structured principles and human-centric thinking to help any leader create more effective and rewarding organizations for engineers to thrive in.

    Aging computer systems present complex technical challenges for organizations both large and small, and Kill It with Fire provides sound strategies for spearheading modernization efforts.Kill It with Fire examines aging computer systems, the evolution of technology over time, and how organizations can modernize, maintain, and future-proof their current systems.In playful and engaging prose, Marianne Bellotti uses real-world case studies to illustrate the technical challenges of modernizing complex legacy systems, as well as the organizational challenges of time-intensive maintenance efforts. The book explains how to evaluate existing architecture, create upgrade plans, and handle communication structures. Team exercises and historical analyses of complex computer systems make this a valuable resource for those in both older and newer companies, and will help readers restore or create systems built to evolve as time goes on.

    For the first time, William Poundstone reveals the toughest questions used at Microsoft and other Fortune 500 companies -- and supplies the answers. He traces the rise and controversial fall of employer-mandated IQ tests, the peculiar obsessions of Bill Gates (who plays jigsaw puzzles as a competitive sport), the sadistic mind games of Wall Street (which reportedly led one job seeker to smash a forty-third-story window), and the bizarre excesses of today's hiring managers (who may start off your interview with a box of Legos or a game of virtual Russian roulette). How Would You Move Mount Fuji? is an indispensable book for anyone in business. Managers seeking the most talented employees will learn to incorporate puzzle interviews in their search for the top candidates. Job seekers will discover how to tackle even the most brain-busting questions, and gain the advantage that could win the job of a lifetime. And anyone who has ever dreamed of going up against the best minds in business may discover that these puzzles are simply a lot of fun. Why are beer cans tapered on the end, anyway?

    Their lives, like all of ours, are filled with a bewildering blizzard of emails, phone calls, yet more emails, meetings, projects, proposals, and plans. Just staying ahead of the storm has become a seemingly insurmountable task.In this book, we travel inside Emily and Paul's brains as they attempt to sort the vast quantities of information they're presented with, figure out how to prioritize it, organize it and act on it. Fortunately for Emily and Paul, they're in good hands: David Rock knows how the brain works-and more specifically, how it works in a work setting. Rock shows how it's possible for Emily and Paul, and thus the reader, not only to survive in today's overwhelming work environment but succeed in it-and still feel energized and accomplished at the end of the day.YOUR BRAIN AT WORK explores issues such as:- why our brains feel so taxed, and how to maximize our mental resources- why it's so hard to focus, and how to better manage distractions- how to maximize your chance of finding insights that can solve seemingly insurmountable problems- how to keep your cool in any situation, so that you can make the best decisions possible- how to collaborate more effectively with others- why providing feedback is so difficult, and how to make it easier- how to be more effective at changing other people's behavior