Video – product development without the product owner

Crisp’s Youtube channel has made a new release – introducing Concepts.

Concepts is used to let passionate people run with ideas, a different approach than that of traditional product ownership. If you do use in conjunction with a product owner, it allows that person to spend more time on the field with customers.

Ps: The mastermind behind the illustrations -> Jimmy Janlén!

More on concepts: crisp.se/concepts

Try out concepts at The Product Owner Survival Camp, 3-4 Nov

Cheers

/Mattias

Squad Health Check model – visualizing what to improve

Squad Health Check model

(Download the cards & instructions as PDF or PPTX)

At Spotify we’ve been experimenting a lot with various ways of visualizing the “health” of a squad, in order to help them improve and find systemic patterns across a tribe. Since a lot of people have been asking me about this, I wrote up an article about it together with coach-colleague Kristian Lindwall.

Read it on the Spotify labs blog: Squad Health Check model – visualizing what to improve.

Agile @ Scale (slides from Sony Mobile tech talk)

Here are the slides from my tech talk Agile @ Scale at Sony Mobile. Full house & very high level of engagement, I was impressed by this crowd! And thanks for the awesome recommendation on LinkedIn :)

 

Some sample pics below:

Visualize and limit WIP

Visual planning

Productivity and motivation

 

Tradeoffs

Vad du inte visste om LOU – Lagen om offentlig upphandling

(this post will be in Swedish since it is a response to Swedish legislation describing how to sell and buy software. If you still are interested, Google Translate is your best friend :)

LOU – Lagen om offentlig upphandling är fröet till många katastrofer för statliga och kommunala mjukvaruprojekt. Tänkt som ett verktyg för att hushålla väl med statliga medel, genom att konkurrensutsätta erbjudanden bidrar LOU tyvärr till att skapa dåliga förutsättningar för att lyckas med mjukvara.

Det knasiga med LOU är de felaktiga incitamenten: Om vi antar att de funktioner som är användbara är relativt okända i ett tidigt stadium av projektet så är default practice vid användandet av LOU att funktionerna skall specas i början och sedan skall billigast leverantör väljas. Det vanligaste sättet att jämföra leverantörer är att skapa en lång lista av den sammanlagda funktionaliten i deras produkter och sedan låta dem bjuda på minsta kostnad. Inte oväntat kommer vinnande leverantör efter kontraktet’s inskrivande att snabbt flytta på senior kompetens ur projektet till fördel för junior och vips befinner både kunden och leverantören i en långsam dödsdans där kundens användare blir förlorarna.

LOU innehåller dock ett antal möjligheter som du som upphandlare kan nyttja smart.

read more »

Why is it so difficult to bring Agile and Lean to the organisational level?

Are you also sensing something is wrong with today´s organisations? If you have been working with Agile or Lean for a while you typically notice that the early wins and benefits on a smaller scale will very soon hit it´s limits. Maybe you have been struggling with getting expected results from your Agile and Lean transformation initiative. Or you feel it is going painfully slow. In this blog I am going to put some light on what is wrong and what to do about it. My intention for you is to better understand the friction we are sensing in today’s organisations and what is getting in the way from creating truly Agile Organisations.

read more »

Product Discovery process framework and tools

Product Discovery defines what should be built – and why. Collaboration Is Key. Your success with agile development depends on delivering the right product requirements at the right time.

During the past few years when I have been working as Lead UX or Product Owner I have come to a core process of how to do the discovery. At my latest gig on Viaplay as Chief Product Owner I had great use of some of these methods and also found it to be a great tool to have it visualised for all Product Owners in a one pager.

Within this process I see lots of different methods that may be used.As I use it I pick different methods in each level depending on organisation, product or project. Sometimes not all steps are neccesary off course. When working methodically for some time you start getting a feel for what seems like a good ide or not.

In this post I’m presenting a framework of the process as well as the methods in short formats. I will try to post more in dept posts on some of the methods going forward. Please let me know what methods you would like to know more about :) Hope you find it useful in your daily work.

Download the one pager for Product Process and Tools here >

Note: Due to some lazyness there are some Swedish material in this article also – sorry for that!

1. Strategy

Why are we doing this? What is the goal & desired impact? 

1.1 Concept
Concepts enables people passionate about a product idea, regardless of role, to realise it all the way to happy client. Concepts is a one page specification, in A3 format that represents a product idea of feature. It is enough to enable a prepared conversation with engineers developing the product. Think of it as a “flexible minimum specification”.  Mattias Skarins blog post on this http://www.crisp.se/concepts

Screen Shot 2014-09-05 at 11.08.12

Here you can download the Concept template I have created from Mattias Skarins examples > read more »

Hello managers, coaches, and other change agents

Here’s the thing. Suppose you introduce a change X to your workplace, and then business improves noticably. That doesn’t mean X caused the business to improve. Well, MAYBE it did. Or perhaps business improved for other reasons, and X was actually detrimental, and business would have improved even more without it. So did things work out well because of the great X, or despite the lousy X? You’ll never know, unless you could rewind the clock and play out the same scenario without X. Correlation doesn’t imply causation.

So people like me who work with organizational change, we are in the business of pseudo-science. We get customer feedback and anecdotal evidence, but we can’t actually prove that we are doing any good, it’s just opinions and observations and guesswork. I think that’s fine, but let’s be honest about it :)