Scaling Up: How a Few Companies Make It...and Why the Rest Don't is the first major revision of this business classic. In Scaling Up, Harnish and his team share practical tools and techniques for building an industry-dominating business. These approaches have been honed from over three decades of advising tens of thousands of CEOs and executives and helping them navigate the increasing complexities (and weight) that come with scaling up a venture. This book is written so everyone -- from frontline employees to senior executives -- can get aligned in contributing to the growth of a firm. There's no reason to do it alone, yet many top leaders feel like they are the ones dragging the rest of the organization up the S-curve of growth. The goal of this book is to help you turn what feels like an anchor into wind at your back -- creating a company where the team is engaged; the customers are doing your marketing; and everyone is making money. To accomplish this, Scaling Up focuses on the four major decision areas every company must get right: People, Strategy, Execution, and Cash. The book includes a series of new one-page tools including the updated One-Page Strategic Plan and the Rockefeller Habits ChecklistTM, which more than 40,000 firms around the globe have used to scale their companies successfully -- many to $1 billion and beyond. Running a business is ultimately about freedom. Scaling Up shows business leaders how to get their organizations moving in sync to create something significant and enjoy the ride.

    It happens because VCs are experts in financings and most entrepreneurs are not. Brad and Jason are out to fix that problem with Venture Deals. This book is long overdue and badly needed."—Fred Wilson, Managing Partner, Union Square Ventures"Feld and Mendelson pack a graduate-level course into this energetic and accessible book.?The authors' frank style and incisive insight make this a must-read for high-growth company entrepreneurs, early-stage investors, and graduate students.?Start here if you want to understand venture capital deal structure and strategies.?I enthusiastically recommend."—Brad Bernthal, CU Boulder, Associate Clinical Professor ofLaw, Technology Policy, Entrepreneurial Law"A must-read book for entrepreneurs.?Brad and Jason demystify the overly complex world of term sheets and M&A, cutting through the legalese and focusing on what really matters.?That's a good thing not just for entrepreneurs, but also for venture capitalists, angels, and lawyers.?Having an educated entrepreneur on the other side of the table means you spend your time negotiating the important issues and ultimately get to the right deal faster."—Greg Gottesman, Managing Director, Madrona Venture Group"Venture Deals is a must-read for any entrepreneur contemplating or currently leading a venture-backed company. Brad and Jason are highly respected investors who shoot straight from the hip and tell it like it is, bringing a level of transparency to a process that is rarely well understood. It's like having a venture capitalist as a best friend who is looking out for your best interests and happy to answer all of your questions."—Emily Mendell, Vice President of Communications,National Venture Capital Association"The adventure of starting and growing a company can be exhilarating or excruciating—or both. Feld and Mendelson have done a masterful job of shedding light on what can either become one of the most helpful or dreadful experiences for entrepreneurs—accepting venture capital into their firm. This book takes the lid off the black box and helps entrepreneurs understand the economics and control provisions of working with a venture partner."—Lesa Mitchell, Vice President, Advancing Innovation, Kauffman Foundation

    Organizational pioneer Schein updates his influential understanding of culture--what it is, how it is created, how it evolves, and how it can be changed. Focusing on today's business realities, Schein draws on a wide range of contemporary research to redefine culture, offers new information on the topic of occupational cultures, and demonstrates the crucial role leaders play in successfully applying the principles of culture to achieve organizational goals. He also tackles the complex question of how an existing culture can be changed--one of the toughest challenges of leadership. The result is a vital resource for understanding and practicing organizational effectiveness.

    Emphasizes possible, realistic and "best practice" approaches for managers, technical leads and self-managed teams. The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classic mistakes, within the context of software-development fundamentals and risk management. Dissects the core issues of rapid development, lifecycle planning, estimation and scheduling. Contains very good and practical discussions of customer-oriented development, motivation and teamwork. Explains such fundamental requirements as team structure, feature-set control (the dreaded feature creep in every project), availability and use of productivity tools and project recovery options. Relevant case studies are analyzed and discussed within the context of specific software development problems. Over 200 pages in this publication are devoted to a summary of best practices, everything from the daily build and smoke test, through prototyping, model selection, measurement, reuse, and the top-10 risks list. This publication is definitely recommended and will become a classic in the field, just as the author's prior publication, "Code Complete" already is.

    

    Rose Randall is the archetypical reluctant project manager. Following a painful project failure years ago, Rose s life is cast into chaos when she is once again thrown into the role against her wishes. Faced with a struggling project, help comes from an unexpected source guiding Rose in the direction of Real Options.When you have read Commitment , you:* understand what the Real Options model is;* can apply the Real Options model to manage project risks successfully;* understand why much of your life involves options that you currently are treating as commitments;* see the world through a different filter opening up many new possibilities;* understand the difference between Commitments and Options.Because the book will:* provide specific examples of how a project can manage its risks using the Real Options model;* outline a simple technique for making decisions;* make you aware of all the decisions you make every day;* build your confidence in your ability to decide when to commit and when to leave options open.In short, this book is indispensable for new and experienced project managers plus anyone else who is interested in knowing more about managing large projects.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    Want to be creative? Then think Inside the Box. The traditional view says that creativity is unstructured and doesn’t follow rules or patterns. That you need to think “outside the box” to be truly original and innovative. That you should start with a problem and then “brainstorm” ideas without restraint until you find a solution. Inside the Box shows that more innovation— and better and quicker innovation—happens when you work inside your familiar world (yes, inside the box) using a set of templates that channel the creative process in a way that makes us more—not less—creative. These techniques were derived from research that discovered a surprising set of common patterns shared by all inventive solutions. They form the basis for Systematic Inventive Thinking, or SIT, now used by hundreds of corporations throughout the world, including industry leaders such as Johnson & Johnson, GE, Procter & Gamble, SAP, and Philips. Many other books discuss how to make creativity a part of corporate culture, but none of them uses the innovative and unconventional SIT approach described in this book. With “inside the box” thinking, companies and organizations of any size can creatively solve problems before they develop—and innovate on an ongoing, systematic basis. This system really works!

    The 11th edition of this text continues to build on four major marketing themes: building and managing profitable customer relationships, building and managing strong brands to create brand equity, harnessing new marketing technologies in the digital age, and marketing in a socially responsible way around the globe.

    With a foreword by design guru Don Norman.Humans make things every day, whether it’s composing an e-mail, cooking a meal, or constructing the Mars Rover. While complexity is often necessary in the development process, unnecessary complexity adds complications. The Simplicity Cycle provides the secret to striking the proper balance. Dan Ward shines a light on how complexity affects the things we make for good or ill, taking us on a journey through the process of making things, with a particular focus on identifying and avoiding complexity-related pitfalls.The standard development process involves increasing complexity to improve the outcome, Ward explains. The problem comes when the complexity starts getting in the way—but often we don’t know where that point is until we pass it. He suggests a number of techniques for identifying the problem and fixing it, including how to overcome several types of wrongheaded thinking—such as the idea that complexity and quality are the same. In clear, compelling language, and using his trademark mix of examples from research, personal experience, and pop culture, Ward offers a universal concept, visually described with a single, evolving diagram.Ideal for business leaders and technologists, The Simplicity Cycle is helpful for anyone looking to simplify and improve everything we do, whether we work in an office, at home, or at the Pentagon.

    Creating high-quality software for the enterprise involves a much different set of challenges. In this practical book, two expert product managers provide straightforward guidance for people looking to join the thriving enterprise market.Authors Blair Reeves and Benjamin Gaines explain critical differences between enterprise and consumer products, and deliver strategies for overcoming challenges when building for the enterprise. You'll learn how to cultivate knowledge of your organization, the products you build, and the industry you serve.Explore why:Identifying customer vs user problems is an enterprise project manager's main challengeEffective collaboration requires in-depth knowledge of the organizationAnalyzing data is key to understanding why users buy and retain your productHaving experience in the industry you're building products for is valuableProduct longevity depends on knowing where the industry is headed

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com

    Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.

    This work covers the project lifecycle, addressing every key issue participants face: politics, people, process, project management, and tools.

    In this plain-English guide, you'll discover how this remarkable quality improvement method can give you the tools to identify and eliminate waste and quality problems in your own work area.Packed with diagrams, cartoons, and real-life examples, What is Lean Six Sigma? reveals the "four keys" of Lean Six Sigma and how they apply to your own job:Delight your customers with speed and qualityImprove your processesWork together for maximum gainBase decisions on data and factsYou'll see the big picture of what your company hopes to gain with Lean Six Sigma, how it may affect your work area, and what it can mean to you personally.