agile

The term minimum viable product, or MVP, has come to be misunderstood and misused in many organizations. It doesn’t mean you should be releasing half-baked, barely feasible software. Instead, you should be thinking of your product’s capabilities as a Specifically Marketable, Useful, Releasable Feature Set—or SMURFS!

Many organizations enforce systems that stifle flexibility by promoting specialization. But encouraging learning new skills and expanding outside core responsibilities promotes flow over resource efficiency, helps cover gaps in time of crisis, and lets you build a team that can deliver continually at a sustainable pace. It's the age of the generalist.

The Scrum Guide was updated recently to make values an explicit part of the framework: commitment, courage, focus, openness, and respect. When these values are embodied and lived by the team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. Is your team practicing them?

Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.