ONLINE EXAM REGISTRATION

6CS1016 SOFTWARE ENGINEERING & AGILE DEVELOPMENT PROJECT

REPORT
Submitted by
A. Siva Prasad (2022BCSE07AED536)
Rk. Abdul Ahad (2022BCSE07AED539)
A. Deepak Reddy (2022BCSE07AED591)
B. Sai Krishna (2022BCSE07AED610)
P. Lakshmi Manoj (2022BCSE07AED660)

In partial fulfilment for the award of the degree of

BACHELOR OF TECHNOLOGY
In
COMPUTER SCIENCE AND ENGINEERING

Under the Supervision of

J MANO SHANKARI

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

ALLIANCE SCHOOL OF ADVANCED COMPUTING
ALLIANCE UNIVERSITY, BENGALURU

APRIL- 2025

1
 BONAFIED CERTIFICATE

This is to certify that the project work entitled “ONLINE EXAM REGISTRATION”
is the Bonafide work done by A. Siva Prasad (2022BCSE07AED536), RK. Abdul
Ahad (2022BCSE07AED539), A. Deepak Reddy (2022BCSE07AED591), B. Sai
Krishna (2022BCSE07AED610), P. Lakshmi Manoj (2022BCSE07AED660)
submitted in partial fulfilment of the requirements for the award of the degree Bachelor of
Technology in COMPUTER SCIENCE AND ENGINEERING during the Academic
year 2025- 2026.

J Mano Shankari Dr. Ramalakshmi K

Supervisor Head of Department

2
 DECLARATION

This is to declare that the report titled “ONLINE EXAM REGISTRATION” has been
made for the partial fulfilment of the Course Bachelor of Technology in Computer
Science Engineering, under the guidance of J Mano Shankari. We confirm that this
report truly represents our work undertaken as a part of our Software Engineering and
Agile Development project work. This work is not a replication of work done previously
by any other person. We also confirm that the contents of the report and the views
contained therein have been discussed and deliberated with the faculty guides.

NAME REGESTRATION NO. SIGNATURE

A. Siva Prasad 2022BCSE07AED536

RK. Abdul Ahad 2022BCSE07AED539
A. Deepak Reddy 2022BCSE07AED591
B. Sai Krishna 2022BCSE07AED610
P. Lakshmi Manoj 2022BCSE07AED660

3
 ACKNOWLEDGEMENT

The satisfaction that accompanies the successful completion of the task would be put
incomplete without the mention of the people that made it possible, whose constant
guidance and encouragement crown all the efforts successfully.
We are very thankful to our supervisor J Mano Shankari for her sustained inspiring
guidance and cooperation throughout the process of this project. Her wise counsel and
valuable suggestions are invaluable.
We avail this chance to express our deep sense of gratitude and hearty thanks to the
Management of Alliance University, for providing world class infrastructure, congenial
atmosphere, and encouragement.
We express our deep sense of gratitude and because of the teaching and non-teaching
staff at our department who stood with us during the project and helped us to make it a
successful venture.
We place highest regards to our parents, our friends and well-wishers who helped plenty
in making the report of this project.

A. SIVA PRASAD
RK. ABDUL AHAD
A. DEEPAK REDDY
B. SAI KRISHNA
P. LAKSHMI MANOJ

4
 Table of Content

Exp. No Contents Page. No

SOFTWARE DEVELOPMENT 7-34

1 Problem Statement 7

2 Software Requirement Specification (SRS) 8-10

3 UML Tools 11

4
UML Diagrams 12-15
Frontend Design
5
16-28
6 Back end 29-31
7 Test Cases, & Conclusion, Future Scope 32-34

AGILE DEVELOPMENT
35-56
8 Background & Driving Forces Behind Adopting Agile
35-36
Software Development
9 Business Value of Adopting Agile Approach
37-38

10 Understand agile development practices

39-40

Passport Automation System Proposal with

41-42
11 Objectives, Vision, Use Cases & UML Diagrams

5
12 Compile Project release map, user stories for 43-44
Personnel Management System

13 Storyboarding Tasks & Detailed Release Plan 45

14 Product Roadmap Design for Proposed Project 46-47

15
Story Mapping for the Proposed Project 48-49

