0

Scenario:

1 online shop running on multiple platforms:

  • desktop
  • mobile web
  • mobile app iOS
  • mobile app Android

there are common functionalities but platform specific too.

Which is the recommended approach to handle this scenario? Can be a backlog for common functionalities and sub-backlogs for platform specific features? Do we have 1 or 4 products?

  • 1
    Do you have to run the platforms in parallel? Can you work sequentially? iOS first, Android, Desktop etc.. – Venture2099 Apr 10 '18 at 15:57
  • Not necessary in parallel, for example we will launch initially all platforms together but as a second steps both mobile apps will be reimplemented using a different technology. – Marta V. Apr 11 '18 at 6:30
  • Possible duplicate of Mobile Application Scrum team - maintaining two apps – Alan Larimer Apr 12 '18 at 12:01
  • One Product Backlog per Scrum team. Period. Do you have more than one team? – Todd A. Jacobs Mar 2 at 16:44
2

Of course, you have one product because you have shared parts, that means you have shared resources, scope and other objectives, therefore, they would have a strong relationship with each other. So the best practice in your case is to have one backlog and one working process for all your tasks.

To differ them, you can:

  • Have a prefix in the name of the task, for example [Desktop]
  • Have a tag for the task
  • Have a color label for the task

You can create sub-backlogs too, but I don't recommend this because it depends on your working process, so you should answer those questions for decision making:

  • Will you duplicate tasks or just move them from the main backlog after, for example, grooming meeting?
  • Will different parts of the team work properly if tasks placed on different backlogs?
0

For me it's one and the same backlog and one and the same product and I assume you have all the items in the same roadmap. There should be also backend part, which is shared by apps, e.g. API. To clearly see the dependencies(e.g. 'need this endpoint to update email from the app') it makes sense too keep all the issues under one roof. Also most likely you'll release one and the same feature simultaneously(or with a short interval) for all the platforms, which makes Business Analyst work by a feature, and not by a platform. But sure it' mandatory to tag or to label or to somehow mark to which platform each issue is related.

0

Product backlog items will initially contain all requirements as a user stories, and we know that the user story is high definition of each user requirements, in addition there will be a test cases design for each platform requirements, every test case will check the happy and bad behaviors for the application, which may lead to specific test-environment configurations for each platform. as "Tanya R" said, you can "add a prefix in the name of the task, for example [Desktop]". make your development driven by user acceptance test, imagine what these test would be, surely end-user will verify for his android, ios... ,so make that verification as a requirements in the PBIs.

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.