Estimating Business Applications

Zenler Player

Your course is loading. Hang tight.

How much and how long? (4:07)
Why are estimates notoriously inaccurate? (4:09)
Estimating time doesn't work (4:32)
Estimating t-shirts doesn't work either (1:07)
Estimates, forecasts and commitments (2:33) Preview
Estimating quiz

Slicing stories (3:42)
Setting a standard story (2:07)
Affinity estimation (2:27)
Planning poker (2:33)
How long will it take? (3:44)
Estimating requirements quiz

Estimating applications (6:19)
Project estimation workshop (8:00)
Estimating initial velocity (5:00)
How much does it cost? (4:56)
Visualising your estimates (7:26)
Estimates in sales proposals (5:20)
Fixed-scope, fixed-price, fixed-date estimates (6:18)
Estimating projects quiz

How can we explain story points to stakeholders? (2:29)
What are the advantages of story points? (2:32)
Aren't story points equivalent to time? (1:19)
When should we estimate backlog items? (2:03)
How often should we update our estimated velocity? (0:51)
How should we report velocity to our stakeholders? (1:27)
Should we fill our sprint backlog up to our estimated velocity? (1:21)
When should we split epics or features into stories? (1:54)
Should we estimate bugs? (1:46)
Should we estimate non-functional requirements? (2:29)
Should we estimate sub-tasks? (1:24)
How do we get quicker at estimating (4:01)
When should we re-estimate stories? (2:41)
Why does the whole team need to be involved in estimating? (1:27)
How does estimating work with multiple teams? (2:22)
How do we prevent estimate inflation? (1:58)
Can we compare teams’ velocities? (1:09)
Can we track the velocity of individual developers? (1:09)
How do we reach consensus when our estimates are different?
How do we create perfect estimates?

Lesson contents locked