LEARN TO CODE
PROJECT PLANNER
“A GOAL WITHOUT A PLAN IS JUST A WISH”.
ANTOINE DE SAINT-EXUPERY
BY @KAURESSS HTTPS://KAURESS.ME
INSTRUCTIONS
0.START
1. Write your project name , deadline & <perceived>
difficulty level [page 1]
2. List all the features of your application [page 1]
3. List all the technologies to be used [page 1]
4. Make a frontend/backend diagram [page1]
5. Deconstruct each feature by : [page 2]
i. sub features
ii.technologies to be used
6. Start coding each feature
7. FINISH!
A TOOL TO BETTER #LEARNTOCODE
LEARN TO CODE PROJECT PLANNER
NAME PROJECT DEADLINE DIFFICULTY[ 0-10]
APP FEATURES TECHNOLOGIES
1. 6. 1.
2. 7. 2.
3. 8. 3.
4. 9. 4.
5. 10. 5.
DRAWING [FRONTEND OR BACK END]
“OUR GOALS CAN ONLY BE REACHED THROUGH A VEHICLE OF A PLAN,....”
PABLO PICASSO 1
DECONSTRUCT EACH FEATURE
1. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
2.FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
3. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
I'M NOT A GREAT PROGRAMMER; I'M JUST A GOOD PROGRAMMER WITH GREAT
HABITS. - KENT BECK
2
DECONSTRUCT EACH FEATURE
4. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
5. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
6. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
IF YOU DON’T KNOW WHERE YOU ARE GOING, YOU’LL END UP SOMEPLACE ELSE.”
- YOGI BERRA
3
DECONSTRUCT EACH FEATURE
7. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
8. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
9. FEATURE NAME SUB-FEATURES/ TECHNOLOGIES
USER FLOW
“PROGRAMS MUST BE WRITTEN FOR PEOPLE TO READ, AND ONLY INCIDENTALLY
FOR MACHINES TO EXECUTE.” ― HAROLD ABELSON
4
NOTES
“PLAN YOUR NEXT MOVE BECAUSE EVERY STEP CONTRIBUTES TOWARDS YOUR
GOAL.” ― SUKANT RATNAKAR
4