Understanding concepts used in CloudBees Engineering Efficiency can help you use features and capabilities more effectively.
Software Delivery Management is an emerging category and practice that aims to help businesses and their cross-functional teams better collaborate and align process with software development, while also connecting and measuring development effort to business KPIs.
CloudBees Software Delivery Management is CloudBees' solution, providing a System of Record with a common data model that normalizes data from across tools. It is the backbone from which modules connect to surface information about the software delivery organization.
CloudBees Engineering Efficiency is a CloudBees Software Delivery Management module that leverages data from across the toolchain to create one centralized view of metrics and analytics on development team performance and efficiency.
System of Record is the backbone of CloudBees Software Delivery Management, including the CloudBees Engineering Efficiency and CloudBees Feature Management modules. This System of Record is a flexible common data model that ingests data from across the toolchain. In addition, CloudBees Software Delivery Management has a flexible app model to ingest data from other tools that may not be supported out-of-the-box. By connecting to this System of Record, you can normalize the data-to-surface information based on different functionality or modules built on top, that provides the actionable insights needed to run an efficient engineering team.
In Software Delivery Management, a build is a specific instance of a pipeline or build run. For example, a Jenkins build run.
- Common data model
Represents data entities and relationships in the simplest possible form in order to integrate processes across various systems and databases. The model is independent from any specific application and provides an additional level of indirection between applications' individual data formats.
- Data type
A data type is a specific kind of data, defined by the values it can contain and how those are accessed.
For example, an
Integer is a
Scalar data type that can hold a whole number and an
Object is a data type that has named fields with their own data types and values.
- Deployment build
A continuous integration (CI)/continuous deployment (CD) job that deploys code changes or artifacts in production.
The process of accepting or receiving data from an external source like Jira or Jenkins.
Learnings presented or derived from data, metrics, and/or analytics.
a job is the definition of an automation that can be executed.
A quantitative measurement often associated with performance, targets, or goals.
A collection of custom-curated apps that extend the foundational capabilities of software delivery management to meet targeted use cases and can be purchased as distinct packages.
In Software Delivery Management, a product is any organized work effort that addresses a market need, either internal or external, and delivers an intentional user outcome. Long running in nature, the product lifecycle includes inception, validation, adoption, growth, and end of life.
- Software Delivery Management
A strategy that breaks down silos, providing visibility across an organization into the software development lifecycle. This strategy relies on four foundational pillars:
Common connected processes
All functions collaborating
These pillars support a unified System of Record in which all functions can enjoy continuous insights and feedback, resulting in faster software delivery with measurable business outcomes.
- System of Record
In CloudBees Software Delivery Management, the System of Record is a powerful, tightly integrated, and extensible document-centric data store with features that make it faster and easier to store and retrieve data. The System of Record records all software delivery activities to support subsequent query, visibility, analytics, insights, workflow orchestration, and other features.
- Uncategorized work
Specific to work categories, uncategorized work is the set of Jira issues that do not match any of the defined work categories for a product.
- Work category
A kind of work that is always present regardless of current efforts and project goals. Examples can include bug fixes, security patches, and technical debt. A work category can also represent work done by people in a role, such as design, documentation, or user experience; or a phases of work, such as feature research, scope discovery, planning, and delivery.