Difference between revisions of "SE2006:group bar:roles"
Jump to navigation
Jump to search
(Fleshing out of roles) |
|||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
In addition to developing code, we've assigned these extra jobs to ourselves. | In addition to developing code, we've assigned these extra jobs to ourselves. | ||
− | * Libarian (Aybars) | + | * Libarian (Aybars) |
− | + | ** maintain minutes | |
− | + | *** What happens (at a high level, but include significant details) | |
− | + | *** Maintain -- in the minutes -- an agenda or TODO list (for the next meeting or just in general) | |
− | + | ** will keep group on task, and make sure individual choices fit with the whole. | |
− | + | *** be aware of what project everyone is currently working on, | |
− | + | *** and be sure to keep us on task in relation to where we would like to go | |
− | + | ** in general keep notes | |
− | * Developer (All of | + | * Developer (All of us) |
− | + | ** write code | |
− | + | ** write documentation | |
− | + | ** help other developers | |
− | + | *** be extra eyes, | |
− | + | *** listen, | |
− | + | *** help others clarify ideas | |
− | + | ** work in teams (team code - "One Keyboard, Two Minds") | |
− | + | ** be friendly and generally good spirited | |
− | + | ** rotate through Speedway runs | |
* Leader (Tobias) | * Leader (Tobias) | ||
− | + | ** Run the meetings | |
− | + | *** keep us on task as regards the meeting's agenda | |
− | + | *** make sure we stay on task (and don't dissipate into jokes) | |
− | + | ** will be a backup librarian -> make sure we're on task, help librarian think | |
− | + | ** generally manage the human factor of the group | |
− | + | ** if a disagreement arises, will be (unbiased) arbiter | |
* Architect (Kevin) | * Architect (Kevin) | ||
− | + | ** Will lead design of basic interfaces for different parts of the model | |
− | + | ** facilitate modularization of development tasks | |
− | + | *** break up problems into smaller, more manageable parts to code |
Latest revision as of 22:18, 27 March 2006
In addition to developing code, we've assigned these extra jobs to ourselves.
- Libarian (Aybars)
- maintain minutes
- What happens (at a high level, but include significant details)
- Maintain -- in the minutes -- an agenda or TODO list (for the next meeting or just in general)
- will keep group on task, and make sure individual choices fit with the whole.
- be aware of what project everyone is currently working on,
- and be sure to keep us on task in relation to where we would like to go
- in general keep notes
- maintain minutes
- Developer (All of us)
- write code
- write documentation
- help other developers
- be extra eyes,
- listen,
- help others clarify ideas
- work in teams (team code - "One Keyboard, Two Minds")
- be friendly and generally good spirited
- rotate through Speedway runs
- Leader (Tobias)
- Run the meetings
- keep us on task as regards the meeting's agenda
- make sure we stay on task (and don't dissipate into jokes)
- will be a backup librarian -> make sure we're on task, help librarian think
- generally manage the human factor of the group
- if a disagreement arises, will be (unbiased) arbiter
- Run the meetings
- Architect (Kevin)
- Will lead design of basic interfaces for different parts of the model
- facilitate modularization of development tasks
- break up problems into smaller, more manageable parts to code