Faceted Feature Analysis - ein Weg zur fast objektiven Priorisierung von Funktionen 30Jul07

Screenshot: boxesandarrows.com

Adam Polansky stellt auf boxesandarrows.com einen Prozess namens "Faceted Feature Analysis" bzw. Facetten-Funktionsanalyse vor. Dabei beschreibt er 6 Schritte mit denen sich die Funktionen eines interaktiven Systems einfach und fast objektiv priorisieren lassen. Der Name bezieht sich auf die drei Sichten bzw. Facetten jedes Entwicklungsprojektes: Geschäftswert, Technischer Umsetzungsaufwand, Nutzwert, welche zur Priorisierung herangezogen werden.

Dieser Prozesses hilft dabei folgende Fragen zu beantworten:

• How can you make sense of ideas from multiple sources–formal requirements, brainstorm sessions, contextual inquiry, and input from the boss’s wife?
• How do you entertain all ideas and still weed out the good stuff from the garbage without hurting someone’s feelings–especially when that someone signs your check?
• How do you factor in real constraints and capabilities before these ideas become etched in stone?
• How do you take in the different points of view that come from a programmers or business owners, not to mention the actual users of your product?
• How do you do all these things and define project scope with some level of integrity that’s more than intuition or politics?

Die nachvollziehbaren Vorteile seiner Methode sieht er darin:

• Increases objectivity. You are leveraging individual bias to generate unbiased feature rankings. This occurs because participants are limited to rating features only from the perspective of their areas of expertise and using overriding, agreed-upon constraints, rather than personal influence, as the means of emphasis.
• Assists in project planning. Scope and estimates provide the basis for a traditional project Gantt chart or the backlog that will feed an Agile iteration plan
• Mitigates churn. This process greatly reduces the second-guessing during development that may occur when features have not been pre-qualified. There are fewer surprises downstream.
• Minimizes politics. A feature rises or drops in the list on its own merit as it relates to the project constraints, not because anyone knocked it down or ram-rodded it to the top. (This can still happen but it’s harder to do without obviously and publicly disregarding the point of the exercise.)

Siehe auch:

Faceted Feature Analysis