Agile requirements?!

Requirements engineering (RE) has a long and successful tradition. While different approaches always existed, RE became optimized for an artefact driven setup where the individuals hand-over documents. Now agile practices spread. They  are geared for a team setup where individuals form one “super-brain” based on intensive interaction. The proven approaches from RE suddendly create a lot of friction and bad smells. So, should we forget about requirements?

Agile conversation: from idea to sketch to increment to product

Continue reading

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

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

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

Meet with user to create great products

Even though – as a UX professional – I must stress the importance of meeting users, I have to admit that the title of this article is not exactly accurate and just meeting users is not really the point. Having revealed this, I should probably explain what really matters when meeting users and give some indication on how to do it. This article covers two stars to road essentials: the UCD cycle and the UX levels.

Continue reading

Bill & Chuck – and how they fight ideas into the market

Let me introduce two characters, Bill and Chuck. To be honest, they are personae distilled from people you could meet. They are especially interesting because of their behavior: Instead of collaborating to let ideas compete they fight to get their ideas into the market. And sadly, they have good reasons to do so.

Continue reading

Five or one guidelines for the minimal viable product

In our current project, we use an approach of the minimal viable product and we steer it with the story mapping technique. From the discussions in our team, here are five guidelines (or just one?) for such an endeavor to ensure a better work-life-balance.

LifeBalance - LeadIn

Continue reading

User experience flow from stars to road

Companies, not surprisingly, want to make business. New products are not created just for fun but they should contribute to this overall plan. For that, a performing team combining a couple fields of expertise is an excellent asset. Each of these experts brings in their respective methodology. The article agile innovation from stars to road outlines a basic collaborative structure. This article is about the methodology from user experience.

UXFlow_LeadIn

Continue reading

User story shopping – a sports event management system

The challenge awaits our project: How to deal with the many expectations from our customers that are far beyond the project budget? The answer in my current project – the sports event management system – is based on user story mapping. 

Continue reading

What if there isn’t a product owner?

Scrum defines three roles: product owner, team, and scrum master. It is actually very simple. And for the team it’s great to have one person – the product owner – to deal with the really difficult stuff. That is the VVIP, the users and why the whole thing just will make money in the market.

ConversationLeadin

Continue reading

grok – negotiate – build up

In our current project, a software for managing sports events, user stories play an important role when it comes to development. Interestingly the focus of the requirements conversation changed completely from one level of maturity to the next. And there is a pattern behind it, as it seems. It leads to story mapping.

StoryMapping_Leadin Continue reading

What is a requirement? A probably agile answer

Requirements focus on value. This at least is the name of a category for this Blog. But what are requirements anyway? If you know the answer, fine. But for all those that are as confused as I am, this article gives the ultimate answer, or hopefully one as helpful as 42 was for Loonquawl and Phouchg.

GlassLaw_Leadin

Continue reading

A case for features – a sports event management system

Currently, I’m involved in a project to develop an event management system for large sports events. The goal is to replace a few existing systems with one integrated system that is able to cater for the coming needs. End of elaboration is closing in and we’re planning for the incremental delivery to follow during construction. 

SportsEvent_BalanceActLeadin

Budgeting, estimation and release planning all turn around features (Part 2).

Continue reading