Es una técnica/modelo de priorización en cinco niveles para *features* de un producto. A mí me gusta mucho usarlo para requisitos funcionales. ## Los cinco niveles son: - **Must-be:** The customers consider the product functional only if these features are included. - **One-dimensional:** These features have a dual nature. While they aren’t a must for a product to work, they remain extremely desirable to customers. The category is closely related to foreseeing customer needs and expectation. When a product includes what customers would be happy to get, they stay satisfied. But if you fail to deliver them, users are more likely to experience disappointment. - **Attractive:** Features in this section add extra satisfaction, or even enjoyment and gratification. Basically, they are unexpected but nice-to-have features. On the other hand, their absence doesn’t leave customers dissatisfied. - **Indifferent:** The attributes here represent the least possible impact on customers satisfaction. In a nutshell, they have no value. - **Reverse:** The features falling into this category are considered to be the most annoying. Their presence has a rather negative effect on customer satisfaction. Alternatively, when they are not introduced, customers consider it a plus. ## Resumen en español: 1. Must-be: aquello que tiene que ser si o si. Hay que ser estricto; realmente tienen que ser cosas que si no se hacen, el proyecto no sirve de nada. 2. Uni-dimensional: si se hace está bien. Si no, está mal. 3. Atractivo: si se hace está bien. Si no, da lo mismo. 4. Indiferente: da lo mismo si se hace o no. 5. Reverso: es malo si se hace.