16 Product Backlog Compilation for Proposed 50-51

Project
17
Sprint Backlog Compilation for Proposed Project 52-53

18 Project Demonstration – Sprint 1 & Sprint 2 54

Releases
19 Final Project Demonstration as per Proposal 55-56

6
 1. Problem Statement

Exam Registration system is used in the effective dispatch of registration forms to all
students. The core of the system is to get the online registration form filled by the
student whose details are verified for genuineness with respect to the already existing
information in the database.
The system also provides the student list of exam dates. The system helps students of
either schools, colleges, or institutions to offer a quick and easy way to appear for an
exam.
The traditional method of exam registration in educational institutions involves a lot of
paperwork, manual verification, long queues, and delays in communication. This
process becomes increasingly inefficient as the number of students grows. There is also
a high chance of human errors during registration and scheduling.

The Online Exam Registration System aims to address these issues by providing a
digital platform where students can register for their exams seamlessly, upload
necessary documents, and receive hall tickets—all from the comfort of their homes. It
ensures real-time validation, secure authentication, and automated scheduling,
significantly reducing administrative overhead and enhancing user convenience.

7
 2. SRS (Software Requirement Specification)

Introduction
Exam Registration System is an interface between the Student and the Exam Controller
responsible for the issue of Hall Ticket. It aims at improving the efficiency in the issue
of Hall Ticket and reduces the complexities involved in it to the maximum possible
extent.
Purpose
If the entire process of "Issue of Hall Ticket" is done in a manual manner, then it would
take several days for the hall ticket to reach the student. Considering the fact that the
number of students for hall tickets is increasing every year, an Automated System
becomes essential to meet the demand.
So this system uses several programming and database techniques to elucidate the work
involved in this process. As this is a matter of National Security, the system has been
carefully verified and validated in order to satisfy it.
Functional Requirements:

1. User Registration and Login – Allows students to sign up, log in, and manage
their profile securely.

2. Exam Form Submission – Students can fill in and submit online exam application
forms.

3. Course Selection – Provides a list of available subjects/courses for selection.

4. Payment Gateway Integration – Enables secure payment of exam fees.

5. Admin Dashboard – Admins can manage student records, course data, and exam
schedules.

6. Slot Booking – Students can choose available exam slots.

7. Hall Ticket Generation – Auto-generates hall tickets post-registration and

verification.

8
 8. Notification System – Sends email/SMS updates regarding registration status and
exam details.

Non-Functional Requirements:

1. Performance – The system should handle concurrent access from multiple

students without lags.

2. Security – User data and credentials must be protected using encryption (e.g.,
bcrypt hashing).

3. Scalability – The system should support increasing numbers of users over time.

4. Usability – Interface should be intuitive, responsive, and accessible on all

devices.

5. Availability – Should be operational 24/7, with minimal downtime.

6. Data Integrity – Ensure no loss or duplication of records during operations.

Scope
 The system provides an online interface to the user where they can fill in
their personal details and submit the necessary documents (may be by
scanning).
 The controller concerned with the issue of hall tickets can use this system to
reduce his workload and process the application in a speedy manner.
 Students will come to know their status of application and the date in which
they must subject themselves for manual document verification.

References
IEEE Software Requirement Specification format.
Technologies to be used
 HTML
 CSS

9
Tools to be used
 XAMPP
 AgroUML (for developing UML Patterns)
 VS Code

Overview
SRS includes two sections: overall description and specific requirements.
 Overall Description will describe the major role of the system components and
interconnections.
 Specific Requirements will describe roles & functions of the actors.

10
 3. UML Tool

The UML Tool that we have used in this project is AgroUML. AgroUML, now known
as diagrams.net, is a versatile online diagramming tool that allows users to create a wide
range of diagrams, including UML (Unified Modelling Language) diagrams. It features
a user-friendly interface with drag-and-drop functionality, making it accessible for both
beginners and experienced users. With a rich library of shapes and templates, AgroUML
supports various diagram types such as class diagrams, sequence diagrams, and use case
diagrams. Additionally, it offers collaboration features, enabling multiple users to work
on diagrams in real-time, and integrates seamlessly with cloud storage services like
Google Drive and Dropbox for easy sharing and storage.

