TAPSS Refinement Sessions

#

Key

Summary

1

TAPSS-2321

UC01 Types of Activities

2

TAPSS-2188

UC16 Activity and Details Visibility - TAP wide

3

TAPSS-2328

UC08 Specify activity User Experience for Call Task (Layout)

#

Jira#

Decision Summary

D-031

1. TAPSS-2321

This ticket is now 'Ready'.  Business sign-off required

D-032

2. TAPSS-2188

How to define 'sensitive' data? : To be defined by Field, not by the record. 

D-033

2. TAPSS-2188

If someone send sensitive information (credit card details etc), we should not store in system.  Not part of this ticket but potential action to addrerss it in the future

1. Training perspective

2. How to remove what's in the system as a separate initiative.

D-034

2. TAPSS-2188

Q: is there any DO who want to keep private activity?  Business to confirm but the discussion is not part of this ticket and  activity should  be public
A:Decision is to keep it public. 

D-035

2. TAPSS-2188

Q: Why block non-tap user to view if we are aiming to not store sensitive data?  A: there are non-tap users who we still want to block further details not just stricktly privacy sensitive but tap-sensitive.  May not be legal-breach, but more for commercial sensitivity.

D-036

3.TAPSS-2328

There are fields that we need business decision on before progressing to the next step. 
Call Subject Picklist vs Subject free text
Call Resulsts picklist values
Purpose picklist values
Type picklist values. 

#

Jira#

Action

Action Owner

A-015

1. TAPSS-2321

Business Sign-off for the ticket
Build efforts will be distributed to other ticket but training and change management to refer this ticket for the confirmed types of activities

@john.lardis @tina.verma for Training piece

A-016

2. TAPSS-2188

Sekar to confirm the design and progress

@sekar.krishnan

A-017

3.TAPSS-2328

4 Jira subtasks for the business decision and input are now assigned to John to finalise so TAPSS-2328 can progress:

TAPSS-2360 Decision on Call subject (Picklist) vs Subject with free text
TAPSS-2361 Decision on Call Result Picklist values

TAPSS-2362 Decision on Purpose Picklist values

TAPSS-2363 Decision on Type Picklist values

@john.lardis

#

Key

Summary

1

TAPSS-2326

Relating Activites to Accounts and Contacts

2

TAPSS-2324

Backdate Actvities

3

TAPSS-2331

Objects with Activity Component

4

TAPSS-2117

Surface Substantive Activity into Task pagelayouts

5

TAPSS-1862

As a Development Officer, I want to have my opportunity stage to be Early Cultivation or Late Cultivation

6

TAPSS-2314

As a Development Officer, I want to update Prospect Pool in opportunity in Late Cultivation stage before moving to Solicitation

7

TAPSS-2311

As a Development Officer, I want to update at least one of Gift Theme in opportunity in Late Cultivation stage before moving to Solicitation

8

TAPSS-2312

As a Development Office, I want to create opportunity with only with Identification & Qualification stage

9

TAPSS-2016 (only briefly)

AQ 26: SmartBatch 2.0 soft credits on Batch Item Transaction need to adjust Batch Approval Reports

#

Jira #

Decision Summary

Labels Added

D-022

1. TAPSS-2326

Focus on Household to reflect all the activities form all contacts associated with it.  User stories to be reflected to this for further communication and training purpose. Priority = Must Have, T-shirt Size = XS

Training

D-023

2. TAPSS-2324

Define the business rule for backdating.    Adding tracking function in the future may assist with future audit - this will be a separate build. Priority = Must Have, T-shirt Size = XS

Training, BusinessRule

D-024

3. TAPSS-2331

Business want the consistent acitvity visibility for Contact and Cases as well.  UX for activity creation will be 'cut over' from Activity reports and surface Email, Event, Call, Task for Activity Priority = Must Have, T-shirt Size = S

Training

D-025

4. TAPSS-2117

Business decision to surface this fields for End user but only 'read only' or to be used purely for insights.  3 options are presented:

1. Show 'Read only' substantive acitvity' for development offier

