- General
-
Ideas
0
Completed
archivate sprints
Hi,
As a Product Owner
i want to mange many the actual and future sprints
to be able to manage development of an long running software product.
i need soekind of visual marker for the actual in progress sprint.
And i want to archivate completed sprints (no direct access through tabbing or at least hiding of that sprints).
Currently i have 10 Sprints in my Backlog and there will be many more.
I need to manage my overview to clearly identify the current sprint and since there will be many more sprints i want to hide the completed sprints to make focusing on actual development easier.
Greetz
Roger
As a Product Owner
i want to mange many the actual and future sprints
to be able to manage development of an long running software product.
i need soekind of visual marker for the actual in progress sprint.
And i want to archivate completed sprints (no direct access through tabbing or at least hiding of that sprints).
Currently i have 10 Sprints in my Backlog and there will be many more.
I need to manage my overview to clearly identify the current sprint and since there will be many more sprints i want to hide the completed sprints to make focusing on actual development easier.
Greetz
Roger
Answer
0
Answer
Completed
Matthew O'Riordan (Founder) 12 years ago
Hi Roger
Can you take a look at the site now as we have implemented a marker for the current sprint. We tried a few variations, but ended up with this option as we think it's clear which sprint is current (white text with shadow), and clearly all sprints before are complete, and all after are not.
Can you tell me what you think?
Matt
Under review
Hi Roger
Apologies, but I am not entirely clear what you are after. Are you saying that you think the current sprint should have a marker to show that it's the current one when in backlog view? Is that so when you are looking at the backlog, you know which stories are currently being worked on?
Would a simple maker suffice, or do you need more than that?
Matt
Matt
I need to know which one of the sprints is the current one.
Also i dont want the backlog to get messed up with tons of allready completet sprints so i want to archivate sprints. They shouldnt be visible as tabs then but still present in the statistics.
Another way to show you what i want to achieve.
Create a new Backlog,
Now add 20 Sprints to the Backlog.
And then imagine this is the product you are working currently on and then tell me which sprint is currently under development.
And then imagine you know that there will be at least 20 more sprints or maybe more.
That Tabview is not flexible enough to handle many sprints and gets messed up.
Does this help you to understand my point of view?
Also i dont want the backlog to get messed up with tons of allready completet sprints so i want to archivate sprints. They shouldnt be visible as tabs then but still present in the statistics.
Another way to show you what i want to achieve.
Create a new Backlog,
Now add 20 Sprints to the Backlog.
And then imagine this is the product you are working currently on and then tell me which sprint is currently under development.
And then imagine you know that there will be at least 20 more sprints or maybe more.
That Tabview is not flexible enough to handle many sprints and gets messed up.
Does this help you to understand my point of view?
Hi Roger
You have some great ideas there. We are thinking of introducing releases, which should solve your sprint archiving problem. The way releases will work is that you can put completed sprints into a release and you will no longer see those sprints in the tabs at the top, you will only see releases at the top, so you will have far less tabs.
In terms of your ideas about showing the current sprint, and which ones are complete, I think this is brilliant. We will either introduce colour coding so you know which ones are complete and which one is current, or use icons. We'll have to play around with this to see what works best. But either way, we'll definitely do this, nice idea.
When we get this working I'll drop you a line to get your feedback.
Matt
Always glad to help making a cool software even cooler :)
Releases would be so cool, i really looking forward to get hands on this!
Feel free to ask me, if u want an quick answer or simply want to hear my opinion feel free to e-mail me.
Releases would be so cool, i really looking forward to get hands on this!
Feel free to ask me, if u want an quick answer or simply want to hear my opinion feel free to e-mail me.
Hi,
i had one suggestion for Releases.
Could you add Stats per Release even for not completed Releases?
The goal i want to achieve is to get some estimated date for the completion of an Release (to make Release planning finally). I think about an Graphic like the current Burn Down where you can see an estimated finish date for the whole backlog.
i had one suggestion for Releases.
Could you add Stats per Release even for not completed Releases?
The goal i want to achieve is to get some estimated date for the completion of an Release (to make Release planning finally). I think about an Graphic like the current Burn Down where you can see an estimated finish date for the whole backlog.
Hi Roger
In response to your last comment about stats per release, that is something we would consider. However, we did not really consider how releases would work for live sprints, only as an after thought to group sprints into releases. When we introduce this functionality, I'll certainly consider this. Unfortunately release management is a bit of a way down our backlog so that won't be introduced very soon.
Matt
Matt
Under review
Hi Roger
Apologies, but I am not entirely clear what you are after. Are you saying that you think the current sprint should have a marker to show that it's the current one when in backlog view? Is that so when you are looking at the backlog, you know which stories are currently being worked on?
Would a simple marker suffice, or do you need more than that?
Matt
Matt
Answer
Completed
Hi Roger
Can you take a look at the site now as we have implemented a marker for the current sprint. We tried a few variations, but ended up with this option as we think it's clear which sprint is current (white text with shadow), and clearly all sprints before are complete, and all after are not.
Can you tell me what you think?
Matt
Hi Matt,
thank you Matt, this is enough for the goal i want to achieve with this feature.
Sure you can get more attention if u play around with colors but i dont think its neccessary.
This is just good enough, you see it when u look for it thats cool.
Roger
thank you Matt, this is enough for the goal i want to achieve with this feature.
Sure you can get more attention if u play around with colors but i dont think its neccessary.
This is just good enough, you see it when u look for it thats cool.
Roger
Great, glad that works. Shout if you have any other ideas, happy to consider them if they improve the user experience.
Customer support service by UserEcho
