Iteration 2 includes the pilot in a supercenter sams

This preview shows page 9 - 12 out of 14 pages.

Iteration 2 includes the pilot in a Supercenter, Sam’s Club and a UK store where data was sent from POS to a temporary repository. This data was sent in observation mode in order for the Analytics Provider to build a Fraud Opportunity Analysis (FOA) database on the solution platform. Iteration 3 Return Authorization – and the purpose of this TDD is to enable long term communications and return authorizations between Walmart/Sam’s and the Analytics Provider when a return is presented at POS. This project should benefit all global markets. 9
Running Head: KURIE KURIE 4.0 QUESTION 4 4.1 Possible risks that might occur during these canoe rides Risk Mitigation Strategy Contingency (Risk is realized) Issues with test environment which affects test execution Get the planned down times from onsite team and plan the test activities accordingly Work with Technical Lead, Development Team, PM Changes in Requirement Work with business to see that requirement is base-lined and signed-off. Work with BA, Technical Lead, Development Team, PM Inadequate test data during test execution Review the test data before testing begins and work with onsite QA team to the data required. Work with Technical Lead, Development Team, PM There is a risk that resource availability could be affected by turnover or illness. This may affect the test effort Accept, as this risk is something that is unavoidable. Plan for extending the schedule Delay in deployment schedule may delay the completion of testing. Work with the deployment team in advance to see that deployment happens as planned. Plan for extending the schedule Documentation proves to be inadequate BA/Customer will ensure that required documents are available as required by the QA Analyst Work with BA, Technical Lead, Development Team, PM Delay in clarifying BRD / DWPD and TDD Queries from QA Analyst BA/Dev Team will ensure that clarifications are available as required by the QA Analyst Work with BA, Technical Lead, Development Team, BA Test Data QA to work with Technical Work with Technical Lead, 10
Running Head: KURIE KURIE Risk Mitigation Strategy Contingency (Risk is realized) Lead and Project team to have the transaction details in TLOG before starting the execution Development Team, PM Delay in build deployment Testing would be delayed Change in schedule could impact resource availability Resource Availability Test Environment readiness and stability Testing would be delayed The testing artifacts are to be reviewed and approved by the Project team Testing would be delayed Testing Requirements related to Cash, Treasury, Accounting & Financial Services Systems These requirements will be tested by coordinating with the corresponding teams, as they are not in POS Testing Scope From a project management perspective for the data mining software project, the major risk management functions are discussed below Risk Management Planning – The data mining project can use a risk management template if

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture