100%(1)1 out of 1 people found this document helpful
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 KURIE4.0 QUESTION 44.1 Possible risks that might occur during these canoe ridesRiskMitigation StrategyContingency (Risk is realized)Issues with test environment which affects test executionGet the planned down times from onsite team and plan thetest activities accordinglyWork with Technical Lead, Development Team, PMChanges in RequirementWork with business to see that requirement is base-lined and signed-off.Work with BA, Technical Lead, Development Team, PMInadequate test data during test executionReview the test data before testing begins and work with onsite QA team to the data required.Work with Technical Lead, Development Team, PMThere is a risk that resource availability could be affected by turnover or illness. Thismay affect the test effortAccept, as this risk is something that is unavoidable.Plan for extending the scheduleDelay 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 scheduleDocumentation proves to be inadequateBA/Customer will ensure that required documents are available as required by the QA AnalystWork with BA, Technical Lead, Development Team, PMDelay in clarifying BRD/ DWPD and TDD Queries from QA AnalystBA/Dev Team will ensure that clarifications are available as required by the QA AnalystWork with BA, Technical Lead, Development Team, BATest DataQA to work with Technical Work with Technical Lead, 10
Running Head: KURIE KURIERiskMitigation StrategyContingency (Risk is realized)Lead and Project team to have the transaction details inTLOG before starting the executionDevelopment Team, PMDelay in build deploymentTesting would be delayedChange in schedule could impact resourceavailabilityResource AvailabilityTest Environment readiness and stabilityTesting would be delayedThe testing artifacts are to be reviewed andapproved by the Project team Testing would be delayedTesting Requirements related to Cash,Treasury, Accounting & Financial ServicesSystemsThese requirements will be tested bycoordinating with the corresponding teams,as they are not in POS Testing ScopeFrom a project management perspective for the data mining software project, the major risk management functions are discussed belowRisk Management Planning– The data mining project can use a risk management template if