Hi Guys, Jacob here again.
In Part 1 we looked at the basics of using trello for project management.
Now that we have the basic layout of our project we will add some general tickets to the epics column. These will describe the main things that we will need to get done for the project to be a success. I have a few ideas for what these will be and I will add more detail as the project develops.
My project is to create website full of tools for role playing games, primrily D&D. We are going to want a dice roller, an initiative tracker, a character sheet, some sort of spell book and a way to switch quickly between the website’s pages.
These are quite broad ideas at the moment but they are definable sections of the project so we will use them to define our epics. We need to click on the add card button under the Epics list and give our first epic a name:
Since the side navigation bar is going to appear on each page of the website, I am going to start with that. Once you have entered the title (given your ticket a name) you can click on the card to view it and fill in more details:
To make tickets assigned to this epic easily recognisable we are going to assign it a colour and a label. On the right side menu under “ADD TO CARD” click on the labels button. This will opening the following window:
Click the colour of the label you want added to the ticket and click on the pen on the right of the colour to write a message in the label. Your ticket will now have that colour highlight and the ticket wording in its header space:
Discuss with your team what the MVP (minimal viable product) of your project is. In this case it means what is the very least we need to do in order to have a functioning piece of software that meets basic requirements.
I use the MoSCoW method to prioritise what is going into the project, things you M – Must have, S – Should have, C – Could have, and W – Won’t have. For example, a navigation bar to switch between pages is a must have, because without it the product will not function. Some sort of server integration would be nice to have, but it is currently outside the current scope and time frame making it a wont have – but it might be brought in on a later release once proof of concept is completed and the project is expanded.
Now that we have a rough outline of our project goals, it is time to start digging into what will be required to achieve them. We are going to fill the backlog column with the tickets that will be worked through during the project. At the beginning of a project, this list may seem overwhelmingly long; but don’t worry, with a well structured work flow, the tickets will soon be moving into the completed column!
Again, it is time for some discussion with your team (if you have one), you need to work out exactly what functionality you need from each epic and break it down into achievable tasks. These tasks should to be more in-depth than the epic cards but they can still be a general heading within the epic, we are going to refine these later and assign sub-tasks to each ticket. You should end up with a growing list of to do tasks and for each one that you add you should see the tasks under your epics increasing.
Let’s breakdown the dice roller as an example: we will need an interface to select which die and how many of them you want to roll, graphics for the interface and a random number generator. We are going to set up tickets for each of those things. It is very similar to setting up the epics: we click on “ADD A CARD” give it a descriptive title then click into it to add task details:
The card looks slightly different to when we were creating the epics, there is an option to add this card into an epic. We are going to add this one to the dice roller epic and as before we are going to go to labels on the right. The options should automatically match the dice roller epic’s colour:
You should now see that the card has the Open status. It will also say that it was added to the Dice Roller epic.
Don’t worry if these are still lacking detail in terms of what you need to do, before you pick up and start working on these tickets you will need a refining session where you: go through and flesh out the subtasks needed to complete the task; identify what other work needs to be done before this task can progress and what will potentially blocking the task from being completed.
Now that we have a plan we need to look at setting up our virtual workspace. This will include the development environment (processes and programming tools used to create programs) that we will use for writing our code and creating a repository for storing our code.
Next time we will look at setting up a repository: a shared storage area for anything we create as part of the project, that all members of our team can access and update even when working on different computers.