Kirsten outlines a number of different techniques we use to help prioritise your project. Some of these techniques lend themselves to short term planning and others help to plan and prioritise on the roadmap level.
Following on from a sketching session, we’ll begin our process of prototyping ideas and testing our solutions on end users before designing a product that we’re all happy with.
We run customer research sessions at the start of a new project, or when introducing a new feature in order to validate that the problem we’re trying to solve exists. Having run quite a few of these sessions over the past couple of months we thought we’d share some of the lessons we’ve learned.
We tried a new type of retrospective: Continuous Attention to Individuals’ Needs (CAIN) and here’s what happened…
Instead of our monthly code kata session we decide to switch things up a bit and give Mob Programming a go. For this, I decided to pose as a typical client and send a small project idea through our website enquiry form. And then allow the ‘Mob’ to interpret those requirements and build some software following MobProgramming techniques.
Kirsten explains why user story mapping is one of the most powerful tools in our discovery toolkit, enabling us to define, prioritise and create a shared understanding of a digital product through the eyes of your end users.
Kirsten explains the motivating factors behind why we moved to Agile in 2010 following the realisation that our biggest pain points were the same reasons why the Agile manifesto was conceived.
In this post, Kirsten explains how to avoid some common pitfalls when writing user stories by focussing on the benefit element of a story.