3 ms·

We have 4 columns: * Proposed * ToDo * In Progress * Done As a developer we mostly care about all but the first (though we drop random stuff in the first). Th

We have 4 columns: * Proposed * ToDo * In Progress * Done As a developer we mostly care about all but the first (though we drop random stuff in the first). The ToDo is always ordered with respect to priority but is generally irrelevant while one has work in-flight. That allows us to, without having to really notice, always grab the most important thing when we are free again. As you can imagine the proposed is the ungroomed/vague/random idea list that is roughly ordered toward whatever the PO (or developers for us since we don’t have product) views as a road map - discussed every week or so. Everything has labels and generally ties to the concept of an epic or bug.

klenwell 8y ago
We organize our columns in Trello around our scrum process. Our Proposed column is called the Wish Heap. It's where stories go before they're groomed (titled as user story, acceptance criteria defined, sized) and added to the Backlog column (or To Do) ready for work. First rule I try to get everyone in the org to follow: all work done by devs has a card. A dev gets approached by a manager who just needs one quick thing done, shouldn't take more than 5 minutes: "That's great. Can you throw it on the Wish Heap or talk to the scrum master?"
- alexchamberlain 8y ago
  Whilst I agree in general, but depending on your internal clientele, I think it can be useful having someone dealing with those 5 minute jobs - if you can save someone a couple of hours work by writing an SQL query for them, you should. It'll improve your relationship with other teams.
- nerdwaller 8y ago
  I’ve gone back and forth mentally on the “every bit of work needs a card” concept. Recently we’ve been trialing the on-call person taking those issues if they’re under a time-estimate threshold (30min) and budgeting the time for that person accordingly. Other issues go up the chain, to avoid the issue of the on-call person getting overwhelmed with unrelated feature requests and such (especially by those they relate to better than others). So far it’s been really positive when the rotation is 6+ persons, when I drops below that it gets a bit more wearing with on call being a bit heavy feeling.

klenwell 8y ago

We organize our columns in Trello around our scrum process. Our Proposed column is called the Wish Heap. It's where stories go before they're groomed (titled as user story, acceptance criteria defined, sized) and added to the Backlog column (or To Do) ready for work. First rule I try to get everyone in the org to follow: all work done by devs has a card. A dev gets approached by a manager who just needs one quick thing done, shouldn't take more than 5 minutes: "That's great. Can you throw it on the Wish Heap or talk to the scrum master?"

alexchamberlain 8y ago
Whilst I agree in general, but depending on your internal clientele, I think it can be useful having someone dealing with those 5 minute jobs - if you can save someone a couple of hours work by writing an SQL query for them, you should. It'll improve your relationship with other teams.
nerdwaller 8y ago
I’ve gone back and forth mentally on the “every bit of work needs a card” concept. Recently we’ve been trialing the on-call person taking those issues if they’re under a time-estimate threshold (30min) and budgeting the time for that person accordingly. Other issues go up the chain, to avoid the issue of the on-call person getting overwhelmed with unrelated feature requests and such (especially by those they relate to better than others). So far it’s been really positive when the rotation is 6+ persons, when I drops below that it gets a bit more wearing with on call being a bit heavy feeling.