Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Managing stories with front end and backend

Hi champs,


I have stories those involved front end and backend development. Wanted to understand the best approach

Approach one - Create a single user story that aligns with the INVEST criteria. Create 2 sub tasks, one for Front end and one for Back end. You are free to assign each sub ask to different developers


Approach 2 - Create 2 different stories, one for Front end and one for Back end and assign these to different developers

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 06, 2023 • edited

Hi @Abhijit Kulkarni 

What problem are you trying to solve?  Knowing that may help the community to provide better suggestions.  Thanks!

And...IMHO there are no "best practices", only better and worse ones, depending on what you are trying to accomplish and how the team collaborates.

For example, if your team is trying to use agile ideas of reducing WIP and focusing team capacity on delivering value, a third approach would be to use one user story.  The team may swarm as they can help (e.g., FE dev, BE dev, etc.), perhaps pairing and mobbing to spread knowledge, reduce rework, and together complete the request sooner.  Then who is assigned to which pieces is less relevant as the team is delivering value.

Kind regards,

Thanks a lot! That really helps

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events