Alignment vs Autonomy and The Purpose Alignment Model
By Chris Lukassen
When scaling agile / Scrum, we invariable run into the alignment vs autonomy
problem. In short: you cannot have autonomous self directing teams if they
have no clue in what direction they should go, or even shorter: Alignment
But how do we create alignment? and what tools can we use to quickly evaluate
if what we want to do is part of the mission or better left out? Niel
Nickolaisen created the Purpose Alignment model and I use it with innovation
labs in large enterprises to decide what should be part of our innovation and
what should be left to others.
So if you struggle with aligning your development approaches with the
market strategy on how their product is going to be successful in the
marketplace, grab a whiteboard. To be successful, a product must do solves a
Thomas Bitman of Gartner wrote a blog post last year about why OpenStack
projects fail. In that article, he outlined three particular metrics which
together cause 60% of OpenStack projects to fall short of expectations:
Wrong people (31% of failures): a successful cloud needs commitment both from
the operations team as well as from "anchor" tenants. Wrong processes (19% of
failures): a successful cloud automates across silos in the software
development lifecycle, not just within silos. Wrong metrics (10% of
failures): a successful cloud focuses on top line transformation by
Since we launched our Agile Digital Transformation Roadmap poster two weeks
ago, several hundred people around the globe have downloaded it - but it's
not clear how many of them have taken the time to work their way through it.
Haven't seen it yet, you say? No worries - you can download the poster for
free at AgileDigitalTransformation.com.
OK then - everyone have the poster handy? Good. Here's how to make sense of
So...Where's the Roadmap?
The first thing you'll notice about the ADT Roadmap is that it doesn't look
too much like the sort of roadmap you'd likely see in the cou... (more)
View DevOps Power Panel ▸ Here
DevOps Patterns and Anti-Patterns: How to Do the Right Things in the Real
In the world of DevOps there are ‘known good practices' - aka ‘patterns'
- and ‘known bad practices' - aka ‘anti-patterns.' Many of these patterns
and anti-patterns have been developed from real world experience, especially
by the early adopters of DevOps theory; but many are more feasible in theory
than in practice, especially for more recent entrants to the DevOps scene.
In this Power Panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps
Conference Chair Andi... (more)
Remember Mad Libs? You'd get a book that contained paragraphs with key words
missing, replaced with hints as to what might fill the blanks. You and your
friends would come up with silly words to complete the sentences, with
predictably hilarious results.
Well, it's time for some Gartner Mad Libs. For this game, the same word
belongs in all the blanks. See if you can figure out what the missing word is
(here's the source if you can't resist peeking).
The current software ecosystem allows only whole products to be
commercialized - not functions or features.... While the number of e... (more)
Five Key Requirements for Enabling Agile Analytics
By Yann Guernion
In today's digital economy, companies are faced with a fast data challenge as
well as a Big Data one. As a result they are under pressure to adapt their
analytics processes and data flows at pace to move beyond traditional data
Big Data projects are either too big or too complex to handle the traditional
way. That's why most projects by companies at the start of their Big Data
initiative have no process at all. Waterfall approaches are notably
inefficient as you probably won't have access to prop... (more)