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. Continue reading →
An important management tool to improve team performance is the Team Squeezer. It’s really simple: just use hierarchical power and exert pressure to make the development team hurry up. Usually the Team Squeezer backfires.
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.
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.
At the recent Agile Unconference in Zürich I came across the concept of lean agile procurement. The key insight for me was: forget preparing RFPs, rather establish a good relationship with a select list of partners.
If you never have had a look at the scaled agile framework, you may want to do so. It’s has some really good concepts in it. Still with all the enthusiasm I feel like being drawn back to the good old times of software engineering. And you know why?
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.
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.
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.