Tuesday, April 1, 2014

Small Group Meeting #7

Here are the notes from our meeting:
  • next week: new hire assignment
    • put out some media characterizing the culture - about us as a team
    • email our ideal candidate description to teaching staff
    • make a 5 minute pitch next Thursday during LGM to a hypothetical candidate
    • 2 things to do:
      • think about who we want to hire
        • e.g. these are the last 5 minutes before they walk out
        • if we could hire two people on our team, what kind of people do we want
        • graphic designer
        • sales person
        • alum will come in and play the role
      • make the case for why they should work here
  • do more user testing - observe the ideal users of our software

We also had a reflection of our performance as a team last quarter.
  • what did we do best?
  • what do we need to do better?
  • what do we want to accomplish this quarter?

Below is our self evaluation:


How much have we taken advantage of the following?Self rating (0 = not at all, 9 = as much as humanly possible)How much can/did this help our project? (0 = no help, 9 = huge help)Notes
Agile programming methodologies (sprint concept, frequent short status meetings)8
Rapid prototyping6
If your team's maximum capability as a unit all working together is 10, what kind of output score would you say you had in Winter? What do you feel like is a realistic expectation for this score given that unlike in the real world, not everyone is primarily committed to this project over other professional responsibilities?7N/AThere were some lulls. Really good with a deadline.
Group dynamics theory/practice (Did you use these to resolve conflicts, reflect about how to work better, etc?)5
Tools - Source control (branching, code review)9
Tools - Issue tracking (e.g., Github)6
Tools - Collaboration (Blogs/FB/Google groups/group messaging etc) to enhance internal and external communications9
Use of media (photos, video, etc.) to capture IP, team culture and to generally communicate effectively7
Meeting with human beings who are likely targets for your software4.5
Observing use of your software in personN/AIncreasingly important
Observing use of your software via analytics0Valuable for this quarter
What did we do best?
What was our weakest point?
What do we want to accomplish this quarter?

No comments:

Post a Comment