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:
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!

Comments

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...

Agile Bert joins the world of blog.

My far more technical compadre and fellow Agile Yorkshire attendee 'Agile Bert' (aka John) has joined the blogging world. Will he become a prolific blogger? Will he become a (thought) leader amongst men? Why is he called Bert? That last one actually has an answer: here

The case for Project Management in Agile?

OK, I know how most of the Agile community feels about Project Managers: Process over People Meetings Documentation Urrgh... But however you name the role (Agile Delivery, Scrum Master, Project Manager) and whoever does it  - someone needs to help the team to: Plan Track Deliver Communicate Being a group of incredibly talented engineers does not give a team the right to ignore 3.5 of these. All too often, engineers want to dive in to designing and building great software, but see planning as a hassle, tracking as a waste of time (or an abuse of their rights), communication as an alien concept and delivery (the fun bit) as something that will be done when it's done. It may be popular to talk about being a 'self-organising team' and railing against any form of 'order' being imposed.  But why is that order being imposed?  Maybe it's to deal with the chaos that your s-o-t has failed to deal with so far. As organisations scale and the senior leadership gets further a...