But how much time you actually spend on your projects, and how much time do you spend responding to emergencies? This book will introduce you to different ways of ordering all of the projects you are working on now, and help you figure out how to staff those projects--even when you've run out of project teams to do the work. Once you learn to manage your portfolio better, you'll avoid emergency "firedrills." The trick is adopting lean and agile approaches to projects, whether they are software projects, projects that include hardware, or projects that depend on chunks of functionality from other suppliers. You may be accustomed to spending time in meetings where you still don't have the data you need to evaluate your projects. Here, with a few measures, you'll be able to quickly evaluate each project and come to a decision quickly. You'll learn how to define your team's, group's, or department's mission with none of the buzzwords that normally accompany a mission statement. Armed with the work and the mission, you can make those decisions that define the true leaders in the organization.

    It's no wonder so many development studios are struggling to survive. Fortunately, there is a solution. Scrum and Agile methods are already revolutionizing development outside the game industry. Now, long-time game developer Clinton Keith shows exactly how to successfully apply these methods to the unique challenges of game development. Keith has spent more than fifteen years developing games, seven of them with Scrum and agile methods. Drawing on this unparalleled expertise, he shows how teams can use Scrum to deliver games more efficiently, rapidly, and cost-effectively; craft games that offer more entertainment value; and make life more fulfilling for development teams at the same time. You'll learn to form successful agile teams that incorporate programmers, producers, artists, testers, and designers--and promote effective collaboration within and beyond those teams, throughout the entire process. From long-range planning to progress tracking and continuous integration, Keith offers dozens of tips, tricks, and solutions--all based firmly in reality and hard-won experience. Coverage includes Understanding Scrum's goals, roles, and practices in the context of game development Communicating and planning your game's vision, features, and progress Using iterative techniques to put your game into a playable state every two to four weeks-- even daily Helping all team participants succeed in their roles Restoring stability and predictability to the development process Managing ambiguous requirements in a fluid marketplace Scaling Scrum to large, geographically distributed development teams Getting started: overcoming inertia and integrating Scrum into your studio's current processes Increasingly, game developers and managers are recognizing that things can't go on the way they have in the past. Game development organizations need a far better way to work. Agile Game Development with Scrum gives them that--and brings the profitability, creativity, and fun back to game development.

    For years, Joel Spolsky has done exactly this at www.joelonsoftware.com. Now, for the first time, you can own a collection of the most important essays from his site in one book, with exclusive commentary and new insights from joel.

    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 GrowthHackers.com.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.

    Today, agile is being hailed as the essential bridge across that chasm. Agile, say its enthusiasts, can transform your company, catapulting you to the head of the pack.Not so fast. In this clear-eyed and indispensable book, Bain & Company thought leader and HBR author Darrell Rigby and colleagues Sarah Elk and Steve Berez provide a much-needed reality check. They dispel the myths and misconceptions that have accompanied agile's growth--the idea that it can reshape your organization all at once, for instance, or that it should be used in every function and for all types of work. They affirm and illustrate that agile teams can indeed transform the work environment, make people's jobs more rewarding, and turbocharge innovation--but only if the method is fully understood and implemented the right way.The key, they argue, is balance. Every organization must optimize and tightly control some of its operations. At the same time, every organization must innovate. Agile, done well, frees and facilitates vigorous innovation without sacrificing the efficiency and reliability essential to traditional operations. The authors break down how agile really works, show what not to do, and explain the crucial importance of scaling agile properly in order to get its full benefit. They then lay out a road map for leading the transition to a truly agile enterprise.Agile isn't a goal in itself; it's a means to the end of a high-performance operation. Doing Agile Right is the must-have guide for any company trying to make the transition--and for those already there, a way to avoid or recover from its potential pitfalls.

    This involves taking detailed and technical product information and distilling it into key marketing and sales messages as well as working among several teams in an organization to plan and execute product releases and launches. This book is a must-have for anyone who works as, or with, a Product Marketing Manager. It not only explains the role but focuses on practical applications of the information presented and ties everything together with entertaining life lessons and anecdotes collected through years of experience by the author as well as interviews with his colleagues and other industry experts. If you are considering a career as a Product Marketing Manager, are new to the profession and looking for guidance and clarification, already have many years of experience in the role and are looking for new inspiration and ideas, or are interested in learning what a Product Marketing Manager colleague of yours is responsible for within your organization, this book is for you.

    And you've crafted a business plan so detailed it's a work of art. Don't get too attached to it.As John Mullins and Randy Komisar explain in Getting to Plan B, new businesses are fraught with uncertainty. To succeed, you must change the plan in real time as the inevitable challenges arise. In fact, studies show that entrepreneurs who stick slavishly to their Plan A stand a greater chance of failing-and that many successful businesses barely resemble their founders' original idea.The authors provide a rigorous process for stress testing your Plan A and determining how to alter it so your business makes money, solves customers' needs, and endures. You'll discover strategies for:-Identifying the leap-of-faith assumptions hidden in your plan-Testing those assumptions and unearthing why the plan might not work-Reconfiguring the five components of your business model-revenue model, gross margin model, operating model, working capital model, and investment model-to create a sounder Plan B.Filled with success stories and cautionary tales, this book offers real cases illustrating the authors' unique process. Whether your idea is for a start-up or a new business unit within your organization, Getting to Plan B contains the road map you need to reach success.

    They quit frustrating corporate jobs to visit the world’s most inspiring companies. While checking off their renowned Bucket List, they share what they have learned so far.This book is for people who know workplaces could, and should, be better. Whether you’re in the leadership team, a rebel who has been suppressed by corporate dogma or a manager who is trapped in the broken system: this book is for you!

    Today, software organizations are transforming the way work gets done through practices like Agile, Lean, and DevOps. But as commonly implemented as these methods are, many transformations still fail, largely because the organization misses a critical step: transforming their culture and the way people communicate. Agile Conversations brings a practical, step-by-step guide to using the human power of conversation to build effective, high-performing teams to achieve truly Agile results. Consultants Douglas Squirrel and Jeffrey Fredrick show readers how to utilize the Five Conversations to help teams build trust, alleviate fear, answer the "whys," define commitments, and hold everyone accountable.These five conversations give teams everything they need to reach peak performance, and they are exactly what's missing from too many teams today. Stop focusing on processes and practices that leave your organization stuck with culture-less rituals. Instead, unleash the unique human power of conversation.

    But in today’s service- and software-driven world, “done” is less obvious. When is Amazon done? When is Google done? Or Facebook? In reality, services powered by digital systems are never done. So then how do we give teams a goal that they can work on?Mostly, we simply ask teams to build features—but features are the wrong way to go. We often build features that create no value. Instead, we need to give teams an outcome to achieve. Using outcomes creates focus and alignment. It eliminates needless work. And it puts the customer at the center of everything you do.Setting goals as outcomes sounds simple, but it can be hard to do in practice. This book is a practical guide to using outcomes to guide the work of your team. "Josh’s crisp volume brims with insight about how to fly at just the right level - the level of outcomes. If you’ve ever wondered how M your MVP should be, or how to get more R in your OKRs, this book will help." --Nick Rockwell, CTO, NY Times

    There are currently a significant number of books on creating, documenting, and implementing software architecture, but precious few resources have addressed how to build a software architecture that aligns with a customer's overall business goals. In this new book, Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions. This book helps technologists grasp the business ramifications of their decisions, and provides business-oriented software professionals (e.g. sales people and marketers) with better knowledge of how robust software can be built and maintained.

    Customer service, they assert, is only needed when a company does something wrong--eliminating the need for service is the best way to satisfy customers. To be successful, companies need to treat service as a data point of dysfunction and figure what they need to do to eliminate the demand. The Best Service Is No Service outlines these seven principles to deliver the best service that ultimately leads to no service: Eliminate dumb contacts Create engaging self-service Be proactive Make it easy to contact your company Own the actions across the company Listen and act Deliver great service experiences

    The Art of Action is a thought-provoking and fresh look at how managers can turn planning into execution, and execution into results.Drawing on his experience as a consultant, senior manager and a highly respected military historian, Stephen Bungay takes a close look at the nineteenth-century Prussian Army, which built its agility on the initiative of its highly empowered junior officers, to show business leaders how they can build more effective, productive organizations. Based on a theoretical framework which has been tested in practice over 150 years, Bungay shows how the approach known as "mission command" has been applied in businesses as diverse as pharmaceuticals and F1 racing today. The Art of Action is scholarly but engaging, rigorous but pragmatic, and shows how common sense can sometimes be surprising.

    It requires you to develop a data culture that involves people throughout the organization. In this O’Reilly report, DJ Patil and Hilary Mason outline the steps you need to take if your company is to be truly data-driven—including the questions you should ask and the methods you should adopt. You’ll not only learn examples of how Google, LinkedIn, and Facebook use their data, but also how Walmart, UPS, and other organizations took advantage of this resource long before the advent of Big Data. No matter how you approach it, building a data culture is the key to success in the 21st century. You’ll explore: Data scientist skills—and why every company needs a Spock How the benefits of giving company-wide access to data outweigh the costs Why data-driven organizations use the scientific method to explore and solve data problems Key questions to help you develop a research-specific process for tackling important issues What to consider when assembling your data team Developing processes to keep your data team (and company) engaged Choosing technologies that are powerful, support teamwork, and easy to use and learn