We are currently working with sprints of 3 weeks. But sometimes a release to the project is ready after the first week of a sprint. Portfolio however does not give the option to calculate this since it says that you can only release after a sprint.
Atlassian Team members are employees working across the company in a wide variety of roles.
November 22, 2015 edited
Hi!
Sorry, but this level of granularity is currently not available in portfolio. Working with the iterative nature of Scrum, we assume things are releasable when they meet the definition of done, which is by nature at the end of a sprint.
Cheers, Allard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will this ever be amended? High-performing orgs are deploying new software sometimes multiple times a day to production. Releases no longer need to be huge bundles of software released weeks or months apart. When a story is complete and a PR is merged, the software is automatically tested and promoted until it hits production. We should have an option to roughly estimate completion time of a story within a sprint and place the release marker at that point. In-sprint prioritization could be done based on manual rank for a first pass but it needs to happen. This makes Portfolio difficult to use.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.