Revisions on Content Analysis: 10 hours
Instructional Strategy: 5 hours
Team Meeting: 2 hours
The focus of our discussion in our team meeting was the approach of the scenario. We were able to storyboard the branching in a manner satisfactory to all of us. In addition, we discussed the color schemes a bit and the content analysis
On the content analysis, I made reviews on the curriculum map and the task analysis based on the discussions and feedback from our client and sponsor. I refined the objectives to reflect the analysis skills and some attitude change in the store managers. Once again reworking the image of the curriculum map took the majority of the time in addition to selecting the action verbs for the objectives that are most appropriate. Accordingly, I made changes on the task analysis. After receiving feedback on it from my teammates, I made the adjustments needed. On the instructional strategy, I stalled. The reason for that is not having a clear instructional model to follow for the approach that we decided to take in the unit. I could not find research-based literature for the mini case-based scenarios that we are designing. Eventually, I decided to compare it to problem-based learning, since the learners are going through the same analytical process to find solutions, though in a more simplified way. Additionally, I referred to blog postings on building e-learning scenarios in order to describe a structure for our instructional approach. I found the perfect structure on the Tom Kulhmann’s blog on rapid e-learning.
Reflections
In order to refine the task analysis, I had to search through the plethora of lists of verbs on Bloom’s taxonomy. I noticed that some verbs are used for more than one level. Therefore, I had to ensure that the verbs chosen reflect the level intended very clearly.
As far as instructional strategy, I was glad to be given the green light to think outside the box. I like clarity but I like creativity as well. By trying to construct a “model” for our instructional approach, I was able to tie ends together. I saw myself trying to synthesize a model from different approaches in the literature.
Perceptions in people change and being assertive pays. These are the two things I learned from our team dynamics this week. Now that we are half-way through the course and the end-product is starting to see the light, I can look at the team experience, rocky as it is, as one facet of real life. I learned how to navigate through misunderstandings, letting go when necessary and holding on when necessary.
Thursday, March 25, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment