Statistics and Probability · Probability
Design a fair spinner game and prove it
Invent a spinner or dice game, test whether it is fair and fix it if not.
- DifficultyBeginner
- Estimated time1 day
- BudgetUnder ₹250
- ClassClass 6–8
- TeamSolo or up to 2
- You needHousehold materials
Prerequisites: None beyond your class work
Original · by TechnifyedGameInvestigationBeginner friendlyLow costResearch oriented
Overview
Invent a spinner or dice game, test whether it is fair and fix it if not.
Skills you will use
Materials and tools
- Card, pencil and paper clip for a spinner
- Dice
- Tally sheet
Step-by-step roadmap
Start
You will finish with: a game, its theoretical and experimental probabilities and the fair version.
- 1
Prerequisites
Nothing special to know first. Then collect the 3 items in the materials list.
- 2
Learn
Read up on probability: expected value, fairness, games. Your textbook chapter and one short video are enough.
- 3
Plan
List the features for version one, sketch the screens or data flow and pick the tools. Keep the first version small.
- 4
Build
- Invent a two-player game with a spinner.
- Predict who should win more often.
- Play 100 rounds and tally.
- Calculate the theoretical probabilities.
- Change the rules to make it fair and test again.
- 5
Test
Try it with wrong, empty and unusual input, and ask someone else to use it without your help.
- 6
Document
Write a README: what it does, how to run it, screenshots and what you learned. Report structure
- 7
Present
Show a live demo of one complete task, then the design and the hardest problem you solved. Presentation structure
- 8
Publish
Put the code on GitHub with the README and, if you can, deploy a live demo.
Expected outcome
A game, its theoretical and experimental probabilities and the fair version.
Other versions of this project
Advanced version
Design a game that looks fair but is not, and explain the trick.
Ways to do this project
Text marked "You write this" is a prompt for your own work; everything else is specific to this project.
- Problem
- You write thisWrite your question as: How does [what you change] affect [what you measure]?
- Hypothesis
- You write thisWrite it as: If [I change this], then [this will happen], because [reason].
- Variables
- You write thisName the one thing you change (independent), the thing you measure (dependent) and what you keep the same (controlled).
Materials and procedure are in Materials and the Roadmap.
Observation table
You write thisDraw a table with one column for what you change, one for each repeat reading and one for the average.
- Graph
- You write thisPlot what you changed along the bottom and what you measured up the side; use a bar chart for categories and a line graph for numbers.
- Results
- You write thisState what the graph shows in one or two sentences, with numbers.
- Conclusion
- You write thisSay whether the result supports your hypothesis and why you think so.
Display board
- Title and your name
- Question
- Hypothesis
- Materials
- Procedure (with photos)
- Data table and graph
- Conclusion
- What you would do next
Questions judges ask
- What would you change if you did this again?
- What was your biggest source of error, and how did you reduce it?
- Where is this idea used in real life?
- Research question
- You write thisOne question you can answer with data, narrow enough to finish in the time you have.
- Hypothesis
- You write thisWhat you expect to find, and why.
- Variables
- You write thisWhat you change or compare, what you measure, and what you hold constant.
- Methodology
- You write thisDescribe the method in enough detail that someone else could repeat it: sample, tools, procedure.
- Data collection
- You write thisSay what you will record, how many times, and how you will keep the records safe.
- Analysis
- You write thisChoose the table, chart or test that answers the question; report averages with their spread.
- Limitations
- You write thisList what could have affected the result: small sample, instrument limits, things you could not control.
Literature review
Find five to eight sources (your textbook, review articles, reports) and note what each says about your question. Group them by idea, not one after another, and end with what is still not known.
References
List every source you used in one style throughout (author, year, title, where it was published, link and the date you opened it).
Use this as the outline of your README or case study.
- Problem
- You write thisThe problem in one or two sentences.
- Why it matters
- You write thisWho has this problem and what it costs them.
- What was built
- A game, its theoretical and experimental probabilities and the fair version.
- Technology
- You write thisThe languages, libraries and tools you used, and why you picked them.
- Architecture
- You write thisOne diagram: the parts and how data moves between them.
- Implementation
- You write thisThe 5 build steps in your own words, with one code or design decision you are proud of.
- Challenges
- You write thisThe hardest bug or decision, and how you got past it.
- Results
- You write thisNumbers: accuracy, speed, users, survey answers.
- Demo and code
- You write thisA link to a live demo or a short video, and to the GitHub repository.
- Lessons learned
- You write thisWhat you would do differently next time.
- Future improvements
- Design a game that looks fair but is not, and explain the trick.
- Problem
- Invent a spinner or dice game, test whether it is fair and fix it if not.
- Target user
- You write thisOne specific person: who they are and when they would use this.
- Solution
- Invent a spinner or dice game, test whether it is fair and fix it if not.
- First version (MVP)
- You write thisThe smallest version that shows the idea working once, end to end.
- Tech stack
- You write thisPick tools your team already knows.
- Architecture
- You write thisA quick sketch of the parts and how they connect.
- Demo
- You write thisThe one scenario you will show live, start to finish, in under two minutes.
- Stretch goals
- Design a game that looks fair but is not, and explain the trick.
Team roles
Plan by length
24-hour
- Hours 0–2: agree the problem, the user and the one thing the demo must show
- Hours 2–16: build only the first version
- Hours 16–20: test the demo path end to end and fix what breaks
- Hours 20–24: slides, a 2-minute demo script and a backup recording
48-hour
- Evening 1: problem, user, sketch and task split
- Day 1: first version working end to end
- Day 2 morning: one stretch goal and testing
- Day 2 afternoon: polish, slides and demo practice
1-week
- Day 1: research the problem and talk to two possible users
- Days 2–4: first version
- Day 5: stretch goals
- Day 6: testing and write-up
- Day 7: demo video and presentation
Working as a team
Solo or up to 2. Suggested roles:
Report and presentation
Report structure
- Title and summary
- Problem and target user
- Features
- Tools and technology
- Design: architecture, data model or screens
- Implementation
- Testing
- Results and screenshots
- Challenges
- Future improvements
- References
Presentation structure
- The problem
- Who it is for
- Live demo
- How it is built (one diagram)
- The hardest part
- Testing and results
- What you learned
- What comes next
Viva questions
Prepare your own answers to these before you present.
- What is the aim of your project, in one sentence?
- What is the principle behind it?
- Why did you choose these materials or tools?
- What result did you get, and was it what you expected?
- What went wrong and how did you fix it?
- How could this be improved or used in real life?
Resources
Source and attribution
Original
Written by Technifyed. Free to use for your own school or college project; write the report in your own words. Added 1 Oct 2026.
Similar projects
More Statistics and Probability projects
Statistics and Probability · Probability
Test the birthday paradox
Calculate and test the chance that two people in a group share a birthday.
Statistics and Probability · Probability
Estimate pi by dropping needles
Drop sticks on ruled paper, count how many cross a line and get an estimate of pi.
Statistics and Probability · Probability
Investigate the Monty Hall problem
Play the three-door game 100 times each way and show why switching wins two-thirds of the time.
Statistics and Probability + Biology
Estimate the size of a crowd or a population by sampling
Use capture-recapture with beans to estimate a hidden total, then judge how accurate the method is.
Two-subject alternatives
Public Health and Epidemiology + Statistics and Probability
Model a disease outbreak with dice
Play an infection game with dice in class and plot the epidemic curve.
Data + Statistics and Probability
Test whether a coin or die is fair with statistics
Roll a die 300 times and test whether the results fit a fair die.
Finance and Banking + Statistics and Probability
Explain how insurance works with simple numbers
Use a classroom simulation to show how pooling risk makes insurance possible.
Artificial Intelligence + Statistics and Probability
Predict house prices with linear regression
Use a public housing dataset to predict price from size, rooms and location.
Same difficulty and budget
Pure Mathematics + Fine Arts
Explore tessellations and design your own
Find which regular polygons tile the plane and create an Escher-style tile.
Pure Mathematics + Biology
Explore the Fibonacci sequence in nature
Count spirals on pine cones, sunflowers and pineapples and test whether they are Fibonacci numbers.
Pure Mathematics · Algebra
Make and analyse a magic square
Build 3×3 and 4×4 magic squares and prove why the centre of a 3×3 must be 5.