Sabrina Rispin
sabrinar
Calendar With Blogs and Submissions
Intro
Time management as an individual is hard to achieve and I have personally found that it is easier said than done. Planning is necessary for anything to get done on time and that is the only reason I havn't submitted anything late (though some are submitted just on time). I have found that my individual time management has improved but in terms of group work it was hard to get things done early because you must rely on others (reflected above as all the later weeks were group activities/assignments). In future I hope to improve my team communication and hence help the group get stuff done on time.
All Claims
1. Completed all activites on time
2. All lectures watched on time
3. All assignments submitted on time
4. Major projects submissions on time
7. On time tutorial attendance
8. Contribution to class notes
9. On time, quality code review
1. All activities are done on time
Claim: I completed most activities early, if not then they were on time
Summary: I have completed all of the activities before the deadline every single week.
Evidence:
- Link to my Current Progress Page - This lists all of my activity submissions and their dates (on time).
- Calendar above underlines all late activities (of which there are none - excluding revision and challenges)
Blogging about Activities:
- (0) (Due Mar 6, Submitted Feb 28) - My recipe confusion activity.
- (0) (1) Tut-Lab - Some activities completed with my lab partner here (yes, also on time).
Module Activities blogs - I blogged about all of the weeks activities (before due date). If there is no blog I will link the submission for proof.
- (2.1 2.2) (Due Mar 20, Last Blogged Mar 15)
- (3) (Due Mar 27, Blogged Mar 23)
- (4.1 4.2) (Due Apr 3, Last Blogged Mar 29)
- (5) (Due Apr 17, Blogged Apr 11)
- (6.1, 6.2, 6.3) (Due Apr 26, Last Blogged Apr 25)
- (7.Wordless, 7.Mandelvision | 7.1, 7.2 ) (Due May 3, Last Blogged May 3)
- (8.1 | 8.2 | 8.3, 8.4) (Due May 8-12, Blogged May 4|7|10)
- (9.Module Reflection only) (Due May 17, Blogged May 17)
- (10.Module Reflection only) (Due May 31, Blogged May 27)
- (11. Module Reflection) Module 11 as of last edititing this page:
2. All lectures watched on time
Claim: Every lecture watched early every week.
Summary: I have watched all of the lectures and blogged about them every week a whole week before the deadline.
Evidence:
- (0) (1) (2) (3) (4) (5) (6) (7) (8) (9) (QW) (10) Lecture Blogs with my notes for each Module - Some early ones might only reference some of the lectures. Watched religiously every Wednesday when the lectures come out (see Calendar).
- Lecture 19 Class notes (Due Mar 27, Submitted Mar 26) - I added to the notes (having seen the lecture).
- Comment on lecture videos - Only one comment :( Need to do more!
3. All Assignments Submitted on time
Claim: Every assignment is submitted on time.
Summary: I have submitted all assignments (individual and group) on time.
Evidence:
- Mini Resume Assignment (Due Mar 20, Submitted Mar 15) - Submitted 5 days early!!!
- Doomsday Assignment (Due Mar 27, Submitted Mar 16) - Completed and submitted a WHOLE 11 DAYS EARLY!
- Something Awesome Proposal (Due Apr 3, Submitted Apr 2) - A day before is still on time.
- Midway Time Management (Due Apr 3, Submitted Apr 3) - On time is on time (you get the idea, I'll stop commenting now)
- Task 2B, Task2 Beauty (Due Apr 26, Submitted Apr 25)
- Submissions testgame.c, struct _game (Due May 3, Both Submitted May 3)
- Mr Pass (Due May 10, Submitted May 10)
- Game.c (Due May 12, Submitted May 12)
- mechanicalTurk.c (Due May 22, Submitted May 21)
- See Resume Page for final editing date of the 4 Resume sections here
4. On Time submissions to the Major Project
Claim: All of my contributions to the major project were on time.
Summary: I submitted all of my components and functions well before the due date and often helped others to submit on time
Evidence:
See the page histories of the major project components below, they show that all of our first submissions were on time and many more after that were made on time for different testing rounds.
My Contributions - below are blogs (made well before the due date) of my function contributions - on time as well as helping others be on time
- 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 thier 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)
5. Evidence of Planning and Reflection
Summary: I have personally evaluated my time management schedule, refleced continually on what happened throughout the week and re-evaluated my time management throughout the course.
Evidence:
Below are my Comp schedules and reflections on previous time management, my plan for Task 2B and reflections from every week.
6. Additional Evidence of Time/Project Management
Claim: I have excecuted my plans/team plans
Summary: I have maintained a steady computing schedule as well as submitted team project segments on time.
Evidence: As above in Planning and Reflection
Claim: On time tutorial Lab attendance every week
Summary: Tut-lab reflections almost every week as well as complete Tut-Lab attendance evidence
Evidence: Link to attendence and image below (just in case)
Claim: Contributed to class notes thoroughly and on time
Summary: I was the first to submit to our tut class notes and added a thorogh summary of the lecture (19)
Evidence: Lecture 19 Class notes (Due Mar 27, Submitted Mar 26)
Claim: Gave a quality code review in the first week
Summary: Amelia and I were the first group to volunteer for code review and completed the necessary activity on time for the review
Evidence: