As a project manager or product owner you may want to plan and track development of 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 approaches on 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
If your project is not so large and lasts for 2-3 months, you may want to release the Features for both your applications synchronously, in the same order and (almost) without delays. In this case Features and higher Epics can be kept within commonly shared backlog.
Features and User Stories are primary hierarchical levels in this setup, while Epics and Tasks can be considered as optional.
You may want to split work on your mobile clients on Project level or Team level. It depends on how many projects are your teams work on in the same time.
Platform-specific Projects
This configuration is recommended when each of your platform-specific teams is focused on single project only. Then you create:
- Common platform-independent project to track requirements on higher level (epics, features, releases, and requests)
- iOS project with iOS-related work items (user stories, tasks and bugs) and skilled developers
- Android project with Android-related work items (user stories, tasks and bugs) and skilled developers
You can start to plan your feature set by creation of the list of Features, Epics, and Releases in the common cross-platform project. Then inside each Feature for every requirement you should create related User Stories - one per each platform - and assign that stories to corresponding project. You may create and plan independent platform-specific Releases with nested Iterations as well.
Planning and Progress Tracking
You will be able to track your progress:
- In common platform-independent project: by Epics, Features. If you don't use iterations, you may also track the progress on Releases level
- In platform-specific projects: by Releases and Sprints (if you use single-project Releases), in Task Boards
Platform-specific Teams
This configuration is recommended when your platform-specific teams work on multiple projects in the same time. It is possible to form iOS and Android team and assign corresponding work to their responsible team. All backlog including high-level planning entities and requirements can be kept within single project.
Do not assign mobile teams to your Features and Epics in this setup. Assign only User Stories, Tasks, and Bugs.
It is possible to organize User Stories, Tasks, and Bugs related to a specific team with Team Iterations. Each team can have independent Team Iterations. Team Iterations are helpful as they can contain work items from multiple Projects.
Planning and Progress Tracking
You will be able to track your progress:
- In common platform-independent project: by Epics, Features. If you don't use iterations, you may also track the progress on Releases level
- In platform-specific backlog: by Team Iterations
This guide is a recommendation. Use it as a starting point, compare and test several 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