Configuration Sprint Planning

Open

Configuration Teams

Group 1:  The Ho, Dev

Group 2: Manpreet, Sidra

Group 3: Yeng

Approach

Each group works in its own Dev Pro Sandbox

When configurations are “done” they are promoted to full Sandbox for QA and functional testing –

1. Who should be responsible for QA?

Defects re-assigned to developers

Changes placed on backlog for consideration – reconfig for MVP or future phase

 Work (JIRA tickets) assigned to developer teams for completion in 4 x 2 weeks sprints

Sprints commence on Tuesdays (Monday evening US)

Sprint planning meeting at the commencement of each sprint (Tuesday morning/Monday evening) to assign tasks to each development team to be worked on during the sprint. Lori/Griffin attend sprint planning meeting.

Daily stand-ups 9am-9:15am, Sydney time; Lori/ Griffin attend on Wednesdays and Fridays

Lori/griffin available 9am - midday, Tuesday - Friday to support developers

If developers have blockers, raise with Lori/Griffin through Jira ticket associated with item

Teams channel will be created and used for communications between development team and can also be used for communications with Lori/Griffin

Commencement of configuration sprints will be undertaken together with Lori/Griffin guiding developers

Integration development use partial sandbox

When each integration built and tested, its promoted to full sandbox

Open

Prerequisites for Configuration Commencement

• All object and field mappings documented

• 2nd conversion testing successfully completed

• Process flows and instructions documented in sufficient detail to be used for configuration specification

Risks

• Integration data identified during configurations that cannot be made available

• Advance data/custom fields identified during configurations not included conversion

• MVP requirements cannot be configured in the time frame

Configuration Sequence

1. Major Gift Prospect Experience

   1. Identify required toolkit for each component {Workflow rule (cases, chatter, email) process builder, flow}

   2. Notifications

   3. Cases

   4. Reports

   5. Persona

      1. DO

      2. Prospect Development

      3. Gift Implementation

      4. Donor Relations

      5. TAP - other

   6. Permission set requirements for each persona (to be done by CSMs not developers)

2. Gift Processing

   1. Identify required toolkit for each component {Workflow rule (cases, chatter, email) process builder, flow}

   2. Notifications

   3. Cases

   4. Reports

   5. Matching Rules

   6. Persona

      1. Gift Administration

      2. DO

      3. Donor Relations

      4. Finance (Integration)

   7. Permission set requirements for each persona (to be done by CSMs not developers)

3. Planned Giving Experience

   1. Identify required toolkit for each component {Workflow rule (cases, chatter, email) process builder, flow}

   2. Notifications

   3. Cases

   4. Reports

   5. Persona

      1. Planned Giving

      2. Prospect Development

      3. Gift Implementation

      4. Donor Relations

      5. TAP - other

   6. Permission set requirements for each persona (to be done by CSMs not developers)

4. Annual Fund Campaign Experience

   1. Identify required toolkit for each component {Workflow rule (cases, chatter, email) process builder, flow}

   2. Notifications

   3. Cases

   4. Reports

   5. Persona

      1. Annual Fund Officers

      2. Prospect Development

      3. Gift Implementation

      4. DO

      5. TAP - other

   6. Permission set requirements for each persona (to be done by CSMs not developers)

5. Reports and Dashboards (all TAP persona)

6. Permission sets for all TAP persona

7. Permission set groups (all TAP persona)

8. Pages layout

9.