2. Keep track of Substantive Activity' backend and not display to development officer

3. Do not create any additional automation for Substantive Activity but once business rule is defined, get the insights from the reporting

BusinessRule

D-026

5. TAPSS-1862

Signed-off

D-027

6. TAPSS-2314

Signed-off

D-028

7. TAPSS-2311

Signed-off

D-029

8. TAPSS-2312

Signed-off

D-030

9. TAPSS-2016

Separately discussed with GA business 

#

Jira #

Action

Action Owner

A-011

1. TAPSS-2326

Once Rommel update the user story and acceptance criteria, assign to Laila for review and sign-off

@rommel.ngo

A-012

2. TAPSS-2324

TAP Business confirm the business rule on backdate.  We will not change this user story and solution but we highlight that system will provide created date vs backdate for potential report and audit if required. Once Rommel update acceptance criteria, assign to Laila for review and sign-off  

@john.lardis

@rommel.ngo

A-013

3. TAPSS-2331

Rommel to confirm the existing activity visibility for Contact and Cases for consistent record type.  Update the user story with acceptance criteria for Contact/ Case and action buttons, assign to Laila for review and sign-off

@rommel.ngo

A-014

4. TAPSS-2117

Park for further development on this until business decision.  TAP business to discuss and confirm.

@john.lardis

#

Jira #

Discussion Summary

D-013

1. TAPSS-2305

Confirmed the ticket to be ‘ready’ with XS size.   This ticket will now move to the future Sprint Planning session

D-014

2. TAPSS-2304

Confirmed the ticket to be ‘ready’ with XS size.   This ticket will now move to the future Sprint Planning session

D-015

3. TAPSS-2303

Confirmed the ticket to be ‘ready’ with S size.   This ticket will now move to the future Sprint Planning session

D-016

4. TAPSS-2301

Confirmed the ticket to be ‘ready’ with XS size.   This ticket will now move to the future Sprint Planning session

D-017

5. TAPSS-2016

Confirmed the ticket to be ‘ready’ with S size.   This ticket will now move to the future Sprint Planning session

D-018

6. TAPSS-1862

Confirmed the ticket with S size.   This ticket is assigned to Laila to review and sign off after demo session on Monday 30/09/2024

D-019

7. TAPSS-2314

Confirmed the ticket with XS size.   This ticket is assigned to Laila to review and sign off after demo session on Monday 30/09/2024

D-020

8. TAPSS-2312

Confirmed the ticket with S size.   This ticket is assigned to Laila to review and sign off after demo session on Monday 30/09/2024

D-021

9.TAPSS-2311

Confirmed the ticket with XS size.   This ticket is assigned to Laila to review and sign off after demo session on Monday 30/09/2024

#

Jira #

Discussion Summary

Action Owner

A-006

6. TAPSS-1862+3

There is scheduled minimum viable demo session on Monday 30/09/2024 for business SME to see visual indicator of the opportunity cultivation stage requirements. Any questions raised will be answered and addressed accordingly and it will help to review and sign-off the requirements with clear understanding.

@seonah.choe

@laila.valterio

A-007

TAPSS-2315

There is an existing validation rule to update ‘Ask Amount’ when moving to Solicitation stage but not when moving to ‘Gift-Handover’. During the above demo session or a separate discussion, we want to review any business intention in this logic and decide on the next step.

@seonah.choe

A-008

8. TAPSS-2312

As we are changing the existing logic on creating opportunity, there will be a task to highlight this change to the business user via communication and training. Relevant screenshot will be provided by Product team

@seonah.choe

A-009

N/A

Provide the current picklist value of Prospect Pool in the related group chat. Any potential enhancement requests from this will be priotised and go through refinement session process as usual. (Completed)

@seonah.choe

A-010

N/A

Set up a meeting with John to go through Jira status and cadence after internal confirmation.

@Adriana Sung

#

Jira #

Discussion Summary

D-012

1. TAPSS-2184

