Quote:
Originally Posted by bludeath
...(I just need a little clarification on how to go about assigning jobs from the gecko)
One thing i was looking into was a gantt chart. A way to keep a organized workflow and time various tasks and set dead lines for various things within the project. I Just wanted to see if any other team out there was using the same method and if they found it effective or not?
put all the management out of the way one thing i mentioned at the beginning was team effort. I value being apart of a team and working unified as such but how do i bring our team closer and getting to know a little bit about one another? I understand that team bonding experiences are important but what would anyone recommend as far as effective team bonding?
|
1) Assigning jobs. I'd suggest that the most important thing here is that the teams reaches a consensus on how jobs, particularly leadership jobs, will be determined. You might want to vote for some (though I'd suggest against this for other reasons); you might want to include a skill test (e.g. for human player); you might conduct interviews. Whatever it is, figure it out as a team. And don't undermine the positions of your own teammates: for instance, don't say "when Bob starts to slip up you can take over".
2) Gantt charts. I'm a fan, particularly if you can get each department to buy into the deadlines beforehand and agree on task interrelationships. You'll want it to be something you fully commit to, though. Let it take up a wall of your shop, or update a digital at every integration meeting. It's a great tool, but only if you use it.
3) Teambuilding. In my experience people get to building relationships pretty quickly when they're locked in a build shop for 20-hour weekends. Eating together is always an excellent teambuilding activity, as are mini-engineering games and just playing frisbee outside. If you're not sure what do to, don't overthink it. Instead of trying to plan out something overly elaborate, just take the time to watch your people interact and see what they need. Adapt; remember you're there to serve them.
Quote:
Originally Posted by Michael Corsetto
2. Improve your written communication skills. Leadership capacity can be cut at the knees by poor communication. Pay more attention to how you present your thoughts in written form. A good reason to pay attention in your English classes  |
This. And never ever, ever, ever let someone tell you that programmers (or engineers) don't need to know how to write. Ever. Seriously. Don't do it.