7
 Team Leader Report AvMCS Analys is Christopher Willig

ChristopherWillig_TeamLeaderReport

Embed Size (px)

Citation preview

Page 1: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 1/7

 

Team Leader Report

AvMCS AnalysisChristopher Willig

Page 2: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 2/7

 

Deliverable Description

● Class Diagram

● Sequence Diagrams

● State Diagrams

Glossary● This deliverable included only one or! pac!age"

 – Wor! pac!age includes all diagrams #and glossary$ listed above"

 – %nly ris! to the or! pac!age as the due date #and not

submitting deliverable completed on time$"● All o& these ere pac!aged into one 'ip &ile #the deliverable$"

Page 3: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 3/7

 

Team %rgani(ation Structure

● %ne)to)one role to participant mapping"

 – *ach role consisted o& only one tas!"

 – Due to &our listed parts to the or! pac!age and ith having&our team members+ one)to)one as the logical choice"

 – ,ncludes mysel&

● Avoided many)to)many due to possible -alienation. o&certain participants"

 – Such as three o& the &our doing all o& the or!"

● Avoided many)to)&e due to danger o& over)commitmentby one or to participants"

Page 4: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 4/7

 

Tas! to /articipant Mapping

● Christopher Willig0 Glossary

● Saa!shi Malhotra0 State Diagrams

● 1ardhaman Metpally0 Class Diagram

● 2ogesh Teani0 Sequence Diagrams

Page 5: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 5/7

 

Schedule

● The amount o& time given to hand in the deliverable aseight days"

● , did not set any milestones &or each team member"

 –

This alloed them to or! around events that ere unrelatedto their tas! #personal li&e events such as shopping$"

● /articipants had all eight days to complete their tas! andsubmit their completed tas!s to me"

,& tas!s ere related to each other+ participantscontacted each other and completed them accordingly#peer)to)peer$"

Page 6: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 6/7

 

Communication /rocesses

● /eer)to)/eer communication

● 3igh level o& dependency beteen &our tas!s

 – /eer)to)/eer most e&&icient method o& team

communication"

● /articipants could not meet in person

 – Communication in&rastructure used as critical to

maintaining peer)to)peer communication"

Page 7: ChristopherWillig_TeamLeaderReport

7/17/2019 ChristopherWillig_TeamLeaderReport

http://slidepdf.com/reader/full/christopherwilligteamleaderreport 7/7

 

Communication ,n&rastructure

● WhatsApp

 – Main communication pipeline

● 4aceboo!

 – Relied on hen , e5perience issues ith WhatsApp

● *mail

 – 4inal tas! submissions ere submitted to me"

● ,n)person meetings – %ne in person meeting #planned &or to$