This week...
I collected information and wrote parts of the analysis report for the Online Course Development Training for Faculty project. Specifically, I wrote the performance analysis and learner context portions of the report. The performance analysis is a review of the desired performance as compared with actual performance and identification of possible causes for gap in performance. The learner context analysis reviews the setting, equipment, support etc. that will be available to the learner while they participate in the instruction.
On Sunday, our team combined all parts of the analysis report and peer reviewed each other’s work. We made edits and suggestions. Later in the week, I reviewed the document, made additional edits and published online prior to the due date. This part of the assignment required our team to think through the client need, stakeholders, and conditions surrounding our project development. The analysis report enabled us to identify critical factors to the success of the project and therefore begin to think through potential risks.
Like my teammates, I have done this type of report twice before. The difference was that this time the work was divided between three of us! Although it is tempting to skip this part of the design process, I realize each time how important analysis is for identifying critical aspects of the project. Understanding earner needs and motivation, learning conditions, support personnel and so on, are all important to the success of an instructional project. I am pleased that this phase of the design process has continued to be reinforced throughout my program. Repetition in a variety of projects has caused me to realize a few things: 1) not all learners are the same, 2) not all problems require instructional solutions, 3) the learning context can be instrumental to the success or failure of the project and 4) documentation is important to the current project as well as future projects.
Before beginning the analysis report, I reviewed similar past reports (my own as well as those of the prior teams). Having examples of prior documentation helped me to focus on the critical parts analysis and move the work forward without wasting a lot of time. I was able to identify missing information quickly, ask for data and write the report efficiently... kind of like a professional J
Overall, the analysis is thorough and contains the necessary information to move forward with the project. I think it could be a little more concise and some of the parts could be rewritten to flow in a more cohesive manner. Combining three writing styles is not always an easy task but overall the report is well done.
This week our team has narrowed down our specific roles for the project and we are beginning the serious work of planning the project. I will write up the scope, deliverables, and risk management portions of the project plan. I am pleased to have these parts because I like to understand the big picture before I begin to iron out the details. Afterward, I need to begin thinking through the content and writing drafts of the objectives and sub-objectives. Concurrently, I need to begin thinking about the overall appearance and aesthetic of the final project (colors, layout, etc.). There are so many parts to this project that must be juggled at once... we are definitely coming into the long stretch of hard work and perseverance. Hopefully our training and will to succeed will see us through!
I collected information and wrote parts of the analysis report for the Online Course Development Training for Faculty project. Specifically, I wrote the performance analysis and learner context portions of the report. The performance analysis is a review of the desired performance as compared with actual performance and identification of possible causes for gap in performance. The learner context analysis reviews the setting, equipment, support etc. that will be available to the learner while they participate in the instruction.
On Sunday, our team combined all parts of the analysis report and peer reviewed each other’s work. We made edits and suggestions. Later in the week, I reviewed the document, made additional edits and published online prior to the due date. This part of the assignment required our team to think through the client need, stakeholders, and conditions surrounding our project development. The analysis report enabled us to identify critical factors to the success of the project and therefore begin to think through potential risks.
Like my teammates, I have done this type of report twice before. The difference was that this time the work was divided between three of us! Although it is tempting to skip this part of the design process, I realize each time how important analysis is for identifying critical aspects of the project. Understanding earner needs and motivation, learning conditions, support personnel and so on, are all important to the success of an instructional project. I am pleased that this phase of the design process has continued to be reinforced throughout my program. Repetition in a variety of projects has caused me to realize a few things: 1) not all learners are the same, 2) not all problems require instructional solutions, 3) the learning context can be instrumental to the success or failure of the project and 4) documentation is important to the current project as well as future projects.
Before beginning the analysis report, I reviewed similar past reports (my own as well as those of the prior teams). Having examples of prior documentation helped me to focus on the critical parts analysis and move the work forward without wasting a lot of time. I was able to identify missing information quickly, ask for data and write the report efficiently... kind of like a professional J
Overall, the analysis is thorough and contains the necessary information to move forward with the project. I think it could be a little more concise and some of the parts could be rewritten to flow in a more cohesive manner. Combining three writing styles is not always an easy task but overall the report is well done.
This week our team has narrowed down our specific roles for the project and we are beginning the serious work of planning the project. I will write up the scope, deliverables, and risk management portions of the project plan. I am pleased to have these parts because I like to understand the big picture before I begin to iron out the details. Afterward, I need to begin thinking through the content and writing drafts of the objectives and sub-objectives. Concurrently, I need to begin thinking about the overall appearance and aesthetic of the final project (colors, layout, etc.). There are so many parts to this project that must be juggled at once... we are definitely coming into the long stretch of hard work and perseverance. Hopefully our training and will to succeed will see us through!
This is your new blog post. Click here and start typing, or drag in elements from the top bar.
RSS Feed
