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.

        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

        don't let broken stories wreck your team's velocity

        Capturing requirements in Agile stories is finicky business. Stories need to be just the right size and shape, have the right bits of detail, point to a clear outcome. They must capture the who, what, and why in a way that speaks unequivocally to the user and to the team. Badly written user stories will slow down your team in any number of ways. A few recommendations... Get the right people writing the story. Even if you've done lots of requirements gathering, or the functionality seems like a no-brainer, don't assume that you have sufficient information to compose stories without stakeholder participation. In fact if at all possible, the stakeholders should do the writing. You are there to ask questions and help clarify. Without this collaboration, you will end up going into iteration planning with hobgoblins, not real stories. The team then must devote time to figuring out what's actually needed, returning to the stakeholder with lots of questions, rewriting and

        Announcing the 45th Eastern Primitive Rendezvous

        The 45th Eastern Primitive Rendezvous takes place September 23-October 1, 2022.   For more information, visit the official EPR website and Facebook group . We will be hosting the 45th Eastern Primitive Rendezvous on our family farm, near East Smithfield, PA. The dates are September 23 - October 1, 2022.  This is a living-history event depicting 18th-century activities. Visitors can tour the camp each day from 10 a.m. to 4 p.m.  Tuesday, September 27 is School Tours Day, during which we welcome classes from all of the area schools. Campers need to preregister ( ), and period-correct clothing and gear are required.  For the exact location and more details, visit the  official EPR website  and Facebook group . For those of you who attended the 2017 EPR, this is the same location.