Tailwind Takeoff ‐ Project Plan & Business Plan

Opening Task

• Scholars will complete opening task on Schoology covering topics learned from HTML/CSS unit
• Randomly selected scholar will facilitate review with peers

GitHub Issues Mini-Lesson (15 Minutes)

• Instructor-led live demo on projector — students follow along in their pre-created repos
• Demo covers:
  • Navigating to the GitHub Project board (already set up by instructor via school organization)
  • The three columns students will use: To Do, In Progress, Done
  • Writing one complete Issue together as a class (“Create shared navigation component”) — title, description, and acceptance criteria
• Key check-for-understanding: ask the class to identify what makes the demo Issue good before moving on (“What would a bad version of this Issue look like?”)

GitHub Issues — Work Time (35 Minutes)

• Groups create GitHub Issues for every pre-filled task in the Planning, Design, and Development sections of the Project Plan handout — one task per Issue

• Each Issue must have: a clear title, a one-sentence description, and an assigned team member

• Groups add any project-specific tasks they identify in the custom rows at the bottom of the handout

• Once Issues are written, groups move each one into the To Do column of their project board and confirm assignments are correct

• Instructor circulates and checks:

  • Are Issues scoped to a single completable task, or are they too broad?
  • Is every team member assigned at least a few Issues?
  • Does the README document the branching convention?

• Key check-for-understanding questions while circulating:

  • “If someone else read this Issue, would they know exactly what done looks like?”
  • “Which Issues could you start working on in parallel right now?”

Break (10 Minutes)

Business Plan Mini-Lesson (15 Minutes)

• Instructor-led walkthrough of what a business plan means at this stage — not a 40-page document, but a clear set of decisions that will drive every design and content choice on the site
• Walk through each section using one real example (e.g. Spotify or a well-known local business):
  • Value proposition: who it’s for, what problem it solves, why it’s different
  • Target audience: specific, not demographic — describe one real person
  • Competitors: direct vs. indirect, and what gap exists
  • Revenue model: how the business actually makes money (freemium, subscription, one-time purchase, service fees, ads)
  • Brand identity: name, tagline, tone, and visual direction
• Emphasize that the business plan is now a tracked task on their GitHub board — it has an owner, and it has a definition of done

Business Plan Workshop (35 Minutes)

• Groups work through the business plan sections collaboratively in a shared Google Doc

• Product owner leads the discussion; all members contribute

• Instructor circulates and pushes for specificity:

  • “Teens who like fashion” → “High school students aged 14–18 who follow streetwear creators on TikTok”
  • “Better than the competition” → “Unlike [Competitor], we offer [specific differentiator]”
  • “We’ll make money from ads” → “We’ll offer a free tier and charge $X/month for premium features”

• Key check-for-understanding questions while circulating:

  • “Who specifically is your customer — can you describe one real person by name?”
  • “If I gave your target customer $20, would they spend it on your product or something else? Why?”
  • “What’s the one thing your brand should never sound like?”

Value Proposition Share-Out (10 Minutes)

• Each group reads their value proposition statement aloud — one sentence
• Peers give one “warm” (what’s clear) and one “wonder” (a question the statement leaves open)
• Instructor flags any value propositions that are still too generic before groups leave — those groups must revise and resubmit before Day 3

Closing & Exit Ticket (10 Minutes)

• Instructor previews Day 3: wireframing and CSS framework introduction
• Exit ticket submitted individually before leaving — three questions:
  1. What role are you playing on this project, and what is the first GitHub Issue you own?
  2. In one sentence, what is your business’s value proposition?
  3. What is one risk you see for your team over the next three weeks?
• Instructor reviews exit tickets before Day 3 to identify uneven workloads, lingering idea problems, or team tension early

Project Plan Completion Rubric