It's the art of anticipating your opponent's next moves, knowing full well that your rival is trying to do the same thing to you. Though parts of game theory involve simple common sense, much is counterintuitive, and it can only be mastered by developing a new way of seeing the world. Using a diverse array of rich case studies—from pop culture, TV, movies, sports, politics, and history—the authors show how nearly every business and personal interaction has a game-theory component to it. Are the winners of reality-TV contests instinctive game theorists? Do big-time investors see things that most people miss? What do great poker players know that you don't? Mastering game theory will make you more successful in business and life, and this lively book is the key to that mastery.

    In this volume, master coach trainer Tony Stoltzfus joins with 12 other professional coaches to present dozens of valuable asking tools, models and exercises, then illustrates these coaching strategies with over 1,000 examples of penetrating questions. Covering the gamut from basic techniques like options and actions to advanced concepts such as challenge and reframing, Coaching Questions is a book that will find a home on any coach's short list of handy references. Coaching Questions: A Coach's Guide to Powerful Asking Skills includes: 1. Dozens of asking tools, models, and strategies. 2. The top ten asking mistakes coaches make, and how to correct each one. 3. Nearly 1200 examples of powerful questions from real coaching situations. 4. Destiny discovery tools organized in a four-part life-purpose model . 5. Overviews of 15 popular coaching niches, with a tool and examples for each. 6. A schedule of training exercises to help you become a "Master of Asking".

    With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 45 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."

    When restructures, mergers, bankruptcies, and layoffs hit the workplace, employees and managers naturally find the resulting situational shifts to be challenging. But the psychological transitions that accompany them are even more stressful. Organizational transitions affect people; it is always people, rather than a company, who have to embrace a new situation and carry out the corresponding change. As veteran business consultant William Bridges explains, transition is successful when employees have a purpose, a plan, and a part to play. This indispensable guide is now updated to reflect the challenges of today's ever-changing, always-on, and globally connected workplaces. Directed at managers on all rungs of the corporate ladder, this expanded edition of the classic bestseller provides practical, step-by-step strategies for minimizing disruptions and navigating uncertain times.

    It describes the roles, teams, values, intentions, habits, activities, policies and work products of a small software development team forwhom time-to-market and development costs are critical considerations.Alistair Cockburn is one of the founders of the Agile software developmentmovement. He spells out proven best practices based on his extensiveexperience helping organizations build software quickly and with less cost. Theauthor understands that small teams cannot be burdened by process-heavysoftware methodologies. By advocating that developers stay close together andremain in steady, good-will communication with customers and users, thisbook teaches the reader how to develop software that not only does what it issupposed to do, but also gets completed on time and within budget.

    The book emphasizes that we all contain the ingredients for leadership, though some elements are better developed than others. "Anyone can improve as a leader simply by building the strength of our weakest elements, " author Gerald M. Weinberg writes. "Mr. Universe doesn't have more muscles than I do, just better developed ones."On one level, the book is an extremely down-to-earth, how-to guide. On a second, it is a set of parables, full of analogies that stick in the mind -- the art of management taught through stories about pinball, tinkertoys, and electric blankets. On yet another level, this is a book about the philosophy and psychology of managing technical projects. On every level, the author brings these entertaining and enlightening elements together to teach you the essentials of leadership.You'll learn how to-- master your fear of becoming a leader-- be creative in solving problems-- motivate people while maintaining quality-- gain organizational power-- plan personal change.-- Whether you manage people, are managed by people, or just want to change the way you interact with others, this book is about success. How to plan it, how to make it happen -- Becoming a Technical Leader shows you how to do it!

    Despite the importance of the job, there is currently no book specifically designed as a comprehensive reference manual for the working BA. The Business Analyst's Handbook solves this problem by providing a useful compendium of tools, tables, lists, and templates that BAs can use on-the-job to carry out their tasks. For example, you might be preparing for an interview session and use the book's checklist of interviewees to verify whether there is appropriate coverage of business stakeholders. Or you might be asked to review some diagrams and refer to the Glossaries of Symbols (organized by diagram type) for guidance. Or you may be asked to prepare textual requirements documentation and refer to the Business Requirement template for a list of artifacts and table of contents. Whatever your BA needs, the Business Analyst's Handbook places the necessary information right at your fingertips.

    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.

    Using information gathered from interviews with over 100 social sector leaders, Jim Collins shows that his "Level 5 Leader" and other good-to-great principles can help social sector organizations make the leap to greatness.

    His groundbreaking revelations shed light not just on business but on the way every human being acts and lives around the world. Rapaille’s breakthrough notion is that we acquire a silent system of Codes as we grow up within our culture. These Codes—the Culture Code—are what make us American, or German, or French, and they invisibly shape how we behave in our personal lives, even when we are completely unaware of our motives. What’s more, we can learn to crack the Codes that guide our actions and achieve new understanding of why we do the things we do. Rapaille has used the Culture Code to help Chrysler build the PT Cruiser—the most successful American car launch in recent memory. He has used it to help Procter & Gamble design its advertising campaign for Folger’s coffee – one of the longest-lasting and most successful campaigns in the annals of advertising. He has used it to help companies as diverse as GE, AT&T, Boeing, Honda, Kellogg, and L’Oréal improve their bottom line at home and overseas. And now, in The Culture Code, he uses it to reveal why Americans act distinctly like Americans, and what makes us different from the world around us. In The Culture Code, Dr. Rapaille decodes two dozen of our most fundamental archetypes—ranging from sex to money to health to America itself—to give us “a new set of glasses” with which to view our actions and motivations. Why are we so often disillusioned by love? Why is fat a solution rather than a problem? Why do we reject the notion of perfection? Why is fast food in our lives to stay? The answers are in the Codes. Understanding the Codes gives us unprecedented freedom over our lives. It lets us do business in dramatically new ways. And it finally explains why people around the world really are different, and reveals the hidden clues to understanding us all.

    But his team members—and Mother Nature—had other plans. An ambitious yet naïve sheepdog is called upon to lead Monarch Enterprises, a troubled organization on a beautiful isle. Confronted with broken systems and challenging personality types, Sam must learn how to marshal his team before the imminent storm washes everything away. Along the way, he gleans valuable lessons from an unlikely mentor: a wise, old puffin.This delightful, quick read will:Teach you communication techniques that enhance teamwork and productivityBring to life the principles used by hundreds of successful organizationsProvide relevant, practical insights based on real-world experiencesStimulate lively and positive interaction (discussion guide included)Based on the principles successfully used by major corporations, health organizations, over 250 colleges and universities, government agencies, churches, and non-profits

    While some fear is healthy (often viewed as a conscience that tells programmers to be careful!), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.

    Providing strategies and solutions for the managers of today, this book offers answers for improving employee commitment and profitability by strategically acknowledging employee effort. How is it done? The deceptively simply answer: with carrots.

    Aimed at undergraduate/MBA-level courses in business ethics in the departments of philosophy or business, this comprehensive text provides a balanced and up-to-date treatment of some of the most prominent issues of business ethics.

    So much so, in fact, that the 12-month design cycles cited in the last edition have shrunk to 6 or even 3 months today. Which is why, more than ever, you need a smart, practical guide that demonstrates how to plan, budget, organize, and manage your Web redesign - or even you initial design - projects from conceptualization to launch. This volume delivers! In these pages Web designer extraordinaire Kelly Goto and coauthor Emily Cotler have distilled their real-world experience into a sound approach to Web redesign workflow that is as much about business priorities as it is about good design. By focusing on where these priorities intersect, Kelly and Emily get straight to the heart of the matter. Each chapter includes a case study that illustrates a key step in the process, and you'll find a plethora of forms, checklists, and worksheets that help you put knowledge into action.This is an AIGA Design Press book published under Peachpit's New Riders imprint in partnership with AIGA.