Sprints

What is the challenge? We have "developer users" planning their work and sprints in the form of releases. However when their releases are marked as done - there is no pushing incomplete features to the next release. (this is because it's a parking...

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...

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...

Sometimes a feature ships but some of its requirements are not marked as done by the developer. Currently we need to manually update the status on each requirement's page in order to stop it from displaying in the backlog.