REQ: Assign priority to tasks & view the active sprint for every project in 1 view.

[MaH Relinace]

Hello,

Complements on taiga! We loved it instantly and are thinking of using Taiga for our Agile process.

There are 2 things we are missing, if they could be added our satisfaction would be complete:

1. Assign priority to tasks. The priority should be visible and changeable in the sprint taskboard and in the task details screen.
   
2. We would like a view where the active sprint of every project is visible.
   

Our reasons:

• We have a user that will be a stakeholder in every project, in our weekly meeting we would like to show all the active sprints at once and discuss priorities, without having to switch between projects.
• This stakeholder usually considers everything to have the top priority and everything should be finished rather yesterday then tomorrow. By having all tasks in one view, we hope to help him make more realistic choices. If we discuss this per project, instead per team (we have one team so the overall overview for us is the same as a team overview), we might not have enough manpower to pick-up all the tasks he specified.

We are currently using the version hosted by you @ tree.taiga.io.

Thanks in advance,

Maarten.

[Alejandro Alonso]

Hello Mah,

Thank you very much for your feedback and for using Taiga.

I'm adding your requirements as possible enhancements for Taiga, they sounds good but we will have to study if it's possible to develop them in the Taiga core

Regards!,

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/f87ed27f-4321-4e56-93c9-6a10a18692e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alejandro Alonso Fernández   CIO & Co-founder alejandr...@kaleidos.net  | Tel: (+34) 627263808 | (+34) 913562995 www.kaleidos.net/FC8EAC/

[MaH Relinace]

Alejandro,

Great!
Since we have one team, multiple projects and always use the same sprint length. Maybe this view can also include a sprintpoint slider per project. So we can decide every week how much effort or manhours will go to which project.
Is this a clear description, or should I explain it in more detail?

Regards,

Maarten.

Op woensdag 21 januari 2015 14:21:03 UTC+1 schreef Alejandro Alonso:

[Alejandro Alonso]

It would be great if you could explain a bit more the part of "sprintpoint slider per project" :)

Thanks! 

[MaH Relinace]

Now I have thought about it more, I realize the name sprintpoints slider is wrong. Maybe it should not be a slider and they should be called team points.
Also to make this work priorities should not be assigned to tasks, but user stories.

On a per project basis, in the backlog, Taiga gives a good representation of amount of effort/time by showing the closed/pending/excess points image and next to it the project, defined and closed points. (This part has a grey background, I will refer to it later as the dark grey project bar.)
Below that the graph showing the amount of sprints, the progress of closed user stories and the progress of user stories being created by defined points.
Even doomline warnings per user story. etc.

It also gives a great insight on a sprint basis with the sprint board.

The overview of the active sprints per project would be an extra layer around that, which shows the projects per team and team status/capacity. We have only one team, but I imagine other parties can have multiple teams working on multiple projects. Sharing projects between multiple teams is not what I suggest. But a structure where the department contains teams, that contain projects, that contain userstories, that contain tasks.

So taiga could show the active sprintboard of project C, above that the dark grey bar project C, above that the same items for project B and A.
Now we had a great overview of the project activities, it's status and have seen the US prios.
Above all this Taiga could give insight in team points and let us set how many team points per project for the upcoming sprint. (We will have the same sprint lenghts for all projects, but maybe for general use the "for the upcoming sprint" part should be omitted.)

Then there would be 1 screen that we can use for the weekly meeting with the stakeholder or it could be just with the team leader or CEO. First show the progress of the projects, then decide on how to divide the team points between the projects, hereby deciding how much time is spent on each project. Before or after the meeting the stakeholder can give prio's to user stories.
This will enable us to spend our time on the most pressing matters and do what is needed most first.

Thank you for your time and attention.

Regards,

Maarten.

Op donderdag 22 januari 2015 14:52:11 UTC+1 schreef Alejandro Alonso:

Thanks! 

--

www.kaleidos.net/FC8EAC/ - private  - private

[Alejandro Alonso]

Thank you very much Maarten,

I think I fully understand your needs and your idea now :)

You wrote " But a structure where the department contains teams, that contain projects, that contain userstories, that contain tasks", it's very similar to our idea of how organizations could work inside Taiga. When we implement this part it could make sense to add this proposed visualization to that level. I'm adding this conversation to our Taiga project so we can follow your suggestions when we start working in this part.

Regards,