11
 4. UML Diagrams

A UML Diagram is a visual representation of a system that illustrates its structure,

interactions, and behavior for better design and analysis. Importance of UML Diagrams:
 Helps in system planning and design
 Provides clear documentation for developers and stakeholders
 Facilitates better communication between teams
 Improve software maintainability and scalability.

1) Use Case Diagram

12
2) Class Diagram

3) Sequence Diagram

13
4) Activity Diagram

5) Collaboration Diagram

14
6) Deployment Diagram

7) Component Diagram

15
 5. Frontend Design

The frontend of the Online Exam Registration System serves as the user interface that
enables students to interact with the platform efficiently. It is designed to be user-
friendly, responsive, and accessible, ensuring that students can easily navigate through
various sections of the system. The frontend is built using web technologies such as
HTML, CSS, JavaScript, and frameworks like React or Angular, ensuring smooth
functionality and an intuitive user experience.
The key sections of the frontend include:
1. Login & Registration:

 This module allows students to create an account using their personal

details such as name, email, contact number, and password.

 Registered users can securely log in using their credentials, ensuring data
privacy and authentication.

 The system may also include two-factor authentication for added security.

2. Dashboard:

 Once logged in, students are directed to a personalized dashboard that

displays their profile, enrolled courses, upcoming exams, and registration
status.

 The dashboard provides quick access to all essential features in a visually

appealing format.

3. Courses & Course Enrolment:

 This section displays a list of available courses for which students can
enroll.

 Each course page provides details such as syllabus, exam dates, eligibility,
and instructor information.

16
  Students can enroll in their preferred courses and track their progress.

4. Exam Registration:

 The core feature of the system, allowing students to register for upcoming
exams.

 Students can select the exam date, time slot, and location (if applicable).

 A real-time confirmation is provided upon successful registration.

5. Feedback & Support:

 To ensure continuous improvement, a feedback system is integrated,

allowing students to share their experience.

 A support section provides FAQs, contact options, and a help desk for
resolving queries.

The frontend design focuses on efficiency, simplicity, and ease of use, ensuring students
can seamlessly register for exams without unnecessary complexities.

17
Step 1 (Login)

18
Coding Part

19
Step 2 (Registration)

20
Coding Part

21
Step 3 (Registration Successful)

Step 4 (My Profile)

22
Step 5 (Dashboard)

1) Course Registration

a) GAI

23
b) SEAD

c) BA

d) DPS

24
Coding Part

25
2) Testimonials

26
3) Support

4) Results

27
Step 6 (Logout)

28
 6. BACK END

The backend of the Online Exam Registration System is responsible for handling data
processing, authentication, and database management. It ensures the smooth functioning
of the system by managing user requests, verifying credentials, storing data, and
generating exam registrations. The backend is developed using PHP as the server-side
scripting language, and XAMPP (which includes Apache, MySQL, and PHP) as the
development environment.
The key components of the backend include:
1. User Authentication & Session Management:

 The backend handles user login and registration by securely storing

credentials in a MySQL database.

 PHP sessions are used to track logged-in users, ensuring security and
preventing unauthorized access.

 Password encryption techniques (such as hashing with bcrypt) are

implemented for data protection.

2. Database Management:

 A MySQL database is used to store student details, course information,

exam schedules, and registration records.

 The backend interacts with the database using SQL queries to perform
CRUD (Create, Read, Update, Delete) operations.

 Foreign keys and relationships ensure data consistency between users,

courses, and exams.

3. Exam Registration Processing:

 When a student registers for an exam, the backend validates their details
and updates the database accordingly.

29
  It checks for availability of exam slots, preventing overbooking.

 Upon successful registration, the system generates a Hall Ticket, which is

stored in the database and can be accessed by the student.

4. Course Management:

 Admins can add, update, and delete courses through the backend.

 The backend ensures that only authorized users (such as administrators or

instructors) can modify course details.

 It tracks course enrollments, linking students with their selected courses.

5. Feedback & Support Handling:

 The backend collects student feedback and stores it in the database for
analysis.

 A contact form allows students to submit support requests, which are

forwarded to the admin panel for response.

 Automated email notifications can be implemented to confirm ticket

