Method

From proof to acceptance, with a record at every step.

We follow one path through requirements, trial, implementation, and acceptance, so the customer IT team always knows what has been done and what will be validated next. The six steps below are expanded: what happens, what the customer should prepare, and what records are left behind.

  1. 01

    Requirements and scope alignment

    Scope comes first, before environments and configuration. Together we review device types and scale, the current management approach, the capabilities that must be validated, and who will operate the platform after go-live. We then align the implementation path and proposal, so goals and delivery work are not describing two different projects.

    What happens

    We hold a scope discussion, agree the target environment, priority scenarios, and the general direction of acceptance, and complete proposal alignment.

    Please prepare

    A rough picture of the fleet (for example, the order of magnitude of Mac, iPhone, and iPad devices), whether Apple Business Manager or Apple School Manager is already in place, whether a Jamf environment already exists, the main security or compliance requirements, and the scenarios you want to validate first.

    What is left behind

    A scope note, plus records of proposal alignment, which become the shared starting point for the trial, implementation, and acceptance.

  2. 02

    Trial environment and ABM enrollment

    We provision a Jamf Cloud trial tenant and help complete the connection between Apple Business Manager (or Apple School Manager, where that applies) and Jamf, including account preparation such as a Jamf ID. The aim is for test devices to come under management during Setup Assistant through Automated Device Enrollment, without a manual, device-by-device build.

    What happens

    We prepare the trial environment, assist with the portal-to-Jamf integration, and confirm that the enrollment path for test devices works.

    Please prepare

    Administrator access to ABM or ASM, a small set of test devices, network access during setup, and a counterpart who can handle account-related tasks.

    What is left behind

    A usable trial environment, a note on the integration status, and a description of the enrollment path for test devices.

  3. 03

    Kick-off workshop and SOP

    Before configuration begins in earnest, we align with the customer IT team on the path: which scenarios will be validated first, what success looks like, and who will carry out the steps on test devices. We provide enrollment documentation and a testing SOP so both sides work from the same method, rather than keeping separate informal notes.

    What happens

    We run a kick-off workshop, agree the staged plan, roles, and test method, and walk through enrollment and the basic operating path.

    Please prepare

    The IT lead and the colleagues who will actually use the console, time for the workshop, and a short description of how devices are issued, returned, and recovered when people leave.

    What is left behind

    Kick-off notes, enrollment documentation, and a testing SOP for the staged validation that follows.

  4. 04

    Staged functional validation

    We advance enrollment, configuration and grouping, app and OS distribution, and the security baseline by agreed scenario. Each stage leaves a traceable test record, instead of applying every policy at once. Issues are recorded and retested in the current stage before the next set of capabilities begins.

    What happens

    On test devices, we validate enrollment, policy, distribution, and security by scenario, and record results and open issues.

    Please prepare

    A representative set of test devices, the necessary app list or installer packages, and any security or network constraints, such as whether peripherals are allowed and who issues certificates.

    What is left behind

    Staged test records, including what has been validated, what remains open, and the results of retests.

  5. 05

    Acceptance checklist

    Agreed capabilities are written into a checklist and reviewed against the test results, so both sides can confirm that the standard has been met. Items that have not passed are marked with the gap and the planned follow-up, rather than closing the stage as “good enough in general.”

    What happens

    We review results against the written checklist, confirm the capabilities that have been met, and record the plan for anything still outstanding.

    Please prepare

    An internal reviewer, and a clear view of what must be in place in this phase and what can wait for a later stage.

    What is left behind

    A confirmed acceptance checklist and the supporting test results, which become the basis for handover and later operations.

  6. 06

    Go-live and ongoing support

    We stay with the move from trial or pilot into daily operations, and confirm that administrators know what to watch, and how to handle new devices and new policies. After go-live we remain available for policy changes and troubleshooting, rather than ending the work on the day of handover.

    What happens

    We help shift into daily operations, review operating ownership and known issues, and agree how later support will be reached.

    Please prepare

    The planned go-live window, the person who will own operations, and a list of known leftover issues.

    What is left behind

    Go-live notes, an operational handover record, and the contact path for later support.