Platform-specific Tasks under common User Stories | User Guide

Platform-specific Tasks under common User Stories

As a project manager or product owner, you may want to plan and track development for several versions of the same project, or support your product for multiple platforms. It is possible to track platform-specific project activities in Targetprocess. In this article, we describe one of the possible approaches to how hierarchical mapping between your actual data structures and entities in Targetprocess can be configured. Other recommendations and best practices can be found here: Use Case: Platform-Specific Backlog

In this setup, the whole backlog is kept under the same multi-platform project. Tasks are platform-specific. This approach works best for very short projects with a minimal number of functionalities. If your whole project can be finished within a month or even few weeks, and you would like to complete User Stories in the same order and as synchronously as possible on every supported platform, you should consider this workflow.

Platform-specific Tasks under common User Stories. Image 1

User Stories and Tasks are the primary hierarchy levels in this setup, while Bugs and high-level planning entities (such as Features and Epics) can be considered as optional.

For instance: for each User Story, you may want to create one or more pairs of Tasks:

  • Design for the iOS client
  • Design for the Android client
  • Code for the iOS client
  • Code for the Android client
  • Tests for the iOS client
  • Tests for the Android client
  • ...and so on

You can distribute Tasks to responsible platform-specific developers by using personal assignments.

Platform-specific Teams

If you have several developers for each mobile client, it is possible to form iOS and Android teams, and assign corresponding Tasks to their responsible team. This use case is helpful when every team works on multiple Projects at the same time.

Platform-specific Teams

Do not assign your User Stories to platform specific teams in this setup. Only assign only Tasks and Bugs.

A team can plan and organize their work with independent Team Iterations.

Platform-specific Teams. Image 3

Team Iterations are helpful because they can contain work items from multiple Projects.

You will be able to track your progress:

  • In common platform-independent projects: by User Stories, by Releases and Sprints, and in Release and Sprint Burndown charts
  • In platform-specific projects: by Tasks, by Team Iteratons, in Team Iteration Burndown charts

The following features can help you to the automate creation and assignment of Tasks:

This guide is a recommendation. Use it as a starting point before testing and comparing other approaches. And let us know which workflow suits your needs best!

Still have a question?

We're here to help! Just contact our friendly support team

Email us
The more details you can give us the better
Live chat
Prefer instant messaging? Try our live chat
Service Desk
Add tickets, comments and track status in our Helpdesk
Slack Community
Shape the future direction of Targetprocess

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.

Start your free trial

Enter your email
By clicking "Continue", you acknowledge and agree that we will process your personal data in accordance with our Service Privacy Policy and Terms of Service.

We’ve sent you a confirmation e-mail — please, go check it.

Or get a live
product demo