5 Reasons To Avoid Analysis in Advance

Neil BensonPodcasts4 years ago75 Views

#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

Original Post https://amazingapps.show/97

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

Leave a reply

Join Us
  • X Network2.1K
  • LinkedIn3.8k
  • Bluesky0.5K
Support The Site
Events
October 2025
MTWTFSS
   1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31   
« Sep   Nov »
Follow
Search
Loading

Signing-in 3 seconds...

Signing-up 3 seconds...