Minimum viable Agile

There’s the “complete” way of doing Agile with all of the “best practices” and then there’s the approach where you just take the “best parts,” the parts that suit your needs.

There are some great aspects to using Agile on OSS projects including the break-up of effort (epics / stories), the systematic prioritisation of work to cope with evolving requirements (sprints / scrums) and scoreboards/ visualisation.

One of the other intents of Agile is to promote speed and reduce overhead. However, that all comes down to its implementation. If you’re targeting “completeness ” of Agile, there is a risk that you’ll miss out on the speed and efficiency benefits.

We’ve heard of the “minimum viable…” mantra in the context of Agile, so can we turn that mantra onto Agile itself?

If this article was helpful, subscribe to the Passionate About OSS Blog to get each new post sent directly to your inbox. 100% free of charge and free of spam.

Our Solutions


Most Recent Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.