This project management system design has several unique features:
(Note: while the hierarchy documented here is Epic-Project-Task but it can be any alternate hierarchy eg Project-Workproduct-Sprint and the it is not limited to 3 levels)
- Establish a Project Management Office (PMO) on the main board to seamlessly coordinate with multiple team boards and distribute tasks by relocating Project cards across different team boards.
- Allow Project cards to be generated directly from any card without requiring an Epic card. This flexibility enables the main board to incorporate any card into the management system seamlessly.
- Additionally, enable Project cards to be linked to Epic cards, streamlining the organisational hierarchy.
- Include the parent card's name in the Project card's title to provide users with clear context regarding the parent-child relationship, eliminating the need to delve into card details.
- Implement a standardised naming convention to facilitate the smooth movement of Project cards across various lists on team boards, such as Inbox or Urgent lists.
- Ensure that task completion updates are reflected on the parent Project card across all participating boards, fostering transparency and accountability.
- Similarly, ensure that Project completion updates are reported to the parent Epic card, if applicable, across all participating boards, enabling comprehensive tracking of project progress.