Project plan

Put your updated plan in plan.txt or plan.md, in a folder if you wish. This can be an edit of your plan1, or it can be a completely reimagined plan now that you've had more time to think.

The preparation of this document is intended to help you organize your thoughts and your work. Yes, I want to read it, but I mainly want you to go through the process of putting it together. Assembling this kind of planning document is a great way to discover gaps in your understanding, potential pitfalls in scheduling your work, etc.

What your document should include

• A short description of the project. I'm thinking 1-4 sentences, but whatever works for you.
• A short list of learning goals--what do you want to end up understanding that you don't understand yet?
• A description of your project's architecture. This could be just a diagram of your expected code organization, but it could also include things like the setup of a target server, the data you're going to need for testing, a build system (e.g., Makefile or something similar), etc.
• A list of feature goals.
• A testing and benchmarking plan.
• A more detailed schedule of development than you wrote last week. In addition to a list of development steps and proposed deadlines, you should feel free to annotate items that feel uncertain at this moment.
• A list of things one or more of you are worried about. This could be stuff you don't understand yet, things you think might take too long, etc.
• A brief explanation of how you're going to communicate and when you're going to meet to work together.
• A brief explanation of how you're going to ensure that all team members contribute substantially to the end product. (It is shockingly easy for one team member to ride the wave of the rest of the team's work, and end up with no contributions to show for themselves, and even less understanding of the project as a whole. Let's make sure this doesn't happen.)

Questions? Hit me.