Should I split user stories on Frontend vs Backend tasks? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

Improve this question

While applying Scrum, the product backlog items are users stories. I have created a sample story on TFS as follows:

As a user, I can signup to system.

I then created the following tasks:

1. A login form should be prepared.
2. User should fill all fields on the form.
3. User should type a valid formatted email.
4. User passwords match between.
5. If user fills the form successfully, send verification email.

Some of the tasks are frontend (HTML, CSS, etc) and some are backend (send email, etc).

1. Should I separate the frontend and backend tasks one to another? And should I separate them into different User Stories?
2. Can the tasks be implemented by different developers?

Answer 1

1. No. Agile focuses on delivering working code to the customer. Without each part implemented the code written offers no value. Unless the tasks can be shown to offer independent value, then they should be kept together.

2. Yes the different parts can be implemented by different people. You need to make sure they coordinate appropriately so that the requested feature as works a whole.

Answer 2

It's all well and good honouring the communication point in Agile and expecting/advising devs to talk to one another, but if you wanted a certain degree of autonomy in terms of the relevant team member picking up the right ticket at the right time, you need to have a workflow that appreciates the componentised nature of product development.

In my head that sounds right...