Historique de la page

...

• Originally, the scope of the project was to enhance the previous team's cart design and add two new renewable sources to increase the battery length of the cart. Since then we learned that only one power source can charge the battery at a time,. We also learned that the previous team's design was not adequate .Therefore, the scope of the project changed to designing a new renewable energy cart with an education forward focus and plug and play capabilities for power sources.
• Our schedule did not change drastically throughout MSD I.  We were able to accomplish everything that was originally put in, but sometimes needed to sacrifice the order in which it was completed.  We ran into the problem of not having enough time to do things, but there were no major schedule changes.  We knew from the start that we would be designing a new cart.
• We learned to be more fluid with our approach to the project. We learned to adept adapt to problems and to pivot past them efficiently.

...

MSD II: Project close-out

• Use this space to organize information for your review. Key elements are listed here

Expectations

...

Status Review

Current state of the project

• Summarize actual performance vs. requirements (include snapshot of current requirements document here, along with a link to the live document.).
  • Which requirements were unmet, and why?
  • How robust is your final design?
  • Did you meet your project budget?
  • What was your customer's assessment of the work you delivered to them? Were they satisfied?

• Compare your current project plan/schedule to your original plan/schedule.
  • Did the scope of your project change during MSD II?
  • How and why did your schedule change during MSD II?
  • What have you learned from these changes that you can apply to future projects?

• Review individual team member status.
  • Did you deliver on your personal responsibilities?
  • Did you use your MSD II plan effectively? Was it realistic? If not already addressed above, what did you learn from this and how can you apply it to future projects?

      Image Added

• Review your current risk assessment and problem solving status.
  • Have you closed out your most important risks?
    • Yes our most important risks have been mitigated and documented.  The risk mitigation was seamless to say the least.
  • Were there risks that you did not anticipate? If so, what do you think the reason is?
    Did any anticipated risks manifest themselves as problems?
    • The wobble turbine as a generation source did not go as planned, there generated power was much lower than expected.
    • Time management to compile a fully functional electrical education kit,  the end of MSD II had a lot of documentation materials to be submitted which took away from finalizing designs and builds. 
    • The PRP did not adequately asses the electrical task requirements needed to be done, this team could have benefited greatly from an additional EE to cover additional scope. 
    • The wobble of the scissor lift was reduced but a long term solution should be investigated.
    • How did you use your problem solving process during the semester?
      • We tested the cart in many different areas and identified problems.  We then brainstormed possible solutions and took action on them.  We were able to solve the majority of problems.

  
  

  Deliverables Checklist and Website Status

  • All documents must be uploaded to your website in advance of the Gate Review.
  • The team should not use gate review time to conduct a detailed examination of specific deliverables unless related to discussion items in the status review.
  • Is prototype hand-off complete, is the team's workspace cleaned up, and have all tools been returned?relevant documents will be shared with faculty customer on the G suite.  A finished prototype will be stored in final customers lab area on 5/6/21.  
  • All Confluence pages for MSD 1 and 2 will be finalized before 5/6/21.  
  • All tools used for the duration of MSD II have been returned to the office. 

  Lessons learned, etc.

  • Does the team have any other lessons learned that were not addressed above?
    • Always ask questions when you get confused. Some of the confusion is not your fault; it is just MSD.
  • What advice would you give to future teams?
    • Keep on top of your CAD work and try to be the first team in the machine shop. It helped our team get ahead and stay ahead. Contact Gary as soon as possible and check your spam folder. 
    • Plan a reasonable amount of work for yourself and make sure you have everything you need before you start working.