Our group meets regularly to discuss our direction, goal, steps, and progress. After the radical constructivism activity in class September 29th, we moved forward with a better plan for working our project plan into the course task assignments. Since the project idea originated for this group outside and before this course began, we are working to adapt my idea to the task assignments without losing fidelity of the idea. Throughout our discussions on September 26th, 29th, and October 3rd we were able to assign and create accountability for our learning goal for this course and the next objectives for Task 2, 3, and 4. The discussion with Dr. Warren and the time we had in class to deconstruct the task assignments allowed us to critically review how the tasks’s purposes could better align with our development and product which lead us to suggest merging 5&6 and 7&8. Additionally, the reflection throughout this process is invaluable however, the mental capital and energy could be used to further develop the theoretical approaches, architectural design, user guides, and even marketing to explain our product to the end users. The close and passionate nature of our group warrants close and critical review of each step in the plan as well as formative feedback of each written component. I feel we are behind in the written portion of our plan and need to move beyond the ideation and concept mapping and use our time wisely to communicate clearly how the theoretical concepts will be implemented with our technical specifications. After a thorough discussion, the following reorganization and division of duties were decided upon:
Proposed Learning Objectives
Danita | Amy | Bau | Janetta
Task 3 >> We will measure the potential learning outcomes of our proposed product. This will be where we set our requirements and architecture for the solution and begin testing it. Our testing methodology will invert the percentage of success and have higher rates at the bottom/easier levels, with lower rates for higher thinking up to the creation level.
Our learning objective for Task 3 is designing and prototyping a test environment, setting a minimum for each level in the digital hierarchy to cumulatively measure participant success. The prototype will be disseminated and participant success will be measured by gathering feedback along with the automated summative results. Our learning objective success will be measured by a brief synopsis of the results.
Task 4 >> We will create an infographic style user guide or job aid to provide participants handy information regarding the testing of our prototype.
Our learning objective for Task 4 is to create a user guide for the participant and analyze the product implementation planning components and requirements. Our learning objective success will be measured by developing and submitting a user guide.
Tasks 5/6 >> We would like to combine Tasks 5 and 6, because measuring success and subsequently value/effectiveness are inextricably related. We propose creating a visual depiction of the systematic interrelationships. We anticipate a visual will provide added value in the research study framework and look forward to accomplishing this. We formed a team because we want to see this concept through in real life. The framework is a good development tool and a real step in the research we want to do.
Our learning objective for Task 5-6 is to create a visual depiction of the systematic interrelationships. Our learning objective success will be measured by submitting the visual framework.
Tasks 7/8 >> We propose combining the creation of a full specifications document so we gain experience in communicating our ideas with reason, detail, and vision to systems engineers and developers for actual creation without the need for unnecessary iterations and sub-par solutions in the end product. Built into our definition of specifications to handoff will be our definition of measurable effectiveness of the engineered solution.
Our learning objective for Task 7-8 is to create a full specification document. Our learning objective success will be measured by writing and submitting a report detailing all specifications needed for creating our dream product with limited-iterations.
The four of us consistently discuss ways to improve our idea; we are passionate about it. In this light, we propose eliminating the upcoming formative reflections in order to focus on both a Mid-term reflection and a Final reflection.
We therefore have 5 proposed deliverables (in bold above, and listed below):
· Task 3 - Amy and Danita
· Task 4, 5/6 - Janetta and Bau
· Task 7/8 - entire team
· Mid-term reflection – each individual teammate
· Final reflection – each individual teammate
Comments