Author: Dan Greening

  • Can You Combine Waterfall and Agile?

    Can You Combine Waterfall and Agile?

    Many well-meaning people think they can be the First Person Ever to combine waterfall and Scrum, name their new process with some catchy name, start teaching this Frankenstein system, then cause internal organizational chaos or sloth.

    Read More

  • Enterprise Scrum Thinking: Part 3 of 3

    Dan Greening explores the challenges of scaling Agile and Scrum concepts beyond the team level to project portfolios with executive involvement. Along the way, he discusses forecasting beyond sprints, commitments vs. lies, dashboard heresy, waterfall compatibility and failing safely, among other thought-provoking ideas. [Part 3: 26 min.]. Interview by Dave Prior at ProjectsAtWork.

    Read More

  • Enterprise Scrum Thinking: Part 2 of 3

    Dave Prior interviewed me on the topic of Enterprise Scrum Thinking. In the second part of three, I discuss the experimental mindset of an Agile-run project, how a Sprint is like a science experiment on production (we make a hypothesis, test the the hypothesis and learn from the results), and why fear of failure can…

    Read More

  • Enterprise Scrum Thinking: Part 1 of 3

    In the first of 3 podcasts, I discuss how to spread agile approaches beyond individual teams to the enterprise level, where potential benefits and challenges multiply. In the realm of project portfolio management, decision-making roles can include a Chief Product Owner and Enterprise ScrumMaster.

    Read More

  • Bulk Estimation

    Bulk Estimation

    Estimating lots of work items can help agile teams dramatically: Estimates help Product Owners make trade-offs, help teams gauge capacity, help Product Owner forecast feature releases, and help team members think about architectural issues. However, in too many cases, estimating is painfully boring and slow. It doesn’t have to be. Why Estimate?

    Read More

  • Agile Abandonment 2: Root Causes

    Agile Abandonment 2: Root Causes

    Agile Abandonment Syndrome is a phenomenon where—after implementing agile practices and seeing direct evidence of their benefits—a company stops improving, its agile behaviors degrade, and ultimately loses market share or productivity. We have seen this in many companies.

    Read More

  • Agile Portfolio Management Helps Retain Agility?
    ,

    Agile Portfolio Management Helps Retain Agility?

    Agile methods create conflict. So to retain agility, we must actively promote it even after agile has taken hold. How can we equip a company with the cultural and process tools to sustain agility? Your choices may depend on your perspective. Social psychologists teach organizations to reinvent themselves, but this approach may be too slow…

    Read More

  • Review: Liz Keogh, Learning and Perverse Incentives

    Review: Liz Keogh, Learning and Perverse Incentives

    Liz Keogh, Learning and Perverse Incentives: The Evil Hat, QCon London 2011 This 50 minute talk discusses perverse incentives: situations where incentivizing individual behavior causes an organization to become dysfunctional.  When we attempt to optimize an organization, but fail to use systems thinking (i.e., when we are optimizing from an internal perspective) we can create…

    Read More

  • ,

    Is Hiring More the Right Answer?

    In my last company, I used to hear people say “We need more people to handle this workload.” Every group in the company considered in isolation could use more people, no matter what group they are in; at least that’s what most people think. But smart folks sometimes say, “We have too many people.”

    Read More

  • Quality is Not Negotiable? A Contrarian View

    In Martin Fowler’s blog post, Tradable Quality Hypothesis, he reiterates the oft-repeated agile cliché that “quality is not negotiable.” I argue that making quality inviolable lets engineers off the hook for understanding and prioritizing quality efforts.

    Read More