In the last post, I spoke about pacing myself and I think that I put my foot in my mouth. Anna Smith in her blog hop post made this comment.
It seems that after I stopped, I found that I lost my flow. Perhaps I just need to embrace the binge doing of a mini-project. I struggled. I reread the assignment about 8 times. I read through the other posts in the community and what others were doing. (I read to collect ideas without reference, so I apologize for not giving those credit as I share my thoughts and process.) I walked away and gave it time.
Here is some of my flow on the topic: How do I go beyond doing puzzles separately? Should we and how would we make rules together? Should there be competition, which is antithetical to my values in education? I love collaborative project building. How can I introduce this project so that it is recommended and not required. I am partial to self-directed learning.
Today, to get jump started I read through some more posts and meditated for a little while. I started to remix the idea of creating the game from the end state. In Kenken, that means finishing with a completed puzzle. I opened up Google Sheets and started to make a simple 3×3 Kenken puzzle to get a feel for the flow and issues. It’s not enough to just center digits in the middle for the solutions. I have to combine cells to put in the operations.
Are we making completed puzzles that have a solution and reasoning for the solutions? If so, how do new Kenken players get to that point? Can we learn Kenken as a team? Perhaps we start small ones in studio together and alone. I think that doing small ones early will get boring quickly for a collaborative group. I could just accelerate the flow from 3×3 to 4×4 to 5×5 pretty quickly. The key thing is to build the apparatus to collect the rule making in a new, growing repository that is reusable.
Good. Now this is starting to sound like a programming project that can generate specifications and steps.
- Share the big picture first — important for gifted learners.
- Create a desired state vision with the team and talk through the process
- Share the plan and get input
- Share my goals:
- Learn the basics of the game
- Introduce rule development
- Store rules to use later
- If we do this for a while and like it, what other things will we be able to make out of it
- Work through problems like a team, introducing hard problems at the pace of the team.
- Record rules
- Give kudos for finding and using rules
- Play, play, play.
- Introduce Kenken game making
- Provide choice for doing this process with a different game – discuss.
I am going to let this rest in my head for a while. My initial concern is that I have written a lesson plan over remaking a game.