lesson 4.6 - agile & scrum project methodologies
Discover Agile and Scrum methodologies for BTEC DIT. Learn how to sprint through digital projects with iterative flexibility and team collaboration.
Ready to sprint? Don't worry, you won't need your running shoes! In the fast-moving tech world, clients often change their minds halfway through a project. If you are using Waterfall, that is a massive headache. But what if there was a way to build software in short, fast bursts, getting feedback along the way? Today, we are diving into Agile and the Scrum framework, learning how modern tech teams stay flexible, communicate daily, and build amazing digital products without getting bogged down by rigid plans!
Learning Outcomes
The Building Blocks (Factual Knowledge)
The Connections and Theories (Conceptual Knowledge)
The Skills and Methods (Procedural Knowledge)
recall the definition of the Agile project management methodology and the Scrum framework
describe the purpose of a sprint and a daily stand-up meeting
analyse how Agile handles changes in client requirements compared to rigid methodologies
The Connections and Theories (Conceptual Knowledge)
describe the concept of iterative development and continuous feedback loops
evaluate the advantages and disadvantages of using Agile for user interface development
apply your understanding of Agile to justify its use for projects with unclear initial requirements
The Skills and Methods (Procedural Knowledge)
describe the process of breaking down a large project into smaller sprint tasks
analyse a project scenario to determine if Agile or Waterfall would be the most effective methodology
create a basic Scrum sprint plan mapping out tasks for a short development cycle
Digital Skill Focus: Digital Project Management
What is Agile?
Have you ever spent hours building a massive block tower, only for someone to tell you they actually wanted a spaceship? If you used the Waterfall methodology, you would have to smash the tower and start completely from scratch.
Enter the Agile methodology! Agile is a highly flexible approach to project management. Instead of trying to build the entire project in one go, an Agile team builds the project in small, bite-sized chunks. After each chunk is built, they show it to the client. This creates a continuous feedback loop. If the client wants to change their mind, it is no problem! The team simply adapts the plan for the next chunk of work. This makes Agile perfect for user interface projects where requirements frequently change.
The Scrum Framework
Agile is the broad concept, but Scrum is a specific framework that tells teams how to be Agile. In Scrum, teams do not work on year-long schedules; they work in short bursts called sprints.
1
The Product Backlog
A massive to-do list of everything the client wants in the final product.
2
The Sprint
A short time-box where the team focuses on completing just a few items from the backlog. Sprints generally last between 1 and 4 weeks.
3
The Daily Stand-Up
A quick daily meeting where team members stand up (to keep the meeting short!) and say what they did yesterday, what they are doing today, and if anything is blocking their progress.
4
The Sprint Review
At the end of the sprint, the team shows the working piece of software to the client to get their feedback. Because Scrum is iterative, it constantly improves the product based on real user feedback, rather than just guessing what the user wants at the start!
Task Sprint Planning & The Kanban Board
You have just been hired as a Junior Scrum Master for a tech company building SnackAttack, a brand new food delivery app. The client has big ideas and we've decided to use the Agile methodology in our project planning. The first thing we need to do is to break this project down, visualise it using a Kanban board, and plan our very first Sprint!
1
Let's do some research!
Before we start on the big plan, use this AI tool to help you to do some research on Agile, Scrum and Sprints.
Agile, Scrum, Sprints?
Act as a supportive, expert computer science tutor. Explain how software development teams use Agile, Scrum and Kanban boards together to manage a sprint. Limit the length of the response to 200 words. Explain this so a 14-year-old Key Stage 4 student can understand. Keep the tone encouraging, clear, and avoiding overly academic jargon. Use a real-world analogy. Do not write my essay for me. No intro, No outro, No deviation from the topic, No follow-up questions.
2
The Master Product Backlog
The client has provided a list of 16 features they want in the final app (in no particular order). This is known as the Product Backlog. Read through these carefully. Pay close attention to the hints in the brackets as they will tell you which tasks rely on other tasks being finished first!
Apple Pay Integration
A quick payment button.
After Checkout Screen
Login Screen
Let users log into their accoun
After User Registration
Restaurant Database
Store all the menus and prices
After Database Setup
Live Driver Map
Show a moving car icon
After GPS Location Tracker
Add to Basket Button
Let users save items to buy
After Menu Screen
Database Setup
Create the storage for the app
Must happen FIRST
Order Confirmation
Tell the user their food is cooking
After Checkout Screen
Profile Page
Show the user their details
After Login Screen
Checkout Screen
Where users type in their card details
After Basket Review Screen
Driver Rating Popup
Give the delivery driver stars
After Order Confirmation
User Registration
Let users create a new account
After Database Setup
Favourite Meals List
Save top meals for later
After Order Confirmation and Profile Page
Menu Screen
Show pictures and prices of the food
After Restaurant Database
Dark Mode Theme
Changes the screen background to black
At the END
Basket Review Screen
See the total cost
After Add to Basket
GPS Location Tracker
Find where the driver is
After Order Confirmation
3
Grab Your Kanban Board
Agile teams use Kanban boards to track their Sprints. Download this pre-populated Kanban board template and make sure it's saved somewhere sensible. Open it up but remember the click Enable Editing if the yellow security bar appears.
The template has four columns:
1
Product Backlog (The master wish-list - pre-populated with the product backlog items)
2
Sprint Backlog (What we are doing in this sprint)
3
In Progress (What we are actively building right now)
4
Done (Completed and tested)
4
Order, orders (tricky!)
First job - place all of the subtasks in chronological order in the product backlog column so that you know what to tackle in the first, and subsequent, sprints. Use the 'predecessor' information in step 2 to help you.
5
Plan your first Sprint
Divide your product backlog into logical groups. The first group should be concerned with setting up the website and user login features.
Move your chosen tasks into the Sprint Backlog column.
Add a description of the sprint in the text box.
6
Duplicate and replicate
Now, in the slide sorter (left hand side of PowerPoint), right click on the existing slide and choose Duplicate. You should get a copy of Sprint 1 called Sprint 2! Move all your sprint backlog tasks into the Done column.
7
Plan the rest of your sprints!
Repeat the process until you have completed the 'project'.
Outcome: A digital Kanban board featuring a fully populated Product Backlog, a justified 4-task Sprint 1 Backlog, and a written Daily Stand-Up script.
Application to the Component Sample PSA
Majestic Cinema (Component 1)
If you are designing the user interface for the Majestic Cinema, you might find that after testing the first prototype, users struggle to find the 'Seat Selection' button. Using an Agile approach means you do not have to scrap the whole project; you can simply add a task to "Redesign Seat Button" in the next sprint and fix it immediately based on real user feedback.
Pedal Power Cycles (Component 2)
When building the data dashboard for Pedal Power Cycles, the shop owner might suddenly decide they want to see "Repairs" data as well as "Sales" data. In a Scrum framework, you would just add this new requirement to the Product Backlog and assign it to a future sprint, ensuring the client gets exactly what they need without derailing the work you are actively doing today.
Out of Lesson Learning
⭐ The Majestic Backlog
Imagine you are starting the Majestic Cinema user interface project. Create a mini Product Backlog by writing down a list of 5 distinct features the app will need (e.g., 'Movie Search Bar'). Number them from 1 to 5 to show the logical order they must be built in, ensuring that features which heavily depend on others are built later in the sequence.
Imagine you are starting the Majestic Cinema user interface project. Create a mini Product Backlog by writing down a list of 5 distinct features the app will need (e.g., 'Movie Search Bar'). Number them from 1 to 5 to show the logical order they must be built in, ensuring that features which heavily depend on others are built later in the sequence.
⭐⭐ Sprint to the Dashboard
You have been given a two-week sprint to begin building the Pedal Power Cycles dashboard. You only have time to create two data visualisations. Decide which two charts or graphs are the most foundational for a bike shop owner to see first. Write a short paragraph justifying your choices and explaining why other charts have been left in the Product Backlog for Sprint 2.
You have been given a two-week sprint to begin building the Pedal Power Cycles dashboard. You only have time to create two data visualisations. Decide which two charts or graphs are the most foundational for a bike shop owner to see first. Write a short paragraph justifying your choices and explaining why other charts have been left in the Product Backlog for Sprint 2.
⭐⭐⭐ The Client Curveball
You are halfway through designing the Majestic Cinema booking system when the client sends an urgent email demanding a brand new "VIP Membership Lounge" section be added to the interface. Write a professional reply email to the client. In your email, explain how the Agile methodology allows you to handle this sudden change smoothly, and briefly describe what would have happened if the team was using the rigid Waterfall methodology instead.
You are halfway through designing the Majestic Cinema booking system when the client sends an urgent email demanding a brand new "VIP Membership Lounge" section be added to the interface. Write a professional reply email to the client. In your email, explain how the Agile methodology allows you to handle this sudden change smoothly, and briefly describe what would have happened if the team was using the rigid Waterfall methodology instead.
Last modified: March 20th, 2026
