Seperating stories into API and Frontend tasks

David Carr

I'm wondering when you have a project that has multiple environments like an API and a frontend website that have different teams. How do you split user stories up?

 

For example, a user story to create a team requires API endpoints and user interface on the front end.

I would normally create a user story for Create team and then 2 sub-tasks.

User story: Create Team

      Task 1) - API create an endpoint

      Task 2) - front end team create the user interface

 

Each sub-task has their own time estimates

 

Curious how other teams approach this.

 

Nic Brough -Adaptavist-

Your approach doesn't work if you're doing anything like Scrum or Kanban.  A sub-task is part of its parent story, and as such, shouldn't be assigned to anyone outside the team that the parent story belongs to.

In your situation, the better practice is to create two stories, one for each team, and link them together to indicate that the teams probably need to talk to each other about it, or that one depends on the other being done.