Technical skill gets software written; process and management get it delivered. This area teaches students how professional teams actually ship - the methodologies, pipelines, and organisational context that turn capable programmers into effective team members.
It’s consistently the area employers thank us for, because a graduate who understands sprints, stand-ups, and CI/CD is productive from their first week.
Topics I cover
Scrum and Kanban
The two Agile frameworks students will meet everywhere: Scrum’s sprint rhythm of planning, delivery, and reflection, and Kanban’s flow-based approach with work-in-progress limits.
CI/CD and DevOps
Automating the path from commit to production: pipelines that build, test, and deploy code automatically - including automated testing with tools such as Selenium - so quality is checked continuously rather than at the end.
Project management
Requirements, estimation, risk, and stakeholder communication - the fundamentals that apply whether a project is run with Agile, traditional methods, or the hybrid most organisations actually use.
Business information systems
How technology serves organisational goals: understanding the business context that decides which systems get built, and why the ‘best’ technical solution isn’t always the right one.
Explore: the sprint cycle
Scrum organises work into short, repeating cycles - here’s one full loop. Click or tap each stage to explore it.
How I teach it
Students work in teams on sprint-based projects with real backlogs, stand-ups, and retrospectives - experiencing Agile rather than memorising it, including the awkward parts like scope pressure and uneven contribution that every real team faces.
On the technical side, students build actual CI/CD pipelines: commit code, watch automated tests run (including Selenium browser tests), and see deployments happen without a human in the loop. Once you’ve seen a pipeline catch your bug before a user could, you never want to work without one.
Test yourself
Three quick questions - click an answer to check it instantly.
1. What is a sprint retrospective for?
2. What does CI stand for in CI/CD?
3. Kanban is best known for limiting what?
Where this leads
These skills convert directly into employability: Scrum, Kanban, and CI/CD appear in nearly every developer job description, and they’re the foundation for routes into project management, delivery, and DevOps roles. Combined with the technical areas on this site, they produce what employers actually ask us for - graduates who can build software and deliver it with a team.
