This is a time to develop a clear narrative to share about your team's work and enjoy sharing it with others in class.
Make your final adjustments to your dashboard and prepare how you will present your dashboard to the class and describe the key improvements made after the evaluations.
Finalize your process documentation (site or poster) and practice how you will present and discuss your team process to the class.
End your presentation with a couple questions for the class that may help you refine the delivery of your team's work. For example, you could ask, "Are there any gaps in our process explanation that we should provide more detail?" or "How could we improve the demonstration of our dashboard?"
Share links to your dashboard and process documentation.
Use the evaluation template as a starting point to customize your team's evaluation. Rephrase or add questions to the grid you will be asking. Discuss and outline with your team how you will conduct the evaluation with each participant--your evaluation script. For example,
Introduce yourself and the context of your dashboard project.
Explain that you are not testing them, but you want to improve your dashboard. Encourage them to think out loud and provide any constructive criticism as well.
Ask them to review your dashboard and give them an appropriate amount of time before you ask them any questions.
Use the evaluation grid to ask your primary questions and record feedback you get.
Thank them for participation.
After the session, review your notes, rate the primary questions, and add any findings that weren't added during the session.
Not only will this help you prepare for evaluation sessions with others, you can actually use this time to critically evaluate the dashboard yourself.
Conduct an evaluation with at least 6 other classmates and at least 6 people outside of class. Make sure to find key stakeholders for the topic your team is addressing with your dashboard. Determine how your team will cover the 12 evaluations.
Documents summarizing your evaluation findings.
Documenting your team process is important for two reasons. One, it is an opportunity for your team to reflect on the project process and what you have learned, and two, it provides a great aid for explaining your work to visitors at the final event. At the least, include the following.
Highlight at least six artifacts that demonstrate key work your team completed in the project process from beginning to end
Include a refined value statement that pulls it all together.
Outline the team member responsibilities.
Your teacher will instruct you on the form of the documentation. Carefully consider how you will present the information in a logical and easy-to-consume fashion that will help you present your team's work to the public, whether in person or online.
Your documentation in a poster or website format.
As a team, review the results of your evaluations and synthesize the main findings that you find most valuable in identify points of improvement.
Make a list of improvements and order them by priority. Priority can be determined by balancing the net effect it will have on the final dashboard and the effort needed to implement the improvement.
Be prepared to update your teacher and class on your development activities.
After confirmation of the solution’s quality, launch and promote the work. Monitor the use of your solution and gather direct feedback from key stakeholders for minor improvements or document recommendations for further development.
