Skip to main content

    Factory delivery path

    From assigned work to your release decision.

    Reign Factory works on assigned work and opens a merge request in your repository. Your checks, reviewers, approval policy, merge decision and release process determine what ships.

    Discuss your delivery prioritiesWhat we measured →

    Your policy governs review, approval, merge and release.

    The delivery path, end to end.

    01

    An item from your backlog, assigned to the Factory.

    Where Reign Factory sits Reign Factory takes eligible assigned work, performs implementation and test work with Reign Gateway on the model path, and opens a merge request in the customer's software project. The customer's checks, review, approval, merge and release controls determine what ships. A named person is involved when review, approval or judgment is needed. Your backlog work items Reign Factory operated for you by iTmethods Eligibility tested criteria Supervisor assigns work Implementation agreed method Reign Gateway policy · routing Person review or decision out of scope · check unmet · judgment needed merge request Your software project existing delivery controls Your repository branch Your checks build · test Review merge request Your approval stages you run Merge your rules Release your process Your developers same path check and review results return to the factory
    Assigned scope. Eligibility rules define which work Factory may take on. Person involvement. A named person reviews the work or makes the decision when judgment is needed. Your decision path. Your checks, approval policy, merge decision and release process determine what ships. When it can’t converge. If it can’t reach a change worth reviewing, it reports that rather than opening a merge request to show activity.

    The ask

    Discuss your delivery priorities.

    Let’s discuss one piece of work you want to advance.

    Discuss your delivery priorities