submissions and resolutions.

6. Security & Performance Optimization:

 Input validation and SQL injection prevention techniques are implemented

to secure the system.

 PHP error handling ensures smooth execution, preventing system crashes.

 Caching and optimized SQL queries improve backend performance,

ensuring fast response times.

The backend acts as the core engine of the system, managing student records, processing
registrations, and ensuring a secure and efficient online exam registration experience.

30
31
 7. Test Cases, Conclusion and Future Scope
Test Test Actual
Test Steps Expected Result Status
Case ID Scenario Result

Fill all valid fields User is registered

User As
TC_01 and click and redirected to ✅ Pass
Registration Expected
"Register" login page

Duplicate Register with an

Error: "Email As
TC_02 Email already ✅ Pass
already exists" Expected
Registration registered email

Login with Enter correct User is logged in

As
TC_03 Valid email and and redirected to ✅ Pass
Expected
Credentials password dashboard

Login with Error message:

Enter incorrect As
TC_04 Invalid "Invalid ✅ Pass
email/password Expected
Credentials credentials"

Select available Slot booked and

Exam Slot As
TC_05 exam and time confirmation ✅ Pass
Booking Expected
slot shown

Duplicate Attempt to book Error: "Slot already As

TC_06 ✅ Pass
Slot Booking same slot twice booked" Expected

Admin Admin logs in

Exam added and As
TC_07 Adding and adds a new ✅ Pass
visible to students Expected
Exam exam

Admin
Admin deletes an Exam removed and As
TC_08 Deleting ✅ Pass
existing exam no longer visible Expected
Exam

32
 Student Student logs in
List of active exams As
TC_09 Viewing and checks ✅ Pass
displayed Expected
Exams available exams

Form Leave Error messages for

As
TC_10 Validation - registration form required fields ✅ Pass
Expected
Empty Fields fields empty shown

Password Enter weak

Error: "Password As
TC_11 Strength password during ✅ Pass
too weak" Expected
Check registration

Complete
Payment Payment success As
TC_12 payment with ✅ Pass
Success message displayed Expected
valid card details

Payment Use invalid card Error: "Payment As

TC_13 ✅ Pass
Failure info for payment failed" Expected

User is logged out

Logout Click logout As
TC_14 and redirected to ✅ Pass
Functionality button Expected
login

Auto logout and

Session Stay inactive for As
TC_15 redirect to login ✅ Pass
Expiry a long time Expected
page

33
Conclusion
The Online Exam Registration System was successfully designed and implemented to
streamline and digitize the exam enrolment process for students. By leveraging modern
web technologies and a structured software engineering approach, the system eliminates
manual errors, reduces administrative workload, and improves the overall efficiency of
the registration process.
The platform enables students to register for exams, make secure payments, and
download admit cards all from a centralized, user-friendly interface. On the other hand,
administrators can easily manage exam schedules, student records, and application
approvals through the backend dashboard.
Comprehensive testing was conducted to validate functionality, security, and usability.
All major features were tested with positive outcomes, ensuring that the system meets
its intended goals. The successful execution of this project highlights the importance of
integrating Agile development methodologies with effective system design to solve
real-world academic challenges.
Future Scope
The Online Exam Registration System can be further enhanced in the following ways:

 Mobile App Integration: Developing a cross-platform mobile app for better

accessibility.

 Biometric Verification: Integrating biometric systems (fingerprint/face

recognition) for secure hall ticket issuance.

 AI-based Proctoring: Enable AI proctoring tools for online examinations.

 Multilingual Support: Adding support for regional languages for inclusive access.

 Data Analytics: Implement dashboards for statistical analysis of registration

trends, student demographics, and exam attendance.

 Cloud Deployment: Moving the system to cloud infrastructure for better

scalability and uptime.

34
 Agile Development
Experiment 8

Aim
To understand and implement Agile methodology in developing the Online Exam
Registration System, focusing on iterative delivery, user involvement, flexibility to
evolving requirements, and incremental delivery of functional software components.

Procedure:

1. Requirement Gathering: The team conducted discussions with stakeholders

including students, faculty, and admin staff to collect detailed requirements. This
included functionalities like student login/logout, user authentication, exam slot
booking, course-wise registration, dynamic hall ticket generation, and session-
based tracking.

