Team Meeting (1hr in class, no other meeting was held this week)
Preparing for showcase (2 hours)
One-on-One Evaluation (1 hour)
In the team meeting, we went over technical issues about the unit. We also assigned our parts for the showcase presentation. We decided that it would be best for each of us to present the parts that we developed. My part was to present the content analysis, including the assessment, plus the instructional strategy. Over the weekend, I prepared my slides for the showcase, selecting key images that will support my talk. The one-on-one evaluation went very well, no major changes were suggested. As for the showcase, although the clients did not show up, it was a good experience to present in front of an audience. While practicing at home, I had to work on how best to articulate my ideas. There is a difference between knowing something and presenting it in a comprehensive manner, similar to designing instruction. Speaking in front of the audience was the only factor that might have caused me to stress. This did not happen because I was comfortable in how I wanted to approach my presentation and the audience ended up being all the friendly faces that I know.
Reflections: I felt that our showcase presentation was different in its approach than the rest of the presentations. It was more of how we worked behind the scene to get to the final product. However, I liked the different approaches taken in the presentations, representing the different styles of work. It is a good reminder of the diversity of styles, visions, and perceptions.
Next is finalizing the formative evaluation and making all the corrections on the unit.
Friday, April 23, 2010
Thursday, April 15, 2010
Bits and Pieces
Team meeting during class time (1hr, no other team meeting was held this week).
Linking Quizmaker and other files to the main Presenter file on Articulate (2hrs).
Reviewing materials and giving feedback to team members (1 hr).
Drafting the showcase overview (1hr).
My role this week was limited to drafting the showcase overview and linking the pretest and posttest to the main file in Articulate Presenter, in addition to adding an Engage slide. Also, I was waiting on the development of the modules and a draft of the evaluation plan from team members for review. As these were sent to me, I reviewed them and sent my feedback. My feedback on the modules was not taken into consideration. At this point, besides my previous concerns about missing several deadlines, which put our project behind schedule, I am concerned about the instructional quality of the modules. Modifications were done on the design and the agreed upon strategy without consultation with the team members. With no time to make changes and no acknowledgment of my feedback, once again I cede. I feel that I have no control or say in the project and I feel that it does not reflect the quality of performance that I would have hoped to have. The main problems I see so far are the lack of consistency in the modules and a busy design. I might be wrong but I am uneasy about it. I pray that when the time comes for the showcase, our presentation will show some coherence of the team work.
As for the feedback on the showcase overview, it was almost a rewrite. So, I accept as is and move on. With everybody on the edge as the final deadline approaches, (especially since we are still talking development at a stage when we should be closing) the communication among the team members has become fuzzy. Hopefully, things will be clarified in our class team meeting tonight.
Besides that, we have not been able to send a first draft for review to the SME. The unit is still being finalized. Moreover, when I try publishing the total of the 154 slides on Articulate, the process freezes on slide 134. I hope we can resolve the issue by chunking the big file into smaller files.
Reflections: On a scale of 1 to 5, my panic level is at 4.5, my confidence in our unit is at 3. Once again, I wonder if this is what team work is about. No one will be completely satisfied nor have a sense of control on the project.
Linking Quizmaker and other files to the main Presenter file on Articulate (2hrs).
Reviewing materials and giving feedback to team members (1 hr).
Drafting the showcase overview (1hr).
My role this week was limited to drafting the showcase overview and linking the pretest and posttest to the main file in Articulate Presenter, in addition to adding an Engage slide. Also, I was waiting on the development of the modules and a draft of the evaluation plan from team members for review. As these were sent to me, I reviewed them and sent my feedback. My feedback on the modules was not taken into consideration. At this point, besides my previous concerns about missing several deadlines, which put our project behind schedule, I am concerned about the instructional quality of the modules. Modifications were done on the design and the agreed upon strategy without consultation with the team members. With no time to make changes and no acknowledgment of my feedback, once again I cede. I feel that I have no control or say in the project and I feel that it does not reflect the quality of performance that I would have hoped to have. The main problems I see so far are the lack of consistency in the modules and a busy design. I might be wrong but I am uneasy about it. I pray that when the time comes for the showcase, our presentation will show some coherence of the team work.
As for the feedback on the showcase overview, it was almost a rewrite. So, I accept as is and move on. With everybody on the edge as the final deadline approaches, (especially since we are still talking development at a stage when we should be closing) the communication among the team members has become fuzzy. Hopefully, things will be clarified in our class team meeting tonight.
Besides that, we have not been able to send a first draft for review to the SME. The unit is still being finalized. Moreover, when I try publishing the total of the 154 slides on Articulate, the process freezes on slide 134. I hope we can resolve the issue by chunking the big file into smaller files.
Reflections: On a scale of 1 to 5, my panic level is at 4.5, my confidence in our unit is at 3. Once again, I wonder if this is what team work is about. No one will be completely satisfied nor have a sense of control on the project.
Thursday, April 8, 2010
Final Stages
Team Meeting: 2 hours.
Working on pretest/posttest in Quizmaker: 2 hours.
Reviewing scenario and design: 0.5 hour.
During the team meeting, the discussion revolved around the documentation that needed to be submitted as well as the prototype of the unit created. As far as documentation, work is still being done on editing and reviewing. As for the prototype, the team manager updated the team on her meeting with the client during which she presented to him the prototype. The client was pleased with the prototype and suggested minor additions. Both of my teammates are now working on finalizing the rest of the scenarios, designing, and developing the rest of the subunits. As we proceed through this stage, each subunit is being sent to the team members for feedback. The first subunit looks really good. However, I felt that the second subunit deviated from the objectives, scenario, and strategy that we have originally agreed upon and subsequently, the design of the second subunit changed as well. I expressed that in my feedback: we have to stay aligned with objectives and instructional strategy. My role in putting the pretest and posttest in Quizmaker was relatively simple. However, since my free trial has expired on my laptop, I had to download it again on my home computer and work from there. One feature I do not like about Quizmaker is that it shuffles the questions and the answers within each question by default. However, by trying to go around that, I learned more about Quizmaker and Articulate and this was a plus. Our pretest/posttest cannot be shuffled because we have tried to simulate a problem-solving approach by developing questions around one scenario that progress through the process of using the leadership values to solve problems.
Reflections: More lessons learned about group dynamics. Reflecting on the last team meeting, I felt that I have learned more about myself. I have to work very hard on taming my frustrations when my expectations of work ethics and quality of work are not met. I still get sensitive towards non-constructive criticism and I have to thicken my skin and not show emotions in the meeting because it does not lead anywhere. However, at this point, I am concerned about more disagreement that will jeopardize the timely submission of the required materials of the project. I hope my next blog post will announce the finalization of the development project and the formative evaluation plan.
Working on pretest/posttest in Quizmaker: 2 hours.
Reviewing scenario and design: 0.5 hour.
During the team meeting, the discussion revolved around the documentation that needed to be submitted as well as the prototype of the unit created. As far as documentation, work is still being done on editing and reviewing. As for the prototype, the team manager updated the team on her meeting with the client during which she presented to him the prototype. The client was pleased with the prototype and suggested minor additions. Both of my teammates are now working on finalizing the rest of the scenarios, designing, and developing the rest of the subunits. As we proceed through this stage, each subunit is being sent to the team members for feedback. The first subunit looks really good. However, I felt that the second subunit deviated from the objectives, scenario, and strategy that we have originally agreed upon and subsequently, the design of the second subunit changed as well. I expressed that in my feedback: we have to stay aligned with objectives and instructional strategy. My role in putting the pretest and posttest in Quizmaker was relatively simple. However, since my free trial has expired on my laptop, I had to download it again on my home computer and work from there. One feature I do not like about Quizmaker is that it shuffles the questions and the answers within each question by default. However, by trying to go around that, I learned more about Quizmaker and Articulate and this was a plus. Our pretest/posttest cannot be shuffled because we have tried to simulate a problem-solving approach by developing questions around one scenario that progress through the process of using the leadership values to solve problems.
Reflections: More lessons learned about group dynamics. Reflecting on the last team meeting, I felt that I have learned more about myself. I have to work very hard on taming my frustrations when my expectations of work ethics and quality of work are not met. I still get sensitive towards non-constructive criticism and I have to thicken my skin and not show emotions in the meeting because it does not lead anywhere. However, at this point, I am concerned about more disagreement that will jeopardize the timely submission of the required materials of the project. I hope my next blog post will announce the finalization of the development project and the formative evaluation plan.
Thursday, April 1, 2010
Development
Team Meeting: 2.5 hours
Reviewing Prototype: 0.5 hour.
My role in the project this week was minimal due to the way the tasks were divided among the team members. I was not assigned to develop nor prepare documentation for this week.
On Friday, we spent the whole team meeting making decisions about the interface. We started from few template slides and color schemes prepared by the other team members. At the end of the meeting, we were all in agreement on the colors, the scenario presentation, the navigation, and the succession of slides for each leadership value. I am very satisfied with the results we came up with.. Few days later, overcoming some problems with navigation in Articulate, the team manager provided a version of the sidles with the interface discussed in the meeting. I reviewed it and sent my comments on revisions I felt needed to be made.
Reflections; Not much to reflect on other than to say that during the team meeting, I learned some features of Articulate Presenter. Since I am not building any of the slides, my skills in Articulate will not be strengthened, unless I practice on something on my own. However, I will be using Quizmaker to enter pre and posttest. More lesson were learned on group dynamics. Having to write the team evaluation this week helps the reflection on the issue. Collaboration is a loose term that is more of a perception than a fact, unless learned through team-building exercises.
Reviewing Prototype: 0.5 hour.
My role in the project this week was minimal due to the way the tasks were divided among the team members. I was not assigned to develop nor prepare documentation for this week.
On Friday, we spent the whole team meeting making decisions about the interface. We started from few template slides and color schemes prepared by the other team members. At the end of the meeting, we were all in agreement on the colors, the scenario presentation, the navigation, and the succession of slides for each leadership value. I am very satisfied with the results we came up with.. Few days later, overcoming some problems with navigation in Articulate, the team manager provided a version of the sidles with the interface discussed in the meeting. I reviewed it and sent my comments on revisions I felt needed to be made.
Reflections; Not much to reflect on other than to say that during the team meeting, I learned some features of Articulate Presenter. Since I am not building any of the slides, my skills in Articulate will not be strengthened, unless I practice on something on my own. However, I will be using Quizmaker to enter pre and posttest. More lesson were learned on group dynamics. Having to write the team evaluation this week helps the reflection on the issue. Collaboration is a loose term that is more of a perception than a fact, unless learned through team-building exercises.
Subscribe to:
Posts (Atom)
Posts
