Re:The rise and fall of the dungeon master on software projects
by giovannibajo1 on Wednesday June 01, 2016 @04:44AM
(#11812914)
It's also true that 90% of users only need 10% of the features of your software. If you decide to drop some features that introduce huge complexity that is not apparent, you might find out that users don't really need (anymore? ever?) that feature in that form, and you might make them achieve the same goal through a different features set that doesn't affect the architecture and code complexity that much.
[ Parent
| on HN ]
Re:The rise and fall of the dungeon master on software projects
by WorldMaker on Wednesday June 01, 2016 @01:43PM
(#11816503)
You just have to beware the corollary that not all users use the same 10%.
Re:The rise and fall of the dungeon master on software projects
by rubbsdecvik on Wednesday June 01, 2016 @08:37AM
(#11813854)
Sure, but consumer/customer re-education is required and usually underestimated. Attrition due to change is a real thing.