Difference between revisions of "SE2006:group bar:roles"

From Earlham CS Department
Jump to navigation Jump to search
(Fleshing out of roles)
 
m
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
+
** maintain minutes
−
- What happens (at a high level, but include significant details)
+
*** 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)
+
*** 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.
+
** will keep group on task, and make sure individual choices fit with the whole.
−
- be aware of what project everyone is currently working on,
+
*** 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
+
*** and be sure to keep us on task in relation to where we would like to go
−
- in general keep notes
+
** in general keep notes
  
−
* Developer (All of usex & ColinC: Developers
+
* Developer (All of usex & ColinC)
−
- write code
+
** write code
−
- write documentation
+
** write documentation
−
- help other developers
+
** help other developers
−
- be extra eyes,
+
*** be extra eyes,
−
- listen,
+
*** listen,
−
- help others clarify ideas
+
*** help others clarify ideas
−
- work in teams (team code - "One Keyboard, Two Minds")
+
** work in teams (team code - "One Keyboard, Two Minds")
−
- be friendly and generally good spirited
+
** be friendly and generally good spirited
−
- rotate through Speedway runs
+
** rotate through Speedway runs
  
 
* Leader (Tobias)
 
* Leader (Tobias)
−
- Run the meetings
+
** Run the meetings
−
- keep us on task as regards the meeting's agenda
+
*** keep us on task as regards the meeting's agenda
−
- make sure we stay on task (and don't dissipate into jokes)
+
*** 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
+
** will be a backup librarian -> make sure we're on task, help librarian think
−
- generally manage the human factor of the group
+
** generally manage the human factor of the group
−
- if a disagreement arises, will be (unbiased) arbiter
+
** if a disagreement arises, will be (unbiased) arbiter
  
 
* Architect (Kevin)
 
* Architect (Kevin)
−
- Will lead design of basic interfaces for different parts of the model
+
** Will lead design of basic interfaces for different parts of the model
−
- facilitate modularization of development tasks
+
** facilitate modularization of development tasks
−
- break up problems into smaller, more manageable parts to code
+
*** break up problems into smaller, more manageable parts to code

Revision as of 23:01, 8 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
  • Developer (All of usex & ColinC)
    • 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
  • 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
Retrieved from "https://wiki.cs.earlham.edu/index.php?title=SE2006:group_bar:roles&oldid=1411"