outcomes.json

{
  "schema_version": 1,
  "outcomes": [
    {
      "id": "github-adoption",
      "name": "Adopt GitHub Enterprise Cloud",
      "tagline": "Stand up GitHub Enterprise Cloud for production teams.",
      "description": "Configure GitHub in the customer's own organization so teams can plan work, review code, enforce governance, run automation, and use AI-assisted delivery in production repositories.",
      "personas": ["customer-developer", "platform-governance", "solution-architect", "platform-engineer"],
      "adoption_stage": ["assess", "pilot", "scale", "operate"],
      "business_value": ["streamline-platform-adoption", "standardize-developer-flow", "improve-governance"],
      "source_platforms": ["greenfield", "github"],
      "challenge_ids": [
        "ghec-ch00",
        "ghec-ch01",
        "ghec-ch02",
        "ghec-ch03",
        "ghec-ch04",
        "ghec-ch06",
        "ghec-ch07",
        "ghec-ch08",
        "ghec-ch09",
        "ghec-ch10",
        "ghec-ch14",
        "ghec-ch16",
        "ghec-ch17",
        "ghec-ch19",
        "ghec-ch20"
      ],
      "success_metrics": [
        "A production repository has teams, permissions, rulesets, required checks, and audit visibility configured in the customer's GitHub organization.",
        "The team's next production pull request runs required checks and merges through the configured ruleset.",
        "Customer developers can plan, code, review, and automate delivery in GitHub without leaving their daily workflow."
      ]
    },
    {
      "id": "platform-migration",
      "name": "Migrate projects to GitHub",
      "tagline": "Move a real project onto GitHub and prove it is ready for production work.",
      "description": "Migrate a customer project into GitHub with repository setup, team permissions, rulesets, CI conversion, security controls, validation evidence, and post-cutover ownership in the customer's tenant.",
      "personas": ["platform-engineer", "platform-governance", "solution-architect", "customer-developer"],
      "adoption_stage": ["assess", "pilot", "scale"],
      "business_value": ["reduce-migration-risk", "accelerate-cutover", "standardize-delivery"],
      "source_platforms": ["azure-devops", "bitbucket", "gitlab", "other"],
      "challenge_ids": [
        "ghec-ch00",
        "ghec-ch21",
        "ghec-ch22",
        "ghec-ch23",
        "ghec-ch24",
        "ghec-ch25",
        "ghec-ch26",
        "ghec-ch04",
        "ghec-ch05",
        "ghec-ch07",
        "ghec-ch08",
        "ghec-ch11",
        "ghec-ch12",
        "ghec-ch13",
        "ghec-ch18"
      ],
      "success_metrics": [
        "A migrated repository in the customer's GitHub organization contains the expected history, default branch, teams, permissions, and rulesets.",
        "The first production pull request after migration runs GitHub-native checks, security scans, and review requirements before merge.",
        "Legacy platform controls have verified GitHub equivalents or documented cutover decisions owned by the customer's platform team."
      ]
    },
    {
      "id": "ghas-adoption",
      "name": "Adopt GitHub Advanced Security",
      "tagline": "Put GitHub Advanced Security into daily pull-request work.",
      "description": "Enable GHAS in the customer's organization so developers and AppSec teams can find, triage, and remediate code, secret, and dependency risk in production repositories.",
      "personas": ["security-lead", "appsec-engineer", "customer-developer", "platform-governance"],
      "adoption_stage": ["pilot", "scale", "operate"],
      "business_value": ["reduce-security-risk", "shift-left-security", "improve-remediation-flow"],
      "source_platforms": ["github", "azure-devops", "bitbucket", "gitlab"],
      "challenge_ids": [
        "ghas-00",
        "ghas-01",
        "ghas-02",
        "ghas-03",
        "ghas-04",
        "ghas-05",
        "ghas-06",
        "ghec-ch11",
        "ghec-ch12",
        "ghec-ch13",
        "ghec-ch15"
      ],
      "success_metrics": [
        "Code scanning, secret scanning, push protection, and dependency alerts are enabled on the customer's target production repositories.",
        "Push protection blocks a real secret from being pushed in the customer's GitHub organization.",
        "A code scanning or dependency alert is triaged, remediated through a pull request, and shown closed in GitHub."
      ]
    },
    {
      "id": "agentic-workflows",
      "name": "Adopt agentic workflows for your SDLC",
      "tagline": "Change how you build software and deliver it throughout your Software Development Lifecycle.",
      "description": "Build and operate GitHub-native agents in the customer's repositories for issue triage, pull-request review, CI diagnosis, documentation, testing, security, and continuous intelligence with reviewable outputs.",
      "personas": ["customer-developer", "platform-engineer", "solution-architect", "platform-governance"],
      "adoption_stage": ["pilot", "scale", "operate"],
      "business_value": ["automate-repetitive-work", "improve-developer-productivity", "standardize-agent-safety"],
      "source_platforms": ["github"],
      "challenge_ids": [
        "ghaw-00",
        "ghaw-01",
        "ghaw-03",
        "ghaw-06",
        "ghaw-07",
        "ghaw-08",
        "ghaw-09",
        "ghaw-10",
        "ghaw-11",
        "ghaw-12",
        "ghaw-14",
        "ghaw-16",
        "ghaw-17",
        "ghaw-18",
        "ghaw-19",
        "ghaw-20",
        "ghaw-21",
        "ghaw-23",
        "ghaw-24"
      ],
      "success_metrics": [
        "An agent workflow runs from a real issue, pull request, or CI failure in the customer's GitHub organization.",
        "Each agent uses documented triggers, least-privilege permissions, allowed tools, logs, and human review points.",
        "Agent-generated changes land only through pull requests with required checks and reviewer approval."
      ]
    },
    {
      "id": "agentic-devops-cloud",
      "name": "Adopt Azure SRE Agent",
      "tagline": "Connect Azure SRE Agent to production signals and GitHub follow-up.",
      "description": "Use Azure SRE Agent in the customer's Azure tenant with Azure Monitor, Log Analytics, Application Insights, service knowledge, source-code context, and GitHub follow-up for production incident investigation.",
      "personas": ["sre", "platform-engineer", "solution-architect"],
      "adoption_stage": ["pilot", "operate"],
      "business_value": ["improve-operational-resilience", "accelerate-cloud-delivery", "reduce-incident-mttx"],
      "source_platforms": ["github", "azure"],
      "challenge_ids": [
        "sre-agent-00",
        "sre-agent-01",
        "sre-agent-03",
        "sre-agent-04",
        "sre-agent-05",
        "ghec-ch19"
      ],
      "success_metrics": [
        "Azure SRE Agent is connected to the customer's monitored application, Azure resources, logs, traces, and runbooks.",
        "A controlled incident produces an alert, investigation evidence, likely cause, and recovery action in the customer's Azure environment.",
        "A GitHub issue or pull request links the operational symptoms to source-code context, logs, and the agreed engineering follow-up."
      ]
    }
  ]
}