Guest User

Untitled

a guest
Apr 23rd, 2018
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.02 KB | None | 0 0
  1. DTR IDEA-BOX
  2.  
  3. Group Member Names:
  4. Gavin
  5.  
  6. Project Expectations: What does each group member hope to get out of this project?
  7. Goals and expectations:
  8. Gavin: Match HTML and CSS spec and finish all phases of the project.
  9. Kent: I would like to improve my understanding of Javascript and become more efficient with Html and Css. Meet all requirements of the project.
  10.  
  11.  
  12. Team strengths:
  13. Gavin: HTML, CSS, JavaScript, Objects, Arrays.
  14. Kent: CSS
  15.  
  16. How to overcome obstacles:
  17. Gavin: open communication, observe all options, try things and see what works.
  18. Kent: Have open communication and be open to any and all options presented.
  19.  
  20. Schedule Expectations (When are we available to work together and individually?):
  21. Gavin: Iā€™m available all weekend and after day after class till 8pm.
  22. Kent: I am available at anytime on any day.
  23.  
  24. Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
  25. Gavin: frequent communication through Slack, reach out as soon as there is a question or concern.
  26. Kent: We should communicate frequently through Slack. Anytime a team member has a question about the project they should communicate with their partner. I am open to text messages if I am away from the computer.
  27.  
  28. Abilities Expectations (Technical strengths and areas for desired improvement):
  29. Gavin: desired improvement in efficiency.
  30. Kent: I feel comfortable with Css and Html and less comfortable with javascript.
  31.  
  32. Workload Expectations (What features do we each want to work on?):
  33. Gavin: we should both work on majority of the project together.
  34. Kent: I feel comfortable styling the page and helping with the javascript.
  35.  
  36. Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):
  37. Gavin: git in it frequently.
  38. Kent: Multiple git uploads and comments every day to help keep track of the project and how it is progressing.
  39.  
  40. Expectations for giving and receiving feedback:
  41. Gavin: open, frequent constructive feedback.
  42. Kent: I expect frank open dialogue about any and everything that pertains to the success of the project.
Add Comment
Please, Sign In to add comment