CS 5150: Software Engineering


Project report #3

As with report #2, the content of your intermediate reports will depend on your selected development methodology and on the milestones you laid out in your project plan (and any updates you have made to it). Remember that their purpose is to provide visibility to the client and demonstrate whether or not your project is on track. To that extent, these reports should always address the status of any milestones whose target dates have passed and include updates to the project plan (especially schedule and risk) if changes are required. They should also include or account for any deliverables ready by the report deadline (including summaries and takeaways from client demos). For heavyweight methodologies, these reports may be a natural place to request client approval of gating deliverables (be sure to request such approval explicitly in separate communication with your client).

Here are some additional recommended elements to include in your third report for methodologies commonly used by CS 5150 projects:

Modified waterfall
Products of design phase (e.g. UI mock-ups, class diagrams, etc.)
Iterative refinement
Refinements to requirements and design, demos of subsequent prototypes
Agile
Products of first sprint (production-ready code & documentation), evaluation of first sprint (slipped tasks, discovered work, velocity), second sprint plan

Unlike report #2, there are no additional required sections for this report (you gave your first formal presentation instead). However, now is a good time to be thinking about user testing, so you might consider including a user testing plan (this will put you on track for the next report, which will focus on testing).