1

In my team, we often complete an MVP feature, i.e. MVP for Authentication. It has all the stuff it needs to be compliant and work, and meets the definition of done.

Then somewhere down the line, someone asks for something else, i.e. log out after x seconds. This is a single user story, which fits under the feature of 'Authentication'. I have usually by this point closed that feature and marked it as done, since it has met the definition of done. It doesn't seem right to add this new story under a closed feature.

So do I create a new feature for this one user story? How would you guys manage this small amount of incremental work in your backlog?

2
  • 2
    Why do you need to add it to a feature? For some kind of tracking? If we knew what you use it for, it might be easier to suggest a solution. – nvoigt Apr 21 at 10:03
  • Usually we have features of functionality that can be delivered and released together. It's more a question of if there is a best practice. I have bugs and new stories which fall under the 'feature' of Authentication, but I am often leaving them unparented, or creating new parents just for that content, in Jira or DevOps. – Johnny Apr 21 at 10:22
0

I would suggest your Definition of Done should apply to the story, not the feature. If your feature is Authentication then presumably that can never be completely done because there could always be a future defect or enhancement raised under the heading of authentication. Assign stories to features if you like but don't treat features as done.

0

Use Tags or Labels for Functional Areas

Your team is misusing the term "feature." What you should be doing is treating the various aspects of your application domain (e.g. authentication) as components, functional areas, or concerns. This allows you to tag or label features, epics, stories, or tasks appropriately within an agile context.

By creating a separation of concerns within your backlog or tracking software, you avoid the overhead of creating new "features" with the same (or similar) names just to hold stories or tasks, and the anti-pattern of re-opening completed work items.

0

When working "Agile" and "Lean" we should eliminate waste, e.g. reduce administration.

So do I create a new feature for this one user story? How would you guys manage this small amount of incremental work in your backlog?

If there is no reason to add more administration, you should not. This sounds like a "git commit" and a "Pull Request", and then merged and deployed to production. You have audit in the good commit message where you clarify why this was done.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.