On June 29, 2017 4:15 pm, Fabien Boucher wrote:
Hi Tristan !On Thu, Jun 29, 2017 at 8:03 AM, Tristan Cacqueray <[email protected]> wrote:Hello folks, It seems like we all agree storyboard is cumbersome when used to manage backlog and sprint. In particular we really need a way to vote on storyI think you mean "priority" vote here ? In that case why not having in the board a "High priority" column that we manage during a grooming session (we add a priority tag to stories) then finalize the discussion and eventually selected them in priority into the current sprint during the sprint planning ?
I mean vote like "+1". That's actually something we never did, the idea is to let anyone vote on stories so that we can plan the work based on user's feedback.
for planning, and better reporting for the review. On the other hand it's already integrated and it does send notification and tasks are updated on gerrit events. Thus I'd like to investigate an external tool for scrum while keeping stories in storyboard. I started to hack a script to dump storyboard content in etherpad, while keeping the structure of the etherpad so that we can easily move stories around, add categories and comment: https://softwarefactory-project.io/etherpad/p/sf-backlog The script is: https://softwarefactory-project.io/r/#/c/8747/1/story2pad/story2pad.py What do you think?Is the etherpad supposed to replace the Storyboard sf-backlog-ng board ?
Yes, that replaces the board by a free-form list.
I know it is difficult to deal with Storyboard but I'm not convinced by adding more complexity, more tools, more scripts around the sprint workflow ... Is there really a blocker to use storyboard boards by only using tags and tags filtering by column w/o any background scripts and complex logic, also using a board by sprint (one script :) (just one) to create the board and our filters). Columns: * Groomed stories backlog (tag: groomed) * Groomed high stories backlog (tag: groomed, tag: p-high) * Confirm bug stories backlog (tag: groomed, tag: bug) * Current sprint tasks * Current sprint tasks done The two last columns are manually managed by the scrum master.
The last few planning were a bit chaotic, we couldn't really use the board, mostly because: * automatic column can't be ordered manually, * story/task can't be duplicated inside a board, * sometime story/task just doesn't appear in the board, * stories are not automatically moved from current tasks to tasks done,* and it's really slow...
Moreover, the board/story/task miss the voting system we could use with-in the etherpad. I don't think this add too much complexcity, the story2pad script can be run periodically while keeping the free form format Hence my proposal to keep storyboard to store stories/tasks, because it's still good at that, but replace the board by a free-form etherpad until, either the board feature is improved to fit our need, or either we find a real tool to manage sprint (while still keeping storyboard as a backend). Regards, -Tristan
pgpgx8nOuqURI.pgp
Description: PGP signature
_______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
