Agile project + diary study = Awesome

So much about Agile makes it feel fast-paced – take some of the jargon associated with it for example: sprints, velocity, burn up, burn down, scrum. On the surface, this doesn’t sound like an ideal environment to run a long piece of research like a diary study. But for me, they were an unlikely match made in heaven.

Running a diary study was also a powerful way to subtly bring customer feedback into our development process and use it to shape our roadmap. Follow customers on their journey using our product, look for changes in their behaviours, learn about the things that upset them once they ‘honeymoon’ period wears off…

Through a diary study I was able to capture great feedback that we would usually have only found out about a month or so after releasing a product update.

Through the case study of a project that I worked on at MYOB, I will talk about how I approached the diary study and maintained the 6-week research program while development of our product continued in parallel. I will share what worked well and what I would change if I had my time again.

Presentation

Sketchnotes

From Gary Barber

Agile project + diary study = Awesome -  Megan Dell

From Norah Han:

From Sergey Vasilyev

Sketchnote from this session, from Sergey Vasilyev Sketchnote from this session, from Sergey Vasilyev Sketchnote from this session, from Sergey Vasilyev