The project undertaken by myself and my valued partner, teacher Michael LaBarre, for class TLT-467 is an interactive Scratch tutorial designed primarily for new users of all ages, titled "Using Scratch to Introduce Scratch: A Brief Overview of Block Coding" . Our priority for this project is to reduce confusion and help learners feel confident when they first start using Scratch, as the initial experience can be overwhelming for those who aren’t experienced with coding. The project aims to provide a basic foundation of understanding for users before they dive deeper into the platform. We intended it to be simple, direct, and effective, guiding users through each block category with interactive instruction. We want this instructional tool to support both students and educators in learning block coding.
I played a crucial role in the development of the interactive Scratch project. After reviewing LaBarre’s initial Scratch project following our brainstorm process under tight time duration, I provided feedback, noting that the robot sprite(deemed by LaBarre as Buzz) was appropriate but that the speed of playback needed to be solved, as it can distract learners from being too slow for their cognitive absorption. So we decided to make it interactive. My primary action was to remix LaBarre's Scratch project- a mechanical term coined from Scratch creators meaning to make a copy of a viewed project. Specifically, I proposed to split the "Nine Block” sprite into nine individual sprites to enable interactivity then to program the interaction to enable user clicks to interact with each block category. Following this was successful implementation that allowed the blocks to be interactive. Beyond direct coding work, I was also involved in the collaborative process by sharing ideas in a Google Doc, reviewing and adding comments to LaBarre's Google Slides presentation aforementioned, and initiating discussions about the project's publishing outside of class, such as the Summer Research Day Expo all while keeping devel opment notes on the process for creating interactive sprites.
Through this project, I have gained insight into various aspects of project-based learning and collaboration. Observing LaBarre's leadership qualities, specifically his ability to assess our strengths and skills in order to direct tasks which organically formed our roles, I recognized this as a valuable management skill essential for teachers to accommodate student learning. This experience highlighted the importance of such assessment in professional settings. My personal objective is to learn to collaborate with teachers in fashion of a competent(but new) instructional designer, aiming to absorb educators’ tendencies to work effectively on shared projects. Though unnatural at first to LaBarre, building a self-guided instructional tool is a project I have accomplished before, indicating an angle between our learning curves in instructional design approaches. I reflected my own experience with learning Scratch and the importance of documenting it for self-teaching purposes, even considering the use of an LLM as a "reporting agent" or "record keeper and journalist" for accelerated documentation suggesting my understanding of the value that reflection of practice and leverage of tools has for efficiency.
AI has unique qualities for this project’s development, particularly reflecting on its potential as a "reporting agent" or "record keeper and journalist" for documenting my experience with learning Scratch. While AI tools like ChatGPT generally helped us brainstorm ideas and improve the tone and pacing of the project's content, and Google's Gemini provided concise reports for what blocks to use for functions I inquired about, I specifically considered leveraging AI for streamlining my process into directives to train a Large Language Model (LLM). In fact, seeing that this writing is largely written with Google’s NotebookLM demonstrates my interest in using AI not just for content generation or feedback, but also for automating the documentation of his learning and development process. I also suggested to LaBarre that AI could handle the writing of reports while we would act as editors. Admittedly this could prove risky seeing that I have not attempted this scale of content generation before but I now can confirm that I am not wrong in my idea. This success lead me to be adamant about digitizing my work and notes in conversion to text objects to make them recognizable to AI tools. In parallel to the promotion of my perspective of artificial intelligence, I commented to LaBarre’s concern for Buzz’s appearance saying that a childlike robot for this project is an appropriate non-threatening symbol of technology, a thing to enable our future’s acceleration in education inspiring demand to be authentic and simple.
Unfortunately I did not have the opportunity for real world testing, however LaBarre considers our project highly practical for various educational settings.
Seeing that it is accessible by smartphones, tablets, and computers- mobile and stationary it is suitable for both virtual and physical classroom settings.
Scratch Foundation’s online network and software has insured our project can be shared, "remixed", and improved by others on Scratch’s Explore page, allowing us broader impact and collaborative enhancement beyond the initial creators.
Our learn-and-play style designed within the project teaches what is essentially HTML coding functions making it applicable to a variety of grade levels and settings, providing a foundational understanding of Scratch and coding.
We have addressed the initial overwhelming confusion new users are proven to face ensuring that users gain a basic understanding before attempting to create their own projects by design.
The development process was not without its difficulties:
- The initial draft gave students a "backseat" in the learning process prompting a review, play-test, and redesign which lead us to make it more interactive.
- The many options of blocks produces cognitive overload that we were challenged to overcome by balancing simplicity with effectiveness in the instructional content.
- Scratch does not allow real-time collaboration, necessitating manual "remixing" and sharing of files between team members which caused delay in collaboration.
- Direct local editing of the custom .sprite3 file format outside Scratch was not possible causing slow down in production from necessary extra learning of the Scratch platform.
- For the plot of the project’s content and story, play-testing with a new user (I acting as a novice learner) was crucial and demonstrated how critical user feedback is, although initial time constraints made it difficult to schedule a dedicated play-test session.
- LaBarre expressed caution regarding the sizing of the robot sprite, its overall suitability, the pacing of text boxes, and the appropriateness of the backdrops, indicating ongoing design considerations.
- LaBarre also noted that building a self-guided instructional tool felt unnatural at first while there was some initial misunderstanding between us regarding the assessment of our relative experience prior to the project.
Despite the challenges, the project achieved several successes:
- The team made the crucial decision to make the project more interactive, allowing users to click through each block category, addressing the "backseat" issue of the initial prototype.
- Google's Gemini provided me concise reports on coding blocks that graced my learning and development experience allowing me to complete tasks timely as professed.
- The chosen robot sprite was deemed appropriate and contributive to the project theme.
- We effectively used Google’s productivity suite alongside text messaging for task management and reporting surprises, particularly Google Docs for sharing ideas and feedback in detail on development updates.
- We have opportunity to share their work with a wider community at the Summer Research Day Expo alongside sharing our project via Scratch aligning with project guidelines to contribute outside the classroom.
- Successful developments, such as interactive elements and timely task coordination, demonstrated our effective problem-solving and technical application.
Please view Using Scratch to Introduce Scratch here