On the day

1. Start Day 1
2. Introduction, why we do this
3. Split team up into experienced & inexperienced tech / nontech
4. Techies go into VP82, nontech into design sprint if they don't want to code
5. buddy system to pair devs
6. three streams
   1. experienced technical (andrew?)
   2. tutorial sessions (ete?)
   3. design sprint (walt)
7. End day 1
8. Pub time!

1. Start Day 2
2. Standup / updates
3. Tutorials
4. Wrapup
5. End Day 2

Development Challenges

Here is the big list of all the items I've tagged with the label AKL092019 - You can pick anything from this list to work on - but we will group them into Tables at the weekend along the main themes below.

Opportunities

BIG Goal here is to complete the closure phase of an opportunity. This includes being able to review the list of invitees and tick off who actually attended, and send out thank you emails etc.

There's also a bunch of email stories - we want people to receive nice emails for all key event state changes in voluntarily.  Walter has done some new designs and the templates are in the code base - we just need to switch them on. 

Then we can also add some new emails that get send out at various stages - including the thank-yous.

People can opt out of receiving emails.

And we setup the pronouns so that email refer to people correctly.

VP-497 - Getting issue details... STATUS

Activities

VP-19 - Getting issue details... STATUS

VP-292 - Getting issue details... STATUS

We have the basic of Activity working. Activities are what are offered by content or activity providers - they are things you can do or ask for. They work like Templates in that a teacher can pick and activity and make it into a live opportunity.

Continue developing the Activity concept - filling out the forms and adding extra data. 

BIG GOAL - create a new opportunity from an activity.

Other goals

Activities can be created and published by members of an Activity Provider Org,

Activity provider orgs can list their portfolio of activities

Branding on the Activity

Badges

Badges is our last big new concept to get into the system we will be introducing the concept and getting an MVP badge system up and running.

VP-240 - Getting issue details... STATUS

Defining badges and awarding them for completed events. 

BIG GOAL - Award a Contributor badge for people completing VP-82. 

Other goals

Award a badge for someone completing an opportunity event.

QA & Performance

Then there is a whole lot of basic usability and bugs to find and fix.  There are a lot of new features that have not had much eyeball time.

Beginners

For new people we have also tagged some of the stories as 'easy' These are ones good as a first challenge if you are new to voluntarily or react coding.

• Page:
  Release Version and deploy to production
• Page:
  Configure a Fresh Dev environment
• Page:
  Setup the schools database
• Page:
  How to add Activity
• Page:
  Setup Enterprise Single Sign On