...
An important consideration in creating these role distinctions is that midnight sun Midnight Sun maintains an open door policy: members are free to join and leave, and are simply given the mantra “you get out what you put in”. This attitude towards recruitment creates the necessity of having projects to work on no matter what state the car is in, so we can always fulfill our primary goal of being a student oriented design team.
1. New Member | 2. Developer | |
Knowledge | Has some programming knowledge. | Has some knowledge of systems from onboarding, knows how a task fits into a project. |
Independence | No independence expected, just onboarding. | Given a task with defined requirements and some design, can implement a technical solution. |
Responsibility | Completing onboarding. | Owns a number of specific tasks, and is responsible for delivering them. |
Commitment | Any. There isn’t any expectation on timelines. | Spend time on their tasks between most standups, such that clear progress has been made. |
3. Project Lead | 4. Lead | |
Knowledge | Has knowledge of their project(s), and knows how the project(s) interact with others. | Has knowledge of the entire system, and can contribute to any portion. |
Independence | Given a project with defined requirements, can design and implement a technical solution, including task decomposition. | Given a system, can develop technical requirements from product requirements and deliver projects to fulfill them. |
Responsibility | Owns a specific project, and is responsible for delivering it on time. If timelines become unachievable, responsible for advocating for a limiting of scope or extension of timelines. | High level architecture and design, ensuring projects are meeting timelines, ensuring team requirements are met. |
Commitment | As much as required to deliver their projects. | As much as required to deliver on the team requirements. |
...