#53. If you're building Microsoft Dynamics 365, Power Apps, Power BI, Power Automate or Power Virtual Agent applications, when and how should you be estimating your requirements, releases and applications?
Check out part 2, Estimating how long and how much (http://amazingapps.show/1127783/5122228-estimating-how-long-and-how-much) , to discover more about forecasting how long it's going to take and how much it's going to cost.
For full show notes and transcription, visit: https://customery.com/002
• We need to estimate our requirements for two reasons: time and money
• We don't always need to estimate our applications, but exceptions are rare
• Accuracy and precision are different things
• Estimation is not a one-time activity and should be repeated
• Are we estimating effort or complexity or something else?
• Ideal time, story points and t-shirt sizes
• My recommended estimation unitsSupport 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
