Hello,
Do we have any kind of conversion factor or multiplication factor that can convert user story points into some business recognizable unit such function points(IFPUG/Cosmic function points) or person days. I have aleady read an earlier post that talks about various factors such as complexity, implementaion language, skillset of workers etc. that might affect this relative coversion. However, I am particularly interested in knowing if there is a rule of thumb for such conversion?
Thanks,
Anshul
Hi:
The key is to have all of your stories be right size (relatively small - flow chart out on about a piece of paper) and equal size. You would then estimate for one story and then multiply this out by the total number of stories. Problem: Story techniques lack a mechanism to guide the BA through a partitioning which would result in such a "chunking".
Tony
Tony,
Thanks for your explanation, it makes a lot of sense. However, how will we consider complexity( development, implementation) while writing user stories? There could be a scenario where a user story is really short but tricky( read: really complex) from implementation point of view. I believe in such scenarios common estimation will not be useful.
Also, if you something else to share about estimating Agile projects, I would love to know about it.
Anshul:
To handlle complexity you need a different mindset. You need to focus more on the interrelationship between stories than is typically done. You can view user stories as data flow diagrams without the data flows.
brought to you by enabling practitioners & organizations to achieve their goals using: