A quick guide for the Dev Team Coordinator

As with everything in BW it is pretty much up to the coordinator how his role looks like, where he/she puts the focus and so on. However, this list from previous coordinators should give you an idea.

If you have any questions, don't hesitate to ask former coordinators any time!

• Philipp ( philipp)

• keep the general overview
  • you should know what's going on in BW, BV, the BoD, other teams your team and the heads of your fellow team members
• keep an eye on the communication
  • make sure that things are communicated, that all relevant people have say, if necessary invite them by private contact
  • make sure that all sides of a discussion are equally represented
  • help to keep the communication productive and to the point
• have your own standing as a team member, be neutral as the coordinator and accept team decisions that do not match your own ideas
• spot the important tasks (code wise and organization wise) and delegate as much as possible
• search for, introduce new members and help them to get started (or make sure that somebody else does it)
• make sure that the dev team keeps connected to the bw members. We are developing for the needs of the members not for our own joy or interests
• make sure that:
  • the website is running stable
  • the data is safe and backed up
  • nobody abuses his access rights
  • bod and bv decisions are followed
• keep the final word on (hardly ever needed):
  • who gets access to what
  • what becomes implemented or not
  • design decisions
• help to prioritize tasks, coordinate releases
• mediate between team members when thy have opposing ideas regarding code architecture, ....
• keep people motivated
• ....

More suggestions (lemon-head speaking)

• Make sure that radical changes to the software are agreed on in the team, before someone starts implementation. Ideally, big changes should be broken up into smaller pieces, with stable intermediate states.