• Written Report Due: 10/19, 11/11
  • Presentations: 10/19, 11/09 and 11/11

While we will frequently exchange information through weekly meetings over the course of the semester, two formal progress reports and presentations are required. Each report should include the following information (it does not need to be in this order):

  • Overview
    • A brief overview of your project and client. This may be very similar (or even identical) to material included in your system design document.
    • An overview of your processes. What are the roles of the members of your group (we discussed these in your team meetings)? What are the mechanisms you are using to keep up with agile/scrum methodologies?
  • Current status of the project:
    • What is the status of communication with your client?:
      • If any requirements from your client have changed, discuss them.
    • What has been completed so far? Make your work more concrete through images.
      • Identify what has changed since your System Design
    • To contextualize your progress and remaining work, include your burn down chart (or a chart that similarly shows progress and trajectory that is directly derived from your ). This should also give a visual approximation of the work that you have left to complete.
  • Reflection on challenges:
    • This may include technical challenges related to the construction of your application, communication challenges that are related to your client, or team challenges that are related to your team-based processes (for example, keeping up with agile/scrum).
    • How are you planning on meeting those challenges? Make this as concrete as possible. For example ‘work harder’ isn’t a concrete solution. Instead, tell me how you will enforce team accountability and transparency that directly results in productivity.
  • Plan for the rest of the semester
    • What are you focusing on now?
    • What are the critical points of potential failure? (What are you worried about?)
    • Given your current trajectory, when do you expect to complete an alpha version of your product?

Deliverables

  • Written Report: The written report is expected 3-5 pages, single-spaced. Refer to our writing rubric. The deliverables will mirror your System Design doc:
    • The link to your repository that contains your rendered markdown.
    • A pdf of your rendered markdown to submit on Google Classroom
    • Your presentation slides submitted via Google Classroom
  • Presentation: Your two progress reports will be accompanied by two presentations.
    1. In your first presentation, focus on your product and client communication. Do not spend time on your team processes for this presentation.
      • (Briefly) What is your project and who is your client?
      • What is the current status of the project - have any of the goals changed? What feedback have you received back from your client? You should show visuals or demos of your product
      • What are the technical or design challenges that threaten your progress (what are the critical points of failure)?
      • When do you expect to complete an alpha version of your product (show a burndown chart)?
    2. Your second presentation will take place on 11/09 and 11/11. While this will include the questions above, it should also involve reflection about your team processes.

    Refer to our presentation rubric