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:
- How can we explain story points to stakeholders?
- What are the advantages of story points?
- Aren't story points equivalent to time?
- When should we estimate backlog items?
- How often should we update our estimated velocity?
- How should we report our velocity to our stakeholders?
- Should we fill up our sprint backlog up to our estimated velocity?
- When should we split epics or features into stories?
- Should we estimate bugs?
- Should we estimate non-functional requirements?
- Should we estimate sub tasks?
- How do we get quicker at estimating?
- When should we re-estimate stories?
- Why does the whole team need to be involved in estimating?
- How does estimating work with multiple teams?
- How do we prevent estimate inflation?
- Can we compare teams' velocities?
- Can we track the velocity of individual developers?
- How do we reach consensus when our estimates are different?
- 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.