this is the proublem solving question they gave us the scenario and questions on that please help me

A computerised hotel reservation system is described below. The system shall treat customer requests as automatically as possible. A request is made over the Internet by either an existing customer or a new prospect/customer. A customer is identified by his identity (eg name, address, email address or telephone number) and shall be captured by the system for him/her. His/her request is set in general terms: the requested hotel category, the number of people, budget the number of rooms and the period required, ete. The managers would like to keep customers happy and therefore request you to develop the system that can handle pending requests automatically that is a request that cannot be satisfied immediately shall be put on a waiting list and be attended to as soon as possible. When a pending request could be satisfied, a corresponding reservation is created and the customer be notified if a customer cancels his/her reservation less than 8 days prior to the starting date of his/her reservation he/she will be charged 50% of the full reservation price The system is expected to have a database holding the necessary information about all the he S The system is expected to have a database holding the necessary information about all the hotels and customers, and to have the functions for creating new records and editing existing records. Unfortunately, the hotel managers who have very little knowledge about computer systems rely heavily on you to specify the systems in a more detailed manner. The development team therefore decided to adopt the Agile methodology and the Scrum process for developing this hotel reservation system, The product backlog included the following items (but not limited to): A customer new or existing) making a request to reserve a hotel room the system to capture his/her details system be able to handle a pending request system be able to charge customers correctly and securely ete, etc The team working on the above system just has its retrospective meeting on the sprint which is for the pending request part of the system and the results of the meeting are as follows: What went well what didn't go well TESUS UT UTM are as TOUWS. What went well? What didn't go well? 1. This sprint was accepted by the customer. eventually. 1. The scrum meeting usually takes about 30 mins longer than what it should 2. Working with the customers did not seem to have a major problem 2. We spent a lot of time in making a decision on the design for the pending request process 3. The team seemed to work reasonably well together 3. The Burndown rate (productivity rate was slower than what was planned. 4. Changing the database design due to the customer's request was done quickly 4. The delivery of the sprint was delayed by One week Study the above case study and for each of the issues/problems raised in the What didn't go we column you are required to suggest What were the boss le causes for the Study the above case study; and for each of the issues/problems raised in the "What didn't go well?" column, you are required to suggest: 1) What was (were) the possible cause(s) for the problem?; and ii) A solution to this problem. The marking scheme for each of these questions is as follows: 1). 7-8 for correct answer with evidence of effort; 11). 5-6 for correct answer (with not much evidence of effort) or evidence of effort (but answer not quite correct) ii). 3-4 for falling short of (i by a fair bit iv) 2 for falling short of (in by a distance ). 1 for falling short of (i) by a big distance vi) zero for no evidence of or the answers simply copied from the Internet or others LA TROBE UNIVERSITY La Trobe Home Library Home My LMS Subjects / 2020-CSE3SOM(BU-1)/CSE5SDM(BU-1) / 2020Problem Solving / 2020283 Question 1 The scrum meeting usually takes about 30 mins longer than what it should. Not yet answered Marked out of 8.00 i 6.B1 I = % SEUS X X + 1. p Flag question We spent a lot of time in making a decision on the design for the pending request process Question 2 Not answered A computerised hotel reservation system is described below. The system shall treat customer requests as automatically as possible. A request is made over the Internet by either an existing customer or a new prospect/customer. A customer is identified by his identity (eg name, address, email address or telephone number) and shall be captured by the system for him/her. His/her request is set in general terms: the requested hotel category, the number of people, budget the number of rooms and the period required, ete. The managers would like to keep customers happy and therefore request you to develop the system that can handle pending requests automatically that is a request that cannot be satisfied immediately shall be put on a waiting list and be attended to as soon as possible. When a pending request could be satisfied, a corresponding reservation is created and the customer be notified if a customer cancels his/her reservation less than 8 days prior to the starting date of his/her reservation he/she will be charged 50% of the full reservation price The system is expected to have a database holding the necessary information about all the he S The system is expected to have a database holding the necessary information about all the hotels and customers, and to have the functions for creating new records and editing existing records. Unfortunately, the hotel managers who have very little knowledge about computer systems rely heavily on you to specify the systems in a more detailed manner. The development team therefore decided to adopt the Agile methodology and the Scrum process for developing this hotel reservation system, The product backlog included the following items (but not limited to): A customer new or existing) making a request to reserve a hotel room the system to capture his/her details system be able to handle a pending request system be able to charge customers correctly and securely ete, etc The team working on the above system just has its retrospective meeting on the sprint which is for the pending request part of the system and the results of the meeting are as follows: What went well what didn't go well TESUS UT UTM are as TOUWS. What went well? What didn't go well? 1. This sprint was accepted by the customer. eventually. 1. The scrum meeting usually takes about 30 mins longer than what it should 2. Working with the customers did not seem to have a major problem 2. We spent a lot of time in making a decision on the design for the pending request process 3. The team seemed to work reasonably well together 3. The Burndown rate (productivity rate was slower than what was planned. 4. Changing the database design due to the customer's request was done quickly 4. The delivery of the sprint was delayed by One week Study the above case study and for each of the issues/problems raised in the What didn't go we column you are required to suggest What were the boss le causes for the Study the above case study; and for each of the issues/problems raised in the "What didn't go well?" column, you are required to suggest: 1) What was (were) the possible cause(s) for the problem?; and ii) A solution to this problem. The marking scheme for each of these questions is as follows: 1). 7-8 for correct answer with evidence of effort; 11). 5-6 for correct answer (with not much evidence of effort) or evidence of effort (but answer not quite correct) ii). 3-4 for falling short of (i by a fair bit iv) 2 for falling short of (in by a distance ). 1 for falling short of (i) by a big distance vi) zero for no evidence of or the answers simply copied from the Internet or others LA TROBE UNIVERSITY La Trobe Home Library Home My LMS Subjects / 2020-CSE3SOM(BU-1)/CSE5SDM(BU-1) / 2020Problem Solving / 2020283 Question 1 The scrum meeting usually takes about 30 mins longer than what it should. Not yet answered Marked out of 8.00 i 6.B1 I = % SEUS X X + 1. p Flag question We spent a lot of time in making a decision on the design for the pending request process Question 2 Not answered