Capstone Project Wiki

User Tools

Site Tools

Trace:
project-wiki:assignments:all_year:weekly_status_updates

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
project-wiki:assignments:all_year:weekly_status_updates [2023/07/26 12:13]
gibsonag 		project-wiki:assignments:all_year:weekly_status_updates [2023/07/26 12:19] (current)
gibsonag
Line 27: Line 27:
   * Report on the previous week's goals and the team’s progress toward meeting them.   * Report on the previous week's goals and the team’s progress toward meeting them.
   * Present the goals for the coming week (some of which may be carried forward from the previous week).   * Present the goals for the coming week (some of which may be carried forward from the previous week).
-  * Contain a list of action items the team is focusing on for the coming week+  * Contain a list of action items the team is focusing on for the coming week;
   * Include requests of things you need from you sponsor – answers to questions, requests for information, items to be reviewed or approved, etc.   * Include requests of things you need from you sponsor – answers to questions, requests for information, items to be reviewed or approved, etc.
  
Line 36: Line 36:
  
 9-10: Status update is clear and communicates how the team has met the previous week's goals and mentions roadblocks/failures and plans to overcome those, clearly states the project goals for the coming week, includes supporting documentation //in the format that makes sense for your project// (documents, video demos, github links, etc). A review of key takeaways and action items should be listed if the status update is a follow-up to a meeting with the sponsor.  9-10: Status update is clear and communicates how the team has met the previous week's goals and mentions roadblocks/failures and plans to overcome those, clearly states the project goals for the coming week, includes supporting documentation //in the format that makes sense for your project// (documents, video demos, github links, etc). A review of key takeaways and action items should be listed if the status update is a follow-up to a meeting with the sponsor. 
-7-8: Status update mentions some pertinent updates but leaves the sponsor with questions about what the team has actually been doing. 
-0-6: Status update focuses on meaningless Capstone deadlines and terminology and does not give the sponsor much indication of what has been done for the project (i.e. "Spent the week working on Concept Development") 
  
-Pro Tip: If your External Relations Manager can't tell which project you're working on from reading your status update (disregarding the team number you've been sure to include in the subject line), you probably haven't included the best information in your update. Think about what YOU would want to know if you were the sponsor. +7-8: Status update mentions some pertinent updates but leaves the sponsor with questions about what the team has actually been doing. Documentation of progress does not makes sense for what is reported. 
 + 
 +0-6: Status update focuses on meaningless Capstone deadlines and terminology and does not give the sponsor much indication of what has been done for the project (i.e. "Spent the week working on Concept Development"), does not include clear updates on project progress, seems hurried and an after-thought, or simply lacks useful information. Missing documentation that seems like it should have been included. 
 + 
 +Pro Tip: If your External Relations Manager can't tell which project you're working on from reading your status update (disregarding the team number you've been sure to include in the subject line), you probably haven't included the best information in your update. Think about what you would want to know **if you were the sponsor**. 
  
  
project-wiki/assignments/all_year/weekly_status_updates.1690395234.txt.gz · Last modified: 2023/07/26 12:13 by gibsonag

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: Copyright Brigham Young University, all rights reserved
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki