How you work today Work in your semester project team (4-5 students) on ONE shared Trello board. Every member writes at least 3 user stories and puts their initials on those cards. Marks are given to each student. |
1. Objectives
By the end of this practical you will be able to:
- Turn your team's project features into user stories in the form "As a ... I want ... so that ...".
- Write acceptance criteria that a tester could check with a clear yes or no.
- Estimate stories with story points and order them by priority (MoSCoW).
- Build a product backlog and plan Sprint 1 on a Trello Scrum board using the team's velocity.
- Use a Scrum board tool (Trello) the way real software teams do (P3: guided response).
2. Word bank
Word | Simple meaning | Real-world example |
|---|---|---|
user story | a short description of a feature, told from the user's point of view | As a student, I want to see today's menu so that I can decide what to order. |
acceptance criteria | the conditions that must be true for the story to count as finished | Prices are shown in rupees next to every item. |
product backlog | the full, ordered list of everything the product might need | all 12 stories of the cafeteria app, most important first |
sprint | a short, fixed period of work (usually 1-4 weeks) that ends with working software | Sprint 1 = the next two weeks |
sprint backlog | the stories the team chooses to finish in one sprint | the 5 stories in the "Sprint 1 To Do" list |
story point | a number that shows how big or difficult a story is, compared with other stories | "see menu" = 2 points, "pay online" = 8 points |
velocity | how many story points a team finishes in one sprint, on average | 18, 22 and 20 points in three sprints: velocity = 20 |
epic | a story that is too big to finish in one sprint; it must be split | "As a student, I want the whole ordering system..." |
MoSCoW | a way to set priority: Must have, Should have, Could have, Won't have (this time) | payment = Must; meal rating = Could |
Definition of Done | the team's checklist that every story must pass before it is "Done" | coded, tested, reviewed by a teammate, shown to the Product Owner |
Scrum board | a board with columns that shows where each piece of work is | To Do | In Progress | Testing | Done |
3. Background
In Lecture 3 you learned that agile teams plan a little, build a little, and learn. Today you will do the planning part with a real tool. Software houses in Lahore, Islamabad and Faisalabad use tools like Jira and Trello every day for exactly this work.
Real-world example: the order rack at a dhaba At a busy dhaba, every order slip moves along a rack: received → cooking → ready → served. Anyone can look at the rack and see what is waiting, what is being cooked and what is finished. Nobody needs to ask. A Scrum board works the same way. Each card is one piece of work, and each column shows its status. |
1. User stories. Agile teams write requirements as short user stories. The usual format (you will study it in Lecture 4) is:
Part | Question it answers | Example (cafeteria app from Lecture 1) |
|---|---|---|
As a <role> | Who wants this? | As a student |
I want <goal> | What do they want to do? | I want to see today's menu with prices |
so that <benefit> | Why does it matter to them? | so that I can decide what to order before the lunch rush |
A story describes a user need, not a technical task. "Create the orders table in MySQL" is a task (it may appear later in a checklist), not a user story.
2. Acceptance criteria. Each story needs 2-4 conditions that decide when it is finished. Good criteria are testable: a tester can answer yes or no. Some teams write them as Given / When / Then:
- Given the canteen has marked "Biryani" as sold out, when a student opens the menu, then Biryani is shown in grey and cannot be ordered.
- Bad: "The menu should look nice." (Nobody can test "nice".)
3. Story points. Teams estimate size, not hours, using numbers from the Fibonacci series: 1, 2, 3, 5, 8, 13. A 2-point story is about twice as big as a 1-point story. Anything bigger than 13 is an epic and must be split.
4. Priority with MoSCoW. Must have (the product is useless without it), Should have (important, but there is a workaround), Could have (nice to have), Won't have this time. The backlog is ordered with Must stories at the top.
5. Velocity and sprint planning. Velocity is the average number of points a team finishes in one sprint. In sprint planning, the team takes stories from the top of the backlog until the total is close to its velocity, without going over it.
Scrum board list (column) | What goes there |
|---|---|
Product Backlog | All stories not yet planned, most important at the top |
Sprint 1 - To Do | Stories chosen for this sprint (the sprint backlog) |
In Progress | Stories someone is working on now (write their initials) |
Testing / Review | Built, now being checked against the acceptance criteria |
Done | Passed the Definition of Done |
Your team has no history yet A new team does not know its velocity. For this lab, use 4 points per team member per 2-week sprint (a team of 5 has velocity 20; a team of 4 has velocity 16). After real sprints you will replace this guess with real numbers. |
Word help Fibonacci = a number series where each number is the sum of the two before it: 1, 2, 3, 5, 8, 13 workaround = another way to get the job done for now |
4. Before you start
1. Open trello.com and sign in with your university or personal e-mail. (The free plan is enough.)
2. One member creates a board named SE401 - <Team name> - <Project name>. Set visibility to Workspace or Private.
3. Invite all team members (Share button). Also invite your teacher using the e-mail written on the board.
4. Do not delete another team's board or cards. Work only on your own board.
5. Time plan (120 minutes)
Time | What you do |
|---|---|
0:00-0:15 | Teacher demo: a Scrum board for the cafeteria app; how to write one good story card |
0:15-0:30 | Part A warm-up, Part B planning maths, Part C find the flaw (individual, on paper) |
0:30-0:45 | Task 1: create the board, lists and labels |
0:45-1:15 | Task 2 and Task 3: user stories and acceptance criteria |
1:15-1:35 | Task 4: story points and MoSCoW; order the backlog |
1:35-1:50 | Task 5: plan Sprint 1 |
1:50-2:00 | Teacher checks boards; Part E post-lab questions; submission |
Part A: Warm-up: user need or technical task?
Write S if the item is a user story (a user need) or T if it is a technical task. For each S item, underline the role.
(a) A student can see today's menu with prices.
(b) Install Node.js on the server.
(c) The canteen owner can mark an item as sold out.
(d) Design the database tables for orders.
(e) A student gets a message when the order is ready.
(f) Write unit tests for the payment module.
(g) The kitchen staff can see all orders in the order they were placed.
(h) Choose between React and Flutter.
Part B: Predict the plan: velocity and sprint maths
The cafeteria team (5 students) has this backlog, already in priority order. Another team of the same size finished 18, 22 and 20 points in its last three sprints. Use that as this team's velocity.
# | User story (short) | Points | MoSCoW |
|---|---|---|---|
1 | See today's menu with prices | 2 | Must |
2 | Place an order for pickup | 5 | Must |
3 | Kitchen sees the order queue | 5 | Must |
4 | Owner marks an item as sold out | 2 | Must |
5 | Pay with JazzCash or Easypaisa | 8 | Must |
6 | Get a message when the order is ready | 3 | Must |
7 | Cancel an order before cooking starts | 3 | Should |
8 | Owner sees the daily sales report | 5 | Should |
9 | See my order history | 3 | Should |
10 | Rate a meal | 2 | Could |
11 | Save favourite items | 2 | Could |
12 | Menu in Urdu | 5 | Could |
(a) What is the team's velocity?
(b) What is the total of the Must stories? Can all of them fit in Sprint 1?
(c) Which stories would you put in Sprint 1? Give the total.
(d) The whole backlog is 45 points. At least how many sprints are needed?
Part C: Find the flaw: bad user stories
Each item below has ONE main problem. Name the problem and rewrite it correctly.
(1) "Create the database tables for orders."
(2) "As a user, I want the app to be fast."
(3) "As a student, I want to order food, pay online, track my order, rate the meal and get a refund."
(4) "As a developer, I want to use React so that the code is modern."
(5) Story: "As a student, I want to see the menu so that I can choose food." Acceptance criterion: "The menu should look nice."
(6) A 21-point story planned for a sprint with velocity 20.
Part D: Graded tasks (20 marks)
Task | Level | What you build | Marks |
|---|---|---|---|
T1 | Easy | Set up the Scrum board | 3 |
T2 | Easy-Medium | Write the product backlog (12 or more user stories) | 4 |
T3 | Medium | Add acceptance criteria | 4 |
T4 | Medium | Estimate and prioritise | 4 |
T5 | Challenge | Plan Sprint 1 | 5 |
Total | 20 |
T1 Set up the Scrum board (3 marks · Easy)
1. Create (or open) your team board: SE401 - <Team name> - <Project name>.
2. Create five lists from left to right: Product Backlog | Sprint 1 - To Do | In Progress | Testing / Review | Done.
3. Create four labels: Must (red), Should (orange), Could (yellow), Won't (grey).
4. Add one card at the top of the Done list called Definition of Done with a checklist of at least 3 items.
5. Make sure every team member and the teacher are members of the board.
Sample: A correct board after Task 1 Lists: Product Backlog | Sprint 1 - To Do | In Progress | Testing / Review | Done Labels: Must (red) · Should (orange) · Could (yellow) · Won't (grey) Card "Definition of Done" checklist: [ ] Code works on a real phone [ ] Acceptance criteria checked by a teammate [ ] Shown to the Product Owner |
T2 Write the product backlog (12 or more user stories) (4 marks · Easy-Medium)
1. Start from the 8 features your team brought (Lecture 3 homework). Add more until you have at least 12 stories.
2. Write each card title as: As a <role>, I want <goal> so that <benefit>.
3. Use at least 3 different roles (for example student, canteen owner, kitchen staff, admin).
4. Every member writes at least 3 stories and adds their initials at the end of the card title, e.g. "(AR)".
5. No technical tasks as cards. Put them later in a card's checklist if needed.
Sample: Example cards (cafeteria app) As a student, I want to see today's menu with prices so that I can decide what to order. (AR) As a canteen owner, I want to mark an item as sold out so that students do not order food we cannot make. (HB) As kitchen staff, I want to see orders in the order they were placed so that we cook them fairly. (MS) |
T3 Add acceptance criteria (4 marks · Medium)
1. Choose the 4 most important stories.
2. Open each card. In the Description, write 2-4 acceptance criteria. Each must be testable (yes/no).
3. Use the Given / When / Then form for at least one criterion.
Sample: Card: "As a student, I want to place an order for pickup so that my food is ready when I arrive." Acceptance criteria: 1. Given I have items in my cart, when I press "Place order", then I see an order number and a pickup time. 2. The order appears in the kitchen queue within 5 seconds. 3. I cannot place an order with an empty cart. |
T4 Estimate and prioritise (4 marks · Medium)
1. As a team, give every story a size in points: 1, 2, 3, 5, 8 or 13. Start the card title with the points in brackets, e.g. "(5) As a student...".
2. Tip (planning poker): everyone shows a number at the same time; if numbers differ a lot, the highest and lowest explain, then vote again.
3. Split any story above 13 points into smaller stories.
4. Add a MoSCoW label to every card.
5. Drag the cards so the Product Backlog is in priority order: all Must stories at the top.
Sample: Top of an ordered backlog (2) [Must] See today's menu with prices (5) [Must] Place an order for pickup (5) [Must] Kitchen sees the order queue ... (5) [Could] Menu in Urdu |
T5 Plan Sprint 1 (5 marks · Challenge)
1. Work out your team's velocity: 4 points x number of members (team of 5 = 20; team of 4 = 16).
2. Move stories from the top of the Product Backlog into Sprint 1 - To Do until the total is as close to the velocity as possible without going over.
3. If a Must story does not fit, explain your choice (move it to Sprint 2, or split it).
4. For every Sprint 1 card: add a member who owns it, a due date at the end of the sprint, and a checklist of 2-4 technical tasks.
5. Create a card at the top of Sprint 1 - To Do called Sprint 1 goal with one sentence and the point total, e.g. "Goal: a student can order and the kitchen can see the order. 20 / 20 points."
6. Move one card to In Progress to show you know how the board flows.
Sample: Sprint 1 goal card (cafeteria team of 5) Goal: a student can see the menu and place an order, and the kitchen can see and finish it. Stories: (2) menu, (5) place order, (5) kitchen queue, (2) sold out, (3) ready message, (3) cancel = 20 / 20 points. Moved to Sprint 2: (8) pay with JazzCash/Easypaisa - students pay cash at the counter in Sprint 1. |
Part E: Post-lab questions
1. What is the difference between the product backlog and the sprint backlog?
2. Why do agile teams estimate in story points instead of hours?
3. Your team's velocity is 16 and the top three Must stories are 8, 5 and 5 points. What will you do?
4. Which Agile Manifesto value does a Scrum board support most, and why?
5. Why should Must stories be only part of the backlog, not all of it?
Marking rubric
Task | Marks | Full marks when ... |
|---|---|---|
T1 Set up the Scrum board | 3 | 1 mark: five lists in order 1 mark: four MoSCoW labels 1 mark: Definition of Done card (3+ checks) and all members invited |
T2 Write the product backlog (12 or more user stories) | 4 | 2 marks: 12+ stories in correct form (1 if 8-11, or several in wrong form) 1 mark: 3+ different roles with real benefits 1 mark: no technical tasks; own 3+ stories with initials (individual) |
T3 Add acceptance criteria | 4 | 1 mark per story with 2+ testable criteria (max 4). Deduct 0.5 for each untestable criterion ("nice", "easy", "fast" with no measure). |
T4 Estimate and prioritise | 4 | 1 mark: every card has valid points 1 mark: every card has a MoSCoW label 1 mark: backlog ordered (Must on top) 1 mark: sensible estimates (bigger stories have bigger points; any epic split) |
T5 Plan Sprint 1 | 5 | 1 mark: correct velocity and total not above it 1 mark: stories taken in priority order (or a reason given) 1 mark: owner + due date on every Sprint 1 card 1 mark: task checklists (2-4 tasks each) 1 mark: clear sprint goal card with total |
Parts A, B, C and E are not marked separately; they prepare you for the tasks and the viva.
Submission
- Before leaving the lab, the teacher checks your board and records your marks.
- Upload to the LMS by the end of the day: (1) the board link, (2) two screenshots (the whole board, and one opened card with acceptance criteria), (3) your answers to Parts A-C and E.
- Copy your own 3 stories, one card with acceptance criteria, and your answers to Part E into the Lab Book (Practical 2 pages).
- Keep the board. You will use it again in Lecture 5 (Scrum) and in later practicals.