Business scenarios and 6 slicing patterns for product owners

Posted on by

It is sometimes beneficial to ramp up a large software step by step. This promises doing earlier business, reducing risk and gaining momentum. Just slicing a large development into arbitrary pieces will however not work well. Teams need a bit more strategy so that each delivery is useful and provides significant value. This article introduces business scenarios and 6 slicing patterns that help product owners and agile teams to align incremental product development with growing the business.

Continue reading →

5 approaches to integrate UX skills and professionals into organizations

Posted on by

Over the last years, many companies adopted user experience (UX) good practices and hired professionals. Some created centralized teams of UX consultants, other included designers into development teams, yet others created a team to contribute a design system or user research. This article is a collection of five approaches on how to include UX skills and UX professionals into organizations, open for discussion and refinement.

Continue reading →

From exciters to liabilities

Posted on by

Classifying customer expectations, Noriaki Kano created the well-known Kano model more than 40 years ago. I felt this model deserves a more in-depth presentation on stars to road for a couple of reasons: First, it helps to prioritize features over the lifetime of a product. Second, it points to typical issues you encounter during product development and provides hints how to improve. Third, it is not too difficult to assess the categories and they are easy to understand. Fourth and most important: you need good understanding of customers and markets to work with the model, a real indirect benefit! All in all, the Kano model is an important foundation in product development one should know.

Continue reading →

Requirements – an agile answer

Posted on by

Understanding what people need and require from a product is important. So requirements are important. But what is a requirements and what are “good” or “bad” ones? I set forth to find the ultimate answer and found 42. So lets add a bit more structure and talk about the problem, solution and the conversation side and conclude with a question: where should the development team invest their energy: into creating the specification or into discussing the best possible solution given the constraints?

Continue reading →

The case of a relevant UX problem

Posted on by

This is not about a Sherlock Holmes mystery and no engineer lost a thumb over it. Even though the machinery involved could easily achieve the latter. It is about industrial robots and tons of machinery to fold metal sheets into origami swans. But mainly it is about a case where creating the right user experience solved the relevant problem.

Continue reading →

Customers, users or fans?

Posted on by

The stuff I find most exciting is making something work for the users or to put it in more modern terms: people have a great experience when using something I helped create. So I focus on users and user experience. Some people rather talk about customers and customer experience. Whatever the name, it is basically the same isn’t it?

Continue reading →

UX in a burn-out system – UX Brunch in Zürich

Posted on by

At the UX Brunch in Zürich on December 6, 2019 Rahel and I held a presentation and some very engaged discussions on how we as UX professionals ourselves heat-up the burn-out systems we are caught in. Here is a summary including some of the slides of this session.

By Markus und Rahel *)

Continue reading →

Agile conversation or requirements engineering?!

Posted on by

Requirements engineering (RE) has a long and successful tradition. Different approaches always existed. Still it is optimized for an artifact driven setup: Individuals pass on documents. Agile practices are however geared for an interaction driven setup where individuals form one “super-brain”. The discussion about requirements is part of the agile conversation. And now, the proven approaches from RE suddenly create friction and bad smells. So, should we forget about requirements?

Continue reading →

Burn-out machine game @ agile breakfast in Zürich

Posted on by

On March 6, I had the opportunity to play the burn-out machine game with about 40 agile consultants in Zürich. We spent two hours with engaged discussions and insights about the very serious and highly relevant topic burn-out. We even had a good time doing so.
https://www.meetup.com/de-DE/Agile-Breakfast-Zurich/

Continue reading →

The team wall – or agile knowledge management

Posted on by

Here’s the situation: A customer asked us to improve the quality of their core system so that they again can act on the demands of their users and customers in a timely manner. We had a team room at our disposal and we again made extensive use of the walls. It turned out that the team wall made the difference!

Using the team wall has high impact on team performance.,
Continue reading →

Keep knowledge alive – living documentation

Posted on by

Keeping knowledge about a product alive is no easy task. Software teams struggle with manually mainting vast documentation in UML tools, text documents, wiki sites and more. We all know about the amount of effort and dedication needed to do this well given the amount of redundancy. There is a promising vision of a living documentation, i.e. a documentaiton automagically created from those things the teams create anyway, like automated and manual tests, backlog items, meeting protocols and more.

Continue reading →