Design Thinking

Identify some of the assumptions made about the success of remote deposit capture functionality.  Assess the risk of each assumption affecting our product by classifying the assumptions into  following four categories:

High impact if wrong, High Probability of it being wrong

High impact if wrong, Low Probability of it being wrong

Low impact if wrong, High Probability of it being wrong

Low impact if wrong, Low Probability of it being wrong

For each assumption, provide the reason why you categorized the assumption into the particular  category.

Current development team does not have experience to develop mobile app.( High impact if  wrong, High Probability of it being wrong )

Reason : A secure service is very important for bank application. If application security fails, it will  result in negative customer experiences that will be quickly shared if it is not secure. The negative  impact on the Bank will be high.

May customer does not have internet banking so they may not use app. (High impact if wrong,  Low Probability of it being wrong )

Reason : If customer doesn't use the mobile application, all the efforts and investment will be lost,  but still bank can do some more marketing to make sure people do use their app.

Quality of the mobile application image scan. ( Low impact if wrong, High Probability of it being  wrong )

Reason : If customer not able to scan the cheque with quality its required from his down device.

Customer may not want to invest in pre-test scanner.

Reason : Customer may not want to invest in purchasing pretest scanner or does impact the  project.

PROMPT For any three assumptions you identified, please list the MVP Tests or Minimum Viable  Experiments you can conduct to validate the assumptions? Please categorize your MVP Tests  according to the following categories. It is okay to have 1 or 2 categories with no tests.

High Cost, High Quality Data (tests that will be costly to conduct, but will result in high quality  data)

High Cost, Low Quality Data (tests that will be costly to conduct and will result in low quality data)

Low Cost, High Quality Data (tests that will be inexpensive to conduct, but will result in high  quality data)

Low Cost, Low Quality Data (tests that will be inexpensive to conduct and will result in low quality  data)

MVP Test

Assumption: Developer should be given training about mobile app security & development.

Test : Test conducted after completion of training program (High cost/High quality)

Assumption: The service reliability and availability will be high.Test : Prototype various  combinations of functionality stress- and load-test application (High cost/High quality)

Prepare small prototype of scanning check in bank branches, letter decide to move on  development of mobile app application depend on the response.

Test : Result of use of prototype.

