Agile: Agile is an iterative, results-driven methodology for building software. Silverchair practices SAFe Agile, though there are numerous variations on Agile methodology.
Alerts: Also known as “email alerts,” this feature allows end-users or institutions to receive email notification about new content, expiring continuing education, subscription actions they need to take, or personalization features.
Architect: Architect is a technical role at Silverchair. Architects evaluate, assess and define a unified approach for application architecture for Silverchair’s product and client solutions, and work with development and delivery teams to ensure that technical nonfunctional requirements (such as security, performance, scalability, and reliability) are addressed in addition to functional business requirements.
Autodeploy: This category of platform release updates go into effect automatically and require no action on the client’s part. This does not mean that the functionality defaults to enabled necessarily, but it means there’s no additional action or cost to add the functionality to their site.
Azure: Microsoft Azure is a cloud computing service for building, testing, deploying, and managing applications and services through Microsoft-managed data centers. Silverchair sites and services are hosted in Azure.
BA: Business Analyst. Elicits, gathers, and defines requirements in order to deliver products that meet stakeholder needs; translates client requirements to the developers and the SQAs to ensure we build the right thing and can test the quality of the work before it goes out the door.
BAU: Business As Usual. Refers to the client workstream for features which already exist in production and which are continually being enhanced.
BITS: Book Interchange Tag Suite. An extension of the JATS XML standard, which gives elements and attributes for exchanging book content. SCBITS is the custom-to-Silverchair XML specification based on BITS.
Cache / Cached: A cache refers to information that is copied then by a system or service to ensure it may be retrieved quickly upon future requests. When information is cached, it will not refresh with updated data until the cache is cleared, which will cause the system to fetch a new copy of the information from scratch.
Confluence: Confluence is a web-based corporate wiki developed by Atlassian. Silverchair teams use Confluence for documentation, project organization, and information sharing.
CS: Client Services. CS is a Tier 2 Support team that answers queries, provides training, and resolves issues submitted by our clients, with analysts located domestically and in Europe. The Client Services team operates from 8:00-6:00 EST and has an active on-call rotation 24 hours a day, 7 days a week in case of emergency.
CSX: Customer Success. Silverchair’s Customer Success team is responsible for overall relationship management, support, and escalation. CSX stays in regular contact with clients through client calls and is the escalation point for clients. Internally, CSX is the client advocate, working closely with DPDs and POs to make sure Silverchair is managing their side of the relationship effectively.
DEV / Dev: May refer to the “development” environment where Silverchair develops features (note that clients do not have access to the DEV environment), or to people in the Software Developer role.
DevOps: Development Operations. Refers to a department at Silverchair which collaborate with development teams to automate system deployment, scaling, and infrastructure, as well as maintain a clean code base and core infrastructure.
DPD: Director of Product Delivery. Current title for the role formerly known as the PDM. The primary point of contact from the launch through the term of the contract and oversees the tactical aspects of the account (estimates, billing). DPDs are responsible for making sure client projects are delivered on time, within agreed scope, and on budget, and strive to understand each client’s unique business needs.
GBOS: Generic Bucket of Sections. GBOS means non-standard content, i.e. content that is not journal, conference, book, or certain standalone multimedia content.
Ingestion: Ingestion refers to a function of Solr, whereby Solr modifies, adds, and deletes data to ensure it is accurate and may be used for Solr-driven features.
JATS: Journal Article Tag Suite. The Journal Article Tag Suite is an application of NISO Z39.96-2012 developed by Mulberry Tech, which defines a set of XML elements and attributes for XML tagging of journal articles and describes three article models. SCJATS is the custom-to-Silverchair XML specification based on the “Publishing” JATS tag set, also known as “Blue JATS”
JATS4R: JATS for Reuse. JATS4R is a working group devoted to optimizing the re-usability of scholarly content by developing best-practice recommendations for tagging content in JATS XML. Many changes made to the SCJATS specifications are driven or supported by JATS4R recommendations.
JIRA: JIRA is the Atlassian tool that Silverchair uses internally for project and issue tracking. Issue tracking in JIRA is done using JIRA tickets.
L&H: Licensing & Hosting. The recurring monthly hosting fees for clients on the Silverchair Platform. These fees exclude transactional enhancements.
LOE: Level of Effort. LOE is typically estimated in terms of the number of hours required to complete an enhancement project.
May Affect Workflows: Platform updates with this tag will affect clients’ internal and/or Silverchair tool workflows and may need advance preparation / training.
Optional Extension: Platform updates with this tag are available as add-ons to the existing platform and bear additional cost.
PDL: Platform Decision Log. This is the internal process through which Silverchair employees submit suggestions for platform-wide functionality.
PDM: Product Delivery Manager. The legacy title for a Director of Product Delivery (DPD) at Silverchair.
PI: Program Increment. The Program Increment is a feature of Agile development that encompasses one 2-week planning period, followed by three 3-week sprints for a total of 11 weeks. The PI provides a manageable planning horizon to align teams’ capacity, business scope, and delivery value.
PI Planning: Program Increment Planning. This term may be used to refer to the PI planning event held during the 2-week planning sprint, or to the PI planning sprint as a whole.
Platform Strategies: Platform Strategies is a Silverchair-hosted industry event series exploring the technologies and strategies that support professional and scholarly knowledge.
PO: Product Owner. Responsible for the day-to-day delivery of the project; works closely with clients to understand their business goals and takes the high-level roadmap to produce an organized, sequenced, and actionable plan for the development team to deliver; ensures the team understands the team’s purpose, deliverables, and schedule to deliver on business commitments.
PROD: The Production environment is the live software environment (either a site or a tool) used by end users. Changes made in PROD appear in the front-end environment.
Release notes: Sprintly email from Silverchair with a listing of highlights from that sprint’s feature and functionality updates, as well as a list of key upcoming enhancements.
Requires Action: Platform updates with this tag carry no additional cost for the client (in most circumstances), but require direct action on the client’s part before they can benefit from the new functionality.
SaaS: Software as a Service. SaaS is an industry term, pronounced as “SASS”. A software delivery model in which software and associated data are centrally hosted on the cloud. SaaS is typically accessed by end users via a web browser. Silverchair uses this business model primarily, by hosting client’s content and allowing them to manage it over the web.
SCBITS: SCBITS refers to the comprehensive set of documents that inform and define the books content specifications for SPT clients at Silverchair. SCBITS is based on a subset of tags and attributes from BITS 2.0.
SCJATS: SCJATS refers to the comprehensive set of documents that inform and define the journals content specifications for SPT clients at Silverchair. SCJATS is based on a subset of tags and attributes from JATS 1.0, however, features from 1.1 and 1.2 have been added as needed.
SCM: Formerly known as SCM6. A way to refer to clients launched pre-2016 (plus AORN), using legacy platform tools.
SCP: Silverchair Custom Platform. A way to refer to clients with unique custom publishing solutions.
Scrum Master: The Scrum Master provides daily leadership and coordination to one or more Agile teams. This role is responsible for ensuring the Agile Team is working efficiently and effectively by synchronizing activities and removing obstacles in the way of successful delivery.
Silverchair Forum: Silverchair’s client-only event series, aimed at building community, sharing key platform updates and strategy, and gathering feedback on future developments.
SLA: Service Level Agreement. SLAs are intended to measure whether Silverchair is meeting certain agreed, measurable criteria.
SME: Subject Matter Expert. Refers to someone with expertise or domain knowledge over a feature, subject area, or technical space.
Solr: A search platform based on Microsoft Lucene. Silverchair uses Solr to drive features such as platform search and user access.
SOW: Statement of Work. Used to describe the formal or informal agreement with a client to complete a set of work (a project).
SPDP: Silverchair Platform Development Plan. Refers to Silverchair’s roadmap for platform development, which includes core service and tool improvements, support for industry initiatives, Silverchair Universe partner integrations, feature enhancements, and other innovations.
Sprint: In Agile methodology, a sprint is a short-duration, time-boxed iteration, during which the Scrum team is focused on producing a potentially shippable product increment that meets the Scrum team’s agreed-upon definition of done. Silverchair normally operates with 3-week sprints which are punctuated on a regular cadence with two week sprints to complete a PI.
SPT: Silverchair Platform Theme. A way to refer to non-custom clients launched after 2016, using latest version of platform tools (including SiteBuilder and ProductBuilder).
SQA: Software Quality Assurance. Software Quality Assurance is a functional department focused on software testing and quality. More broadly, SQA Engineers also monitor software engineering processes and methods used to ensure quality. At Silverchair, our SQA Engineers are often referred to as “SQAs” for short.
SQL: Structured Query Language. Structured Query Language, pronounced as “SEE-QUHLL” or “S-Q-L” is a special-purpose programming language used to manage and search relational databases.
SSO: Single Sign On. A property of access control of multiple related, but independent software systems. A user is able to login in once and gain access to all integrated systems without being prompted to log into each individual integrated system separately.
Staging or STAG: Staging is a software development environment where the features of the software are supposed to function nearly like the production environment. The code / features on staging should be able to be promoted to the live or production site (data or content is not the same, necessarily).
SWAG: SWAG = Scientific Wild-Ass Guess. This usually refers to the first phase of estimation for a product or project. Related terms and phrases include “Ready for SWAG” or “SWAGed”.
TL / Tech Lead: Technical Lead. Tech Leads are Software Engineers who lead and are accountable for their team’s technical projects, work with and mentor Software Developers, and collaborate with technical and delivery teams to support development.
TechOps: Technical Operations. Refers to a department at Silverchair which is responsible for configuring hardware, peripherals, services, settings, directories, storage, etc. in accordance with standards and project/operational requirements, as well as maintaining systems and security monitoring for Silverchair’s sites and services.
UX / UI: User Experience / User Interface. “UX / UI” may be used to refer to a front-end team, where the team members focus on all aspects of the product’s front-end behavior, from user-interactions, to accessibility, to the underlying front-end architecture. “UI” can also refer to a product’s user interface, AKA the product’s front end.