Microsoft Software / SaaS United States

HP

Application Refactoring · Enterprise Knowledge Search

HP wanted to modernize and standardize software development so its global developer community could work faster, collaborate better, and spend less time on repetitive coding tasks.

Several thousand developers actively use GitHub Copilot every day

Reported impact

Business outcome

HP reports marked gains in developer productivity and cross-team collaboration, with Copilot helping engineers focus on higher-value product work and move software improvements to market faster.

  • Productivity Improvement
  • Speed to Market

Solution

HP rolled out GitHub Copilot Business across an enterprise software toolchain built around GitHub Enterprise, Azure DevOps, Visual Studio, supported IDEs, and CLI workflows. Developers use Copilot for inline code suggestions, chat-based answers to coding questions, code review acceleration, and modernization of older code, while the existing GitHub and Azure DevOps stack keeps collaboration, governance, and release practices in the same workflow. Rather than treating AI as a separate experiment, HP embedded Copilot directly into day-to-day engineering work so thousands of developers could write, review, and update software faster without getting stuck on scaffolding or syntax. The result is a more connected developer community and a reusable AI-assisted development pattern across HP’s hardware, software, and services ecosystem.

Data flow

Developers prompt and code inside their IDEs and CLIs, GitHub Copilot Business returns inline suggestions and chat answers in context, and the resulting code continues through GitHub Enterprise and Azure DevOps for collaboration, review, and delivery.

Solution architecture

4 components · 2 layers
  1. Serving
    • GitHub Copilot Business Provides AI code suggestions and chat-based assistance inside supported developer workflows.
    • Visual Studio Acts as one of the development surfaces where Copilot assistance is consumed.
  2. Orchestration
    • GitHub Enterprise Supplies the collaborative source-control and governance environment around HP’s engineering work.
    • Azure DevOps Supports enterprise development workflows, delivery practices, and adjacent toolchain integration.

Architecture clues

  • Copilot is used for inline code suggestions and coding Q&A inside IDEs and CLIs
  • HP uses Copilot alongside GitHub Enterprise and Azure DevOps rather than as a standalone tool
  • Older code assessment and updates are part of the workflow

Evidence from the source

HP incorporated GitHub Copilot into its workflow, and developers quickly found that they code faster and solve issues more quickly without getting bogged down in tedious code scaffolding and syntax.
Scheessele says HP currently has several thousand developers actively using GitHub Copilot every day.
Using GitHub Copilot, they could easily assess and update older code and more rapidly problem-solve for new projects.
Transparency Evidence & methodology 75/100 reference value · 82% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    HP customer story

    First-party
    https://www.microsoft.com/en/customers/story/1770317375595733395-hp-github-professional-services-en-united-states
    Source type
    Vendor-published customer story
    Published
    May 21, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 21, 2024 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.