Agile adoption roadblocks in Enterprise – is the opposite of Continuous Improvement really Intermittent Deterioration?
“The question isn’t who is going to let me; it’s who is going to stop me.” ~Ayn Rand
Everybody seems to want to “do Agile” these days, but few understand what that entails. Likewise, they don’t seem to realize that you can’t just “do Agile” but you can either “be Agile” or be what you’ve always been (or something else).
English: Extract from Raspberry Pi board at TransferSummit 2011 (Photo credit: Wikipedia)
Today, I’d like to expand on some thoughts I shared on Mike Cohn’s “Mountain Goat Software” blog on Agile:
https://www.mountaingoatsoftware.com/blog/why-your-product-backlog-should-look-like-an-iceberg
For the most part, those comments are simply summarizing some of my frustrations trying to push Agile adoption within an Enterprise company setup for very traditional Waterfall projects and Software Delivery LifeCycle (SDLC).
It’s a problem many Dev teams face.
BC$ = Behavior, Content, Money
The goal of the BC$ project is to raise awareness and make changes with respect to the three pillars of information freedom - Behavior (pursuit of interests and passions), Content (sharing/exchanging ideas in various formats), Money (fairness and accessibility) - bringing to light the fact that:
1. We regularly hand over our browser histories, search histories and daily online activities to companies that want our money, or, to benefit from our use of their services with lucrative ad deals or sales of personal information.
2. We create and/or consume interesting content on their services, but we aren't adequately rewarded for our creative efforts or loyalty.
3. We pay money to be connected online (and possibly also over mobile), yet we lose both time and money by allowing companies to market to us with unsolicited advertisements, irrelevant product offers and unfairly structured service pricing plans.