In the world of software development, there is a movement towards using a "Sprint" as a way to improve productivity. The basic idea is that a development team meets and agrees on a work outcome. They are given a short period of time to build their product. They then meet to show the group their outcome. They get feedback and set up another sprint to adapt their work based on the feedback. I have been chatting with groups of teachers about the power of sprints in the classroom. Here is an example of what we have discussed: Instead of giving students a long period of time to work on a project, try giving them a very short period of time (5-10 minutes) to sketch out their product. Then share it with a partner and get feedback. Now give them time to reflect on the feedback and adapt their sketch to the feedback. Continue this cycle of work/feedback/reflect multiple times. Here are a few reasons why this process works better than just giving them the longer period of wo...
Education Through the Lens of Future Readiness