Lab Report: 01
Title:
Course Title: Object-oriented analysis and design (OOAD)
Course Code: CSE 314
3rd Year 1st Semester Examination 2024
Submitted to :-
Sarnali Basak
Associate Professor
Submitted by :-
Zakia Binta Syeed
Roll- 402
Session – 2021-2022
Submitted Date:-
08.05.2025
1. Introduction
This lab session focused on visualizing task scheduling and progress tracking using the
principles of Agile methodology. We practiced managing task flow using a simple board with
columns representing different stages: To Do, Doing, Testing, and Done. This simulation helped
us understand real-world software team workflows.
2. Objective
To learn and simulate agile task scheduling.
To apply basic OOAD teamwork principles in a practical setting.
To observe the flow of task completion and identify blockers or delays.
To understand the nature of long-term or unachievable tasks within a timebox.
3. Equipment Used
Sticky Notes
Pen
Whiteboard or Chart Paper
Team Members
4. Procedure (Step-by-Step Execution)
Step 1: To Do
We began by listing all tasks in the To Do column. Each sticky note represented a single task
like:
“Find each member’s age”
“Find favorite food”
“Favorite programming language”
“Find sum/product of ages”
Step 2: Doing
Each team member picked a task and moved it to the Doing column to begin working on it.
Tasks were distributed based on interest and clarity.
Step 3: Testing
Once a task was completed, it was shifted to the Testing column. Other team members cross-
checked the results to verify correctness.
Step 4: Done
Successfully tested tasks were then moved to the Done column, indicating completion.
Step 5: Climbing Mount Everest (Still in Doing)
We introduced a symbolic, complex task — “Climb Mount Everest” — to represent a big,
ambitious item. This task was added to the Doing column but due to its complexity, we couldn’t
complete it in the session.
Step 6: Collecting Information on Climbing (Still in Doing)
We researched the resources and steps needed for “Climb Mount Everest.” However, this
information-gathering process remained incomplete and the task stayed in Doing. It served as an
example of how certain tasks might remain unfinished within a limited sprint or time frame.
5. Observations and Discussion
The visual board made team progress clear and helped distribute tasks efficiently.
Testing stage helped reduce mistakes and maintain consistency.
“Climb Mount Everest” was a metaphorical task showing how large goals need long-term
planning.
The exercise demonstrated how bottlenecks can arise, especially with tasks requiring
external input or excessive effort.
6. Conclusion
Through this lab, we learned how Agile task boards function in collaborative development. From
simple tasks to complex symbolic ones, each item followed a pipeline. The inability to finish the
Everest task in time taught us that not all goals are achievable in a single cycle — and planning
accordingly is essential.
