Sabrina Rispin
sabrinar
Intro
Teamwork is more than just being stuck with a bunch of random people and told to get something done. It is probably one of the hardest skills to learn but one of the most important skills to have. It takes a great deal of communication to coordinate people to cooperate and work constructively together. In many ways many hands make light work and with many great minds comes different ideas. I have alwyas had trouble with teamwork, wishing to get a task done my way I am quick to exclude others in order to quickly solve a problem. But the major project (Game.c) has really taught me that there are some tasks to big for one person, you need others and can't do it without others. I have aimed to take my controlling personality and channel it into team management (someone has to be the 'you must get this done' person) and helping others to write code (instead of doing it by myself).
Of all of the skills I have developed I feel this one was the hardest but most rewarding.
All Claims
1. Contribution to the major project
3. Contribution as a lab partner
4. Helping others in the course
1. Effective Contribution to the Major Project
Claim: I contributed greatly to the major project.
Summary: Not only did I complete all of my assigned sections of the project, I would also help others to complete their sections as well.
Evidence:
- As from the time management section on the major project:
See the page histories of the major project components below, they show that all of our submissions
My Contributions - below are blogs of my function contributions - as well as helping others with their sections
- Setting up testGame.c (shows leadership, and planning - I assigned random test functions for everyone)
- My testGame functions completed
- Link to testGame.c first submission and code - all of my tests completed
- First group meeting and collabedit for game struct
- My Game.c functions and some testGame stuff (blog)
- Reflection on Game (May 10, due May 12)
- Implementing my Game.c functions, cleaning up Game.c and creating the printGame function
- More on printGame, my extra functions and helping others with their functions
- Backed up by blog by Amelia
- Group page - with extensive posting from me to get everyones functions ready (Post May 11, day before Game.c due)
- Game Completion - helping everyone to add their functions! (Posted blog 13, occured the night of May 12 - Due date of Game.c)
- Going through the round results
Other peoples/team blogs that also outline my contribution
The mechanical Turk - my blogs and contribution
- I completed Mr Pass
- mechanicalTurk history - shows my role in submitting the turk (unless I was unavailable)
- My functions in mechanical turk
- Checking the turk results
Darren's blogs
Also see the comments from my team members above on my contribution and teamwork
2. Effective Contribution to Task 2B
Claim: I contributed a lot to Task 2B
Summary: I acted as the unofficial "keeper on tracker" often working on the project to complete my own sections as well as help my partner with his tasks as well. We spent many sessions together working on the project.
Evidence:
- The page I created of our game plan as well as who completed what tasks
My Blogs
- Module 5 Reflection
- First Tut Lab as new partners
- First official mandelbrot blog
- Completing escape steps and printMandelbrot (in ascii)
- Nick and I working on simpleServer with printMandelbrot
- Nick and I struggling with BMP stuff
- Completing parsing and finishing Task 2B
- Task 2B submissions
- Final Task 2B submission
Nicholas Everton's Blogs
3. Contribution to Lab Partners
Claim: Every week I was present and working with my lab partners
Summary: All of the group activities were worked on with my partner/s in the labs and were blogged about each week on the day of or day after the lab.
Evidence:
- Tut-Lab blogs (Partners were Amelia initially, then Nick for Task 2B, then Darren for mechanicalTurk + Amelia, Nick, Jesse for Game.c)
- (Module 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 - Quiet Week, 10, 11 - no blog for last 2 weeks)
- All teamwork blogs for the Game and Task 2B above also apply for contribution to lab partners
Was present for every tut-lab this semester
- Link to attendence and image below (just in case)
4. Helping others in the Course
Summary: I commented on at least 3 peoples posts a week if not more and would often help others solve their problems or improve thier work online
Evidence:
- See someof the comments above of other people outside of my partner groups that I have helped (not even all of them)
- Contribution to class notes: Lecture 19 Class notes
Every week after each reflection I would comment on 3 peoples blogs in order to give constructive feedback, here they all are:
5. Additional Evidence
Summary: Task 2B plan, and the major project nagger
Evidence:
Claim: I have worked on identifying problems and worked with others to solve them
Summary: Pretty straightforward
Evidence: See all of the Game.c and Task 2B stuff above, for specific examples see below
- Collabedit with Amelia
- Game Completion - helping everyone to add their functions!
- Task 2B weekend teamwork
Claim: I have supported and encouraged others
Summary: See all of the comments in the infographic above as well as the module reflections
Evidence: