Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,096
Community Members
 
Community Events
168
Community Groups

New Feature versus Story

Team I am supporting is using New Feature > Story as their hierarchy to deliver on work. They are gross-estimating for purpose of PO prioritization at Feature level and then teams breakdown Features into Stories; and estimate on actual work. 

**What is considered features in this case IS NOT really features - they used it "simply because".**

Since estimates are at both Feature & Story level, the story points are a summation however really the Feature shouldn't have any story points. I am concerned that the various Reports are representing incorrectly. I also find it difficult to visualize the parent>child relationships since Jira doesn't view it that way. Can use some sound boarding on this approach.  What does everyone else do? 

1 comment

Hi Simran,

I would consider changing either the New Feature to an Epic, or the stories to subtasks. This should help you with the parent child visualization and give your tasks a more natural progression through your process. 

Hope this helps,
Regan

Comment

Log in or Sign up to comment