Skip to main content

get it done with trello, part ii

Everyone likes to think that the meeting they're sitting in is productive and staying on track. One of the best things about using a Kanban system is that it provides a highly visual representation of your team's progress.

I've found that Trello works great for conducting meetings, work sessions, and other group activities. After all, what is a meeting but a short-duration collaborative project?

If you go into every meeting with an agendaas you shouldthen you have a predefined set of items for the To Do column. Then it is a matter of simply moving them through the steps required to bring them to conclusion. Furthermore, you can use Trello features such as commenting and voting to capture all sorts of information during the session.

Here are a couple of the meetings and work sessions we handle using Trello:

Agile Iteration Planning

trello board: agile iteration planning process


The main part of our Iteration Planning is done by the entire team. Once that is completed, the Scrum Master takes care of a number of bookkeeping steps to get the Iteration underway.

We use four simple columns to track this work:
  1.  To Do 
  2.  In Progress 
  3.  Done
  4. Optional 
And here are the cards, in order:
  1. As the iteration winds down, check with team one last time to see if any more cases can be resolved.
  2. Make sure all cases in the 'Completed' Kanban column are resolved.
  3. Update the Iteration wiki page with velocity info.
  4. Close all resolved stories in the Iteration Backlog.
  5. Create new milestone in FogBugz for the iteration the team's about to plan.
  6. Set up, in our calendaring system, the retrospective/planning meeting to take place at the end of the upcoming Iteration.
  7. Prepare space for retrospective and planning session.
  8. Team participates in Iteration Retrospective.
  9. Add the Retrospective Objective (in the data for the Iteration just ended) on the Iterations Wiki Page
  10. Add the Retrospective Objective Story to the upcoming Iteration. (Create a Feature as a parent case if it makes sense to do so.)
  11. Move any stories in the Iteration Backlog that the team does *not* want to work on in the upcoming iteration back to milestone 'Undecided.'
  12. Move Stories in the Iteration Backlog that the team *does* want to continue working on to upcoming iteration's milestone.
  13. Change the Current Iteration shared filters to display the iteration just beginning.
  14. Move appropriate items in Iteration Planning wiki page into the new Iteration Backlog.
  15. Decide what else to work on in upcoming Iteration: [a] Top-Priority items, [b] Analysis stories leading to future work, [c] Stories to balance work across the team.
  16. Make sure all Stories in upcoming Iteration have Story Points and that the Story Point count doesn't grossly exceed the team's capacity.
  17. Make sure all new Stories created have the appropriate Feature as their parent case.
  18. Make sure all Stories in upcoming Iteration are in the correct column on the Kanban board.
  19. Team can now begin new iteration.
  20. Any new Features or Bugs? Make sure they're in the FogBugz and Trello Backlogs. (See checklist.)
  21. Groom Product Backlog. (See checklist.)
    In the Optional column:
        • If appropriate, give Stories in the new Iteration a backlog order (will show up in Iteration Backlog shared filters).
        • Team prioritizes Features in FogBugz Product Backlog.
        Labels

        We use Trello's labels to indicate if the task is done by the team or the facilitator, and whether the task is related to the previous Iteration, the upcoming Iteration, or the Product Backlog.

        Agile Retrospective


        Our team runs Agile Retrospectives using the techniques described in James Shore's The Art of Agile Development: Retrospectives. Our Retrospective Trello board has just two columns:
        1. To Do
        2. Done
        The Cards:
        1. Facilitator posts column-header cards on wall.
        2. Team posts cards with activities, experiences under columns.
        3. Facilitator marks each team card with column symbol and removes column-header cards.
        4. Affinity mapping: team groups its cards into emerging categories.
        5. Facilitator and team label each category.
        6. Team members vote on categories.
        7. Team members vote on a single card in winning category; card becomes retrospective objective.
        8. Team brainstorms on how to address retrospective objective.
        9. One team member volunteers to take ownership of retrospective objective.
        10. Facilitator makes sure retrospective objective.
        See these two Trello boards:

        Popular posts from this blog

        the case for incremental redesign: part i

        Consider the dashboard of your automobile. Aside from a number of extras that have crept in over the decades, it's essentially configured the same as the dash of the car you drove as a kid. In fact, the design of the automobile's critical controls hasn't significantly altered since the Model T Ford. It's worked for more than 100 years, and we love it.

        Plone Advocate Andreas Mantke to Lead Site-Administration Workshop at 2012 LibreOffice Conference

        I just published this article at plone.org on Andreas Mantke, a deputy member of the Board of Directors of the Document Foundation for LibreOffice . Mantke led a workshop for new Plone site administrators in the LibreOffice community during its annual conference last week. See the full article at plone.org/news/andreas-mantke-to-lead-site-administration-workshop .