Do you feel like you could be getting more out of your retrospectives and fuelling continuous improvement in your teams? You may already find retrospectives valuable, but suspect there are ways of making them better.This book condenses down eight years of experience working with the retrospective practice within the context of real agile teams. It offers you practice advice on how to make your retrospectives even more effective including topics such as: Best methods to prepare for a retrospective Picking just the right materials Facilitating retrospectives with ease Dealing with common retrospective smells Retrospectives in different contexts including distributed, large and small groups A checklist for preparation Ensuring retrospectives result in change

    But being a great ScrumMaster, one who truly embodies the principles of servant-leadership and helps move a team to the high performance levels possible with Scrum, is much harder and much more elusive. In his over ten years of coaching numerous Scrum teams, the highly-respected and experienced Scrum coach Geoff Watts has identified patterns that separate a good ScrumMaster from a great one. In this book, he not only illustrates these patterns through stories of his own experiences and those of the many Scrum teams he has encountered but offers practical guidance for you on your own path to greatness.In this book you will learn:The skills and characteristics of great ScrumMastersHow to generate, maintain and increase engagement from the teamHow to increase the effectiveness of the Scrum meetings, such as retrospectives and daily scrums.How to foster a more creative and collaborative teamHow to increase the performance of the teamHow to know when you are a successful ScrumMaster\Scrum Mastery is for practicing ScrumMasters who want to develop themselves into a great servant-leader capable of taking their teams beyond simple process compliance.Comments on the bookMike Cohn, in his foreword for the book, said:"Most books rehash well-trod territory and I don’t finish them any wiser. I am positive I will be referring back to this book for many years" Roman Pichler, author of Agile Product Management with Scrum: Creating Products That Customers Love said:"I am thoroughly impressed with how comprehensive and well-written the book is. It will be indispensable for many people"Jean Tabaka, Agile Fellow, Rally Software:"Geoff brings us a personal and inspired peak into what truly moves us from good to great: great in how we serve; great in how we lead; great in how we create mastery in our teams and organizations; and, great in how we recognize the impediments to our own growth to greatness. Scrum mastery is a skill that can be honed and Geoff gives us rich tools to sharpen our craft."

    Richard Rumelt shows that there has been a growing and unfortunate tendency to equate Mom-and-apple-pie values, fluffy packages of buzzwords, motivational slogans, and financial goals with “strategy.” He debunks these elements of “bad strategy” and awakens an understanding of the power of a “good strategy.” A good strategy is a specific and coherent response to—and approach for overcoming—the obstacles to progress. A good strategy works by harnessing and applying power where it will have the greatest effect in challenges as varied as putting a man on the moon, fighting a war, launching a new product, responding to changing market dynamics, starting a charter school, or setting up a government program. Rumelt’snine sources of power—ranging from using leverage to effectively focusing on growth—are eye-opening yet pragmatic tools that can be put to work on Monday morning.Surprisingly, a good strategy is often unexpected because most organizations don’t have one. Instead, they have “visions,” mistake financial goals for strategy,and pursue a “dog’s dinner” of conflicting policies and actions.Rumelt argues that the heart of a good strategy is insight—into the true nature of the situation, into the hidden power in a situation, and into an appropriate response. He shows you how insight can be cultivated with a wide variety of tools for guiding yourown thinking.Good Strategy/Bad Strategy uses fascinating examples from business, nonprofit, and military affairs to bring its original and pragmatic ideas to life. The detailed examples range from Apple to General Motors, from the two Iraq wars to Afghanistan, from a small local market to Wal-Mart, from Nvidia to Silicon Graphics, from the Getty Trust to the Los Angeles Unified School District, from Cisco Systems to Paccar, and from Global Crossing to the 2007–08 financial crisis.Reflecting an astonishing grasp and integration of economics, finance, technology, history, and the brilliance and foibles of the human character, Good Strategy/Bad Strategy stems from Rumelt’s decades of digging beyond the superficial to address hard questions with honesty and integrity.From the Hardcover edition.

    You'll be taught each and every step of the influence process-including robust strategies for making change inevitable in your personal life, your business, and your world. You'll learn how to:- Identify a handful of high-leverage behaviors that lead to rapid and profound change.- Apply strategies for changing both thoughts and actions.- Marshall six sources of influence to make change inevitable.Influencer takes you on a fascinating journey from San Francisco to Thailand where you'll see how seemingly “insignificant” people are making incredibly significant improvements in solving problems others would think impossible. You'll learn how savvy folks make change not only achievable and sustainable, but inevitable. You'll discover why some managers have increased productivity repeatedly and significantly-while others have failed miserably.

    You open the box and right on top is a quick-start guide. Being a novice, you follow the guide, and quickly get up and running. As you become more experienced, the other box contents address common advanced issues you'd face, like right-sizing teams, estimation, hitting deadlines, transitioning from Scrum or Waterfall, deploying components and services, and using Kanban within larger organizations.Real-world experience from a direct practitioner working on Xbox and Xbox.comA concise, pragmatic, and easy-to-read guide with clear, fresh, and hard-won guidanceUsing Kanban within larger organizations - how to deal with upper management, planning, and dependencies

    Topics covered range from the difference between deductive and inductive reasoning, to a discussion of how to highlight the structure of information.

    In a brilliant and unconventional book, Phil Rosenzweig unmasks the delusions that are commonly found in the corporate world. These delusions affect the business press and academic research, as well as many bestselling books that promise to reveal the secrets of success or the path to greatness. Such books claim to be based on rigorous thinking, but operate mainly at the level of storytelling. They provide comfort and inspiration, but deceive managers about the true nature of business success.The most pervasive delusion is the Halo Effect. When a company's sales and profits are up, people often conclude that it has a brilliant strategy, a visionary leader, capable employees, and a superb corporate culture. When performance falters, they conclude that the strategy was wrong, the leader became arrogant, the people were complacent, and the culture was stagnant. In fact, little may have changed -- company performance creates a Halo that shapes the way we perceive strategy, leadership, people, culture, and more.Drawing on examples from leading companies including Cisco Systems, IBM, Nokia, and ABB, Rosenzweig shows how the Halo Effect is widespread, undermining the usefulness of business bestsellers from "In Search of Excellence" to "Built to Last" and "Good to Great."Rosenzweig identifies nine popular business delusions. Among them:"The Delusion of Absolute Performance: " Company performance is relative to competition, not absolute, which is why following a formula can never guarantee results. Success comes from doing things better than rivals, which means that managers have to take risks."The Delusion of Rigorous Research: " Many bestselling authors praise themselves for the vast amount of data they have gathered, but forget that if the data aren't valid, it doesn't matter how much was gathered or how sophisticated the research methods appear to be. They trick the reader by substituting sizzle for substance."The Delusion of Single Explanations: " Many studies show that a particular factor, such as corporate culture or social responsibility or customer focus, leads to improved performance. But since many of these factors are highly correlated, the effect of each one is usually less than suggested.In what promises to be a landmark book, "The Halo Effect" replaces mistaken thinking with a sharper understanding of what drives business success and failure. "The Halo Effect" is a guide for the thinking manager, a way to detect errors in business research and to reach a clearer understanding of what drives business success and failure.Skeptical, brilliant, iconoclastic, and mercifully free of business jargon, Rosenzweig's book is nevertheless dead serious, making his arguments about important issues in an unsparing and direct way that will appeal to a broad business audience. For managers who want to separate fact from fiction in the world of business, "The Halo Effect" is essential reading -- witty, often funny, and sharply argued, it's an antidote to so much of the conventional thinking that clutters business bookshelves.

    His second book is the natural extension of Start with Why, expanding his ideas at the organizational level. Determining a company’s WHY is crucial, but only the beginning. The next step is how do you get people on board with your WHY? How do you inspire deep trust and commitment to the company and one another? He cites the Marine Corps for having found a way to build a culture in which men and women are willing to risk their lives, because they know others would do the same for them. It’s not brainwashing; it’s actually based on the biology of how and when people are naturally at their best. If businesses could adopt this supportive mentality, employees would be more motivated to take bigger risks, because they’d know their colleagues and company would back them up, no matter what. Drawing on powerful and inspiring stories, Sinek shows how to sustain an organization’s WHY while continually adding people to the mix.

    The rules? No marketing budget, no PR stunts, and it must be sustainably successful. No short-term fads.This is not a game of chance. It is a game of skill and strategy.And it begins with a single question: given competing products of equal pricing, promotion, and perceived quality, why does one outsell the others?The answer doesn’t live in the sustainably successful products or services. The answer lives in those who use them.Our goal is to craft a strategy for creating successful users. And that strategy is full of surprising, counter-intuitive, and astonishingly simple techniques that don’t depend on a massive marketing or development budget. Techniques typically overlooked by even the most well-funded, well-staffed product teams.Every role is a key player in this game. Product development, engineering, marketing, user experience, support—everyone on the team. Even if that team is a start-up of one. Armed with a surprisingly overlooked science and a unique POV, we can can reduce the role of luck. We can build sustainably successful products and services that rely not on unethical persuasive marketing tricks but on helping our users have deeper, richer experiences. Not just in the moments while they’re using our product but, more importantly, in the moments when they aren’t.

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    It’s about how people, organizations and societies can and must hit refresh—transform—in their persistent quest for new energy, new ideas, relevance and renewal. At the core, it’s about us humans and our unique qualities, like empathy, which will become ever more valuable in a world where the torrent of technology will disrupt like never before. As much a humanist as a technologist, Nadella defines his mission and that of the company he leads as empowering every person and every organization on the planet to achieve more.

    But today, success is increasingly dependent on how we interact with others. It turns out that at work, most people operate as either takers, matchers, or givers. Whereas takers strive to get as much as possible from others and matchers aim to trade evenly, givers are the rare breed of people who contribute to others without expecting anything in return. Using his own pioneering research as Wharton's youngest tenured professor, Grant shows that these styles have a surprising impact on success. Although some givers get exploited and burn out, the rest achieve extraordinary results across a wide range of industries. Combining cutting-edge evidence with captivating stories, this landmark book shows how one of America's best networkers developed his connections, why the creative genius behind one of the most popular shows in television history toiled for years in anonymity, how a basketball executive responsible for multiple draft busts transformed his franchise into a winner, and how we could have anticipated Enron's demise four years before the company collapsed - without ever looking at a single number. Praised by bestselling authors such as Dan Pink, Tony Hsieh, Dan Ariely, Susan Cain, Dan Gilbert, Gretchen Rubin, Bob Sutton, David Allen, Robert Cialdini, and Seth Godin-as well as senior leaders from Google, McKinsey, Merck, Estee Lauder, Nike, and NASA - Give and Take highlights what effective networking, collaboration, influence, negotiation, and leadership skills have in common. This landmark book opens up an approach to success that has the power to transform not just individuals and groups, but entire organizations and communities.

    By outlining the process every organization must go through to achieve its goals, and by identifying where and how even top performers derail during the change process, Kotter provides a practical resource for leaders and managers charged with making change initiatives work.Needed more today than at any time in the past, this immensely relevant bestselling business book serves as both visionary guide and practical toolkit on how to approach the difficult yet crucial work of leading change in any type of organization. Reading this highly personal book is like spending a day with the world’s foremost expert on business leadership. You’re sure to walk away inspired—and armed with the tools you need to inspire others. Published by Harvard Business Review Press.

    Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.

    Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations.Building on Eric Evans’ seminal book, Domain-Driven Design, the author presents practical DDD techniques through examples from familiar domains. Each principle is backed up by realistic Java examples–all applicable to C# developers–and all content is tied together by a single case study: the delivery of a large-scale Scrum-based SaaS system for a multitenant environment.The author takes you far beyond “DDD-lite” approaches that embrace DDD solely as a technical toolset, and shows you how to fully leverage DDD’s “strategic design patterns” using Bounded Context, Context Maps, and the Ubiquitous Language. Using these techniques and examples, you can reduce time to market and improve quality, as you build software that is more flexible, more scalable, and more tightly aligned to business goals.