#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
• Scrum.org (https://www.scrum.org/)
• Customery Academy (https://customery.academy/)
• Amazing Applications podcast page on LinkedIn (https://www.linkedin.com/company/amazing-apps-show)
• Amazing Applications podcast page on Podchaser (https://podchaser.com/amazingapplications)
• Scrum for Microsoft Business Apps online course at Customery Academy (https://customery.com/scrum)
• Agile Foundations for Microsoft Business Apps free online mini-course at Customery Academy (https://customery.com/foundations) Support the show (https://buymeacoffee.com/amazingapps)
CONNECT
🌏 Amazing Apps (https://amazingapps.show) website
🟦 Customery on LinkedIn (https://linkedin.com/company/customery)
🟦 Neil Benson on LinkedIn (https://linkedin.com/in/neilbenson)
MY ONLINE COURSES
🚀 Agile Foundations for Microsoft Business Apps (https://customery.com/foundations)
🏉 Scrum for Microsoft Business Apps (https://customery.com/scrum)
📐 Estimating Business Apps (https://customery.com/estimating)
Keep experimenting 🧪
-Neil
