Here is the continuation of Lex's work in part 1:
6. Know your limits
How long does it take to create something? Unfortunately that's a question that can only be answered with experience. However, once you can estimate the amount of time it would take to make something, scoping can get much easier
7. What are your priorities?
Is your goal to build functionality? To make something look pretty? To make a specific piece of information clear? To convey some message? Or to simply learn? This is a vital part of scoping. Complete the most important goal first. This also helps to decide on how much to push yourself.
8. Cut out pieces of the project
This ties into #7. But when things go really badly. You have to decide what to cut out. Having a few completed pieces will probably look better than 10 things that are not presentable at all. Learn what you wasted time on by accident and where you can improve on for the next time.
9. Ask for help when needed
You can always figure something out alone, spend all the time you need reading about a topic and learning it thoroughly. However, we do not always have time for that. Asking for help can let you complete a task much more quickly and sometimes learn much more quickly too.
10. Know how much time you have
At first this seems like the easiest part. However, there is a lot more to consider than you would expect. How often do you get distracted? (I do all the time) How many breaks to you need? What if you get stuck in the elevator?
What are the actual deliverables? (Maybe there's something outside of the main project you have to do by the deadline) Did you leave time for additional communication with the stakeholders and rescoping? How good at being on time are you? You have to consider all of this when counting how many hours you have for a project.