However, where in Basecamp we used a To Do list to represent an Epic, Trello’s “To Do lists” are its columns, referred to as “Boards.” Since, in Trello, we will likely want to use these columns to represent the statuses a story/task passes through, one option then is to document the Epics elsewhere, but represent them using Trello labels.
Trello has similar simplicity and, thereby, similar limitations as Basecamp. Create Epics, Stories/Tasks, or Subtasks in Trello Trello is a very popular tool for managing projects with lists and “cards.” Like Basecamp, the interface is very intuitive, responsive and reliable yet at the same time it is a completely different user experience. Let’s try to represent an idea breaking down into smaller tasks with Trello.
This has obvious limitations, but could work ok, if you were stuck with this tool for some reason. The first way I thought to do this was with bullet points and emojis. Subtasking Stories is where we reach the limits of Basecamp. These can have additional details and can handle assignment and due dates etc, so it can work pretty well. Teammates can then discuss and subscribe to that Epic from within itself. With Epics as Basecamp To Do lists, the Stories end up being To Do list items. So, we can use a whole To Do list to represent an Epic. Create Epics, Stories/Tasks, or Subtasks in Basecampīasecamp doesn’t have an explicit concept of an Epic. Let’s try to represent an idea breaking down into smaller tasks. The interface is very intuitive, responsive and reliable. Basecampīasecamp is a very popular tool for managing projects using lists and todos. If we agree with the concept of breaking work down into smaller actionable pieces, in order to truly commit to completing them, then we will want our tool of choice to enhance this way of working.īuilding on to Epics, Stories, Tasks, Subtasks… what’s the difference, let’s explore applying this strategy while using some of the common tools of choice.
0 kommentar(er)
