For those curious you can see my first draft in a series of how the apps team use of trello below
https://docs.google.com/document/d/101RAyXz1lyZb1b8eVOOgNBTSKPRfoXap-YohxZS4cjI/edit?usp=sharing --tomasz On Tue, Apr 8, 2014 at 10:36 AM, Arthur Richards <[email protected]> wrote: > During our most recent retrospective, the mobile web team decided to try out > Trello for managing our workflow. I will be spending time over the rest of > the week plotting our migration and could use some help from other Trello > users. > > Form a tool management perspective, I am scratching my head over two things: > 1) What's the best way to migrate existing stories/bugs from Mingle -> > Trello? Fortunately, we have a relatively small backlog that will need > migrating - I think we'll keep the old stuff archived in Mingle for now. S > and the Flow team - how did you all pull it off? > > 2) I've seen how the Mobile apps team manages their boards and a bit of how > the Flow team manages theirs - but I'm not sure either approach is 100% > right for us. How can we set up boards in such a way to make it easy to: > a) manage an overall/project backlog > b) manage an iteration backlog and track work status therein > c) this is the big bonus: be able to look at work completed in past > iterations and also begin seeding a future iteration's backlog > > Thanks! > > -- > Arthur Richards > Software Engineer, Mobile > [[User:Awjrichards]] > IRC: awjr > +1-415-839-6885 x6687 > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices > _______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
