Difference between revisions of "INLS 740: Status Reports"

From Pomerantz
Jump to: navigation, search
 
Line 5: Line 5:
 
Each working group will post brief biweekly status reports, throughout most of the duration of the semester.
 
Each working group will post brief biweekly status reports, throughout most of the duration of the semester.
  
Status reports should describe your working group's work and planning to date. The first report should include your agenda and action plan. Subsequent reports should include a summary of work accomplished (in total and since the last report), and a plan for future work. Posts may also include such items as: sketches, concept maps, wireframes, To Do lists, etc. Please tag your posts with the tag ''Status report''.
+
Status reports should describe your working group's work and planning to date. The first report should include your agenda and action plan. Subsequent reports should include a summary of work accomplished (in total and since the last report), and a plan for future work. Posts may also include such items as: sketches, concept maps, wireframes, To Do lists, etc. Give your post the category ''Status Report''.
  
 
We will discuss status reports in class. In thinking about the status reports from other working groups, consider the following: Have you come across information, in the course of working on your project or in your environmental scanning, that might be useful to another working group? Do you have experience with a piece of technology / set of standards / process / etc. that another working group is working with? Might your working group be able to collaborate with another working group on some aspect of the DL?
 
We will discuss status reports in class. In thinking about the status reports from other working groups, consider the following: Have you come across information, in the course of working on your project or in your environmental scanning, that might be useful to another working group? Do you have experience with a piece of technology / set of standards / process / etc. that another working group is working with? Might your working group be able to collaborate with another working group on some aspect of the DL?

Latest revision as of 13:28, 3 January 2013

The function of this assignment is twofold:

  1. To facilitate project management and communication between working groups, and
  2. To provide you with constructive and actionable feedback on your work and planning to date, so that you may make modifications if appropriate.

Each working group will post brief biweekly status reports, throughout most of the duration of the semester.

Status reports should describe your working group's work and planning to date. The first report should include your agenda and action plan. Subsequent reports should include a summary of work accomplished (in total and since the last report), and a plan for future work. Posts may also include such items as: sketches, concept maps, wireframes, To Do lists, etc. Give your post the category Status Report.

We will discuss status reports in class. In thinking about the status reports from other working groups, consider the following: Have you come across information, in the course of working on your project or in your environmental scanning, that might be useful to another working group? Do you have experience with a piece of technology / set of standards / process / etc. that another working group is working with? Might your working group be able to collaborate with another working group on some aspect of the DL?

Note: The commentary that your working group receives -- from me and from other working groups -- will be from a range of perspectives. You will agree with some comments and you will disagree with some. Discuss the feedback that you get among the members of your working group, and with the other relevant working group(s). You do not need to implement all suggestions that you receive. Implement only those suggestions that your group deems appropriate: those that are consistent with the goals of your DL, those that may be useful, those that are technically feasible, etc.


« Back to course main page »