Product Tags and Components

The product team uses components and product tags within Jira to categorize Initiatives. These help to define which domains, teams, milestones, and other groupings are needed to organize work across the all teams. These are logical collections and in some cases there will be overlap.

Components

Components are used to define the feature areas, domains, availability options (bank/cu/cores) and teams. Examples: Business, Credit Union, Bank, Prism, People, Bill pay, etc.

SOP:

• The product team adds components for feature areas, domains, and availability options. If you need a new component, or a change in components please let a product manager know.
• Any team can add their team component. If your team doesn’t have a component, it can be added.
• All Initiatives should have the following components:
  • One or both Bank/Credit Union components (we’re moving toward core-specific components soon)
  • Product domains
  • Teams (will be updated as Initiatives progress through the process stages)

Conventions:

• Components should be generally understandable across the organization.
• Components should be reusable with an indefinite time frame.

Product Tags

Product tags are used to define groups of initiatives related to: milestones, roadmap flags, delivery expectations, product specific classifications, etc.

SOP:

• The product team adds tags for appropriate groupings of features. If you need changes to a product tag please let a product manager know.
• Any milestone, delivery, or release related product tags must have appropriate components or other product tags to differentiate from unrelated efforts that may have the same tags.

Conventions:

• Milestone related tags are product driven feature groupings. They should be labeled as: Milestone# (# representing a number). Stand alone projects would not have milestones, only efforts related to larger themes/goals.
• Delivery target related tags are date driven feature groupings. They should be labeled as _TargetMonYr _(Mon = 3 letter month, Yr = 2 number year, eg TargetJul23). These groupings can change as we understand the feasibility of delivering projects within the target timeframe.
• Release related targets are product driven groupings for communicated feature sets. Beta, MVP, GA, etc.
• Product tags are additive, meaning a feature can fall into multiple groupings. An example for Banno Business is Beta features will also be NearNT features
• Not all product tags are used for cross-functional organization, some exist purely for the benefit of product managers organizing work. If you don’t understand a product tag you can most likely ignore it.
• Roadmap related tags are:
  • CustBeta = customer beta required
  • AtRisk = Timeline is at risk
  • IdeaLab = Some amount of scope comes from IdeaLab
  • Dependency = Project has an external dependency

Current shared efforts

Definitions

Bank Business Beta

Set of projects we intend to be beta’d as part of Banno Business.

Bank Business MVP

Set of projects we are considering is generally available (GA), so operations can roll out and implement Banno Business once this set is complete.

Credit Union Business Milestone 1

Set of projects required for Freedom First to be able to do any measure of testing within Banno Business. This is not a releasable product.

Credit Union Business Beta

Set of projects required for a credit union to deliver MVP business functionality to their accountholders. This feature set could be enabled for beta testing CUs but may not be able to be rolled out en masse.

Bank Business generally available

Set of projects considered generally available. Our sales and operations teams are enabled to successfully sell and implement this feature set en masse. We have communicated this as an June 2023 release, so the features within are constrained to that.

Credit Union Business generally available

Set of projects considered generally available. Our sales and operations teams are enabled to successfully sell and implement this feature set en masse.

Bank Business Near NT Parity

Set of projects required to declare we have achieved near parity with NetTeller. This is not full feature parity.