Team Project. 1.1 Deliverable: Initial Planning Milestone Submission For the Initial Planning Milestone, you will submit the following artifacts:

Size: px

Start display at page:

Download "Team Project. 1.1 Deliverable: Initial Planning Milestone Submission For the Initial Planning Milestone, you will submit the following artifacts:"

Beatrice West
5 years ago
Views:

1 Team Prject Yur team will wrk n the prject ver rughly 8 weeks, and yu will receive grades bth fr yur team s perfrmance as a whle and fr yur individual cntributins t the prject. The prject will be divided up int an initial planning perid (rughly 2 weeks) and tw develpment iteratins, Alpha and Beta, (rughly 3 weeks each). First, this dcument describes the team deliverables and grading criteria fr each stage f the prject. Then, it describes gals and grading criteria fr yur individual cntributins thrughut the prject. 1 Team Deliverables: Initial Prject Planning The main deliverables t cme ut f the initial planning are a cllectin f artifacts regarding prject requirements, planning, and design. These artifacts are cllectively call the Initial Planning Milestne. 1.1 Deliverable: Initial Planning Milestne Submissin Fr the Initial Planning Milestne, yu will submit the fllwing artifacts: 1. a set f user stries, 2. a sitemap fr yur web app, 3. user interface sketches, and 4. a class diagram f yur mdel. The artifacts shuld satisfy the fllwing grading criteria: Tagged submissin in GitHub. T grade yur cde, I will clne yur team s GitHub rep, and checkut a tagged versin f yur cde. Yu must tag yur cde as plan. Artifact quality. All yur artifacts must be f high quality. User stry quality. Yur USs must fllw the guidelines/principles described in lecture. Fr example, they must fllw the templates given and must satisfy the INVEST criteria. Sitemap quality. I dn t care abut the exact ntatin yu use fr this diagram. Hwever, it shuld be easy t figure ut what pages yur site will have and hw thse pages will be intercnnected. UI-sketch quality. Yur UI sketches shuld shw the basic page elements (fields, buttns, etc.). They may r may nt be styled (e.g., with clrs/graphics). Such sketches are smetimes referred t as wireframes. Design quality. Yur designs shuld fllw principles f gd design, such as the SRP (Single Respnsibility Principle) and DRY (Dn t Repeat Yurself) principles. Class diagram quality. Use prper class diagram ntatin (as given in lecture). Label all assciatins, and include all multiplicities. Include attribute types (e.g., name : string ). Cnsistent naming. Yu must use cnsistent names fr things acrss artifacts. That way, fr example, we can tell where each UI sketch fits int the sitemap. Diagram frmat. Diagrams need nt be anal-retentively typeset; they simply must be readable. Thus, yu may hand-draw diagrams n paper/whitebard, and scan them int a

2 digital frmat (PDF preferred). Of curse, if yu really want t typeset them, that s OK t. Diagram submissin. Keep the diagrams and USs with yur web app cde. Specifically, add a flder misc t the tp level f yur prject, and place the file(s) in there. Keep in mind that these artifacts will evlve as the prject rlls alng. Plan fr such evlutin. Nte that there is an A&B eligible rle belw (Quality Assurance Czar) with special respnsibilities regarding the milestne submissin. 2 Team Deliverables: Alpha Iteratin There are three main deliverables fr the Alpha Iteratin: a dem vide, a cllectin f prject artifacts, cllectively referred t as the Alpha Milestne, and a live in-class dem sessin. 2.1 Deliverable: Alpha Iteratin Dem Vide Yur team will be respnsible fr creating a dem vide f yur sftware. This vide is mainly t assist the curse instructrs in grading yur prgress n the prject. The vide must als have an accmpanying text dcument that lists wh built each f the demed features. The dem vide and dcument must meet the fllwing grading criteria: Criterin: Demnstrate the prgress that the team has made s far. All the new features. Include all the latest features in the dem. Dn t leave any ut. A big pint f this exercise is t demnstrate all the wnderful prgress that the team has made. Nte that this criterin des nt mean that yu shuld skip redeming ld features. It just means yu shuldn t skip the new nes. What s new? Clearly state which features are new as they are being demed. Yu need nt explicitly state which features are ld, unless yu think there may be cnfusin. Backend t. Althugh UI features are a high pririty, yu may als demnstrate that backend functinality is wrking, even if it s nt yet cnnected t the frntend. The key thing is t prve that the cde runs and wrks! Alng thse lines, yu may dem autmated tests. Criterin: Make clear wh cntributed what t the prject. Wh made it? In the text dcument, give an entry fr each new/updated feature demed. Each entry must include the name f the feature, the time ffset in the vide where the feature was demed, and the U f M username(s) f wh built the feature. If multiple peple cntributed t a feature, say wh did what. Dn t frget t credit anyne. Be sure nt t make any factual errrs. New r ld? If it s nt clear, make it clear what part f the wrk is new. Criterin: Display the team s wrk in the best pssible light. Stry frm. Any demnstratin f UI must take place in the cntext f a chesive stry. That is, the presenter must describe ne r mre characters (with names, like Alice and/r Bb) and relate a stry abut the character using the sftware. The presenter must stick t this stry frmat. The stry and accmpanying dem must be well thught ut, and nt leave the audience with the impressin that the presenter is making it up as he/she ges alng. Use realistic names fr things and nt made-up placehlders, like f and slafjsd.