2. Sprint Planning:

 Sprint 1: Design and implementation of user registration and secure login

mechanism.

 Sprint 2: Development of exam/course selection module integrated with

user dashboard.

 Sprint 3: Admin panel development including student record management

and hall ticket issue.

3. Daily Stand-ups: Conducted brief morning meetings daily to assess individual

progress, identify blockers, reassign priorities, and ensure alignment among
developers and UI designers.

4. Development & Testing: Employed a test-driven development (TDD) approach.

Unit and integration tests were created during the sprint for every component.

35
 5. Sprint Review & Retrospective: At the end of every sprint, the team conducted a
review session with mock users followed by a retrospective meeting to evaluate
sprint efficiency and note areas of improvement.

6. Deployment: XAMPP was used for local deployment. Functional validation was
performed on multiple browsers, and mobile responsiveness was checked using
developer tools.

Output:
A partially deployed Online Exam Registration system with features including user
login, exam registration, validation mechanisms, and partial admin control.

Result:
The Agile model provided flexibility to accommodate new requirements and early
validation of modules by users. Continuous delivery helped reduce risk, and the
incremental deployment ensured the functionality was usable from early stages.

36
 Experiment 9

Aim:
To understand the business value of using Agile methodology in the Online Exam
Registration System, focusing on rapid prototyping, stakeholder feedback integration,
and cost-effective development cycles.
Procedure:

