Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
B
Business Systems Analysts
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.com
    • Business Technology
    • Enterprise Applications
  • Business Systems Analysts
  • Business Systems Analysts
  • Issues
  • #33

Closed
Open
Opened Nov 06, 2020 by Barbara Roncato@broncatoOwner1 of 4 tasks completed1/4 tasks

Enterprise Apps: future Subgroup and Projects structure

Purpose of this issue

In this issue, Project Leads will document the future structure of the Group and Projects of the Enterprise Apps Subgroup.

Overview of the current Enterprise Apps Subgroups and Projects structure

Current Enterprise Apps Subgroup here.

Enterprise Apps Subgroup

graph TD
  A[Enterprise Apps] --> B[BT Integrations]
  A --> C[Finance Systems]
  A --> D[Business Systems Analysts]
  A --> E[Enterprise Applications Operations]
  E --> F(Intake)
  E --> G(Meta)
  E --> H(Incident Management)

Legend

graph TD
    A[Group]
    B(Project)

Notes

  • There will be 5 subgroup(s) within the Enterprise Apps Subgroup
  • There will be xx project(s) within the Enterprise Apps Subgroup

Future Enterprise Apps Subgroups & Projects

  1. BT Integrations subgroup (more details here)
  2. Finance Systems subgroup (more details here)
  3. Business Systems Analysts subgroup (more details here)
  4. Enterprise Applications Operations subgroup:
    • General items that overlap all Enterprise Applications teams such as:
      • Intake: For issue detection and logging, categorization, investigation and diagnosis.
      • Meta: Milestone planning and process refinement for all Enterprise Apps teams.
      • Incident Management: For incident registration & categorization, prioritization, investigation and diagnosis, resolution, and finally closure.
      • CHANGE MANAGEMENT?

Overview of the current BT Integrations Subgroups and Projects structure

Current BT Integrations Subgroup here.

BT Integrations Subgroup

TBD

Legend

graph TD
    A[Group]
    B(Project)

Notes

  • There will be xx subgroup(s) within the BT Integrations Subgroup
  • There will be xx project(s) within the BT Integrations Subgroup

Overview of the current FinanceOps Subgroups and Projects structure

Current BT Integrations Subgroup here.

Finance Systems Subgroup

graph LR
  A[Finance Systems] --> B(Documentation)

Legend

graph TD
    A[Group]
    B(Project)

Notes

  • There will be xx project(s) within the Finance Systems Subgroup

Finance Systems Projects

  1. Documentation
    • Project to track all documentation that the Finance System Admins are working on such as the How to create custom fields in Netsuite.

Overview of the current Business Systems Analysts Subgroups and Projects structure

Current Business Systems Analysts Subgroup here.

Business Systems Analysts Subgroup

graph LR
  A[Business Systems Analysts] --> B(Documentation)
  A --> C(Projects)

Legend

graph TD
    A[Group]
    B(Project)

Notes

  • There will be 2 project within the Business Systems Analysts Subgroup

Business Systems Analysts Projects

  1. Documentation
    • Project to track all documentation that the BSAs are working on such as the Systems Process Flows.
  2. Projects
    • Project to track all implementation or projects that the BSAs are leading.

NEXT STEPS

  • @broncato check this idea with @ccnelson: Should we have a subgroup in EntApps called "Service operations" to house the projects Intake, Meta and Incident Management?
  • @broncato check this idea with @ccnelson: Should we have a project in the BSA subgroup for Documentation?
  • @broncato check this idea with @ccnelson: Should we have a project in the BSA subgroup for Projects/Implementations?
  • @broncato to brainstorm projects for Finance Systems with @ccnelson.
Edited Nov 24, 2020 by Barbara Roncato
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Dec 18, 2020
Due date
Dec 18, 2020
Reference: gitlab-com/business-ops/enterprise-apps/bsa/business-systems-analysts#33