New Workloads

New Feature work required from Aurora Commerce should be issued by you in a single definitive volume. Generally only one volume will be handled at a time through to full Go Live and Sign Off, until the next is accepted; this is to prevent workload crossovers and Go Live conflicts with development work.
If a New Feature workload is issued to us and there is other work already in the flow for a Site, then the new workload could be stored, and it will then be addressed for you by your assigned Account Manager in the next agreed workload wave, once the current workload in the flow is fully signed off and live.

When work is issued to us, we book an initial pre-assessment slot for the assigned developer. This will be 30 minutes per point and this booking will be subject to our booking system.
The pre-assessment will define the time required to do a full assessment, a basic roll out quote estimate, and ball park cost for the workload.

• Pre-assessment estimates are always issued with the expectancy that Speccing will be required; however, should it transpire that it not be required, then billing will be adjusted accordingly during the full assessment phase.

• Pre-assessment estimates are approximations of how long something would take to actually turnaround end to end.

• During full assessment, precise plans will be set in detail that will define the overall plan for the workload. The precise plan could adjust the overall rollout and therefore expenditure for a workload as quoted during the pre-assessment phase.

• During full assessment all quotes are subject to a mark up for Quality Assurance and testing time, which is assessed on a case by case basis. 

When new Aurora User Guide documentation is required for a New Feature, this will be a billable addition to the workload. This will be defined by us as a requirement during the workload's full assessment.

When a body of work that we have worked on is ready for Go Live, we and your Agency must BOTH approve the Go Live as safe to go ahead, prior to the actual Go Live deployment. This is to prevent workload crossover issues and errors being caused on the live site.

We can agree and plan works for a specific Site months in advance utilising a Period Planner, ordering works in priority for future delivery. Should this be a requirement that you wish to explore, please contact your assigned Account Manager.

Our ongoing New Workload processing logic, with workloads generally issued one at a time to completion until the next is accepted, is in place for two core reasons: firstly to ensure that there are no workload crossovers, causing code base issues, Go Live conflicts, other errors, or potential fatal issues on sites. Secondly to ensure we can book and guarantee protection of one Site’s work from that of the others that we handle.
We look to avoid a 'who shouts loudest' culture and workflow model by using defined rules and a structure that is clear, fair, and highly efficient for all, and that has a proven track record of very fast turnarounds whilst of course retaining a focus on quality.