Bootcamps
Coming soon · the subjects below are what they will draw on
Subjects
What it is
Sprints, backlog refinement, estimation, retrospectives, and the roles on a delivery team. SE 359 is undergraduate; SE 6316 and SSW 555 are graduate-numbered.
Where it sits
School of Product Management · Core
You get
The whole Scrum framework run as practice rather than lecture: roles, ceremonies, backlog, estimation, velocity and retrospectives on work you actually deliver.
Still to add
The engineering side of an agile course: pair programming, test-first development and refactoring, and building and integrating working software on an agile team project. C32 teaches the process and its deliverables are not code.
What it is
User research, prototyping, heuristics, usability testing, and designing for people who are not you.
Where it sits
School of Product Management · Core
Crunch Product — AI-Era Product Management
You get
Discovery run properly: user interviews, framing the right problem, specs a team can ship from, and experiments you can trust.
Still to add
Usability-study method — heuristic evaluation, think-aloud protocols, task analysis.
Crunch Front — Senior Frontend Engineering
You get
The implementation half, including accessibility taken seriously rather than as a checklist.
What it is
Discovery, roadmapping, prioritization, metrics, and shipping a product against real constraints.
Where it sits
School of Product Management · Core
Crunch Product — AI-Era Product Management
You get
Running discovery properly, framing the right problem, writing specs teams ship from, defensible prioritisation, answering product questions in SQL, trustworthy experiments, working with design and engineering, and pricing, growth and monetisation.
What it is
Scope, schedule, budget, risk, stakeholders, and the artifacts that keep a project honest.
Where it sits
School of Product Management · Core
Crunch Project Management — Agile Delivery for Tech Teams
You get
The whole lifecycle, Agile for real, owning a backlog, honest estimation and planning, risk and dependency management, stakeholder alignment, measuring delivery with data, budget and capacity planning in SQL rather than spreadsheets, and shipping quality releases.
What it is
Requirements, design, version control, team process, testing, and shipping software as a group instead of alone.
Where it sits
School of Product Management · Core
You get
The delivery process for real: sprints, backlog refinement, estimation, standups and retrospectives, and the roles on a team that ships.
Still to add
Requirements engineering and formal specification, and a term-long team project with an outside stakeholder.
You get
The collaboration mechanics: branching, pull requests, review, merge conflicts and history you can read six months later.
Crunch Mesh — Microservices & Distributed Systems
You get
The design half at the level a senior engineer works: service boundaries, contracts, failure modes and the trade-offs behind each.