Timeline for What would you do to improve the working of a small Development team?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2013 at 14:31 | comment | added | Omar Kooheji | Our organization excels at creating single points of failure which is something I'd like to minimize. I'd also like to enhance the communication between the team members because at the moment it's non existent, which hasn't been good for morale. | |
| Oct 29, 2013 at 13:49 | comment | added | Dunk | @Omar:Don't be fooled into thinking that having 2 developers on a project instead of 1 will make things better or be accomplished smoothly. Especially if everyone is used to working alone. As soon as you add that 2nd person you have this little thing called "communication" that likes to throw all kinds of monkey wrenches at problems. If your projects are small enough to be accomplished by 1 person then that is the most efficient way to get the job done. It may not be the best way, but will certainly be the most efficient. I would not be surprised to see productivity go way down with 2 people. | |
| Oct 29, 2013 at 11:04 | comment | added | Omar Kooheji | We can't ditch .Net completely sadly as some of the things we integrate with only have a .Net interface and there are some things that are easier to do in .Net (Mainly windows forms apps) | |
| Oct 29, 2013 at 11:01 | comment | added | Omar Kooheji | Ideally I'd like to have it so that we don't have just one person working on a task. I think it's dangerous. My idea was to assign at least two people per project have them break it up into tasks and then have them responsible for taking up smaller tasks. We currently have a problem where if a team member goes on holiday the project has to go on hiatus because no one else knows what is happening. | |
| Oct 29, 2013 at 10:51 | history | answered | gbjbaanb | CC BY-SA 3.0 |