#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