Timeline for How can we effectively manage software projects without killing creativity?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2017 at 13:11 | comment | added | Murphy | "leave the day-to-day management to the developers themselves": Joel described this management style once as "moving the furniture out of the way, so people can concentrate on their work" | |
| Aug 23, 2017 at 16:32 | vote | accept | Frank Puffer | ||
| Aug 18, 2017 at 12:04 | comment | added | Euphoric | @DerekElkins It is not question of who, but why. If manager demands that it is done and uses that to track progress/performance, then that is wrong. If it is done, because developer wants it done to track his own work, then that is fine. Some (or most) developers simply don't need fine-grained time/task tracking to be productive. | |
| Aug 18, 2017 at 8:00 | comment | added | Frank Puffer | @DerekElkins: Yes, of course a developer should do this. But does it make a big difference? I find it hard to be creative when creating a task list or WBS. And I find it hard to be creative when implementing the tasks, no matter who defined them. | |
| Aug 18, 2017 at 7:51 | comment | added | Derek Elkins left SE | The person who should be doing the "splitting [of] the project into bite-sized chunks" is you! The project manager shouldn't be doing this. I don't think the OP is talking about a situation where the project manager or someone other than the development team is doing this. | |
| Aug 18, 2017 at 7:11 | history | answered | Euphoric | CC BY-SA 3.0 |