5. Amazing Estimates for Power Platform and Dynamics 365 Teams

Estimating Business Apps

Welcome to Estimating Business Apps episode 5. This is the final episode in the Estimating Business Apps podcast mini-series.

In this episode, I introduce the final section of the Estimating Business Apps course.

Join me as I answer 20 frequently asked questions about how my teams estimate Power Platform and Dynamics 365 applications:

1. How can we explain story points to stakeholders?
2. What are the advantages of story points?
3. Aren't story points equivalent to time?
4. When should we estimate backlog items?
5. How often should we update our estimated velocity?  
6.  How should we report our velocity to our stakeholders?
7. Should we fill up our sprint backlog up to our estimated velocity?
8. When should we split epics or features into stories?
9. Should we estimate bugs?
10. Should we estimate non-functional requirements?
11.  Should we estimate sub tasks?
12.  How do we get quicker at estimating?
13. When should we re-estimate stories?
14. Why does the whole team need to be involved in estimating?
15. How does estimating work with multiple teams?
16. How do we prevent estimate inflation?
17. Can we compare teams' velocities?
18. Can we track the velocity of individual developers?
19. How do we reach consensus when our estimates are different?
20. How do we create perfect estimates?

The Estimating Business Apps is a companion podcast to my Estimating Business Apps online video course.

Using the discount code in this episode, you can register for the Estimating Business Apps course here:

https://events.humanitix.com/estimating-usd

And my Successful Scrum for Microsoft Business Apps course here:

https://events.humanitix.com/scrum-usd

Thanks for your support. Your support for my paid courses helps me keep creating free content.