ITEC 325 2017fall ibarland

home—lects—hws
D2L—breeze (snow day)

project-team-feedback
itec325 project feedback

(due May.04 17:00, under ibarland's office door or on D2L)

Name                                                             

Team Number            Your role/responsibility                                                             

Evaluation of other teams

Go to the websites, and actually try out each product, for each other team.

Note that you are allowed to try to enter “bad” inputs — either into the form, or POST/GET requests. However, do not attempt to inject SQL which alters (much less drops) any tables; you certainly can try to enter information which yields error messages, ill-formatted HTML pages, or even “bad” rows being stored in the table. Likewise, do not use tools/attacks that do more than make POST/GET requests. Keep in mind, other students may be trying such values on your forms — use htmlspecialchars, mysql_real_escape_string, and stripslashes (with get_magic_quotes_gpc()) as appropriate.

Imagine that you have four dear relatives, each starting a business in our class's project areas (what a coincidence!). For a gift, you will invest in each of the other teams’ products. Make your judgement based on the product as currently working and presented, plus the opportunity for (say) 10 person-hours of touch-up work.

Fortunately you just won $40,000 in the lottery², and you'll allocate that among your four investments (e.g. $20,000 to one team, $9500 to two others, and $1000 to the third.) Don't enter any an amount next to your own project — you've already invested enough in your own project! You are encouraged (but not required) to look at the projects from the other course-section, even though you didn't see their formal presentation. URL is https://php.radford.edu/~projN/, except as indicated.

• Team 1:             Team Team Name (RU Betting)
• Team 2:             unnamed (RadfordPedia)
• Team 3:             Team Bluey (teaching badges)
• Team 4:             Team Hydroponic Chicken (workload tracker)
• Team 5:             unnamed (dance prof's site)

Evaluation of your team

Consider your teammates in light of the following categories:

• Communication/Professionalism: Did they reply to emails/texts in a timely manner; available for meetings and on-time for them? If they had delays or difficulties, did they communicate this to the team?
• Completion: Did they do the work they were expected to? Did they put in sufficient time?
• Helpfulness: Did they contribute the team overall (ideas as well as code)? Were they approachable? Were they willing to help, when issues arose? Was working with them enjoyable?

• Teammate's name                                    
  
  Teammate's role/responsibility                                                                                                
  
  Communication/Professionalism:        Completion:        Helpfulness:       
  
  Any other comments about this teammate:
  
  
  
  
  
  I'll include the gist of this comment in summarized, unattributed feedback to that person, unless you check here:     
• Teammate's name                                    
  
  Teammate's role/responsibility                                                                                                
  
  Communication/Professionalism:        Completion:        Helpfulness:       
  
  Any other comments about this teammate:
  
  
  
  
  
  I'll include the gist of this comment in summarized, unattributed feedback to that person, unless you check here:     
• Teammate's name                                    
  
  Teammate's role/responsibility                                                                                                
  
  Communication/Professionalism:        Completion:        Helpfulness:       
  
  Any other comments about this teammate:
  
  
  
  
  
  I'll include the gist of this comment in summarized, unattributed feedback to that person, unless you check here:     

Reflection on your project

What was your favorite part of your team's project?
(Is there a feature, idea, or bit of code that you are particularly proud of, personally?)





What would you do differently, if you had it to do over?





What tips/suggestions would you give next year's project teams?

home—lects—hws
D2L—breeze (snow day)

©2017, Ian Barland, Radford University Last modified 2017.Dec.13 (Wed)

Please mail any suggestions (incl. typos, broken links) to ibarlandradford.edu