CP Delivery 2: System Development Progress and Planning

Your cover sheet should list: (1) title of deliverable “[Client Name] Interim Status Report”, (2) team name, (3) names of team members, and (4) details on how access will be provided to professor for their review and evaluation of your software progress (both as a user and as a developer).

Include a Table of Contents as the 2nd page of the report that lists the sections/subsections of your report with page numbers

A concise 1-page letter to your client(s) that summarizes the status of your project (i.e., % planned vs % actual), plans for completion through the end of the project, risk update, explain report components, and likelihood of meeting all project objectives (cc your professor). NOTE: This is not persuasive. Be transparent about good and bad. Include this summary as the body of the email to your client and cc your Professor.

Include a screenshot of the original Feasibility Matrix from when Inception ended. During each retrospective, create a new Feasibility Matrix Mural to reflect completed work, and changes in value and or difficulty. For D2, include a screenshot of your current/updated Feasibility Matrix that captures any changes in the relative value of user stories as well as the relative feasibility of user stories.
Write a short paragraph to describe any changes to relative value and relative feasibility of user stories and why the changes occurred.

Include a screenshot of your original project timeline when Inception ended. During each retrospective, create a new Project Timeline Mural to reflect completed work, and changes to stories planned in current/future sprints based on updates to the Feasibility Matrix. For D2, include a screenshot of your current/updated project timeline to capture project progress. The current timeline should reflect your team’s current status of all sprints, including actual dates of sprint completion and updated planned start/end dates for current/future sprints.
Write a short paragraph to describe the updates that were made to the timeline and reasons for the changes (e.g. new user stories added, user stories cut from scope, updates to expected start and end dates of user stories, changes to order of user stories).
Include a bulleted list to capture the status of each user story (Not Started, In Progress, In Review, Completed). Please use abbreviated user story names (e.g. US1: Add Donor).
For stories marked “In progress” or “In review,” show percent complete.

Include a link to your User Stories Trello Board. Be sure that Trello is continuously updated to show progress, any potential scope updates, and current status

Write a summary of your approach to how your team tests the system internally. For completed sprints and the current sprint, include a summary of the components tested and those still to be tested. Include statistics and details on testing progress up to this point, such as percentages and specifics on issues found and resolutions. Write about % of testing complete and incomplete as well as bugs found. Facts and transparency!

Include a link to the Excel Test Tracker stored in UT Box as well as a link to the folder that includes the documentation regarding test execution.

Summarize your approach and progress for UAT. Summarize feedback received from your client after each sprint and changes your team made based on their feedback.
UAT will be on-going at this point. For your completed sprints, provide all details around UAT and the results. Include any instructions or sample data/materials provided to the users for testing of overall user stories and integrated functionality. Provide information around which user will perform the task, what they need to do (e.g. add a recurring donation), when they need to execute the test, and how they should provide feedback to your team.
Clearly indicate which user acceptance tests resulted in functionality accepted by your client and notes around areas that were not and how that was addressed.