3 UI first. Since the UI is generally mst interesting, yu shuld lead with that. General audience. Dn t frget that nt everyne is as familiar with yur prject as yu are. T be n the safe side, explain it as if yu are talking t smene wh has never seen it befre. N special effects r fancy editing. The vide shuld clearly shw a user (r users) interacting with yur web app. Dn t add special effects r sund effects, which distract r detract frm the authenticity f the interactin. Criterin: Length and frmat cnstraints. Time limit. The vide must be n mre than 10 minutes lng. Fill the Time. Yur vide shuld be at least 8 minutes; therwise, yu re prbably ding it wrng. Vide frmat. The vide must be in a frmat playable in VLC ( which accepts mst cmmn frmats. Nte that the creatrs f the dem vide and accmpanying dcument are eligible fr A&B pints (see belw). 2.2 Deliverable: Alpha Milestne Submissin Fr the Alpha Milestne, yu will submit the fllwing artifacts: 1. a cpy f yur cde (tagged in GitHub), and 2. up-t-date versins f yur Initial Planning artifacts (i.e., USs, sitemap, UI sketches, and mdel-class diagram). The artifacts shuld satisfy the fllwing grading criteria: Tagged submissin in GitHub. T grade yur cde, I will clne yur team s GitHub rep, and checkut a tagged versin f yur cde. Yu must tag yur cde as alpha. Cde builds and runs. I shuld be able t build and run yur cde using the usual apprach frm the Bt Camp prjects. If any special instructins are required t build/run yur sftware, include them in the README file in yur prject s tp-level directry. Replicable dem. I shuld be able t replicate yur dem vide. If seed data is required t d s, yu must smehw make that data available t me (pssibly giving instructins in the README). Artifact quality. All yur artifacts must be f high quality. The criteria frm the Initial Planning Milestne still apply, with the fllwing additin. Cde quality. Yur cde must fllw cmmn style guidelines and be well rganized and readable. Fr example, all cde must be prperly indented, and class/variable/methd names must be sensible. Yu shuld als d yur utmst t avid bugs and ther slppiness. Custmer satisfactin. Yur custmer will prvide feedback n hw well yur team has satisfied the requirements he/she gave yu and hw well aligned yur team s priritizatin f the wrk has been with the custmer s pririties.

4 Nte that there is an A&B eligible rle belw (Quality Assurance Czar) with special respnsibilities regarding the milestne submissin. 2.3 Live In-Class Dem Sessin Fr this sessin, each team will perate a dem bth. One member f yur team (the dembth peratr ) must run the bth, prviding visitrs with an interactive dem f yur team s sftware. The remaining members f yur team will circulate abut the ther bths, acting as visitrs. The interactive dem must meet the fllwing grading criteria: Clearly explain yur prject t visitrs. Assume that visitrs have never seen yur prject befre. Thrughly and clearly explain what prblem yur prject slves and hw it des s. Display the team s wrk in the best pssible light. Use presentatin techniques discussed this semester t present yur team's sftware in an engaging and cmpelling way. Als, think abut the best way t set up yur bth. What equipment will yu need? Extra mnitrs? Allw visitrs t use yur prject. This is an interactive dem, which mean that visitrs shuld be allwed t try ut yur prject. Time limits. Dn't g t lng. The dem must be n mre than 10 minutes lng. Be sure t allw enugh time fr users t play with yur system. Fill the time. Keep yur visitrs engaged thrughut the 10 minutes. Nte that dem-bth peratr is an A&B eligible rle (see belw). Figure 1 belw prvides an idea f what the flrplan fr the dem sessin will be like. 3 Team Deliverables: Beta Iteratin The deliverables fr Beta Iteratin will be mstly the same as fr Alpha Iteratin, with nly a cuple changes: Dem vide. Fllw the instructins abve fr creating the vide. This time, the vide may be up t 15 minutes lng. Make the dem a gd verall tur f yur system, including bth new and ld features. Als, make the wh-did-what dcument the same as befre, except nly credit wrk dne in the Beta Iteratin. T clarify, the dem shuld include wrk dne in Alpha Iteratin, but dn t say anything abut it in the dcument. Make sure that the wh-did-what dcument is specific and precise s that n Alpha Iteratin wrk might be accidentally credited as Beta Iteratin wrk. Milestne submissin. Fllw the instructins abve fr creating yur milestne submissin, except this time, tag yur cde versin as beta. Make sure that all yur submissin dcuments are up t date (esp. yur user stries and class diagram). Live in-class dem sessin. Fllw the instructins abve fr presenting the dem. This time, the dem shuld 15 minutes lng (instead f 10). This iteratin has the same A&B pprtunities as the Alpha Iteratin.

5 4 Individual Prductivity 4.1 Regular Prductivity The majrity f yur individual prductivity pints are assciated with regular prductivity. Each team member is assigned certain tasks fr each iteratin, and it is expected that he/she will cmplete his/her assigned tasks in a timely manner. It is als expected that team members will be cntinuusly prductive, and nt t put ff their wrk, rushing t slap smething tgether at the last minute. We will use a cmbinatin f the fllwing criteria t assess yur regular prductivity: Make it int the dem! A key indicatr f whether yu are prducing value fr yur team is whether yur wrk is visible in the dem. If yur cntributins are nwhere t be seen in the dem, it will almst certainly cunt against yu. Minimum acceptable cntributin. Yur cmpleted wrk (as reprted with the dem vide) will be cmpared against the minimum acceptable wrk in the iteratin plan. Teammate evaluatins. Yur teammates will prvide their subjective assessment as t yur perfrmance. GitHub metrics. GitHub tracks hw much each team member has cntributed t the cde base. These metrics will prvide further evidence f yur cntributins. If a team member s prductivity is fund t be particularly unsatisfactry, they may receive the fllwing additinal penalty: Milestne Deductin fr Unprductiveness. A student wh demnstrates unsatisfactry prductivity may als lse pints n the assciated milestne. This deductin is meant t accunt fr the lack f cntributin made by an unprductive team member t the prject. 4.2 Abve and Beynd Prductivity T achieve the highest grades in the curse, yu will need t g abve and beynd the call f duty; thus, yur individual prductivity grade als accunts fr Abve and Beynd prductivity. Yu may earn A&B pints in the fllwing ways. Play a special rle. Each iteratin, yu will have an pprtunity t play a special rle. The team shuld assign these rles demcratically, since the rles serve key functins n the team. Prject Manager (PM). This rle is cncerned with custmer and instructr cmmunicatin, and with task planning and teammate crdinatin and cmmunicatin. Here sme additinal details: Reliable. Must be highly reliable (e.g., attends all classes/meetings and respnds quickly t s). Organized. Must be rganized and detail riented. Fr example, this persn will be held respnsible if class prcedures are nt fllwed crrectly. Deciding vte. Althugh mst team decisins shuld be made demcratically, the PM des have authrity t break any stalemates that shuld arise.

6 Cmpensatin: 1 A&B pint per iteratin (1 persn nly). Quality Assurance Czar. This rle is cncerned with ensuring that the milestne artifacts are f high quality. Here are sme additinal details: Cde gatekeeper. This persn must make sure that the submissin instructins are fllwed, and that cntributrs adhere t gd design and cding standards. Rep rganizer. He/she must ensure that the rep stays well rganized. Class diagram creatr. He/she is respnsible fr prducing the class diagram, and making sure that the cde is cnsistent with the design. Cmpensatin: 1 A&B pint per iteratin (1 persn nly). Vide-Dem Creatr(s). The team member(s) wh create the vide dem will receive special cmpensatin fr their extra effrt. Cmpensatin: 2 A&B pints per team per iteratin, t be divided based n cntributin (multiples f.25 r.33) t whever wrked n the vide. Dem-Bth Operatr. The team member wh perates the dem bth will receive special cmpensatin fr their extra effrt. Cmpensatin: 1 A&B pint fr the bth peratr (1 persn nly). Be a tp cntributr. Each iteratin, I may identify ne r tw members f each team wh have made exceptinal cntributins in the past iteratin. These 10Xers will receive an A&B bnus fr their exceptinal wrk. Negtiate additinal wrk. In additin t yur planned wrk in a given iteratin, yu may take n additinal wrk fr A&B pints. Yu must negtiate the wrk and cmpensatin with me, and I must apprve it. Such wrk ften invlves adding bnus features t the prject; hwever, I am pen t yur ideas.

7 Figure 1. Dem sessin flrplan.

Assessment Field Activity Collaborative Assessment, Planning, and Support: Safety and Risk in Teams

Assessment Field Activity Collaborative Assessment, Planning, and Support: Safety and Risk in Teams Assessment Field Activity Cllabrative Assessment, Planning, and Supprt: Safety and Risk in Teams OBSERVATION Identify a case fr which a team meeting t discuss safety and/r safety planning is needed r scheduled.