Tag Info

New answers tagged

6

Don't do this. You're not going to like this, but you're missing the point of story card sizing. It's NOT to measure productivity. It's to measure relative complexity of work. These are not the same thing, and never will be. See, there's a fuzzy correlation between requirement complexity and time to completion, but that's ALL that it is. Your goal ...


4

I find myself writing code for hours, even days without running the compiler for anything but an occasional syntax check. Hours to days - that's a clear sign that you miss the ability to break down your code into smaller chunks which can be verified and tested on their own. You should definitely work on that. I tend to write bigger chunks of code ...


-1

Depends on the soundscape. I prefer working in a busy room with other people and a low level of idle chat in the background as opposed to dead silence. I believe many people generally prefer a constant level idle noise at a low frequency. The humming of a talking crowd at a café can be pleasant and help me focus on my work. But a room with only 2 people ...


3

I think "quiet" verses "loud" misses the point slightly. The issue is with environments that contain distractions that the team feel they cannot ignore. Any noise that is unrelated to the work that you doing (I.E. background noise) can be classified as such. I've worked in plenty of "loud" environments that have been very productive since the volume was ...



Top 50 recent answers are included