13/09/2024 Friday
Participants: laila.valterio jessica.wood sekar.krishnan rommel.ngo jing.xie seonah.choe gaurang.fichadia John Lardis
Jira Tickets discussed in the session:
TAPSS-2184 Funds Received Flag fix - Gift in Kind
Decisions
# | Jira # | Discussion Summary |
D-012 | Confirmed the ticket to be ‘ready’ with M size, Must Have priority. This ticket will now move to the future Sprint Planning session |
23/08/2024 Friday
Participants: laila.valterio jessica.wood sekar.krishnan rommel.ngo jing.xie seonah.choe
Jira Tickets discussed in the session:
[TAPSS-1873] Gift/Pledge Opportunity Pagelayout Enhancement 1 - JIRA (atlassian.net)
[TAPSS-2144] Account Alternative Channel Update Issue - JIRA (atlassian.net)
Decisions
# | 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 | This ticket will move to ‘Marketing Automation’ board and will be picked up by MA team. | |
D-011 | 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. |
Actions
# | 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. |
16/08/2024 Friday
Participants: laila.valterio jessica.wood sekar.krishnan rommel.ngo jing.xie seonah.choe
Recording Link
Jira Tickets discussed in the session:
TAPSS-2143 Default picklist value for Mailing Address Status on Contact/Account to "Active"
TAPSS-2142 Activity Report field "Results" is a rich text box to be migrated to Salesforce Activity constraints
TAPSS-1873 Gift/Pledge Opportunity page layout Enhancement
Decisions
# | Jira # | Discussion Summary |
D-006 | This ticket officially move to ‘Marketing Automation’ board and will be picked up by MA team. | |
D-007 | 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 | 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. |
Actions
# | Jira # | Action Summary | Action Owner |
A-003 |
| ||
A-004 | Go through the current opportunity epic including cultivation and set up a session with Laila to address any potential gaps |
09/08/2024 Friday
Participants: laila.valterio jessica.wood gaurang.fichadia sekar.krishnan rommel.ngo jing.xie seonah.choe
Recording Link
Jira Tickets discussed in the session:
TAPSS-2143 Default picklist value for Mailing Address Status on Contact/Account to "Active"
TAPSS-2124 Prevent Receipt from being sent more than once
TAPSS-2129 Notification to case owner when a case has been updated
TAPSS-2132 Only the owner can submit a spend plan
TAPSS-2142 Activity Report field "Results" is a rich text box to be migrated to Salesforce Activity constraints
Decisions
# | Jira # | Discussion Summary |
D-001 | 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 | 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 | 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 | 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 | This is a part of ongoing discussion, and we will continue to refine. |
Actions
# | Jira # | Action Summary | Action Owner |
A-001 | Gaurang to have discussion with Api to confirm the future end users and future point of contact for Spend Plan. | ||
A-002 | Rommel to share the Activity field type migration impact analysis with Api and Laila for further discussion. |