It will allow you to avoid some likely pitfalls and it will guide you to asking, yourself and your clients, the right questions. Though many people focus on the visualization techniques in Kanban the true value only emerges when you, as a kanban system manager, are apt at noticing the anti-patterns that occur on the kanban board and are able to take appropriate actions. David generously shares his vast experience in this field, with plenty real case scenarios, to the benefit of the reader. After reading this book I toyed with the idea: Would I've changed my approach to coaching my previous clients, in their adoption of agile values and practices, had I read this at the time? Well, I certainly would have, for all of them, and I'm sure it would have meant a smoother change process for the agilely challenged organizations. David provides a comprehensive guide to implementing Kanban in a software development/maintenance environment. Covering the mechanics, dynamics, principles and rationale behind why Kanban is a so promising framework for managing the work of a variety of teams and groups and being an evolutionary-based change management driver. Kanban is the practical approach to implement Lean Software Development, and this book is the practical guide for how to start using Kanban, and how to adapt the system for advanced needs. The book is clear and flowing, even though it covers some quite technical material. I would recommend it to Development managers, Project/Program managers, Agile Coaches/Consultants. It addresses concerns/needs of Novice as well as those already familiar with Kanban and looking for advanced answers. Even if you don't intend to implement a kanban system, there are a lot of techniques and ideas that are easily applicable to any product development/maintenance environment, agile or not. Bottom line, highly recommended.

    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

    In 1999, Tony introduced Clayton Christensen to the idea that “people have underlying needs or processes in their lives, that they are addressing in some way right now”—an insight that was to become Jobs-to-be-Done Theory. For 25 years, Ulwick and his company, Strategyn, have helped over 400 companies, applying Jobs-to-be-Done Theory in practice with a success rate of 86%—a 5-fold improvement. “Ulwick has taken the guesswork out of innovation,” says the ‘father of modern marketing,’ Philip Kotler, S. C. Johnson Distinguished Professor of International Marketing at the Kellogg School of Management, Northwestern University. “He has done this by introducing us to Jobs-to-be-Done theory, and converting it to practice using his rigorous innovation process known as Outcome-Driven Innovation. I call him the Deming of Innovation because, more than anyone else, Tony has turned innovation into a science,” adds Kotler. LEARN - Why companies fail at innovation and how to avoid critical mistakes. - How to employ the Jobs-to-be-Done Theory Needs Framework to categorize, define, capture, and prioritize customer needs. - A Jobs-to-be-Done Growth Strategy Matrix to categorize, understand, and employ the 5 strategies that drive growth. - Outcome-Based Segmentation: how does it create new opportunities? - The details of the innovation process known as Outcome-Driven Innovation. It ties customer-defined metrics to the customer’s Job-to-be-Done, transforming every aspect of opportunity discovery, marketing and innovation. - The Language of Job-to-be-Done – the syntax and lexicon of innovation.

    Unfortunately, reliable guidance on Agile management has been scarce indeed. Now, leading Agile manager Jurgen Appelo fills that gap, introducing a realistic approach to leading, managing, and growing your Agile team or organization. Writing for current managers and developers moving into management, Appelo shares insights that are grounded in modern complex systems theory, reflecting the intense complexity of modern software development. Appelo's Management 3.0 model recognizes that today's organizations are living, networked systems; and that management is primarily about people and relationships. Management 3.0 doesn't offer mere checklists or prescriptions to follow slavishly; rather, it deepens your understanding of how organizations and Agile teams work and gives you tools to solve your own problems. Drawing on his extensive experience as an Agile manager, the author identifies the most important practices of Agile management and helps you improve each of them. Coverage includes - Getting beyond "Management 1.0" control and "Management 2.0" fads - Understanding how complexity affects your organization - Keeping your people active, creative, innovative, and motivated - Giving teams the care and authority they need to grow on their own - Defining boundaries so teams can succeed in alignment with business goals - Sowing the seeds for a culture of software craftsmanship - Crafting an organizational network that promotes success - Implementing continuous improvement that actually works Thoroughly pragmatic-and never trendy-Jurgen Appelo's Management 3.0 helps you bring greater agility to any software organization, team, or project.

    The Ten Types of Innovation explores these insights to diagnose patterns of innovation within industries, to identify innovation opportunities, and to evaluate how firms are performing against competitors. The framework has proven to be one of the most enduring and useful ways to start thinking about transformation.Details how you can use these innovation principles to bring about meaningful--and sustainable--growth within your organization Author Larry Keeley is a world renowned speaker, innovation consultant, and president and co-founder of Doblin, the innovation practice of Monitor Group; BusinessWeek named Keeley one of seven Innovation Gurus who are changing the field The Ten Types of Innovation concept has influenced thousands of executives and companies around the world since its discovery in 1998. The Ten Types of Innovation is the first book explaining how to implement it.

    So what separates the startups that get disrupted and disappear from the ones who grow to become global giants?The secret is blitzscaling: a set of techniques for scaling up at a dizzying pace that blows competitors out of the water. The objective of Blitzscaling is not to go from zero to one, but from one to one billion -as quickly as possible.When growing at a breakneck pace, getting to next level requires very different strategies from those that got you to where you are today. In a book inspired by their popular class at Stanford Business School, Hoffman and Yeh reveal how to navigate the necessary shifts and weather the unique challenges that arise at each stage of a company's life cycle, such as: how to design business models for igniting and sustaining relentless growth; strategies for hiring and managing; how the role of the founder and company culture must evolve as the business matures, and more.Whether your business has ten employees or ten thousand, Blitzscaling is the essential playbook for winning in a world where speed is the only competitive advantage that matters.

    Strategic planning is essential. People's competencies should be measured and their weaknesses shored up. People crave feedback.These may sound like basic truths of our work lives today. But actually, they're lies. As strengths guru and bestselling author Marcus Buckingham and Cisco Leadership and Team Intelligence head Ashley Goodall show in this provocative, inspiring book, there are some big lies--distortions, faulty assumptions, wrong thinking--running through our organizational lives. Nine lies, to be exact. They cause dysfunction and frustration and ultimately result in a strange feeling of unreality that pervades our workplaces.But there are those who can get past the lies and discover what's real. These are freethinking leaders who recognize the power and beauty of our individual uniqueness, who know that emergent patterns are more valuable than received wisdom, and that evidence is more powerful than dogma. With engaging stories and incisive analysis, the authors reveal the essential truths that such freethinking leaders will recognize immediately: that it is the strength and cohesiveness of your team, not your company's culture, that matters most; that we need less focus on top-down planning and more on giving our people reliable, real-time intelligence; that rather than trying to align people's goals we should strive to align people's sense of purpose and meaning; that people don't want constant feedback, they want helpful attention. This is the real world of work.If you embrace each person's uniqueness and see this as key for all healthy organizations; if you reject dogma and engage with the real world; if you seek out emergent patterns and put your faith in evidence, not philosophy; if you thrill to the power of teams--if you do all of these, then you are a freethinking leader, and this book is for you.

    A pocket-sized overview of roles, artifacts and the sprint cycle, adapted from the bestseller The Elements of Scrum by Chris Sims & Hillary Louise Johnson

    As newly appointed captain of the USS Santa Fe, a nuclear-powered submarine, he was responsible for more than a hundred sailors, deep in the sea. In this high-stress environment, where there is no margin for error, it was crucial his men did their job and did it well.But the ship was dogged by poor morale, poor performance, and the worst retention in the fleet. Marquet acted like any other captain until, one day, he unknowingly gave an impossible order, and his crew tried to follow it anyway. When he asked why the order wasn't challenged, the answer was "Because you told me to." Marquet realized he was leading in a culture of followers, and they were all in danger unless they fundamentally changed the way they did things. That's when Marquet took matters into his own hands and pushed for leadership at every level. Turn the Ship Around! is the true story of how the Santa Fe skyrocketed from worst to first in the fleet by challenging the U.S. Navy's traditional leader-follower approach. Struggling against his own instincts to take control, he instead achieved the vastly more powerful model of giving control. Before long, each member of Marquet's crew became a leader and assumed responsibility for everything he did, from clerical tasks to crucial combat decisions. The crew became fully engaged, contributing their full intellectual capacity every day, and the Santa Fe started winning awards and promoting a highly disproportionate number of officers to submarine command.No matter your business or position, you can apply Marquet's radical guidelines to turn your own ship around. The payoff: a workplace where everyone around you is taking responsibility for their actions, where people are healthier and happier, where everyone is a leader.

    . . joy. As a package-delivery person once remarked, “I don’t know what you do, but whatever it is, I want to work here.”Every year, thousands of visitors come from around the world to visit Menlo Innovations, a small software company in Ann Arbor, Michigan. They make the trek not to learn about technology but to witness a radically different approach to company culture.CEO and “Chief Storyteller” Rich Sheridan removed the fear and ambiguity that typically make a workplace miserable. His own experience in the software industry taught him that, for many, work was marked by long hours and mismanaged projects with low-quality results. There had to be a better way.With joy as the explicit goal, Sheridan and his team changed everything about how the company was run. They established a shared belief system that supports working in pairs and embraces making mistakes, all while fostering dignity for the team.The results blew away all expectations. Menlo has won numerous growth awards and was named an Inc. magazine “audacious small company.” It has tripled its physical office three times and produced products that dominate markets for its clients.Joy, Inc. offers an inside look at how Sheridan and Menlo created a joyful culture, and shows how any organization can follow their methods for a more passionate team and sustainable, profitable results. Sheridan also shows how to run smarter meetings and build cultural training into your hiring process.Joy, Inc. offers an inspirational blueprint for readers in any field who want a committed, energizing atmosphere at work—leading to sustainable business results.

    Womack, Chairman and Founder, Lean Enterprise Institute. This game-changing book puts you behind the curtain of Toyota, providing new insight into the legendary automaker's management practices and offering practical guidance for leading and developing people in a way that makes the best use of their brainpower. Drawing on six years of research into Toyota's employee-management routines, Toyota Kata examines and elucidates, for the first time, the company's organizational routines--called kata--that power its success with continuous improvement and adaptation. The book also reaches beyond Toyota to explain issues of human behavior in organizations and provide specific answers to questions such as: How can we make improvement and adaptation part of everyday work throughout the organization? How can we develop and utilize the capability of everyone in the organization to repeatedly work toward and achieve new levels of performance? How can we give an organization the power to handle dynamic, unpredictable situations and keep satisfying customers? Mike Rother explains how to improve our prevailing management approach through the use of two kata: Improvement Kata--a repeating routine of establishing challenging target conditions, working step-by-step through obstacles, and always learning from the problems we encounter; and Coaching Kata: a pattern of teaching the improvement kata to employees at every level to ensure it motivates their ways of thinking and acting. With clear detail, an abundance of practical examples, and a cohesive explanation from start to finish, Toyota Kata gives executives and managers at any level actionable routines of thought and behavior that produce superior results and sustained competitive advantage.

    But it is hard. It’s hard because it forces people and organizations to make specific choices about their future—something that doesn’t happen in most companies.Now two of today’s best-known business thinkers get to the heart of strategy—explaining what it’s for, how to think about it, why you need it, and how to get it done. And they use one of the most successful corporate turnarounds of the past century, which they achieved together, to prove their point.A.G. Lafley, former CEO of Procter & Gamble, in close partnership with strategic adviser Roger Martin, doubled P&G’s sales, quadrupled its profits, and increased its market value by more than $100 billion in just ten years. Now, drawn from their years of experience at P&G and the Rotman School of Management, where Martin is dean, this book shows how leaders in organizations of all sizes can guide everyday actions with larger strategic goals built around the clear, essential elements that determine business success—where to play and how to win.The result is a playbook for winning. Lafley and Martin have created a set of five essential strategic choices that, when addressed in an integrated way, will move you ahead of your competitors. They are:• What is our winning aspiration?• Where will we play?• How will we win?• What capabilities must we have in place to win?• What management systems are required to support our choices?The stories of how P&G repeatedly won by applying this method to iconic brands such as Olay, Bounty, Gillette, Swiffer, and Febreze clearly illustrate how deciding on a strategic approach—and then making the right choices to support it—makes the difference between just playing the game and actually winning.

    It was also a weapon.Simplicity isn’t just a design principle at Apple—it’s a value that permeates every level of the organization. The obsession with Simplicity is what separates Apple from other technology companies. It’s what helped Apple recover from near death in 1997 to become the most valuable company on Earth in 2011.Thanks to Steve Jobs’s uncompromising ways, you can see Simplicity in everything Apple does: the way it’s structured, the way it innovates, and the way it speaks to its customers.It’s by crushing the forces of Complexity that the company remains on its stellar trajectory.As ad agency creative director, Ken Segall played a key role in Apple’s resurrection, helping to create such critical marketing campaigns as Think different. By naming the iMac, he also laid the foundation for naming waves of i-products to come.Segall has a unique perspective, given his years of experience creating campaigns for other iconic tech companies, including IBM, Intel, and Dell. It was the stark contrast of Apple’s ways that made Segall appreciate the power of Simplicity—and inspired him to help others benefit from it.In Insanely Simple, you’ll be a fly on the wall inside a conference room with Steve Jobs, and on the receiving end of his midnight phone calls. You’ll understand how his obsession with Simplicity helped Apple perform better and faster, sometimes saving millions in the process. You’ll also learn, for example, how to:• Think Minimal: Distilling choices to a minimum brings clarity to a company and its customers—as Jobs proved when he replaced over twenty product models with a lineup of four.• Think Small: Swearing allegiance to the concept of “small groups of smart people” raises both morale and productivity.• Think Motion: Keeping project teams in constant motion focuses creative thinking on well-defined goals and minimizes distractions.• Think Iconic: Using a simple, powerful image to symbolize the benefit of a product or idea creates a deeper impression in the minds of customers.• Think War: Giving yourself an unfair advantage—using every weapon at your disposal—is the best way to ensure that your ideas survive unscathed.Segall brings Apple’s quest for Simplicity to life using fascinating (and previously untold) stories from behind the scenes. Through his insight and wit, you’ll discover how companies that leverage this power can stand out from competitors—and individuals who master it can become critical assets to their organizations.

    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."

    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