The second term for your projects is going to be awesome. Now comes the fun part. You have working products, all the setup work is done — now you get to enjoy the fruits of your labors and add features, tweak and refine, make things look pretty, and ship the final product!

But now is also a good time to work out the project’s future direction. You have some feedback, and some bug reports, now what?

We’ll start out the term with some self-reflection about the project — to try to incorporate feedback from user testing and consider any pivots, etc. This should be an in-person conversation that you have with your whole team.

This is a markdown worksheet template that you should copy into a github issue and fill out. These are starting points for discussion with your team. Don’t skimp on this. We’ll discuss it in person during next class.

🚀 Start a new GitHub issue titled: T2 Project Reflection and Next Steps Worksheet (you can use hackmd and then copy/paste carefully (double check formatting!!)).

✅ Assign everyone on your team to the issue.

## T2 Project Reflection and Next Steps Worksheet

## Original idea
*Revisit your original goals (check out your project proposal).*

#### MVP Progress?
*What progress did you make towards your original MVP / on your stretch goals?*

#### How is it different?
*How is your project different from what you envisioned?*

#### Still happy with direction?
*Most importantly, are you still happy with the direction that your project is headed?*

#### What do you wish went differently?
*What do you wish had gone differently / are there features you wish you hadn't made or made differently?*

## Feedback
*What feedback from last term do you think is relevant and interesting to incorporate. List your feedback broadly and label them with how they stack up for your vision. These may already be in ZenHub but after this discussion they should be.*

* [critical 🔥]
* [stretch goal 🍦]
* [rejected ⛔]

#### Questions
*Think about where the project is headed. What are some questions that you/users/me have about direction/features/functionality that could use some validation?*

#### Answers
*Think of ways that you might validate these: discussion with your team, advice from me, polling the class, asking users, and/or collecting and analyzing usage data. Write down some ideas here. This isn't how to validate your project as a whole, but about specific feedback/features.*

## Vision
*Refine your vision.*

#### Feedback Analysis
*How does the current feedback/user testing/progress change how you think about the direction of the project?*

#### Pivot/Adjustment
*If you were to consider a pivot or adjustment in what the product is, what would it be?*

#### Ideal Goal
*In an ideal world if you could build out your project to be anything without any constraints of time or skill what would you want to do? Dream big — you can do more than you think. Try to push the limits. This does **not** commit you to anything, so don't worry about overpromising, this is to get you dream about where you **really** want your project to go without constraints. Please don't skimp on this part.*

#### Mission Statement
*Now write a mission statement for your project as you see it after all of this great brain activity. Just a few sentences suffices.*

## How to get there
*Now that you've thought about where your project is headed and where you want it to go write down how might approach getting there.*

#### What are your concrete next steps?

#### What are some blockers in your way? 

## TeamWork
*lastly, at the end of last term in the term summary you did a bit of work around teamwork. this is just a reminder for everyone to revisit that and if you have any new or further thoughts after the break feel free to record them here.*

To Turn In

• Your GitHub issue (name it with this assignment’s title) is your submission.
• Add the label documentation to the issue.
• When you’re done, move it to review for the graders.