Skip to end of banner
Go to start of banner

Confluence Roadmap and Initiatives

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

In Progress

SummaryArea of ImpactGoalLeadNext Step(s)
Space cleanup: Apps Upgrade and AppWorxIT Applications

There was originally a Banner upgrade space (within the Apps Upgrade space) that was inconsistently used for Banner upgrades. It is being expanded to include all Application upgrades. A basic framework for the space is being implemented and upgrade templates defined. These are being piloted now. 

 

The AppWorx section of the Application space is being inventoried and assessed for duplication and redundancy. We will be designing a new taxonomy for the section and presenting it to ERP Support since they are the main users of the AppWorx section besides the Operations team.

  1. Finalize framework/templates/taxonomy

  2. Add labels to previous Banner upgrade documents

  3. Get feedback from Support team

  4. Move pages into new structure

Taxonomy and content cleanup/organization (Confluence 2.0)IT ApplicationsDevelop standardized templates and structures to hold IT Applications documentation. Presently, several versions and iterations of "Application Page" templates are in use - this effort will ultimately consolidate those into a single template with all relevant information (as reviewed and approved by Applications leadership) and simplify the structure of the Applications Confluence Spaces and Pages. In other words, the number of Apps Spaces will likely decrease.
  1. Revive "Training Matrix" page: /wiki/spaces/IUA/pages/45354395.
  2. Re-organize Applications Division Home Page with links to Standards and SOP landing pages: In progress: needs more work to sort and locate new homes for existing content.
  3. Finalize new structures and templates
  4. Begin migration of existing content into new structure and demise old content as applicable


Pipeline

SummaryArea of ImpactGoalLead
Procure and implement the Midori archiving pluginIT ApplicationsKeep IT Applications Confluence documentation up-to-date and accurate through automated expiry and notification of pages that become old or unused.TBD
Develop and implement a process for plugin evaluation, procurement and implementationAllCreate an implement a process to facilitate the identification of need, evaluation, procurement, and installation of plugins that augment OOB Confluence functionality. Current pain points are related to Search and Label Management - it is believed that these can be addressed with 3rd party plugins.TBD


Completed

SummaryArea of ImpactGoalLeadOutcome
Review an archiving addon to help maintain pagesIT ApplicationsKeep Confluence documentation up-to-date and accurate through automated expiry and notification of pages that become old or unused.
12/2017: The Midori archiving plugin was identified as a viable solution. Procurement of the plugin is on hold until Confluence is upgraded and a new architecture is finalized.
Review options for hosting ConfluenceAllSummarize the costs of three options for upgrading and hosting Confluence. Organize the three options into a matrix that includes installation costs, monthly labor costs, monthly hosing costs vs annual hosting costs, and benefits and risks.
1/2018: Leadership opted to continue with on premise installation, rearchitected to facilitate enhanced security and high availability.
Upgrade Confluence to latest versionAllEnsure continued vendor support and introduce new features for UNM's Confluence instance.

2/2018: Upgrade completed successfully

Re-architect and operationalize ConfluenceAllRe-deploy Confluence in a more secure, sustainable manner. Develop and implement formal support processes, SLAs, and other key service elements.Jim Dryden11/04/18 completed
  • No labels