Why is it important?

- Currently, many of our projects…experience a large amount of rework and waste,…things like defects, missed requirements,…scope creep, over-engineered features,…and frustrated users.…This rework is often due to elicitation and analysis…not happening or not happening well on projects.…I find that rework is typically a result of moving forward…to development without really knowing…what the true needs and scope are.…Teams often forge ahead without much consideration…for discovering and analyzing what aspects…of a solution matter to the customer.…

Without the needed layers of discovery and analysis…to get it right, we often build the wrong thing…for our customers.…For example, any retail organization can build…a mobile shopping experience, and that might be…what the stakeholder asked for.…But how do we really know what experience…and the details of it will serve the customer…and the organizational strategy the best?…Just because it's a mobile shopping experience…doesn't mean that it actually serves the needs…of the customer and aligns to the strategy.…