Quick Links

• Jump To Final Project Schedule Index
• Jump To In-Class Workshops Index

Congratulations, you've survived over 10 weeks of learning and practicing lots of new coding content related to full stack software development! Now its time to show off all you've learned with a 3 week long final team project. You and your team will present your final project application to employers on January 13, 14, or 15 (TBD).

Guidelines

• Teams have been strategically formed by instructors and career services
• Every individual must pitch an idea
• Be original! Projects should address a need or a problem that is not currently being addressed
• Do some research. If the idea already exists, be prepared to explain why yours is different or better
• No social media sites
• Nothing illegal

• No projects previously done by WCCI students (..this is not a complete list)

  • Previous project recordings on WCCI YouTube channel
  • Spring and Summer 2020 Demo Day project recordings under the Projects and Grads tab
• Simple enough to hit MVP in a few weeks (...use the scope of Modules 3 and 5 as a guideline)
• Complex enough to keep the team busy for a few weeks
• Expandable beyond the 3 week project
• Something that will demo well and you'll be proud to show employers (a couple dozen of them, I bet)

• Showcase as many full stack software development skills as possible:

  • Front end: HTML, CSS, JavaScript, responsiveness
  • Back end: SQL Database
  • Other: TDD, .Net Core Web Application, MVC Pattern, Repository Pattern, Code First EF, JSON, RESTful APIs
  • DO NOT USE without permission from instructors: React

How to Pitch

• Pitch practice and pitches on the afternoon of Thursday, November 19
• 3 minute time limit per pitch, followed by questions
• The pitch ideas should appeal to your entire team

• Pitches must include:

  • A project name
  • A description of the user of the application
  • What problem your application solves
  • The features of the Minimum Viable Product
  • Explain how you project could be expanded in the future
• Show excitement for your idea! We want to know why its worth doing.
• Give your idea some thought and include details! We want to know exactly what your application will do, not what it might or could or should do.

Teams

Team A Members:

• James Barney
• Sam Blaha
• Joe Brooks
• Jihad Dupuy
• Brian Yuhas

Team B Members:

• Ed Carroll
• Maureen Joyce
• Hugh McGee
• Trevor Trammell

Tentative Schedule

Resources

Workshop and Exercises Index

All Workshop Videos on Google Drive

Personal Expectations

Good attendance - Take breaks - Help each other - Timeblock work - Ask questions if confused - Make mistakes and ask questions - Learn from mistakes - Self drive - Friendly - Don't sit in blockers too long - Hard work - Stick with figuring out a bug or error before giving up and looking for the answer - Team work - Preparation - Assume the best of everyone - Be mindful of the unseen circumstances of others - Engagement - Show up for class - Follow up lesson with study materials - Be a mentor to team mates - Dedication

Instructor Expectations

Understanding for beginners - Networking for job placement - Responsive - Knowledgeable - Understanding of blockers - Point out common mistakes - Expand and focus on topics that may require further explanation - Tutoring - Explain material and concepts in an easy way to grasp - Availability when students have trouble comprehending concepts - Teach better coding habits - Teach students how to think more like a developer - Teach students how to properly read documentation - Teach C# - Prepare students for careers in the space - Patience - Constructive criticism - Controlling the pace of the material - Giving students good communication strategies for teams

Return to Top