TAPSS Refinement Sessions

#

Jira #

Discussion Summary

D-006

TAPSS-2143

This ticket is 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

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