1. Feature Prioritization: The team performed MoSCoW (Must-have, Should-have,

Could-have, Won't-have) prioritization on collected requirements. Critical
features such as user login, application submission, and hall ticket access were
identified as high-priority.

2. Sprint Planning:

 Sprint 1: Focused on student login, registration and authentication

mechanisms.

 Sprint 2: Included course-wise subject selection and submission tracking.

 Sprint 3: Admin functionalities such as verifying student details and

generating admit cards.

3. Continuous Feedback: Regular feedback sessions were conducted with the

faculty coordinator and a selected group of students to validate usability and UX.

4. Value Delivery: Each sprint delivered a set of usable features. Hall ticket
generation and status check features reduced administrative burden significantly.

5. Adaptation and Change Management: Any inconsistencies in logic or UX design

suggested by users were implemented within the same sprint whenever feasible.

37
Output:
High-priority features were delivered incrementally and adopted by users immediately.
Business stakeholders were able to track real-time project progress.

Result:
Agile practices ensured early realization of benefits, reduced rework, improved
satisfaction among stakeholders, and aligned deliverables with academic schedules and
institutional requirements.

38
 Experiment 10

Aim:
To explore and implement Agile best practices in building the Online Exam Registration
System such as sprint-based planning, version control integration, automated testing,
and collaborative retrospectives.

Procedure:

1. User Story Creation:

 “As a student, I want to register and view my exam hall ticket.”

 “As an admin, I need to validate student applications and update their

exam status.”

2. Sprint Planning and Effort Estimation: Sprints were planned in 2-week cycles
with story points estimated using the Planning Poker technique.

3. Daily Stand-ups and Task Boards: Conducted quick status meetings and used a
Kanban board for visualizing tasks (To-Do, In-Progress, Done).

4. Version Control with Git: All team members pushed code to a central Git
repository. GitHub issues were used for tracking bugs.

5. Testing Strategy: Unit testing with assertions was done for each form
submission and authentication module. Security was tested using input fuzzing.

6. Retrospective Sessions: After each sprint, feedback was gathered from the team
to improve process efficiency and reduce bottlenecks.

39
Output:
The project evolved iteratively with well-documented commits, validated test cases, and
bug reports. The login and registration system became robust and secure over multiple
iterations.

Result:
Agile principles significantly increased code quality, allowed better traceability of
work, and ensured team collaboration and accountability throughout the project.

40
 Experiment 11

Aim:
To propose the Online Exam Registration project with comprehensive objectives, a clear
vision, detailed use cases, and relevant UML diagrams to support system design and
stakeholder understanding.

Procedure:

1. Project Objectives:

 Digitize and simplify the student exam registration process.

 Ensure secure and verifiable document uploads (photos, IDs).

 Generate personalized hall tickets automatically.

 Enable real-time tracking and admin-based application control.

2. Vision Statement: The system envisions a centralized web-based portal that

provides students with a seamless and reliable experience to register for academic
exams, access exam-related information, download hall tickets, and receive
timely updates, while providing administrators full control to monitor and
manage registrations effectively.

3. Use Case Identification:

 For Students:

 Register and log in securely.

 Fill out exam application forms.

 Upload necessary documents.

 Track application status and download hall tickets.

 For Administrators:

41
  Authenticate and log in as admin.

 View student applications and uploaded documents.

 Approve or reject exam registrations.

 Generate and assign hall ticket numbers.

4. UML Diagrams:

 Use Case Diagram: Displays interactions between actors (Student, Admin)

and system use cases.

 Class Diagram: Represents key system classes like User, Exam, Document,
and Admin.

 Activity Diagram: Visualizes the exam registration flow.

 Sequence Diagram: Illustrates interactions for student registration and

admin approval.

Output:
A well-documented requirement set with visual diagrams supporting analysis, planning,
and communication.

Result:
The comprehensive planning and modelling phase led to clear expectations, reduced
ambiguity, and enhanced design clarity.

42
 Experiment 12

Aim:
To create a structured project release map and formulate user stories that align with
Agile practices for the Online Exam Registration System.

Procedure:

1. Module Identification: System divided into key modules—authentication, exam

registration, document handling, and admin workflows.

2. Sprint-based Release Planning:

 Sprint 1: Account creation, login validation, password encryption.

 Sprint 2: Form-based subject selection and exam type filtering.

 Sprint 3: Admin review dashboard and notification system.

 Sprint 4: Final testing, bug fixing, hall ticket generation, and logout.

3. User Story Creation:

 Student Stories:

 “As a student, I want to sign up and access the exam form easily.”

 “As a student, I want to view my hall ticket once my form is

approved.”

 Admin Stories:

 “As an admin, I want to review submitted applications and verify

authenticity.”

 “As an admin, I need to update students' application status and

generate admit cards.”

43
 4. Story Mapping: Aligned each story with backlog items and assigned story points.

Output:
Mapped development into five sprints with relevant epics and user stories documented
in Jira.

Result:
Well-structured sprint planning enabled focused execution and ensured important
features were developed first, based on user priorities.

44
 Experiment 13

Aim:
To visualize system interactions through storyboarding and establish a release plan
based on user-centric interfaces and backend tasks.

Procedure:

1. Storyboard Creation: Illustrated key screens such as Registration Page, Login

Interface, Application Form, Upload Page, Status Tracker, Admin Portal.

2. UI-to-Backend Mapping: Linked every user screen to backend functions (e.g.,

database validation, file storage, and status update logic).

3. Feature Prioritization: Focused first on “happy path” scenarios like successful

registration and application, followed by edge cases like invalid form handling
and file rejection.

4. Sprint-Based Release Planning: Created a four-phase rollout plan, each ending

with a milestone review. Prioritized student access first, followed by admin
management features.

Output:
Comprehensive flowchart of user journey, tasks, transitions, and modules per sprint.

Result:
Storyboarding improved communication between frontend and backend developers,
while the release plan helped ensure alignment with academic timelines.

45
 Experiment 14

Aim:
To prepare a product roadmap that lays out system features, timelines, dependencies,
and delivery targets.
Procedure:

1. Project Breakdown into Phases:

 Phase 1: Requirement gathering and initial wireframes.

 Phase 2: Core functionality—login, registration, exam forms.

 Phase 3: Admin dashboard, hall ticket, and scheduling engine.

 Phase 4: Security audit, UI polish, PDF export.

2. Sprint Allocation: Each phase was mapped to two-week sprints, with internal
check-ins after every milestone.

3. Dependency Management:

 Login had to be completed before form design.

 Upload and admin approval modules were developed in parallel.

4. Visualization: A Gantt chart was created showing overlaps, parallel tasks, and
sprint durations.

46
Output:
A well-structured timeline for feature rollout with visible dependencies and realistic
effort estimates.

Result:
The roadmap enabled project coordination, monitored progress, and maintained
development velocity.

47
 Experiment 15

Aim:
To construct a user story map for the Online Exam Registration System to break down
functionality into task groups based on priorities and dependencies.
Procedure:

1. Activity Definition: Segregated high-level activities:

 User Registration/Login

 Application Submission

 Document Upload

 Status Tracking

 Admin Review and Approval

2. Task Breakdown:

 For each activity, identified functional sub-tasks.

 Example: “Upload Documents” → Select file, validate format, preview

image, submit.

3. Priority Mapping:

 MVP (Must-Have): Authentication, Application Form

 Essential: Document Upload, Status Check

 Optional: Email alerts, Reschedule request

4. Sprint Mapping: Distributed tasks across sprints while balancing complexity and
interdependencies.

48
Output:
Prioritized and sprint-mapped task board designed on Miro (digital whiteboard).

Result:
Story mapping gave the team a complete overview, prevented scope creep, and
improved sprint goal definitions.

49
 Experiment 16

Aim:
To prepare a product backlog capturing all technical and functional tasks required to
develop the Online Exam Registration System.

Procedure:

1. Backlog Compilation:

 Reviewed requirement document.

 Translated each module into granular backlog items.

2. Examples of PBIs:

 Build registration screen

 Connect PHP to MySQL for login

 Validate file upload types (PDF, PNG, JPG)

 Implement admin panel login with session handling

3. Priority & Effort Estimation:

 Prioritized tasks using MoSCoW.

 Assigned story points using Fibonacci scale (1, 2, 3, 5, 8).

4. Grouping & Tagging:

 Tagged tasks by module: Student | Admin | Database | UI

50
Output:
Complete backlog listed on Jira/Trello with task owners, deadlines, and dependency
tags.

Result:
The backlog facilitated smooth sprint planning and reduced idle time between
development tasks.

51
 Experiment 17

Aim:
To create a Sprint Backlog from the product backlog and outline tasks for Sprint 1
execution.
Procedure:

1. Sprint Planning Session:

 Reviewed high-priority PBIs.

 Selected login, registration, and database creation tasks for Sprint 1.

2. Task Breakdown:

 UI Design for Login Page

 Backend: PHP script for validation

 MySQL table creation and integration

3. Assignee Allocation: Each team member took responsibility for a vertical slice
(UI + logic).

4. Task Monitoring: Used Jira board with statuses: To Do, In Progress, In Review,
Done.

52
Output:
Sprint Backlog for Week 1 with 8 development tasks and 2 review/test tasks.

Result:
Having a sprint backlog increased focus, reduced multitasking, and improved
collaboration.

53
 Experiment 18

Aim:
To demonstrate the outcome of Sprint 1 and Sprint 2 including real-time working
modules of the Online Exam Registration System.
Procedure:

1. Feature Review:

 Sprint 1: User Registration, Login, Welcome Dashboard

 Sprint 2: Exam Application Form, Document Upload

2. Demonstration: Conducted internal demo in class for test users (students).

3. Feedback:

 Positive: Easy navigation, fast form validation

 Issues: UI alignment and browser compatibility (Firefox)

4. Bug Fixing: Applied quick fixes post-demo and planned enhancement tickets for
Sprint 3.

Output:
Working prototype accessed at localhost/online_exam, with completed workflows.
Result:
Demo validated the system’s design and usability. Real-time feedback reduced
development errors in upcoming sprints.

54
 Experiment 19

Aim:
To analyse project progress and task distribution using Agile project tracking tools like
Jira, Kanban, and burndown charts.

Procedure:

1. Jira Dashboard Setup: Configured Sprint Boards, Filters, and User Roles.

2. Progress Review:

 “To Do”: 25%

 “In Progress”: 40%

 “Done”: 35%

3. Team Contribution:

 Developer 1: Authentication & Forms

 Developer 2: File Upload, Backend

 Developer 3: Admin Panel, Testing

4. Burn-Down Analysis: Chart indicated that Sprint 2 finished 2 days early due to
optimized task flow.

5. Velocity Metrics: Calculated average story points completed per sprint (approx.
22).

55
Output:
Visual task tracking board and burndown charts.

Result:
Improved workload balance, sprint goal tracking, and a data-backed decision-making
process for future development stages.

56