Content Comparison

Our scope of work for AVI includes multiple project streams as well as ongoing support items. Due to the complex nature of overlap and conflict between items of development within a typical Salesforce implementation, there are significant challenges with managing version control of deployed components. The purpose of this document is to outline our agreed strategy for management of sandbox instances and our production deployment cycle.

...

1. No new development can be undertaken without the explicit engagement of AVI client IT Team (or similar approval)

2. Monthly Journey development cycle - items selected for development at the monthly scheduling meeting to be deployed to production within that cycle (UAT completion and monthly journey hours permitting)

3. Bug fixes to be actioned and deployed according to support agreement (refer to SLA)

4. Project development to be managed and scheduled according to project SOW

5. Any conflict or overlap between project development and journey development items to be discussed by Vertic and AVI before proceeding New Components when created, are to always be added to the AVI - Lightning Components (for both Journey & Project Work).

Instance Management

...

• Separate PDEV sandbox for each project development stream

• Alternating JDEV sandboxes for ongoing Journey development

• JDEV sandboxes to be refreshed every two months (or monthly if all in-progress development items are deployed

• UATPC (Partial Copy) Sandbox for QA and internal testing

• UATPC refresh can be scheduled when agreed by Vertic and AVIthe client

...

1. Backlog (not yet approved for development)

2. Selected for Development (approved for development)

3. In Progress (currently assigned to a developer and under development)

4. Vertic Review (assigned to project lead fo of internal QA testing and review)

5. Client Review (ready for testing/review by relevant AVI client team member)

6. Deployed (successfully deployed to production environment)

Project or PDEV sandboxes will be created or refreshed before the commencement of any new project development as required, Journey or JDEV sandboxes to be refreshed every two months 

...

1. An estimate for the effort has been provided by Vertic and that has been approved by AVI the client via a comment; or

2. The ticket has been discussed and approved for Development in a Journey Planning Meeting; or

3. AVI requires an urgent piece of development and are still within their development cycle.

Issue Type Management

• Bugs are errors, flaws or faults in development which produces SF to act in an unintended way.

  • should automatically be moved into Selected for Development.

• Stories are requests for larger work which are then divided into subtasks.

  • as these are larger tickets, each subtask is required to be given an estimate for that particular ticket.

  • These issue types require greater information surrounding estimates compared to Tasks when work is in excess of 2.5hours.

• Tasks are used for single updates

  • Simple estimates are provided here, which can then be broken down further on request.

...

• • .

Production Deployment Scheduling

Scheduling for deployments into the AVI client’s live production environment will be dependant on whether it is project-related development or Journey development.

• Project go live or production deployments are to be determined by the agreed project timelines and subject to approval by both the AVI client’s IT Team and the Project Manager

• All Client Journey development tickets with a “Client Approved” status will be deployed on the agreed monthly deployment date

• Critical bug fixes, warranty items or other agreed-upon urgent items will be deployed on an ASAP basis

• Deployed tickets to include a link to the relevant Changeset or the Clickset ID

...

• ClicksetId