PRE2018 3 Group11:Organization: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
(Initial structure of the organizational page (group composition, deliverables, milestones, task division, planning, log))
 
No edit summary
Line 1: Line 1:
<link rel=http://cstwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group11&action=edit"stylesheet" type="text/css" href="theme.css">
<link href='https://fonts.googleapis.com/css?family=Roboto' rel='stylesheet'>
<div style="width:calc(100vw - 175px);background-color:#EFEFEF;padding-bottom:35px;position:absolute;top:0;left:0;">
<div style="font-family: 'Roboto','q_serif', Georgia, Times, 'Times New Roman', serif; font-size: 14px; line-height: 1.5; max-width: 900px; word-wrap: break-word; color: #333; font-weight: 400; box-shadow: 0px 25px 35px -5px rgba(0,0,0,0.75); margin-left: auto; margin-right: auto; padding: 70px; background-color: white; padding-top: 25px;">
= Group Composition =
= Group Composition =
We explain the composition of our group. We can do this in textual format, or include a table. I (daniel) believe it is a nice idea to do this textually. That way, we can include information on strong and weak points as discussed in the meeting.
 
Group 11 consists of five diverse people. Firstly, there is Nimo Beeren (1019824). Nimo is a double bachelor student, doing both Software Science as well as Web Science. As expected, his strong points include programming. Secondly we have Noah Rachdi (1283197), a student who knows his way around Psychology and Technology. Noah is a critical thinker, and provides a psychological point of view to the team. To strengthen the team of programming-savvy people there is Işılsu Keleş (1035673). Işılsu brings not online programming knowledge to the team as Software Science student, but provides her great writing skills as well. Since no robot-building team is complete without at least one mechanical engineer, this group contains one as well. Pim Van Hees (0966509) is the go-to person when it comes to building anything. Finally, there is Daniel Barenholz (0998941), a third Software Scientist. He is decent at organisation and management, and provides this to the team. All in all, group 11 is a small but experienced multidisciplinary team.


= Deliverables =
= Deliverables =
Line 15: Line 22:
We can change this as time goes on.
We can change this as time goes on.


<!-- Not sure if we want this.
= Log =
= Log =
A weekly log of the things we have done.
A weekly log of the things we have done.
-->

Revision as of 14:29, 11 February 2019

<link rel=http://cstwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group11&action=edit"stylesheet" type="text/css" href="theme.css"> <link href='https://fonts.googleapis.com/css?family=Roboto' rel='stylesheet'>


Group Composition

Group 11 consists of five diverse people. Firstly, there is Nimo Beeren (1019824). Nimo is a double bachelor student, doing both Software Science as well as Web Science. As expected, his strong points include programming. Secondly we have Noah Rachdi (1283197), a student who knows his way around Psychology and Technology. Noah is a critical thinker, and provides a psychological point of view to the team. To strengthen the team of programming-savvy people there is Işılsu Keleş (1035673). Işılsu brings not online programming knowledge to the team as Software Science student, but provides her great writing skills as well. Since no robot-building team is complete without at least one mechanical engineer, this group contains one as well. Pim Van Hees (0966509) is the go-to person when it comes to building anything. Finally, there is Daniel Barenholz (0998941), a third Software Scientist. He is decent at organisation and management, and provides this to the team. All in all, group 11 is a small but experienced multidisciplinary team.

Deliverables

These are the main things that must be done by the end of the project.

Milestones

These are the deliverables split up into smaller tasks that we can set deadlines for.

Task division

Who will work towards what milestone/deliverable.

Planning

The planning of the whole project should include deadlines for each of the deliverables and milestones that were established. We can change this as time goes on.