Harrier Open Standards
  • Open Standards
  • Technical
    • Best Practices
      • Naming conventions
        • Object / Metadata Type / Settings Conventions
        • Custom Permissions Conventions
        • Profile Conventions
        • Permission Set (Group) Conventions
        • Apex Style Guide
      • Feature flags
    • Documentation
      • GPT Instructions
    • Frameworks
      • flxbl - Continuous Delivery
      • fflib - Apex Framework
      • Nebula Logger - Logging
    • Integration Strategies
      • Data warehouse & Reverse ETL
    • Development & Deployment Strategies
  • Functional
    • Requirement definition
      • GPT Instructions
    • Documentation
Powered by GitBook
On this page
  • Overview
  • Modularity
  • Incremental Modularity
  • Happy Soup

Was this helpful?

  1. Technical

Development & Deployment Strategies

Overview

To do: describe the different strategies we support, what the considerations are to move things like UAT left, etc. Describe it from a technical and functional point of view.

Modularity

To do: describe our favorite state, modularity. Bing bang modular development migration / refactor to packages or green field.

Incremental Modularity

To do: describe a tactic to migrate over to modularity step by step.

Happy Soup

To do: descibe our least favorite way of working, something that should be avoided.

PreviousData warehouse & Reverse ETLNextRequirement definition

Last updated 1 year ago

Was this helpful?