April 20, 2020
Estimated Post Reading Time ~

Pointing Map while Development

Point Estimate DescriptionEffort EstimatePoints
Defects and incident response0 – 8 hours 3 pts
Well known work0 – 8 hours 3 pts
Somewhat well thought out, maybe risky or in high critical area
Simple change but in an area of code that this known to be spaghetti so more regression testing will be needed since change in one place often can make something else fail
Complex business rules involved
Large amount of data creation and staging needed
9 – 24 hours5 pts
Not quite as well known
Integration, 3rd party (data being pushed/received from another team)
25 – 40 hours8 pts
Work that has never been done before
Any user story initially sized al XL should be decomposed to smaller, more manageable stories
40+ hours13 pts

While pointing, we'll see the estimate for both Dev & QA effort for a story in terms of hours. For example, for a particular story, an individual thinks that development will take 10 hours and testing effort will be 5 hours. The total will be 15 hours which will be 5 points. This individual points 5 points for this story.
If a story is pointed as 13 points, then we would decompose it into smaller ones.


By aem4beginner

No comments:

Post a Comment

If you have any doubts or questions, please let us know.