Le 29/06/2016 à 14:28, Matthieu Huin a écrit : > So we don't use redmine at all ? And should we wait until 2.2.3 ?
Storyboard should be usable in SF in the 2.2.3 version so yes once we have upgraded sf-project.io we will be able to migrate our content from redmine to storyboard. We need a (on shot) tool to move the content. Or could this be done manually ? And finally once we migrated, we can I guess safely remove definitely Redmine from SF ? WDYT ? > ----- Original Message ----- >> From: "Fabien Boucher" <[email protected]> >> To: [email protected] >> Sent: Wednesday, June 29, 2016 12:25:43 PM >> Subject: Re: [Softwarefactory-dev] Using storyboard to manage product >> backlog and sprint >> >> Hi Tristan, >> >> Thx for this follow up about using Storyboard for our sprints. >> Few inlines comments. >> >> Le 27/06/2016 à 23:09, Tristan Cacqueray a écrit : >>> Hello folks, >>> >>> I'd like to propose/discuss a new workflow to manage our backlog. >>> The two main improvements will be: >>> * create tasks attached to a story >>> * associate stories or tasks to a sprint >>> >>> Here is how it will work in practice if we use storyboard: >>> >>> During the grooming: >>> * story are created as usual >>> * initial conditions of satisfaction are now tasks >>> * story type can be tagged (e.g. improvements, fix, security, ...) >>> >>> During the planning: >>> * we create a new board with a due date: >>> | Stories | Todo | In Progress | Need help | Need Review | Done | ... >>> >>> * for each story, we vote (mostly to be sure everyone understand) and >>> we create all the tasks >>> * Selected story are added to the stories column >>> * Stories' tasks can be added to the todo column >>> >>> During the sprint: >>> * we move task to the correct column >>> * Once all the task of a story are completed, we remove the story >> >> We can also have during the retro: >> * Create a task by actions (we can have a Retro' actions board) >> >>> This should remove the need of the "standup etherpad" and we could >>> focus on sprint discussion based on the board state instead (e.g., what >>> is in progress, what needs help, ...) >> >> I'm agree with that proposed workflow, sounds exciting ! >> >>> If that works out well, here are a few more improvements: >>> >>> * feature release board where we could plan new release in >>> advance and track progress independently from sprints. >>> * Create a "daily-standup" board view where it only show cards that >>> changed the last 24 hours. >> >> Does storyboard is able to do that, or we need to write a tool to refresh >> the board ? >> >> Cheers, >> Fabien >> >> _______________________________________________ >> Softwarefactory-dev mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/softwarefactory-dev >> _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
