Closing a sprint

[Arnaud Bailly]

Hello,

Thanks a lot for the great work! Taiga rocks, hope you will have the wisdom to stop before morphing into Jira...

My question: is it possible to close a sprint? If I have some US not completed during the sprint, should I move them manually to other sprint or backlog?

Thanks

Arnaud

[Jesús Espino]

Hi Arnaud,

Thanks for your kind words, and for using Taiga.

The sprints are closed automatically based on the status of the users
stories contained in it. A sprint closed with open user stories have
no sense. You have to close the user stories or move the user story to
the next sprint.

Anyway is possible to close the sprint through the API, but if you
change any of the user stories in the sprint, the sprint will be
reopened.

Regards.

> --
> 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+u...@googlegroups.com.
> To post to this group, send email to tai...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/taigaio/6587262b-67ec-4e6f-a705-75893b57e6f6%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[MaH Relinace]

Hey Jesus,

We have a similar question. Is it possible to move all the user stories that have not been closed to the most recent sprint?
We have a project with a lot of small user stories which we are dragging to the new sprint manually, every time we create a new sprint.

Maybe creating a button to automate this could be a good addition to Taiga?

Regards,

Maarten.

Op maandag 23 februari 2015 07:19:19 UTC+1 schreef Arnaud Bailly:

[Ivan Storck]

I agree with Maarten's idea, because sprints are supposed to be time-boxed http://scrummethodology.com/scrum-sprint/

[Jesús Espino]

Hi,

Now, we have multiple selection and drag and drop from backlog to
sprint, but no between sprints. The idea of a button to move all
not-closed stories to the last sprint may work well on some workflows
but not in another, for example, people with various teams with
various sprints at the same time. I prefer the idea of multiple
selection and drag&drop.

I will add the multiple selection and the button as possible
enhancement to talk about it with the team. Anyway, the concept of
sprints is time-boxing for fulfill a commitment, the need to move a
lot of user-stories from one sprint to another, must be rare, and is a
symptom of infraestimation of the user stories or overestimation of
your team capacity.

Regards.

> --
> 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+u...@googlegroups.com.
> To post to this group, send email to tai...@googlegroups.com.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/taigaio/ecfe93c3-bd62-406f-8137-fd2e43af6aee%40googlegroups.com.

[MaH Relinace]

Hello Jesús,

A button to move all the unfinished user stories from a sprint to the backlog would also serve us well.

Regards,

Maarten

Op dinsdag 10 maart 2015 09:20:57 UTC+1 schreef Jesús Espino:

Hi,

Now, we have multiple selection and drag and drop from backlog to
sprint, but no between sprints. The idea of a button to move all
not-closed stories to the last sprint may work well on some workflows
but not in another, for example, people with various teams with
various sprints at the same time. I prefer the idea of multiple
selection and drag&drop.

I will add the multiple selection and the button as possible
enhancement to talk about it with the team. Anyway, the concept of
sprints is time-boxing for fulfill a commitment, the need to move a
lot of user-stories from one sprint to another, must be rare, and is a
symptom of infraestimation of the user stories or overestimation of
your team capacity.

Regards.

2015-03-04 18:45 GMT+01:00 Ivan Storck <ivan...@gmail.com>:
> I agree with Maarten's idea, because sprints are supposed to be time-boxed

> http://scrummethodology.com/scrum-sprint/ - private

> https://groups.google.com/d/msgid/taigaio/ecfe93c3-bd62-406f-8137-fd2e43af6aee%40googlegroups.com - private.
>
> For more options, visit https://groups.google.com/d/optout - private.

[Jesús Espino]

Mmm, this sound more "generic", I add this suggestion to the
enhancement proposal.

Thanks!

> https://groups.google.com/d/msgid/taigaio/18623292-a057-4bdd-b399-874df74ba59b%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Xavi Julián]

I don't agree with any special button option.
A sprint is a time-boxed space of time where your team commit to finish a group of user stories, so moving user stories between sprints or to the backlog shouldn't happen, or at least, shouldn't be more than one or two stories, and means that you are not doing something correctly. If this happens in every sprint, your project workflow might fit better in a kanban approach, or you might need to reestimate the team capacity in each sprint.

I need to understand better the use case. I won't like to add a functionality for a rare use case or a misuse in the taiga core.

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/CADn2Td%3DGkBNeNk3U9O_oNesXUjD7O8SVg3oHmUnXPe0cE5CADA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Xavier Julián Olmos  xavier...@kaleidos.net | Tel: (+34) 913562995                     www.kaleidos.net

[or...@upwardautomation.com]

On Tuesday, March 10, 2015 at 3:43:24 AM UTC-7, Xavi Julián wrote:

I don't agree with any special button option.   

A sprint is a time-boxed space of time where your team commit to finish a group of user stories, so moving user stories between sprints or to the backlog shouldn't happen, or at least, shouldn't be more than one or two stories, and means that you are not doing something correctly.

I would agree with you if sprint's were considered closed by Taiga if the current date is greater than the end date specified for the sprint. However, this isn't the case with taiga at the moment. So the notion of "time boxing" is in name only and isn't actually represented by the taiga implementation at the moment. Adding to lack of actual time boxing, a sprint cannot close until all of it's tasks are completed, moved to the backlog, or moved to another sprint. So at the moment "sprints" in Taiga at the moment are really just a Software Requirements Specification that isn't completed until the software meats the spec or the spec is changed to match the software. 

Unless a team consistently sets low expectations for itself or has extremely predictable tasks & projects; for tasks to be time-boxed (i.e. a sprint for this discussion) implies a team is not going to complete certain tasks xor complete more than initially planned on.

 

[t.licht...@gmail.com]

I'd like to propose to auto-move remaining stories to the backlog when the sprint is closed. This would in turn mean that sprints should be closed manually (by pressing a button). 

Thomas

[or...@upwardautomation.com]

On Tuesday, September 15, 2015 at 6:38:12 AM UTC-7, t.licht...@gmail.com wrote:

I'd like to propose to auto-move remaining stories to the backlog when the sprint is closed. This would in turn mean that sprints should be closed manually (by pressing a button). 

How Taiga would be more intuitive to me with regards to this topic:

Sprint Auto-Closing

When current date is greater than the end date of a sprint, taiga considers that sprint closed.*
2 days after the end date of the sprint following actions happen**

1. non-completed tasks are moved to the back log
2. tasks that are in the work pipeline (i.e. not set to new/read but something like in-progress) their US points are reset to '?'***
3. the sprint is hidden on the backlog page in the sprints side-pane the side-pane and only viewed by selecting "view closed sprints"

Manual Sprint Closing

When a user selects the edit button for a sprint, next to the option of selecting to the 'delete the sprint' should be the option of manually closing the sprint and performing the same auto move of uncompleted user-stories.

Notes

* There should still be some way of denoting what tasks weren't completed in closed sprints for reviewing actual % completed tasks for the time-boxed sprint. This way people can self correct on how much work they can actually complete within their sprint period.

** The number of days before auto moving of non-completed tasks should be able to be changed.

*** The reasons that I think user-stories US points should be reset to '?' is because since they are in the work pipeline they presumably will take less time in the next sprint (possibly more if something else came up)

[Alejandro Alonso]

Thank you very much for the ideas!,

I've created an enhancement request for storing all the feedback/ideas related to this topic -> https://tree.taiga.io/project/taiga/issue/3259

Regards!,

--

Alejandro Alonso Fernández   CIO & Co-founder alejandr...@kaleidos.net  | Tel: (+34) 627263808 | (+34) 913562995 www.kaleidos.net/FC8EAC/