TargetProcess3 has quite powerful multi-teams concept, but early beta release revealed some limitations. The main limitation is that you can't track functional sub-teams in a single project. That may sound like a waterfallish approach, but it is not in fact. There are many viable cases when this is useful (separate UX phase, separate deployment phase, etc.)
Another case is when several teams with different processes work on a single project. Imagine large projects with two development teams: Scrum and Kanban. Work split between these two teams, but we want to easily track progress on a project level.
The proposed solution will enable both cases above, but with a price of the system complication.
User Story (Bug, Feature, Task, etc) will have two states: Team State and Project State. Team State and Project State will have mapping to each other. Thus a single Team can work on several Projects with different processes:
On the image below in the center you see typical Project states. Left flow (column) is a Kanban team that does development. Right flow is UX team. You see that Project State is linked to Team State. Thus you can easily track high level progress when creating a board with Project State. And can track Team progress when creating a board with Team State.
Project State - Team State mapping allows some automatic transition. For example, if we change Project State from Open to UX Phase, then UX Team State will be set to New. Team Status is something lightweight, it can be setup easily and mapped to statuses in various projects (thus a team with a defined flow can work in several projects with different flows).
The one restriction is that User Story has a single Team Status. Thus only a single Team can work on a user story in any given state. For example, when UX Team is completed User Story design, this User Story should be moved to Development (Kanban) Team.
History is preserved, so it is known what teams worked on what user stories. However, history reports are complicated.
We don't expect to implement this solution in the next 4-6 months. Maybe more feedback will get us more ideas to improve multi-teams support. If you see any problems with the solution above, please share them.















































