Sprint Backlog and Product Backlog-Team Euler - Flight Management System-Sprint2
Sprint Backlog and Product Backlog-Team Euler - Flight Management System-Sprint2
Product Impact(L-Low,
MoSCoW ID Source Priority (M/S/C/W) User Story ID User Story Name Complexity Type Comments
Backlog ID M- Medium, H-
High)
1 1 M Us:101 Customer must create his Account Very Simple L Functional
2 2 M Us:102 Customer must login into the application Complex M Functional
3 3 M Us:103 Customer can check for available flights (check all flights b/w given route) Very Simple L Technical
4 4 M Us:104 Customer can make a booking (Id genrated automatically) Very Simple L Technical
5 5 M Us:105 Customer can view the booking made Very Simple L Technical
6 6 M Us:106 Customer can cancel or modify a booking Very Simple L Technical
7 7 S Us:107 Customer should have 12-digit Unique Identification number Average L Technical
8 8 S Us:108 Customer can change their credentials (Forgot Password) Average L Technical
9 9 C Us:109 Customer can delete account Very Simple L Technical
10 10 M Us: 110 Admin can login into the application Complex H Functional
11 11 M Us: 111 Admin can add flights, schedule flights Complex L Technical
12 12 M Us: 112 Admin can view flights, schedule flights Average L Technical
13 13 M Us: 113 Admin can cancel or modify flight, schedule flights and route details Average L Technical
14 14 S Us: 114 Admin can delete the account of Customer Very Simple L Technical
15 15 S Us: 115 Admin can view and validate the Customer Very Simple L Technical
16 16 S Us: 116 Admin can update Airport Details Very Simple L Technical
17 17 W Us: 117 The application does not cover boarding pass generation and seating plans. Very Simple L Non-Functional
18 18 W Us: 118 Third party applications like email & sms integrations. Very Simple L Non-Functional
19 19 W Us: 119 Payments are not yet accepted by the application Very Simple L Non-Functional
20 20 W Us: 120 Customers are not able to do Web Check-In Very Simple L Non-Functional
21 21 W Us: 121 Customers cannot check their Flight Status Very Simple L Non-Functional
22 22 M Us: 122 Admin can add Airport Simple L Technical
23 23 M Us: 123 Authentication of the User(Valid/Invalid User) Average L Functional
24 24 M Us: 124 Admin can add/modify Customer and Passenger Average M Technical
25 25 C Us: 125 Session Timeout(if no activity) Complex M Functional
26 26 W Us: 126 Chatbot Average H Non-Functional
27 27 S Us: 127 User can Logout Average L Functional
28 28 C Us: 128 Asking for choice again on wrong selection Average L Technical
29 29 C Us: 129 Ticket options as business, economy, first class. Average L Technical
30 30 M Us: 130 Admin can schedule the flights Average L Technical
User
Product User Story
Assigned
Backlog Story Task Task Step description
to
ID ID Step
number
P:01 Us:101 1 POJO class for User Vaibhav
P:02 Us:122 1 POJO class for Airport Vaibhav
P:03 Us:104 1 Create POJO class for Booking Shaivi
P:04 Us:124 1 Create POJO class for Passenger Shaivi
P:05 Us:111 1 Create POJO for Schedule Flights Shivani
P:06 Us: 130 1 Create POJO for Schedule Shivani
P:07 Us:111 1 Create POJO for Flights details Sanchit
P:08
Make Us:101
Database and
1 apply annotation and all required validation in POJO
Shivaniclasse of Users
P:09
Make Databse
Us:130 and 1apply annotation and all required validation in POJO
Vaibhav
classe of Schedule
P:10
MakeUs:111
Databse and
1 apply annotation and all required validation in POJO
Vaibhavclasse of Flight
P:11
MakeUs:
Databse
122 and1 apply annotation and all required validation in POJO
Sanchit
classe of Airport
Make
P:12Databse
Us: 111
and apply
1 annotation and all required validation in POJOSanchit
classe of Schedule Flight
P:20 Us: 102 1 make front end for Welcome Customer Vaibhav
P:21 Us:111 1 make frond end for admin Vaibhav
P:22 Us: 113 1 make front end for update flight Shaivi
P:23 Us: 105 1 front end for Your booking Shaivi
P:24 Us: 110 1 make front end for Welcome Admin Shivani
P:25 Us:104 1 front end for booking confirmend message Shivani
P:26 Us:104 1 front end for Booking Details Sanchit
P:27 Us:113 1 front end for update flight enter details Sanchit
P:41 Us:130
Connect 1angular component of ScheduleFlight with other components
Shivani
2 Angular Componet with angular Validations Shivani
P:42 Us:111
Connect angular
1 component of Flight and Airport with other Shaivi
components
2 Angular Componet with angular Validations Shaivi
P:43 Us:101 Connect
1 angular component of User with other components
Vaibhav
2 Angular Componet with angular Validations Vaibhav
P:44 Connect
Us:104angular
1 component of Login/SignUp and Booking with Sanchit
other components
2 Angular Componet with angular Validations Sanchit
P:45 Us:101 1 Adding Login Functionality in Angular Sanchit
2 Adding Logout Functionality in Angular Sanchit
3 Adding SignUp Functionality in Angular Sanchit
will look after the completiton of front end as need to study about Spring Security. Its Front End is Completed lookin
will look after the completiton of front end as need to study about Spring Security. Its Front End is Completed lookin
will look after the completiton of front end as need to study about Spring Security. Its Front End is Completed lookin
will look after the completiton of front end as need to study about Spring Security. Its Front End is Completed lookin
will look after the completiton of front end as need to study about Spring Security. Its Front End is Completed lookin