Quality Testing

Goal: Merge Member Accounts

Issue: Migrate from an “account centric” to a “member centric” system.

The prior system at the Credit Union was “account centric” versus the new system being “member centric.” Prior to the core system conversion, every new account created a new entity number, which made it a challenge to identify an individual. Each individual account that was opened created a separate entity or individual. For example, if one person has seven accounts under their name, each of the seven accounts is a separate entity or individual. Additionally, the prior system had limitations where a member profile count not be fully created for joint account holders. This meant that date of birth, social security number, email address, home address, etc. count not be maintained for joint account holders.

The new core system is member centric and to use the system as designed and use all functionalities, it is necessary to merge the separate entities of the individual account holder. This was not done as part of the conversion, given the high risk to match entities without error. Now that the core systems conversion has been completed, a project plan must be designed and implemented to merge these entities. Things that need to be considered are:

• The primary account holder’s entity is used to communicate with online banking. When selecting the surviving entity, who else has access to this online account must be considered. Prior to the systems conversion, joint account holders shared one set of credentials for online banking.
• The process must consider the gathering of information to obtain complete profiles for all account holders; it must consider consistent information and data for all accounts (name, date of birth, social security number, address, etc.); it must consider that a high percentage of members do not have a social security number as they have a Visa or reside overseas.
• Another consideration is that the selection of the surviving entity will have an effect on the online banking account and all the features, payments, etc. that are set up for each account.

The actual merge process is to be completed by the Member Services Officer and the member, so that they can provide input into the surviving entity.

With this in mind:

• 1)Would the Agile method be an appropriate way to manage this project? Why or why not?
• 2)Provide a few user stories for this project.
• 3)Describe what sprints/iterations you would identify.
• 4)How can a daily stand up benefit this project? How would it make it different from bi-monthly meetings? What are the benefits?
• 5)What blockers do you think might get in the team members way?
• 6)How would you integrate quality testing throughout the process?
• 7)What criteria or data do you think should be used to do a secure entity merge? What criteria, ideas or data do you think should be used to make a secure entity merge? (i.e.: name, social security number, date of birth, etc.)
• 8)Given the above summary/issue – what approach would you implement for this project?