TAG: EstimationPractice

Establish a "done" definition for a story to be READY for the team	2016/06/16 08:57	Hans Peter Samios
Establish a "Things That Matter" Matrix	2016/06/16 09:33	Hans Peter Samios
Establish a Keystone User Story	2016/06/16 09:11	Hans Peter Samios
Establish Points Guidelines for Each Point Value	2016/06/16 09:15	Hans Peter Samios
Establish Typical Sizes for Typical Work	2016/06/16 09:28	Hans Peter Samios
Estimates Are Based on Current Knowledge	2016/06/16 10:21	Hans Peter Samios
Give Default Estimates for Classes of Work and Then Work Exceptions	2016/06/16 09:42	Hans Peter Samios
If It Involves Work, Then It Should Have a Non-zero Estimate	2016/06/16 09:53	Hans Peter Samios
Only Use Fibonacci Sequence Numbers	2016/06/16 09:59	Hans Peter Samios
Review all the 5s to see that the represent the same relative size of work	2016/06/16 10:04	Hans Peter Samios
Split Every Story Until It Represents a Small Common Size	2016/06/16 10:09	Hans Peter Samios
Team Has Right to Reject Stories for Estimation That are Not READY	2016/06/16 09:00	Hans Peter Samios
Track "Accuracy of Commit" Metric	2016/06/16 10:30	Hans Peter Samios
Track "Adopted Work" Metric	2016/06/16 11:10	Hans Peter Samios
Track "Found Work" Metric	2016/06/16 11:14	Hans Peter Samios
Track Accuracy of Estimate Metric	2016/06/16 10:58	Hans Peter Samios
Use Ranges to Understand Risk	2016/06/16 11:04	Hans Peter Samios