Category: MBCA

Bug report template

Summary

Description

• Steps should be as specific as possible;

• Examples of pages, profiles, vacancies, etc. that could be used for easier bug reproducing should be provided in any suitable form (URL, ID, etc.);

• Actual and Expected results should be provided with appropriate screenshots, whenever applicable;

• During bug creation, separate critical/major/minor bugs and create a separate bug for each issue;
  You can combine the bugs if they have the same priority. But if the priority is different – please create 2 or more bugs.

• If during retesting the bug, the issues described initially are fixed, close the bug, and for all new issues that appeared after the fix and weren’t described in the bug initially create a NEW bug.

Bug template

Verification statuses templates

1. Document Revision History 

2. Approvals 

The Test Strategy is approved by the following stakeholders: 

3. Purpose

The purpose of the test strategy is to define the testing approach, the types of tests, test environments, tools to be used for testing, and the high-level details of how the test strategy will be aligned with other processes. The test strategy document is intended to be a living document and will be updated when we get more clarity on Requirements, Test environment and Build management approach, etc.

4. Project Overview

The main purpose of the MBCA project is to create and style the site based on the requirements.

Issue overview:

The Midsize Bank Coalition of America (MBCA) has a longstanding public-facing website https://midsizebanks.com/, but that website lacks a member-only portal. Thus, the 1500+ senior officers of MBCA’s 101 member banks lack a secure, confidential repository of confidential documents and videos that they can access on a self-service basis.  Instead, they send hundreds of emails each week to the MBCA’s Executive Director asking questions and requesting documents or links to video recordings of MBCA meetings – these questions and requests could be more efficiently handled on a largely self-service, member-only portal.

Scope of work:

Redesign of the previously developed by us member-only portal (Initial requirements). The main point of it is to make the design more dynamic and desired for partners (not members-only)- additional functionality, which should be developed on the portal - it’s the ability to register and post content for Partners + Consultant Law firms.
In the future - make additional traffic to sell advertisements on the portal.

5. Tools for QA planning and testing purposes

Confluence will be used for storing all project-related information.

JIRA will be used as a bug tracking system, and for planning, tracking, and analyzing project activities and tasks.

Google docs will be used for creating different supporting documentation (for ex. checklist).

BrowserStack will be used for cross-browser/device testing.

6. Requirements references for MBCA

7. Test Environment

8. Testing Types

The following testing types will be executed during the MBCA project:

8.1. Functional testing

The functional testing will be executed to evaluate the compliance of a system or component or third party with specified functional requirements and corresponding predicted results. Functional testing is performed for each planned feature and is guided by approved client requirements.

8.2. Regression testing

The regression testing will be performed to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not caused any problems to previous versions of the software.

Regression testing is usually performed when all the components are tested based on created high-priority test cases; no critical and blocking bugs are open that were found during the component testing.

The regression testing is usually done after the code freeze and is always done before the deployment to production.

8.3. Design (Responsive) testing

The design testing will be performed for all testing levels to assure that it meets the design-related specifications.

Responsive testing on tablet and mobile devices is focused on business logic for the project in the scope of features.

Design testing will be based on the approved scope of the UI designs - <link to the design>

Design testing will NOT be based on the pixel-to-pixel verification, but generally look only (elements positions, colors).

Responsive testing on other intermediate resolution values is OOS.

8.4. Cross-browser compatibility testing

The cross-browser compatibility testing will be performed to check the ability of the solution to interact with the agreed list of browsers.

Cross-browser testing will be covered manually on Test Environment only on browsers defined for cross-browser testing.

9. Planned testing types on the test environments (browsers, devices, email clients)

9.1. Browsers and Devices Scope

Browsers and Devices Scope

9.2. Email Clients

10. Approach for Process Flow

10.1 Work with Bugs

Bug creation tips:

• In case the found bug is related to a certain task - it should be linked to the task and Active sprint.

• In case QA found Blocker/Critical bug during the testing ticket which is not related to the task - it should be added to the Active sprint.

• In case QA found a Major/Minor/Trivial bug during the testing ticket which is not related to the task - it should be reported and added to the Active sprint.

Bug verification tips:

• In case the ticket is passed - QA should add a detailed comment with a screenshot (video if needed) and move it to the “QA Approved” status.

• In case the ticket is failed - QA should add a detailed comment with a screenshot (video if needed) and the ticket should have the “To Do“ status.

10.2 Regression testing procedure

Should be performed after each new functionality implementation and after related bug fixing

11. Checklists and Test Cases creation approach

The high-level checklists and test cases (if needed) for component testing will be created in the internal checklists for component and regression testing.

Approvals 

Legend:

APPROVED DECLINED REVIEW

Browsers and Devices Scope

Email Clients

Meeting w/ Kyler, Brant, Jordan, Chase – 13.06.22

Design comments:
4 Tabs: Connect, Engage, Learn, Partner

Connect
Dropdown list for each of the groups – CRO, CRI, …
User could connect with each other inside the groups
LinkedIn, Email, personal information about the user should be available there
Bank profiles – list of members (map)
Connect board (Messaging board) by group

Engage
Details for each of those groups: Impersonal Programs, Past Programs, Zoom recordings, Surveys, BankTank, Background page for a Partnership with a group called FinMay,..
? To pick and post posts from the LinkedIn profile – post to be available in the Page (need to be checked)

Learn
Inside ecosystem where consultant law firms & partners – create there a account, post additional stuff – Blog

Partner
Highlight fin techs, or people/partners who want to pay & be highlighted on the site, recurring revenue model
Blog, make posts

Dashboard
New posts from all 4 tabs should be highlighted there
Dynamic picture or video
Rotating banner with recent posts, updates

Basic style changes:
Color – Change the color scheme to Royal Blue

+ Login – create the account for consultants

Meeting w/ Kyler, Brant, Jordan, Chase – 22.07.22 (after design updates)

Design comments https://www.figma.com/file/ZlnITGjKxDzFnHoPQbnU65/mbca?node-id=1401%3A1257 :

• Bank profiles fields – Name(hyperlink), Location, Website

• Engage – Schedule of MBCA Programs (examples –
  https://www.uschamber.com/events and https://curinos.com/insights/)
  Engage tabs – Upcoming Programs, Past Programs, Surveys, Zoom Recordings, Presentations

• Combine Learn + Partner – same purpose (content posting from Partners, Consultants, highlighting Partners)

Meeting w/ Kyler, Brant, Jordan – 10.08.22

Dashboard

Hero Banner (make it shorter on the design)
Latest Insights* (Blog – add header)
Upcoming Engagements** (needed Design)

*Blog – is it possible to highlight automatically posts from specific Partner? (for example – this week are for Partner1 posts & we automatically hightlight all of posts from this author on the Dashboard page + ability to mix partners one week – Partner1+Partner2)

**Upcoming Events – automatically updated each week (parameter could be changed) from the Engagements page

+ Add automatic rotate for Blog & Events

Connect

• Users – Make sure that User contact info is only showing for certain assigned group

• Message board – add Subject field for messages

Engage

• Upcoming Engagements (design needed)

• Surveys (Check SurveyMonkey API)

• Materials
  *Hide all other sub-tabs from menu

Learn & Partners

• Add ability so search by author / keyword

• Make another type of posts – Article + Announcement*
  *Announcement – Name, Description, Image (not obligatory), HyperLink to another page

Overview

The Midsize Bank Coalition of America (MBCA) has a longstanding public facing website https://midsizebanks.com/   but that website lacks a member only portal.   Thus, the 1500+ senior officers of MBCA’s 101 member banks lack a secure, confidential repository of confidential documents and videos that they can access on a self-service basis.  Instead, they send hundreds of emails each week to the MBCA’s Executive Director asking questions and requesting documents or links to video recordings of MBCA meetings – these questions and requests could be more efficiently handled on a largely self-service, member-only portal, that satisfies the following criteria:

Criteria:

• Initial enrollment (регистрация) (manual, but should require minimal MBCA administration time).  

  • Applicants for member only access will not have automatic enrollment.  Instead, applicants should reach a page linked to the public website that alternatively invites a login for already registered member-only site users or an application for credentials permitting member-only access.   Persons who have not previously set up a user name/password should be able to complete a brief survey (e.g., name, bank, bank title/role, email address, phone number, business address); the completed survey should enter a queue pending authorization decisions by the MBCA’s webmaster.  Usernames should be the applicant’s business email address (almost all will be their employer-bank email addresses); this will aid in alerting the webmaster to unauthorized user attempts to obtain credentials.   The MBCA’s webmaster would set up users with a default password requiring the user to re-set his/her password at the beginning of the first login experience.

  • Users should select and maintain their own passwords, and to re-set/recover forgotten passwords.  +

  • Initial password setting/password reset authentication should require a user to access his/her business email at a member bank domain or other whitelisted domain to obtain a passcode to be used for authentication (multi-factorial authentication).  The MBCA webmaster should have the administrative power to authorize non-whitelisted user email addresses (for experts, advisors and other nonbank authorized users). (генерить ссылку для сброса пароля.

  • Users should not be able to change their user ids – this change should require webmaster intervention.  (This helps prevent individuals who leave the employ of their member banks from changing user ids – for example:  we don’t want jsmith@abcbank.com able to change his user name to jsmith@gmail.com).

  • The system should be able to generate periodic reporting of enrollments and logins and deliver same to the MBCA webmaster/to the MBCA executive director.  Ideally, this reporting feature would also generate activity reports sorted by member bank that the MBCA Webmaster can send to member bank administrators (one or two individuals at each bank with oversight over who should have access to resource group materials on MBCA website

• Internal access restrictions (Website should restrict authorized users within the website). 

  • Once a user has credentials he or she should be able to see a non-public home page, with several “all hands” tabs and resource materials that are available to all users.   However, we need to be able to restrict access to specific committee and resource groups to users authorized to view these committee or resource group materials.   Perhaps this could be done on a top down basis (CEOs serving on MBCA’s executive committee see all materials;  C-suite members (however defined) can see all groups except executive committee;  Some more junior level resource group members should be limited to their own group materials (and, of course, the nonpublic home page and all hands pages/tabs discussed above).   The MBCA webmaster would manually assign users to access groups after reviewing each user’s survey requesting access.   The website programming should permit the webmaster to grant access (in addition to the nonpublic home page and all hands tabs) as follows:

    • The user IDs for the Executive Director and the approximately 15 CEO members of Executive Committee (and their administrative assistants, when requested) would have broad access to all member only resources.  The Executive Director could authorize other users to have this EC level access if desired.

    • The Webmaster would use the onboarding survey discussed above to give other user IDs access authority to one or more groups or Resource Groups (e.g., C-Suite, CRO group, BSA officer).   The MBCA Webmaster should have the power to give specific users access to multiple groups…for example, a typical Chief Risk Officer would have access to the C-Suite group as well as numbers 4, 8, 10, 11, 12, 13 and 15 (in many banks these functions report up to the CRO).

Here are the MBCA’s Resource Groups at present:

• Chief Executive Officers

• Chief Financial Officers

• CxOs (Presidents, Chief Operating / Operations / Administrative Officers)

• Chief Risk Officers

• General Counsels

• Chief Information Officers

• Chief Human Resource Officers

• Chief Credit Officers

• Chief Internal Audit Executives

• BSA Officers

• Chief Information Security Officers

• ERM/ORM Leaders

• Chief Compliance Officers

• Chief Communicators (Head of Communications / Marketing/ PR)

• Data Governance Leaders

• Many of the foregoing Resource Group members (primarily members of 1,2,3,4,5, 7 and 8) are also members of the C-Suite group.  The Executive Committee (the governing board of the MBCA), plus 1-15 above, should have its own access controlled pages to host the materials discussed below.  

• Given the groups listed above, and the fact the MBCA has about 100 member banks, MBCA estimates 1500-2000 users (including administrative assistants etc) in the near term. 

• Content to be posted on the members-only website.

  • We contemplate a variety of materials to be posted on the nonpublic home page (directly or via tabs or links) that greets member bank executives when they log in to the members only website.   These materials will be available to all users, regardless of their status or resource group membership.   The home page should also have links to the Executive Committee and to the 15 resource groups listed above.

  • Surveys.  These are subject matter surveys that MBCA regularly conducts using products such as Survey Monkey.   Based on longstanding practices, MBCA requires a member bank to answer a survey as a prerequisite for having access to survey results.   This is a highly manual process.  For purposes of website design, the website should be able to host password protected survey results done by Resource Groups, not conduct the taking of the survey.  The M-BCA webmaster would also post the survey questions on the applicable Resource Group’s page and on the home page, as non-passworded, unprotected text .   

  • FAQs – To be developed apart from the website development.   The website will host/display these FAQs.   MBCA will build these (and refine them over time) based on the most common questions fielded by the ED about the MBCA.  Would also include subject matter FAQs (for example, links to useful documents on non-MBCA websites.  Most FAQs would be posted on the home page available to all users – but resource group pages should include tabs for specific FAQs.  The MBCA webmaster will upload and maintain these.

  • Presentation decks.  MBCA Webmaster uploads to the home page (when appropriate) and for the resource groups.

  • Member Bank officer directories…perhaps collected/updated via survey…but in this case survey results would not be password protected.  This data will be collected and uploaded by the MBCA webmaster to the home page.  The website will simply host directories prepared apart from the website.

  • Member bank profile…spreadsheet sortable by regulator, size, office/branch locations, etc.  Again, collected/updated via survey but not password protected.  Links to primary website/investor website, etc.  The MBCA webmaster will collect and upload this data to the home page.

  • Zoom links to recorded C-Suite and resource group programs.  These will be links to zoom sessions recorded/hosted elsewhere.

  • MBCA history/governing rules.  Annual report.

  • Advisors listing, with links to MBCA’s primary law, consulting, accounting firms  (helps induce these experts to provide pro-bono help to MBCA)

  • Congressional/regulatory/administration contacts – matrix connecting Member Bank footprint/personal relationships to government officials.  MBCA webmaster to upload this workproduct when it is created.

  • Integrated calendar of past/future events.  MBCA webmaster to upload calendar to home page tab.

  • Resource group message boards – with a subscription/signup feature at the option of resource group members.

• The member-only portal should have the following features:

  • Subgroup level word search features (alternatively, if user permission can control span of search this would be better…for example, a C-Suite level user would be able to see search results anywhere on the portal (except executive committee materials), but a BSA subgroup user would see only BSA page search results.

  • Regular backup and business continuity protections.

  • The member portal could reside on a separate website than the existing MBCA website, accessible via a link on the existing MBCA website. 

  • General comment:  Many of the active users on MBCA’s member-only website will be highly knowledgeable about cybersecurity risks, including some of our member bank  CEOs, most of the CROs and all of the CIOs and CISOs.    Even though this website will not host GLBA or other highly confidential information….it should be designed as though it did.   For most of our 100 member banks’ cybersecurity experts, this website will be their first introduction both to MBCA’s attention to good cybersecurity practices as well as to Shatterproof’s expertise in this space.  This is tough audience.

🤝Team

 Description

Issue overview:

The Midsize Bank Coalition of America (MBCA) has a longstanding public facing website https://midsizebanks.com/, but that website lacks a member only portal. Thus, the 1500+ senior officers of MBCA’s 101 member banks lack a secure, confidential repository of confidential documents and videos that they can access on a self-service basis.  Instead, they send hundreds of emails each week to the MBCA’s Executive Director asking questions and requesting documents or links to video recordings of MBCA meetings – these questions and requests could be more efficiently handled on a largely self-service, member-only portal.

Scope of work:

Redesign of the previously developed by us member-only portal (Initial requirements). Main point of it to make design more dynamic and desired for partners (not members-only)- additional functionality, which should be on the developed on the portal – it’s ability to register and posting content for Partners + Consultant Law firms.
In the future – make additional traffic to sell advertisements on the portal.

References:

• https://curinos.com/insights/

🔗Accesses & Useful links

 Milestones

(No requirements/deadlines from the client’s side, just initial plans)

 Requirements / functionality

 Open Questions

🆘 Change Requests

 Out of Scope

---