Sprints
Sort by:
Trending
Status:
Future consideration
Showing 29
5
VOTE
Allow multiple assignees on Features and requirements
What is the challenge? Many teams have more than 1 person working on something. For example a couple of devs and a tester could be working on a complicated feature together. We currently can't do that. Additionally for performance reviews it's nic...
0
Future consideration
3
VOTE
Restrict ability to open or close sprints
What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...
1
Future consideration
2
VOTE
Have a place to store the sprint goal
What is the challenge? It's very common for teams to have a sprint goal as an aid to sprint planning and an aid to keeping the sprint focussed What is the impact? Sprint planning is a little less focussed without it and the goal of the sprint is s...
0
Future consideration
1
VOTE
Sprint start and end dates should not overlap
What is the challenge? When I create a new sprint the start date, is the same date as the end date of the last sprint. What is the impact? I have to change the date to the next day. Describe your idea Add one more day to the start date of the next...
0
Future consideration
2
VOTE
Bulk edit remove records from sprint
What is the challenge? Currently you can use a bulk edit to assign records to a sprint but you cannot bulk remove records from a sprint. What is the impact? You cannot remove a large number of records from a sprint easily. Describe your idea Updat...
0
Future consideration
5
VOTE
Allow customization of sprint dates when generated by a Program Increment (PI)
It's great that it's possible to auto-generate sprints based on the PI that they belong to. However, there are times we need to adjust the dates of sprints based on various factors, such as holidays. It's not currently possible to adjust the sprin...
0
Future consideration
20
VOTE
Burn *Up* charts for Sprints, Releases, Epics, and Features
My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature For more on the requirements for a Burn Up chart and why it is more useful than a Bur...
2
Future consideration
1
VOTE
Add a "create retrospective option" to develop
What is the challenge? Having retrospectives is an important scrum practice, at the moment it's pretty manual. go to documents create a whiteboard add a copy of the end of sprint review insert a retrospective template. What is the impact? It's jus...
0
Future consideration
1
VOTE
Add automated capacity planning to sprints
What is the challenge? People are notoriously bad at estimating, points or hours are equally bad, and often people feel pressured into lower estimates, making the problem worse. What is the impact? Accurate sprint planning is hard to do and repeat...
0
Future consideration
1
VOTE
New requirements that are created under a parent feature that is already in the prioritized backlog should automatically be placed in the prioritized backlog.
What is the challenge? New requirements that are created under a parent feature that is placed in the prioritized backlog is placed in another area of the workboard. The user then has to find the new requirement and move it to the prioritized back...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved