Advertisement
TheScriptan

Untitled

Dec 13th, 2017
83
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.04 KB | None | 0 0
  1. I defined my role as a checker, since I prefer to have everything structured and checked. As an example I like to see our project folder hierarchy organized, so none of us gets lost, so it is my duty to optimize hierarchy in order to achieve full efficiency when browsing through folders. Other thing I was taking care of is evaluation of how we as a group doing in terms of finishing the project. Time and accomplished tasks were two factors in order to determine if we were behind or ahead of project work. When I was sharing this information during the meetings we as a group noticed that I prefer to say directly how we are doing without hiding something. According to Edward T. Hall contexts I follow Low-context culture of expressing my thoughts. There is a risk it can cause discomfort, but I believe the faster we realize the issue, the better our end result will look like.
  2.  
  3. BELBIN ROLES
  4. To strengthen our teamwork efficiency we've done Belbin Roles in order to figure out where each of us strives the best.
  5.  
  6. Plant: Sharing my creative thoughts and putting them into realization is what I like so I always share my ideas with the group whenever we're working on a problem.
  7.  
  8. Implementor: For me, system how we will approach a problem matters the most, I find it difficult to function in a messy organisation as everything is split apart and there are no linear tasks to follow, in order to achieve a comfortable working environment I try to suggest ideas how we can organize our tasks so the whole group can work faster.
  9.  
  10. Coordinator: Whenever we as a group face problems I always try my best to approach it with a calm mindset, so the solution can be achieved without stressing and wasting time on what we could have done better. End-goal is my priority when working together.
  11.  
  12. Strengths:
  13. - Fast information lookup
  14. - High school experience in programming
  15. - Communicatie
  16. - Easy-going
  17.  
  18. Weaknesses
  19. - Lack of drive
  20. - Lack of self-motivation
  21. - Indecisive
  22. - Distractive
  23.  
  24. Tasks
  25. - Project Description, setting up working environment (Google Drive, Trello, Github)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement