4 ms·

This. I will backburner a ticket for days, then when what I need to do comes together I will sit down and bang it out in an hour. It's to the point that I wil

This. I will backburner a ticket for days, then when what I need to do comes together I will sit down and bang it out in an hour. It's to the point that I will deliberately review a ticket and code segment every day, even if I'm not actively working it, just to have the pieces come together in my mind and crank out the ticket. This method is not very scrum friendly, because in truth I'm actually brain-working all of my tickets at the same time, but I haven't shifted any electrons, just neurons. Sometimes, when I hit a sticking point, I go do something completely different - like read Hacker News - in order to push stuff into what I call "background processing" in my subconscious.

jjav 5y ago
> This method is not very scrum friendly, because in truth I'm actually brain-working all of my tickets at the same time, but I haven't shifted any electrons, just neurons. This really highlights why I hate agile so much. Intellectual work doesn't lead itself to reporting status on completed tickets every single day.
- wonderwonder 5y ago
  I absolutely hate having to do a daily stand up. I'll have my tickets done by the end of sprint, just not before that though.
  - viceroyalbean 5y ago
    I agree that there is that implicit pressure, but really it should (as in the ideal case) be fine to just say "I've been thinking about A, B, and C" and leave it at that. That still gives you the room to say that issue C has blocker X etc if it needs to be resolved in the team.
- zoomablemind 5y ago
  > ...Intellectual work doesn't lead itself to reporting status on completed tickets every single day. Status is WIP until completion. As for the intellectual work, that's just outright Analysis stage. Most of dev's work is actually analysis. Sure, there's implementation, testing and such, but Analysis is almost non-stop. Anonter way to put this is Evaluation of Alternatives, Optimization of Approaches.
hotz 5y ago
I operate in exactly the same way. I wish more people would understand that process.
- flatiron 5y ago
  Here I am thinking I’m the only one. Tossing and turning in the middle of the night for hours just to bang it out for 15 minutes the next day for everyone to go “oh that was easy” no it wasn’t!

jjav 5y ago

> This method is not very scrum friendly, because in truth I'm actually brain-working all of my tickets at the same time, but I haven't shifted any electrons, just neurons. This really highlights why I hate agile so much. Intellectual work doesn't lead itself to reporting status on completed tickets every single day.

wonderwonder 5y ago
I absolutely hate having to do a daily stand up. I'll have my tickets done by the end of sprint, just not before that though.
- viceroyalbean 5y ago
  I agree that there is that implicit pressure, but really it should (as in the ideal case) be fine to just say "I've been thinking about A, B, and C" and leave it at that. That still gives you the room to say that issue C has blocker X etc if it needs to be resolved in the team.
zoomablemind 5y ago
> ...Intellectual work doesn't lead itself to reporting status on completed tickets every single day. Status is WIP until completion. As for the intellectual work, that's just outright Analysis stage. Most of dev's work is actually analysis. Sure, there's implementation, testing and such, but Analysis is almost non-stop. Anonter way to put this is Evaluation of Alternatives, Optimization of Approaches.

hotz 5y ago

I operate in exactly the same way. I wish more people would understand that process.

flatiron 5y ago
Here I am thinking I’m the only one. Tossing and turning in the middle of the night for hours just to bang it out for 15 minutes the next day for everyone to go “oh that was easy” no it wasn’t!