Week 8: Report

Our team meeting tonight was lively, as usual. We went through the project timeline I provided and discussed various deliverables and actions listed. We reviewed Daisy's most recent screen designs and discussed elements to add to it. Ideas of interest from that discussion:

• Captivate suggested as a tool to teach the learner about our module (how to navigate, what to expect, etc.)
• Add navigation to module (help, back/foward buttons, icons for diff activities)
• Use different objects in interface for exercises in particular units.
  • Unit 1: identification, imagery, and case studies (folder with tests, documents)
  • Unit 2: client interactions (phone call)
• Adapt the notebook object to record a synopsis of the lesson, perhaps as closing summary.

The evaluation section of the project timeline was reviewed. Remi, suggest edits as needed. For our beta evaluation, Remi has suggested having 2 tests - one for each unit of our module. I will talk to Duren about who we can ask to do this, as well as timing. The beta eval will probably be near Thanksgiving, which could be difficult if we don't plan ahead.

We've decided to keep up with our time on our blogs, not in a separate spreadsheet. Be sure that you do this!

I suspect our 6200 consultants may be getting antsy from not having had much assigned yet. We are entering our development phase, so we should start distributing tasks very soon.

• Week 8 Assignments

Week 8: Assignments

To do for next week:

• Post recent documents (Emily)
• Determine interactivity for content (Kazu, HueiHsien, Emily)
  • document ideas as needed (sketch, storyboard, description, etc.)
• Screen and graphic design: look-and-feel, navigation, etc. (Daisy, Ahram)
• Flowchart and screen specs of online system (Emily, HueiHsien)
• Review project calendar docs (All)
• Send to Holly, Duren (Emily)
  • Formative Evaluation Plan
  • Hardware/software specs

Team meeting, October 11:
To be outlined later....

• Present/discuss ideas for interactivity
• Distribute interactive work as possible
• Present/discuss updates to screen design
• other items of interest....

Upcoming work:

• Flowchart, storyboards (Nov 1)

Week 7: Report

This week Remi, Ahram, HueiHsien, and Kazu worked on flowcharts for each of our 3 goals. There is some concern about the size of our content, which we will need to discuss as a group. We've decided on a direction for our treatment and Daisy has been developing those screens. Emily has been working on the flowchart of the online learning system and will be putting together our presentation for the studio briefing tomorrow night.
Our weekly assignments are posted here:

• Week 7: Assignments

Most of our documents and content have been uploaded to the documentation section of our blog:

• Documentation

Hopefully we will begin major development work on our module this next week. We are all beginning to feel the crunch at this point in our project and are anxious to see development underway.

Content

• Plant Pathology Module Outline
• Unit 1 - Basic Plant Pathology
• Unit 2 - Plant Science Investigation
• IPM Plant Disease Clinic Form
• Plant Pathology Images (refered to in unit material)

Week 7: Assignments

To do for next week:

• Flowchart of content and activities
  • Goals 1 & 3 (Ahram, Remi)
  • Goal 2 (HueiHsien, Kazu)
• Hardware/software specs edits (HueiHsien)
• Formative eval plan edits (Remi)
• Screen design (Daisy, Emily)
• Flowchart of online system (Emily)
• Group presentation PPT (Emily)
• Send to Holly, Duren (Emily)
  • Task analysis
  • Objectives
  • User profile

Team meeting, October 4:

• Review flowcharts for goals, system
• Review screen design
• Plan for
  • future screen development
  • distribution of graphic work
  • storyboarding
• other items of interest....

Upcoming work:

• Flowchart, storyboards (Nov 1)

Week 6

The ICC team has spent more time with the task analysis, performance objectives, and test items this week. After reviewing the ordered and somewhat revised content, a number of changes were needed to bring our tasks in line to the plant pathology content. The team has split into sub-groups to develop parts of this tasks and objectives. We will still request a review of this documentation before sending it to our client for sign-off.

Drafts of our formative evaluation plan, hardware/software specs, and user profile have been reviewed by our group, designated 6200 volunteer, and have been sent to Dr. Clinton for review.

An assignment list was not posted this week, although the following items were assigned:

• Ahram, Remi, Daisy review and develop tasks and objectives for:
  • 1a. plant disease
  • 1b. plant disease triangle
  • 1c. pathogen groups
  • 2a. communicating with clients
  • 2c. sample collection
• Emily, HueiHsien, Kazu - review and develop tasks and objectives for:
  • 1d. integrated pest management
  • 2d. sample submission
  • 2e. interpreting sample diagnoses and recommendations
• Myra review the following docs:
  • Formative evaluation draft (Remi)
  • User profile (Kazu)
• Notify 6200 consultants of duties, timelines
• Daisy develop screen design based on group direction in meeting
• Emily ask Duren about access to agents for evaluation
• Emily ask Holly about items for pre- and post-testing

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.

• Week 5 Assignments

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.

• Project Scope - 9/16/07
• Needs Assessment- 9/17/07

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.