![]() If you think you really need something more comprehensive, try to have a 'default category' (probably User story) which doesn't require a label and apply labels to the other cards. can mean you end up spending your life categorising your cards, rather than getting actual work done. Having labels for things like 'tasks' or 'story' etc. Make it red, which stands out better than other colours for humans scanning the board. My recommendation is to start off with just one label, for bugs. Labels are good right? So let's create a nice taxonomy of everything we could add (User story, Task, Bug, Epic, etc.) and use labels to classify each card!Įrm. Some people's next instinct is that they should be using more labels. ![]() So, you've got your board set up and you're starting to add some cards for an upcoming sprint. The slightly less basics Using Labels without going insane This is probably best for larger tasks on a backlog which your stakeholders are looking at rather than on your primary Scrum board. This can be a good way to make things a little more visual and allow people to more easily find the card they're looking for on busier boards. Secondly, you can add whatever documents you want, including linking to documents in Google Drive, Dropbox, Box or One Drive.įinally, if you want to, you can attach an image to the card which will also appear on it in the list. Firstly, you can use markdown in your description, letting you easily create nicely formatted descriptions of what you want (details here). There are some niceties when it comes to setting up your user stories on cards in Trello. This is especially useful when combined with a Cumulative Flow Diagram (see useful plugins below). Lots of cards stuck in test? Now you can see if they are ‘Waiting for test’ or ‘In test’, each could have different causes and quite different solutions. This can make it easier to see why work is building up. One other useful addition is to add a ‘Ready for’ list ahead of each of your ‘in progress’ lists. I'll cover that below in the release management section. The other big difference is where you keep your future sprints and the rest of your backlog, which is why I didn't include lists for that above. This is a nice way to keep track of what got done in recent sprints, something which always seems impossible to remember when you need to :). When it's appropriate you can decide the older sprints aren't relevant and archive them. This way you have an archive moving off to the right of your board showing what got done in the last few sprints. Most notably, some people call their ‘done’ list after the current sprint (ie ‘Done 29th Feb 16’) and once the sprint is finished create a new list for the next sprint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |