Wednesday, September 19, 2007

Week 5

The team has been working on a number of documents this week, as outlined in our assignment list. Audra and Brent, two 6200 consultants, along with our SME Holly, have been helping Emily make the content more understandable and functional as lesson material.

Duren approved the Scope document and Needs Assessment this week with few changes. He is concerned about CAES-OIT's commitment to developing the system we mock up and has contacted the OIT director with a formal request for service.Our task analysis and performance objectives have been reviewed by Dr. Clinton. These should be ready to send to our client this weekend or early next week. Our plan is to share these with the SME first, as she is the expert on the subject.

Thursday, September 13, 2007

Week 5: Assignments

To do for next week:
By Thursday, September 20 (unless otherwise noted)

  • Edit content - ASAP (Emily)
    • Give to 6200 consultants for review with brief guidelines
    • 6200 consultants review by 9/18, 5pm (flexible?)
    • Send edited copy to team
  • Project timeline: update timeline and brief report (Emily)
    • Daisy send example to Emily
    • Ahram help review
  • Hardware/software specs: draft (HueiHsien)
  • User profile: draft (Kazu)
    • Emily send existing data to Kazu
  • Formative evaluation plan: draft (Remi)
    • Daisy to help
  • Screen specs/treatment: design ideas (Daisy)
    • Emily send web template screenshot
  • Review content, bring ideas to next team meeting (all)

Team meeting, September 20:

  • Clarify any unclear content areas
  • Discuss content in context of screen specs and treatment, activities, etc.
  • Start Screen Specs and Treatment Rationale docs as group in meeting
  • Jobs for 6200 students (specifics or timeline of needs)
  • Other items of interest...

Upcoming work: (to be reviewed and given to client)
See project management plan for suggested review process.

  • Hardware/software specs
  • Screen design specs
  • Treatment rationale and description
  • User profile
  • Formative evaluation plan
Ongoing work:

Monday, September 10, 2007

Week 4: Project Documentation

Team Meeting
The team discussion centered on documentation and on the content analysis from the client. The projects’ Instructional goals and objectives were narrowed down.
Team divided required deliverables.
HueiHsien made changes to the Scope document
Kazu made changes to the Needs Analysis document
Ahram Daisy and Remi continued development of the Objectives and Task analysis.
To do for next week: By Tuesday, September 18
Submission of earlier documents to Client for approval
User profile
Treatment Rationale and Description
Hardware/Software Specifications
Screen design Specifications
Formative Evaluation Plan

Tuesday, September 4, 2007

Week 3: Scope and Needs

The team has been collaborating on the scope document and needs assessment. We've determined a design for our documentation and divyyed up tasks among our group. Remi has taken the place of PM in Emily's absence. Duren has been contacted with a brief timeline of upcoming reports and notification of our current progress.

Our tasks for this week can be seen here:
Week 3: Assignments

(note - this entry is backdated to fit into our timeline.)

Thursday, August 30, 2007

Week 3: Assignments

To do for next week:
By Tuesday, September 4

  • Needs Assessment: Update Performance Eval and brief user info (Remi)
  • Scope document: Update Resources, Cost Analysis, Background (Emily)
  • Scope document: Communication plan (Kazu)
  • Scope document: Update Constraints (HueiHsien)
  • Documentation outline, formatting, and client sign-off (Emily)
  • Scope and Needs documents review w/ Greg
By next team meeting, Sept 6
  • Project management plan (Emily)
  • Client sign off on Scope and Needs documents
Upcoming work:
Lead indicated, although all team members may contribute.
  • Review content provided by SME (all)
  • Objectives list and task analysis - Sept 13 (Ahram)
  • Review content and brainstorm presentation ideas (Kazu)
  • Outline Learning System (Emily and HueiHsien)
Ongoing work:

Project Activity Log

Please download the project activity log here: http://www.4shared.com/file/23236388/c970a7f1/activityLog.html

Use this to record the following basic information for your time on this project:

  • Date
  • Time spent
  • Phase (PM + ADDIE)
  • Short description of activity
  • To do notes (if needed)

This will help us analyze our total time spent at the end of the project.

Tuesday, August 28, 2007

Week 2: Defining the Project

Thursday night our team met to discuss items developed last week and to start the activities for this week. We are still waiting on content from our SME. I met with Holly on Monday morning to flesh out what we need from her and give her a general direction for delivering content to us. Hopefully we'll be collecting that on Wednesday. Our client answered a number of our questions regarding the goals and needs of the project, as well as information to describe our learners. At the moment, our needs assessment and project scope are being developed and have been shared with the group for comment. I expect that we will have content tomorrow to review before our next team meeting.

We also presented our project to the 6200 class to recruit consultants. Six people have asked to work with us -- I think they will be great additions to our team. I hope that we can define their objectives in enough time to use their time well. Although we've been getting answers from our clients, it does feel like our project is languishing a little bit in this start-up stage.

To do for next week:

  • Outline consultant needs for job fair
  • Draft analysis document
  • Draft project management plan
  • Draft scope document
  • Start project activity logs
  • Send notes on system and scope to client for approval/negotiation
  • SME to provide content outline and rough material by Monday
  • Schedule meeting for Week 2 w/ SME Met Monday AM
  • Stakeholders to provide direction for agent perspective
  • Email roles and responsibilities to all (project and client team)
  • Review content with team
  • Define team tasks with content to support task analysis
  • Initiate task analysis (if content satisfactory)