Closing A Sprint

[Toni]

Hi,

I am trying to figure out what actually closes a sprint. In particular,
if, at the end of a sprint, there are unfinished user stories (there are
many real life scenarios in which this can happen, eg. when a developer
or their child falls ill), I want to move them to the next sprint. But
the sprint from which I am removing the user story, should be closed if
no open user stories are left. In my current installation, which is the
stock stable code from Github, the sprint stays open after I moved all
unfinished user stories to a different sprint. I seem to have noticed
that the sprint only closes if I move all tasks which are associated
with user stories, to the 'DONE' swimlane on the Kanban board, but maybe
I am just confused?


Kind regards,
Toni

[Toni]

I forgot to say:

On Mon, Jun 18, 2018 at 10:16:59PM +0100, Toni wrote:
> if, at the end of a sprint, there are unfinished user stories (there are
> many real life scenarios in which this can happen, eg. when a developer
> or their child falls ill), I want to move them to the next sprint. But
> the sprint from which I am removing the user story, should be closed if
> no open user stories are left. In my current installation, which is the
> stock stable code from Github, the sprint stays open after I moved all
> unfinished user stories to a different sprint.

I actually want to close a sprint programmatically, and it actually
makes not much sense to me to move the tasks or userstories to the
"DONE" state, when they are in fact not yet done.


Thanks,
Toni

[Pablo Ruiz Múzquiz]

Hi Toni

A sprint is closed when all tasks in it are closed (any "closed" valid state). That is consistent with agile practices. If you happen to reach the end of a sprint with unfinished tasks (and, therefore, unfinished US) then the most common action is to move US from that sprint to a newly created one to be able to finish the US during the new sprint. The moment you only leave behind closed tasks, the sprint will change to CLOSED.

Some people like to move the entire (non finished) US to a new sprint, regardless of the number of closed child tasks, that is 100% SCRUM as it reflects that the value to the user wasn't delivered (it's pretty much binary, either it's there or it's not).

Other people prefer to create a follow-up US in the new sprint and create those unfinished tasks there, while deleting the unfinished tasks belonging to the original US. We are working to make this super-quick. We are also working to be able to automagically (one clic) move _all_ unfinished US from one open sprint to another valid open sprint from the list of open sprints. 

I hope this made some sense.

Best

Pablo

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
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+unsubscribe@googlegroups.com.
To post to this group, send an email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/20180618212610.skqhfwvguqme5rhd%40bla.tonimueller.org.
For more options, visit https://groups.google.com/d/optout.

--

Pablo Ruiz Múzquiz   CEO & Co-founder pablo...@kaleidos.net  | Tel: (+34) 639635072 | (+44) 07719222665 | (+34) 913562995 www.kaleidos.net/761CEC

[Toni Mueller]

Hi Pablo,

On Tue, Jun 19, 2018 at 02:52:59PM +0200, Pablo Ruiz Múzquiz wrote:
> one to be able to finish the US during the new sprint. The moment you only
> leave behind closed tasks, the sprint will change to CLOSED.

well, that may have a delay, because in my testing, this did not appear
to be the case, or at least not instantly. Can't really tell the
details, but expect to see the source code of that stuff I'm developing
up on Github soonish.

> Some people like to move the entire (non finished) US to a new sprint,
> regardless of the number of closed child tasks, that is 100% SCRUM as it
> reflects that the value to the user wasn't delivered (it's pretty much
> binary, either it's there or it's not).

So far, we are following this route.

> those unfinished tasks there, while deleting the unfinished tasks belonging
> to the original US. We are working to make this super-quick. We are also
> working to be able to automagically (one clic) move _all_ unfinished US
> from one open sprint to another valid open sprint from the list of open
> sprints.

In theory, sans the non-instant reflection of the openness or closedness
of sprints, which may be an artifact of my setup, I have this
functionality, the bulk move of open US to an open sprint, implemented
already. The one bit that's missing, is to integrate with creating a new
sprint where the remaining US should wind up.


Thanks,
Toni

[Pablo Ruiz Múzquiz]

Hi Toni

During our tests yesterday, the closedness of sprint was semi-instantaneous. I would have two tabs open, one with the sprint taskboard and one with the sprint backlog + sprints. The moment I closed the last task on the sprint taskboard, it only took 1 sec to reflect (no reloading necessary) the closedness of the sprint. Also, when I reopened a task, again it was just a matter of 1 second to see the closed sprint open again.

We agree that it would be great to very easily move unfinished US from sprint to sprint, we will work on that very soon.

Best

Pablo