Confirmed the ticket to be ‘ready’ with M size, Must Have priority.  This ticket will now move to the future Sprint Planning session

#

Jira #

Discussion Summary

D-009

TAPSS-1873 & +2

This is one of Q3 priorities that the team is focusing on. 1 big ticket is now broken down to 3 tickets and assigned to @laila.valterio for review & sign off for next available sprint.

D-010

TAPSS-2144

This ticket will move to ‘Marketing Automation’ board and will be picked up by MA team.

D-011

TAPSS-2160

There was a positive progress for AQ upgrade. Product team (Sarah, Rommel and Jing) conducted a series of testing with manual steps as well as confirmed with Salesforce support team to unblock the upgrade item and the team will align the platform sandbox refresh schedule with next upgrade step to progress further.

#

Jira #

Action Summary

Action Owner

A-005

TAPSS-1873 & +2

Laila to review 3 tickets for sign-off. Sarah and Rommel to provide any guidance and/or clarification if required.

@laila.valterio @seonah.choe @rommel.ngo

#

Jira #

Discussion Summary

D-006

TAPSS-2143

This ticket officially move to ‘Marketing Automation’ board and will be picked up by MA team.

D-007

TAPSS-2142

This ticket will be a part of further actions to be set for Activity roadmap. Further discussions with Api, Gaurang and Laila will be held in near future.

D-008

TAPSS-1873

This is one of Q3 priorities that the team is focusing on. The overall requirement in the ticket is aligned and size of the ticket is estimated as size 'M'.

We need to perform further analysis on 1) Persona 2) Overall page layout change matrix 3) Align the testing procedure 4) Align with business end user testing.

The team will prioritize to complete these tasks and verify with Laila with sign off for next available sprint.

If there are any business gap for opportunity uplift, we will set some time with Laila early next week to address and discuss.

#

Jira #

Action Summary

Action Owner

A-003

TAPSS-1873

Created sub tasks for Opportunity page layout enhancement and work on them (Done)

@seonah.choe

A-004

TAPSS-1873

Go through the current opportunity epic including cultivation and set up a session with Laila to address any potential gaps

@rommel.ngo @seonah.choe

#

Jira #

Discussion Summary

D-001

TAPSS-2143

Concern was raised for this requirement that defaulting ‘active’ will create active records without mail address, ultimately creating a similar problem for inconsistent data records.  Also, the solution of creating a new flow is not preferable for the business.

 Decided to park the ticket, focus on the training the users, and monitor this function with Marketing Automation (MA) stream.

+++

 Later the same day during the Enhancement Review session, another feedback was discussed:

Since the current interface for Lead conversion as well as AQ Account creation requires users to revisit the created Account records to update the address status even though address values are there, it will be worthwhile to re-visit this requirement for refinement. This kind of extra step usually cause more user errors as they have to manually check these details every time.

It was decided to revert the status to Refine and schedule for revisit in the future.

D-002

TAPSS-2124

Confirmed the ticket to be ‘ready’ with XS size, Could Have priority.  This ticket will now move to the future Sprint Planning session

D-003

TAPSS-2129

This requirement will also resolve another existing issue of already closed case with new enquiry not re-triggering case to open, as it will notify the team to look at.

Potential risk is raised that team might be receiving too many emails for notification; however, the volume of the notification will not be large, so risk is small.

Confirmed the ticket to be ‘Ready’ with S size, Should Have priority. .  This ticket will now move to the future Sprint Planning session

D-004

TAPSS-2132

Confirmed the ticket to be ‘Design’ with size 'M' for Sekar to review.

There is a current gap for the future point of contact for Spend Plan and we need to address this gap first.

D-005

TAPSS-2142

This is a part of ongoing discussion, and we will continue to refine.

#

Jira #

Action Summary

Action Owner

A-001

TAPSS-2132

Gaurang to have discussion with Api to confirm the future end users and future point of contact for Spend Plan.

@gaurang.fichadia

A-002

TAPSS-2142

Rommel to share the Activity field type migration impact analysis with Api and Laila for further discussion.

@rommel.ngo