B Case Study: 4 Scenario A bank is upgrading its systems to include an on-line investment service, allowing investors to trade with each other, in a mini-stock market environment. The upgrade will be carried out using Agile development (within the Scrum framework). Here, the iterations are referred to as Sprints. For each Sprint the required functionality will be defined as a set of user-stories. The user stories are typically 1-2 lines long, indicating what the business wants the system to do. These user stories will be built then tested. There will be 3 Sprints: 1) Creation of the mini-stock market trading environment. 2) Creation of additional front-end enhancements. 3) Linking to stock exchange for pricing. You are the test manager. You lead a team of 4 testers, and there are 6 developers. Your team has worked on Agile projects previously, and on average, Sprints usually last 4 weeks. At the end of all Sprints, a full end to end test is carried out. This is called the E2E test phase. You are worried that 4 weeks will not be sufficient time for the first Sprint. You have decided to conduct a Risk Management exercise before the project starts.