Copilot outcome guides to support the ESSP (#55892)
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com> Co-authored-by: jclement136 <jclement136@github.com> Co-authored-by: John Clement <70238417+jclement136@users.noreply.github.com>
This commit is contained in:
Isaac Brown
26
content/copilot/get-started/achieve-engineering-goals.md
Normal file
26
content/copilot/get-started/achieve-engineering-goals.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: Achieving your company's engineering goals with GitHub Copilot
|
||||
shortTitle: Achieve company goals
|
||||
intro: 'Plan your rollout based on GitHub''s recommended approach for driving and measuring improvements.'
|
||||
versions:
|
||||
feature: copilot
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
When your company rolls out a new tool such as {% data variables.product.prodname_copilot %}, you will want to measure the impact of the tool on your engineering systems and assess the tool's contribution to your company's goals.
|
||||
|
||||
{% data variables.product.company_short %}'s [Engineering System Success Playbook](https://resources.github.com/engineering-system-success-playbook/) (ESSP) provides strategies and metrics for driving meaningful and measurable improvements. The playbook recommends a three-step process for solving engineering challenges:
|
||||
|
||||
1. Identify the current barriers to success.
|
||||
1. Evaluate what needs to be done to achieve your goals.
|
||||
1. Implement your changes, monitor results, and adjust.
|
||||
|
||||
## Define your goals
|
||||
|
||||
Based on the recommendations of the ESSP, the following guides show how {% data variables.product.prodname_copilot %} can help you achieve your company's goals in specific areas. They explain how {% data variables.product.prodname_copilot_short %} can help, provide advice and resources for an effective rollout, and recommend metrics for assessing {% data variables.product.prodname_copilot_short %}'s impact.
|
||||
|
||||
We recommend defining your goals and planning your rollout accordingly. You should communicate your goals to staff and organize training to enable everyone to contribute.
|
||||
|
||||
* [AUTOTITLE](/copilot/tutorials/rolling-out-github-copilot-at-scale/driving-downstream-impact/increase-test-coverage)
|
||||
* [AUTOTITLE](/copilot/tutorials/rolling-out-github-copilot-at-scale/driving-downstream-impact/accelerate-pull-requests)
|
||||
* [AUTOTITLE](/copilot/tutorials/rolling-out-github-copilot-at-scale/driving-downstream-impact/reduce-security-debt)
|
||||
@@ -0,0 +1,86 @@
|
||||
---
|
||||
title: Choosing your enterprise's plan for GitHub Copilot
|
||||
shortTitle: Choose enterprise plan
|
||||
intro: 'Choose between {% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %}.'
|
||||
versions:
|
||||
feature: copilot
|
||||
topics:
|
||||
- Copilot
|
||||
permissions: Enterprise owners and billing managers
|
||||
redirect_from:
|
||||
- /copilot/rolling-out-github-copilot-at-scale/choosing-your-enterprises-plan-for-github-copilot
|
||||
- /copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot
|
||||
- /copilot/tutorials/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot
|
||||
---
|
||||
|
||||
When you adopt {% data variables.product.prodname_copilot %} in a company, you will sign up to a {% data variables.product.prodname_copilot_short %} plan designed for businesses. These plans allow you to:
|
||||
|
||||
* Choose which users receive access to {% data variables.product.prodname_copilot_short %}
|
||||
* Meet regulations and security requirements with features like file exclusion, policies, and audit logs
|
||||
* Benefit from advanced {% data variables.product.prodname_copilot_short %} features
|
||||
|
||||
{% data variables.copilot.copilot_enterprise_short %} offers additional features for enterprises that want to customize {% data variables.product.prodname_copilot_short %} for their needs.
|
||||
|
||||
This article helps you to decide whether to adopt {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %}.
|
||||
|
||||
<a href="https://github.com/github-copilot/purchase?ref_cta=Copilot+Enterprise+trial&ref_cta=Copilot+Business+trial&ref_loc=choosing+enterprise+plan" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_copilot_short %}</span> {% octicon "link-external" height:16 aria-label="link-external" %}</a>
|
||||
|
||||
## About the plans
|
||||
|
||||
{% data variables.product.company_short %} offers two {% data variables.product.prodname_copilot_short %} plans for customers on {% data variables.product.prodname_ghe_cloud %}:
|
||||
|
||||
* **{% data variables.copilot.copilot_business_short %}** ({% data variables.copilot.cfb_price_per_month %} per user per month): includes most {% data variables.product.prodname_copilot_short %} features in IDEs and on the {% data variables.product.github %} website.
|
||||
* **{% data variables.copilot.copilot_enterprise_short %}** ({% data variables.copilot.ce_price_per_month %} per user per month): allows companies to customize {% data variables.product.prodname_copilot_short %} for their code and processes, and includes a higher allowance for premium requests. To learn more, see the sections below.
|
||||
|
||||
For a full comparison, see our [plans page](https://github.com/features/copilot/plans).
|
||||
|
||||
## About mixed plans
|
||||
|
||||
When you subscribe your enterprise account to {% data variables.copilot.copilot_enterprise_short %}, you don't need to use this plan across the whole enterprise. Instead, you can choose a plan individually for each organization in your enterprise. This approach allows you to:
|
||||
|
||||
* Evaluate the benefits of {% data variables.copilot.copilot_enterprise_short %} for a smaller group of users before rolling it out further.
|
||||
* Enable {% data variables.copilot.copilot_enterprise_short %} in the organizations where it will have the most impact, such as organizations with complex documentation or specialized engineering requirements.
|
||||
|
||||
## What are our goals for {% data variables.product.prodname_copilot_short %}?
|
||||
|
||||
To drive and measure downstream impact of {% data variables.product.prodname_copilot_short %}, {% data variables.product.company_short %} recommends leading your rollout with specific engineering goals in mind. Your requirements for {% data variables.product.prodname_copilot_short %} features will depend on your overall goal for the rollout.
|
||||
|
||||
For examples of how {% data variables.product.prodname_copilot_short %} can help with common problems in engineering teams, see [AUTOTITLE](/copilot/get-started/achieve-engineering-goals).
|
||||
|
||||
## Do we have projects with complex requirements?
|
||||
|
||||
For complex projects like monorepos or legacy codebases, developers in your company may need to spend a long time finding and reading documentation before they can contribute.
|
||||
|
||||
With {% data variables.copilot.copilot_enterprise_short %}, you can create **knowledge bases** that bring together documentation from one or more repositories in an organization, allowing {% data variables.product.prodname_copilot_short %} to synthesize information from your documentation in its responses.
|
||||
|
||||
## Will we use {% data variables.copilot.copilot_code-review_short %} at scale?
|
||||
|
||||
With {% data variables.copilot.copilot_code-review_short %}, {% data variables.product.prodname_copilot_short %} can provide feedback on pull requests on {% data variables.product.github %}. How much you use this feature depends on the goals of your rollout. For example, if a goal is to increase velocity by accelerating approvals of pull requests, then you may be encouraging developers to use {% data variables.copilot.copilot_code-review_short %} as much as possible.
|
||||
|
||||
With {% data variables.copilot.copilot_enterprise_short %}, you can make {% data variables.product.prodname_copilot_short %}'s reviews more consistent across your repositories by adding **custom coding guidelines** written in natural language. {% data variables.product.prodname_copilot_short %} will give feedback based on the guidelines when it reviews code, which can increase developers' confidence in the reviews and allow you to encourage consistency in coding standards across teams.
|
||||
|
||||
{% data reusables.copilot.code-review.custom-coding-guidelines-prerequisites %}
|
||||
|
||||
{% data variables.copilot.copilot_enterprise_short %} also includes a higher allowance for premium requests, which include code reviews. To learn more, see [How much will we benefit from premium requests?](#how-much-will-we-benefit-from-premium-requests).
|
||||
|
||||
## How much will we benefit from premium requests?
|
||||
|
||||
{% data reusables.copilot.premium-requests-for-enterprises %}
|
||||
|
||||
To decide if you will benefit from a higher allowance for premium requests, compare the goals of your rollout to **development tasks** that each model is specialized in. For example, the o1 model is focused on math and science. Teams who work in specialized areas may require more requests to premium models. To learn about the benefits of different models, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task).
|
||||
|
||||
Regardless of your plan, you can set a spending limit for premium requests over your plan's allowance. Premium requests over the allowance will be charged at a rate of {% data variables.copilot.additional_premium_requests %} per request, with an additional multiplier applied to certain models.
|
||||
|
||||
## Making a decision
|
||||
|
||||
To summarize:
|
||||
|
||||
* Choose {% data variables.copilot.copilot_enterprise_short %} if your company has projects with complex requirements or large amounts of documentation. Knowledge bases give {% data variables.product.prodname_copilot_short %} enhanced context, which can save developers time and allow them to focus on tasks they enjoy.
|
||||
* If you think your developers will benefit from premium models and {% data variables.product.prodname_copilot_short %} code reviews, it may be cost effective to choose {% data variables.copilot.copilot_enterprise_short %} rather than pay for premium requests over your allowance.
|
||||
* If you're not sure about a full rollout, choose {% data variables.copilot.copilot_enterprise_short %} at the enterprise level and enable it for individual organizations where it will have the most impact.
|
||||
* Make your decision based on your downstream goals for the {% data variables.product.prodname_copilot_short %} rollout.
|
||||
|
||||
## Further reading
|
||||
|
||||
* [AUTOTITLE](/enterprise-cloud@latest/copilot/customizing-copilot/managing-copilot-knowledge-bases)
|
||||
* [AUTOTITLE](/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task)
|
||||
@@ -12,6 +12,8 @@ children:
|
||||
- /plans-for-github-copilot
|
||||
- /github-copilot-features
|
||||
- /best-practices-for-using-github-copilot
|
||||
- /choosing-your-enterprises-plan-for-github-copilot
|
||||
- /achieve-engineering-goals
|
||||
redirect_from:
|
||||
- /copilot/about-github-copilot
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user