Team Members: Elijah Jamison, Robert Lesnick, Jerald Kahn
Accomplishments:
1. Rob and Eli collaborated on the project schedule, and are preparing the final schedule
2. Myself and Rob met with Courtney on the phone Monday, 10/24 and discussed way to to get the BAs to start producing deliverables
3. Myself and Eli met with Courtney on the phone Monday, 10/17
4. I Reviewed my documentation with Courtney before class (risk directory, quality management, stakeholder list, RACI, communication plan)
5. Rob met with the BA’s on Thursday afternoon and helped them come up with a plan to start producing a final solution
6. Scheduled remaining appointments with Courtney
Goals:
1. Schedule project status meeting with the BAs for next week
2. Schedule a Documentation QA session for the following week
3. Schedule a prototype QA session for two weeks out
4. Finalize the stakeholder list, organizational chart, risk directory
5. Write written sections of risk management and quality management plan
6. Post final version of project schedule

Team Members: Stephanie Cheng, Jonathan Holland, Jacky Wong
Period: 10/24/2016-10/28/2016
Hours: 5
Hours to Date: 40
Accomplishments:
1. Met with Courtney for better feedback on our documentation.
2. PMs met with each other so we could update the documentation
Goals for Next Week:
1. We should have the first look of the prototype for all of the use cases.
2. We will make sure all the previous documentation is up to date.
3. Revising management documentations for Courtney to go over.
Issues:
1. We still have some questions trying to figure out how to format our documentations

Goals for November 4th, 2016
1) Finish project schedule for review
2) Finish project budget for review
3) Review BA’s project prototype for critique
All three of these are the same as we continue to work towards finishing the project

Issues:
1) BAs have yet to begin their prototyping process and need to begin it immediately
2) Test this week makes it difficult to focus on anything else but that

Goals for November 4th, 2016
1) Finish project schedule for review
2) Finish project budget for review
3) Review BA’s project prototype for critique
All three of these are the same as we continue to work towards finishing the project

Issues:
1) BAs have yet to begin their prototyping process and need to begin it immediately
2) Test this week makes it difficult to focus on anything else but the test

My partner and I have started working on the scope, budget, project schedule, and risk registry report. We also met with Courtney and discussed our current worries and plans for our project. Our goal for next week is to compete the rough drafts of the previously mentioned documents we started work on.

Team Sara Tony and Phil.
Weekly Progress Report
Accomplishments this week:
We had our bi-weekly meeting with Courtney and received great feedback about our documents.
During Thursday night’s class we presented our quality management plan to the class.
Plans for this week:
Meet with PM’s on Monday to begin to revise our documents with the feedback we got from Courtney during the bi-weekly meeting and in-class review.
Weekly meeting on Wednesday with BA’s to see how their first BA only meeting, Justinmind tutoring, and meeting with professor Lavin went.
Issues:
Our BA’s motivational level and if they actually made progress independently of us last week since they cancelled our full team meeting.

From: Darpan Patel, Will Agentowicz
To: Mart Doyle, Tony Messina
Subject: Weekly Progress Report
Subject: Weekly Progress Report – October 28th, 2016
Period: 10/21/16 – 10/28/16
Hours: 20
Hours to Date: 20
Accomplishments:
1. Finished several deliverables including all Risk Assessment Plan.
2. Reached out to multiple charities in order to achieve results
3. Spoke with Project Sponsor to help her re-think development companies
Goals
1. Help project sponsor find proper development companies
2. Continue to contact charities for growing interest in app/website
3. Help project sponsor stay focused on ultimate goal
Issues
1. Engineering student has started to figure out her company, but there are still many obstacles in the way before she is able to dedicate herself to her own company

From: Adama Traore, Dario and Michael ( Group B)
To: Anthony Messina
Subject: Weekly Progress Report
Period: 10/21-10/28
Hours: 5
Hours to Date: 25
Accomplishments:
1) Created a risk registry and change management log
2) Finished the WBS
3) Had our Project Charter revised/looked at
4) Revised our communications plan and quality management plan
5) Met with Courtney to go over current progress and issue we are facing with the project
Goals:
1) Have our budget number correct on our WBS
2) Have a set weekly meeting with our BAs where people show up
Issues:
1) Being able to meet with our BAs on a weekly basis and not just talk through GroupMe/email

From: Team 6 (Dan, Wilbert, Tyler)
To: Anthony Messina
Subject: Weekly Progress Report – October 28, 2016
Period: 10/22/16-10/28/16
Hours: 20 Hours to Date: 85
Accomplishments for October 21, 2016
1) Meet with engineers to determine their remaining tasks to confirm that we are still
on schedule.
2) Went over documents including WBC, schedule, Project Scope, project charter,
and budget with team to find areas for improvement.
Goals for November 4, 2016
1) Continue to work on draft documents and have other sources, including Courtney
review them.
2) Continue to help improve upon project presentation, by trying to set up mock final
presentation with other teams in the class.
3) Assist in grip testing that is currently being conducted for the prosthetic hand.
Issues:
1) At least one project manager was not able to attend meeting with engineers and
their faculty advisor this week.
2) Was not able to meet as an entire group this week, only with project managers and
engineering team lead.

Accomplishments:
1. Met with all system leads and created finalized WBS hierarchy
2. Generated cross-system WBS and mapped out dependencies
3. Established process for tracking resources hours to create budget

Issues:
1. Behind on critical deliverables
2. We often need to redo deliverables that we have already created. They don’t properly serve the project as we increase our understanding. The scope has gone through 3 iterations before settling on a refined document. We have also gone through the WBS about 3 times as well, and we are expecting the same for the schedule. We attribute the issue to our inexperience and the scope of the project being so large.