Ditching "Project"

Brazil has suggested that tracking "project" and "maintenance" might not be as useful as I had thought :)

Ditching the Project vs. Maintenance distinction on our board.

The circle went something like:

1. Big projects are different from maintenance, different speed
2. Big projects will be tracked as one item to reduce noise on the board
3. We'll break up the detail in Jira as subtasks
4. Problem is, developers need to look in two places instead of one (Jira, board)
5. Everything we're working on should be the same level of detail
6. Everything should be on the board
7. We can ditch the swim lanes and convert Jira subtasks to normal ones

So over the past couple of days we've converted subtasks into distinct Jira items and added them to the board.

This has already had a positive impact - as we've begun to put the additional tasks on the board, it's started to fill out the apparent gap that we had between "Queue" and "Dev-WIP".

Hopefully this will become easier to manage now.

I'm also suspecting it will become easier to set WIP limits now, we'll see...