Empfehlungen basierend auf "Collaboration Explained Facilitation Skills for Software Project Leaders"

The foremost authority on innovation and growth presents a path-breaking book every company needs to transform innovation from a game of chance to one in which they develop products and services customers not only want to buy, but are willing to pay premium prices for. How do companies know how to grow? How can they create products that they are sure customers want to buy? Can innovation be more than a game of hit and miss? Harvard Business School professor Clayton Christensen has the answer. A generation ago, Christensen revolutionized business with his groundbreaking theory of disruptive innovation. Now, he goes further, offering powerful new insights. After years of research, Christensen has come to one critical conclusion: our long held maxim—that understanding the customer is the crux of innovation—is wrong. Customers don’t buy products or services; they "hire" them to do a job. Understanding customers does not drive innovation success, he argues. Understanding customer jobs does. The "Jobs to Be Done" approach can be seen in some of the world’s most respected companies and fast-growing startups, including Amazon, Intuit, Uber, Airbnb, and Chobani yogurt, to name just a few. But this book is not about celebrating these successes—it’s about predicting new ones. Christensen contends that by understanding what causes customers to "hire" a product or service, any business can improve its innovation track record, creating products that customers not only want to hire, but that they’ll pay premium prices to bring into their lives. Jobs theory offers new hope for growth to companies frustrated by their hit and miss efforts. This book carefully lays down Christensen’s provocative framework, providing a comprehensive explanation of the theory and why it is predictive, how to use it in the real world—and, most importantly, how not to squander the insights it provides.

This book explains the keys to successful investment and the pitfalls that can destroy capital or ruin a career. Utilizing passages from his memos to illustrate his ideas, Marks teaches by example, detailing the development of an investment philosophy that fully acknowledges the complexities of investing and the perils of the financial world. Brilliantly applying insight to today's volatile markets, Marks offers a volume that is part memoir, part creed, with a number of broad takeaways.

“Absolutely brilliant. Clayton Christensen provides an insightful analysis of changing technology and its importance to a company’s future success.”—Michael R. Bloomberg“This book ought to chill any executive who feels bulletproof —and inspire entrepreneurs aiming their guns.”—ForbesThe Innovator’s Dilemma is the revolutionary business book that has forever changed corporate America. Based on a truly radical idea—that great companies can fail precisely because they do everything right—this Wall Street Journal, Business Week and New York Times Business bestseller is one of the most provocative and important business books ever written. Entrepreneurs, managers, and CEOs ignore its wisdom and its warnings at their great peril.

Don't Take On A Problem If It Isn't Yours! This book, one of the most liberating in the extraordinary One Minute Manager library, teachers an unforgettable lesson; how to save time to do what you want and need to do. Step by Step, the authors show how mangers can free themselves from doing everyone else's job and ensure that every problem is handled by the proper person. By using the Four Rules of Monkey Management, Managers will learn to become effective supervisors of time, energy and talent-especially their own.

Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it. What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

Here is the bestselling guide that created a new game plan for marketing in high-tech industries. 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.

The definitive playbook by the pioneers of Growth Hacking, one of the hottest business methodologies in Silicon Valley and beyond. It seems hard to believe today, but there was a time when Airbnb was the best-kept secret of travel hackers and couch surfers, Pinterest was a niche web site frequented only by bakers and crafters, LinkedIn was an exclusive network for C-suite executives and top-level recruiters, Facebook was MySpace’s sorry step-brother, and Uber was a scrappy upstart that didn’t stand a chance against the Goliath that was  New York City Yellow Cabs.  So how did these companies grow from these humble beginnings into the powerhouses they are today? Contrary to popular belief, they didn’t explode to massive worldwide popularity simply by building  a great product then crossing their fingers and hoping it would catch on. There was a studied, carefully implemented methodology behind these companies’ extraordinary rise. That methodology is called Growth Hacking, and it’s practitioners include not just today’s hottest start-ups, but also companies like IBM, Walmart, and Microsoft as well as the millions of entrepreneurs, marketers, managers and executives who make up the community of Growth Hackers. Think of the Growth Hacking methodology as doing for market-share growth what Lean Start-Up did for product development, and Scrum did for productivity. It involves cross-functional teams and rapid-tempo testing and iteration that focuses customers: attaining them, retaining them, engaging them, and motivating them to come back and buy more.    An accessible and practical toolkit that teams and companies in all industries can use to increase their customer base and market share, this book walks readers through the process of creating and executing their own custom-made growth hacking strategy. It is a must read for any marketer, entrepreneur, innovator or manger looking to replace wasteful big bets and "spaghetti-on-the-wall" approaches with more consistent, replicable, cost-effective, and data-driven results.

Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control. Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned. Fundamentals of XP include: Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system--several times a day. Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable. Why is XP so controversial? Some sacred cows don't make the cut in XP: Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XPprogrammers continue to make analysis and design decisions throughout development. Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code. You may love XP, or you may hate it, but "Extreme Programming Explained" will force you to take a fresh look at how you develop software. 0201616416B04062001

A captivating blend of cutting-edge scientific evidence and real-world stories providing leaders and managers with proven and practical strategies and tools for navigating today's emotionally taxing workplace.Broad changes have dramatically disrupted our workplaces and increased the emotional demands on leaders everywhere. Leaders now must support their teams' mental health and burnout (while managing their own), build trust with and motivate a remote and diverse workforce, allay employee fears of obsolescence while driving the integration of new technologies like AI, and demonstrate bottomless sensitivity and compassion while still delivering results at a relentless pace. No wonder leaders are burning out. Emotional labor is a daily unrecognized burden leaders carry and can have significant costs for their health and performance over time.However, achieving high performance and fulfillment without compromising your well-being is possible, and Emotionally Charged shows you how. Dina Denham Smith and Alicia A. Grandey debunk myths and equip you to handle emotionally loaded work events, from preparing for high-stakes scenarios to managing curveballs and conflicts, supporting distressed employees, and recovering effectively after being drained at work.Blending real-world cases from leaders and evidence-based insights, Emotionally Charged will help all leaders--from front-line managers to C-Suite execs--manage the new work landscape. Anchored in the science of emotions, Emotionally Charged will equip you with practical strategies and tools to lead successfully and thrive in the new age of work.

Use cases have become a very popular requirements-gathering technique, yet many developers struggle when faced with writing them. They grasp the basic concepts, but find that writing effective use cases turns out to be more difficult than they expected. One factor contributing to this difficulty is that the community lacks objective criteria for judging the quality of use cases. This new book articulates the qualities of effective use cases by applying the proven patterns concept of development to this requirements-gathering technique. The authors present a catalog of thirty-six patterns that help the reader become proficient at judging the quality of their (and other's) patterns. These patterns represent solutions to recurring problems that application developers have faced in writing use cases. Each pattern is presented with examples that help the reader understand the benefit of the pattern, and just as importantly, the consequences of ignoring its proper use.