1 / 8

Project Status Reports Friday (UO) / Saturday (PKU)

Project Status Reports Friday (UO) / Saturday (PKU). How to prepare for . Agenda. Collaborative presentation 20 minutes per team, together You will need to divide the presentation Video feed between UO and PKU Evening U.S. time / Morning PKU time Project overview (very brief)

nerita
Download Presentation

Project Status Reports Friday (UO) / Saturday (PKU)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Status ReportsFriday (UO) / Saturday (PKU) How to prepare for

  2. Agenda Collaborative presentation 20 minutes per team, together You will need to divide the presentation Video feed between UO and PKU Evening U.S. time / Morning PKU time Project overview (very brief) Status (planned & actual) Demo Lessons learned

  3. Plan and Status What did you plan to have done by this point? What is actually done? Demo Avoid: “80% of the way to feature X” Instead: “We have tested X.a and X.b which will be part of feature X when we get X.c. We have reviewed the design of X.c and plan to finish it by Wednesday.”

  4. Architectural Design • What is the division of responsibilities? • Modular decomposition + allocation • What can be done in parallel? • What are the main dependences? • How do the dependences constrain the development schedule? Where does progress of one sub-team depend on the other? • What is the incremental build plan? • How does the plan reflect the dependences?

  5. Decompose and stage versions of a module to support parallel development decompose

  6. Show us your documents ... • (Excerpts of) project plan • (Excerpts of) architectural design • Not just a diagram. We’d like to review (parts of) the actual design document in Assembla. • Diagrams are useful to augment, not replace the architectural design document • (Excerpts of) other documents you have produced or are working on

  7. Lessons Learned (so far) How has your team coordinated? How did you make a plan? How did you divide the work? What lead to delays (if any)? Has the design allowed you to work independently (so far)? Have you encountered unanticipated dependencies? What will you do the same or different in the remainder of the term?

  8. All that in 20 minutes? Plan carefully. Be selective. Plan your materials to fit in less than 20 minutes, with both UO and PKU teams presenting.

More Related