Loading...
Community presentation
Lesson 2: How Software Gets Built: The SDLC Your class 60 minutes in class Students High school students (Elite 101, Fall 2026) Delivery Live class on Zoom, instructor-facilitat…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Lesson 2: How Software Gets Built: The SDLC Your class 60 minutes in class Students High school students (Elite 101, Fall 2026) Delivery Live class on Zoom, instructor-facilitated Prep Time 30 to 40 minutes Materials The lesson URL open in two tabs (one instructor, one student), Zoom with breakout rooms, and your section page in HireWheel. No GitHub and no Codespaces today. Learning Objectives By the end of this lesson, students should be able to: Name the six phases of the Software Development Life Cycle (Planning, Analysis, Design, Implementation, Testing, Maintenance) and state the question each phase answers. Explain the SDLC honestly: Waterfall runs the phases in strict order, while many modern teams loop through the same phases in small, repeating cycles, without calling the SDLC itself 'iterative'. Match real software activities to the correct SDLC phase, including the tricky Planning-vs-Analysis and Testing-vs-Maintenance distinctions. Define 'stakeholder' and identify where a student startup sits on the SDLC arc at this point in the term. Sketch the six-phase life cycle of a familiar app as a squad. Before Class Starts Click through all 7 zones with ?role=instructor&mode=live on the lesson URL. Today has no code cells, no repo work and no Codespaces: you need Zoom, the lesson URL, and breakout rooms. Open a second tab with ?role=student&mode=live and screen-share THAT one. The instructor tab prints the instructor notes and answer keys inline, so sharing it shows the class every answer. Open your section page in HireWheel, check the Squads panel, and pre-build breakout rooms from it. If squads are not listed yet, plan to auto-assign rooms of 3 to 4; those are not the final squads, and that is fine for today. Pick the fallback app you will hand a stalled squad (Spotify works) and be ready to say one sentence per phase for it yourself. Know the deadline you will announce: the exit ticket is due tonight by 9:59 PM Central. Solo Reps and Stretch are optional and unscored. Your hour in class 60 minutes total Time Mins What happens What you are doing 0:00 5 min Standup Favorite-app hook + confidence pulse You teach, they listen and follow along 0:05 15 min Core Concept The six phases; Waterfall vs modern cycles; stakeholders You teach, they listen and follow along 0:20 20 min Guided Practice Match 8 activities to phases; lunch-app case study You drive, they do it with you step by step 0:40 15 min Startup Time Squad maps a familiar app across the six phases (facilitated) They build, you circulate and unblock 0:55 5 min Wrap-Up Land the lesson, name what is due, open the exit ticket together You close it out together 1:00 Class ends. Everything below this line is theirs, not yours. After class, on their own Student work. It is not part of your hour and you do not need to cover it live. Solo Reps about 10 min Self-paced 'name that phase' reps Practice drills on their own. Nothing for you to run. Stretch about 10 min Two real software failures: which phase failed? (optional) Optional and unscored. Do NOT spend class time on this. Point at it for anyone who wants more and move on. Exit Ticket about 10 min 4 MC + reflection + exit pulse Open it together in the last few minutes so they know where it is, then they finish it on their own by 9:59 PM CT. Follow Design: {"palette":["Deep Terminal Navy #0B101B — canvas background","Electric Cyan #00F0FF — primary highlight and phase markers","Cyber Lime #CCFF00 — live breakouts and active timers","Card Obsidian #151D2C — container cards and phase panels","Ice White #F3F6FC — primary titles and high-contrast text","Muted Slate #8F9CAE — secondary descriptions and metadata"],"fonts":{"Space Grotesk":"https://fonts.googleapis.com/css2?family=Space+Grotesk:wght@300..700&display=swap","Plus Jakarta Sans":"https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:ital,wght@0,200..800;1,200..800&display=swap","JetBrains Mono":"https://fonts.googleapis.com/css2?family=JetBrains+Mono:ital,wght@0,100..800;1,100..800&display=swap"},"type":"Space Grotesk at heavy weights (700) for energetic tech headers with tight tracking; Plus Jakarta Sans (400/500) for high-legibility body instructions; JetBrains Mono for time stamps, squad badges, and live Zoom agenda markers.","layout":"16:9 modular grid optimized for Zoom screenshare with generous 64px outer padding. Left-anchored phase pipelines with right-column activity cards, fixed top utility rails showing current session time (0:00 to 1:00), and bold split-screen comparisons for Waterfall versus iterative cycles.","framework_treatment":"Deep dark-mode cards with subtle 1px border glows in Cyan and Lime. Numbered hexagon badges for the six SDLC phases, connected by directional trace lines. Activity zones feature pill-shaped status chips ('Solo Reps', 'Startup Time', 'Exit Ticket') and prominent countdown containers.","feels_like":"A high-octane engineering lab interface in a modern Y Combinator teen incubator"}
Presentation overview
This community presentation was shared by James Barnett as a complete 8-slide example. Lesson 2: How Software Gets Built: The SDLC Your class 60 minutes in class Students High school students (Elite 101, Fall 2026) Delivery Live class on Zoom, instructor-facilitat… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
