I'm playing with this idea here: https://phabricator.wikimedia.org/project/sprint/board/942/
Problems with using epics is that they can literally capture any category of task -- in any team, for any type of work whether it's testing and practices/process stuff or API/platform work or user-facing releases. Much of this doesn't belong in a roadmap. So in order for this to work with "epic" alone, we'd have to .. - stash a lot of epics away into a column where they don't bother us - hypercategorize the workboard, which would make it less readable as a roadmap - spend a fair bit of time grooming the backlog to keep it manageable I'm not fond of these possibilities. I think having a "Roadmap" project would force a more conscious choice -- you add this if a task meets certain specified criteria _and_ you know that you're going to actually schedule it for completion. "Epic" seems to mostly have value intra-team but less value cross-team, IMO. Erik -- Erik Möller VP of Product & Strategy, Wikimedia Foundation
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
