Skip to main content

Spotify...

I was sent these videos earlier on the way Spotify operates.
It looks a lot closer to Agile utopia than many companies.
Well worth a watch:
Part 1

Part 2
If this doesn't make you want to be more Agile at work then I despair!
Maybe we'll never get to this level but we can keep trying.

 The bad news?  Most workplaces I've experienced have been a huge distance from this experience.

 The good news? I wasn't sent these video links by one of my cutting edge start-up contacts, but by a Head-of Delivery in a major European Insurance company.  The desire is there and it's moving up through the hierarchy.

 The slow realisation that the way in which they create, buy and deploy tech is paramount is dawning.

 Let's focus on doing it the right way and learn from the hard lessons of other industries.

 Mining and textiles were thrown away in the UK in the pursuit of being cheap (at the cost of quality - and jobs).

 The British Automotive Industry fell apart in the 1970s with failure to modernise and appalling quality playing their part.

 Can we stop ourselves going the same way?

 We can certainly contribute by focusing on continuous improvement, quality and delivering business benefit time after time.

 Ultimately whether we survive or fail in the long term depends on whether we're seen as a good investment by the bean counters; so keep delivering!
Labels:

Comments

Post a Comment

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...
Post a Comment
Read more

Fear and blame.

Hands up if you've ever heard someone say: "We don't have a fear-and-blame culture." And keep them up if the reaction of the 'doers' was to roll their eyes and mutter something sarcastic. It's a nice phrase to trot out at a senior leadership conference or to write in your 'best employer of 2020' application, but if you have to say it, it's probably not true. And repeating the mantra won't make it any more true. In fact, people might respect you more if you were honest and admitted that there is blame and where the boundaries lie.  At least in that scenario, the individual knows where they stand. Instead, we often have the jarring dissonance of hearing our leaders say one thing and seeing them act entirely differently. As a leader (especially a senior leader): When you stand at the front of a room and tell the assembly that there is no fear-and-blame, look at their faces.   If they mostly appear too scared to dis...
Post a Comment
Read more

Agile Armchair Generals

If you're an Agile practitioner of any sort you will understand what I mean by Armchair Generals (if not, it may be an idea to check if you are one..). Apropos of nothing an email arrives that questions the management of your project in terms of whether it is properly 'Agile'. Feedback is, of course, a great tool.  But it must always be understood within the context of the person providing it. So when the email lands questioning the type of contingency you've built into your project or the depth of analysis performed on your requirements set, ask yourself: 1. Has the questioner spotted something you and the team have missed? It happens.  That's why independent reviews can be helpful. 2. Has the questioner misunderstood something about your project?  If so, maybe your communications weren't quite clear enough or they've missed something - it happens, we're all busy. If the questioner has understood the topic correctly and is simply disagreeing ...
Post a Comment
Read more