Imagine that you have an intellectual production - you create and maintain websites.
For the customer, the task of developing the site is the functional requirements and wishes written in free form; for you - a lot of work, including:
graphic and / or information design;
testing and etc.
It turns out that there are different levels of representation of the same business value and, as a consequence, different levels of detail.
In our system, the customer can be invited to the workspace with the summary board and work with him together on functional requirements, and the team will work on the subtasks in their boards where the customer will not have access.
This access structure in our demo-company without authorization:
1. Working space for stakeholders, epics level
Here the summary board is "Development"
2. Working space of the 2-nd level, where work is underway on the project
Click on the menu on the left to see cards from the summary board
From this sidebar, performers drag tasks onto their boards.
The advantage of summary boards is that cards move across them automatically. When at least one child task is moved to the In Progress column on the Executive Board, the parent card is moved to the second column of the summary board (usually called In Progress).
When all child tasks are in the Done columns, the parent card is moved to the final column of the summary board.
Thus, the customer always sees the current status of work on his project without any effort on your part.