5 Reasons To Avoid Analysis in Advance

#97. I share five reasons why I think you should avoid analysis in advance when you're building Dynamics 365 and Power Platform applications.

My five top reasons:

Peak ignorance. You're analyzing the requirements during the period when your stakeholders know least about Microsoft business applications and your analysts know least about their needs.
Priority categorization. Your requirement specification doesn't order the requirements by business value.
Over-engineering. Your requirements are likely to lead to over-engineered complexity and a rejected user experience.
Wasted effort. You're spending time chasing the illusion of completeness and putting yourself at risk of a significant change that will derail your requirements specification.
Opportunity cost. By deferring deployment you're deferring the benefits, and costing your organization money.

Resources

Support the show

CONNECT
🌏 Amazing Apps website
🟦 Customery on LinkedIn
🟦 Neil Benson on LinkedIn

MY ONLINE COURSES
🚀 Agile Foundations for Microsoft Business Apps
🏉 Scrum for Microsoft Business Apps
📐 Estimating Business Apps

Keep experimenting 🧪
-Neil

0 Votes: 0 Upvotes, 0 Downvotes (0 Points)