better planning estimation options

suvarna dixit April 8, 2024

 

1) Time spent in each sprint
   --  Orginal estimate
         a) Dev task  b) QA task
   ---  Actual efforts
         a) Dev task   b) QA task
This gives how much deviation from orginal to acutal by dev and QA.

 

2)  User stories added after sprint start date in current sprint.

 

3) Estimates in actual hours ( currently in Jira it is like X WEEKS Y DAYZ Z HRS)

 

4) Time spent at story level by Dev and QA including defect fixes.
( Assume story cbc-123 estimated 10 dev hrs and 20 QA hrs, after story completion we realize that 15 dev hrs and 40 QA hrs are spent.  Out of these 5 dev hrs and 20 QA hrs are bug fixes related to that story.   

 

1 answer

0 votes
Rebekka Heilmann _viadee_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 8, 2024

Hi @suvarna dixit 

what is your question exactly?

suvarna dixit April 10, 2024

Is there any Jira version where we can have above features , or else I have to create few customized calculated fields to showcase difference between actual vs planned efforts

and how can we found User stories added after sprint start date in current sprint..

 

 

Suggest an answer

Log in or Sign up to answer