Timeline for Is Agile the new micromanagement?
Current License: CC BY-SA 2.5
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2013 at 11:07 | history | made wiki | Post Made Community Wiki by Swab.Jat | ||
| Dec 20, 2012 at 6:13 | comment | added | Erik Reppen | @Dan I had a string of interviews a few years back where three startups told me they had to move the sales guys away from the devs because they were too !@#$ing loud. | |
| Jul 9, 2011 at 1:49 | vote | accept | Smith James | ||
| Mar 16, 2011 at 12:30 | comment | added | Dan Ray | @Kevin - My development department is an open cubicle farm, right next to an array of three bells labelled "Sale", "Big Sale", and "Huge Sale". A few times a day, sales people ring those and yell "wooooo!". :-\ | |
| Mar 16, 2011 at 11:59 | comment | added | Berin Loritsch | @Kevin Cathcart, we are in violent agreement on that one. Now, I've been in a company where the opposite was true. We had ~40 people in a bullpen with open tables and no cubes. The only team that could get anything done was the one that made the majority of the noise. That's the type of environment you want to protect against. | |
| Mar 15, 2011 at 19:58 | comment | added | Kevin Cathcart | A quiet workplace would be one where if you are not having a conversation, things are generally quiet, and where you can have a conversation without disturbing others. That means no culture of paging people over the intercom, and use of white noise generators or other methods of minimizing the apparent level of sound in areas where many people work. A no talking rule does not make a quiet workplace. | |
| Mar 15, 2011 at 19:12 | comment | added | Berin Loritsch | The only thing close I could find was a "Joel on Software" post on the top 12 things every company should provide for their programmers. One of the 12 was a quiet place to work. I doubt Joel Spolsky meant this, though. | |
| Mar 15, 2011 at 18:54 | comment | added | S.Lott | There are many practices (like pair programming, automated unit testing, etc.) that support Agile. "provide a complete vacuum for ... developers" isn't one of the practices I've ever heard of. But maybe it's a recommended practice somewhere. | |
| Mar 15, 2011 at 17:09 | history | migrated | from stackoverflow.com (revisions) | ||
| Mar 15, 2011 at 17:08 | history | answered | Sami Lehtinen | CC BY-SA 2.5 |