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 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, ...) 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. * Hack an irc bot to update task based on certain pattern: "working on $task_name": move task to in_progress "$task_name completed": move task to done "need help on $task_name": move task to need help ... Cheers, -Tristan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
