Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

TAPSS Refinement Sessions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

27/09/2024

Participants: laila.valterio Adriana Sung rommel.ngo jing.xie seonah.choe John Lardis

Recording Link

Observation/Feedback:

  • We are currently exploring right channels to share prioritized managed package upgrade progress (eg Affinaquest version upgrade) with our business product owner. It was discussed to have a separate session for managed package upgrade while refinement session can be focused on enhancement prioritieis such as minor enhancements, opportunities and/or activities.

  • Clear definition of Jira ticket status and purpose of each meeting around refinement, sprint planning, sprint review will be helpful for everyone so we all can work with the consistent languages and terminology and share the same understanding.

  • Importance of capacity for high priorities are stressed in the meeting so we are focusing on the priority items.

Jira Tickets discussed in the session:

  1. TAPSS-2305 AQ 26: Gift/Pledges

  2. TAPSS-2304 AQ 26: Gift Date and Credited Year GA Managed Package - Blackthorn Payments

  3. TAPSS-2303 AQ 26: Smart Batch 2.0

  4. TAPSS-2301 AQ 26: Smart Batch 2.0 Permission GA Security - Profiles and Permissions

  5. TAPSS-2016 AQ 26: SmartBatch 2.0 soft credits on Batch Item Transaction need to adjust Batch Approval Reports GA

  6. TAPSS-1862 As a Development Officer, I want to have my opportunity stage to be Early Cultivation or Late Cultivation

  7. TAPSS-2314 As a Development Officer, I want to update Prospect Pool 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-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

Decisions

#

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

  1. TAPSS-2304

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

D-015

  1. TAPSS-2303

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

D-016

  1. TAPSS-2301

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

D-017

  1. TAPSS-2016

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

D-018

  1. 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

  1. 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

  1. 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

Actions

#

Jira #

Discussion Summary

Action Owner

A-006

  1. 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

  1. 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

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:

  1. TAPSS-2184 Funds Received Flag fix - Gift in Kind

Decisions

#

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

23/08/2024 Friday

Participants: laila.valterio jessica.wood sekar.krishnan rommel.ngo jing.xie seonah.choe

Jira Tickets discussed in the session:

  1. [TAPSS-1873] Gift/Pledge Opportunity Pagelayout Enhancement 1 - JIRA (atlassian.net)

    1. [TAPSS-2177] Gift/Pledge Opportunity Pagelayout Enhancement 2 - Stage Keyfields & Persona - JIRA (atlassian.net)

    2. [TAPSS-2178] Gift/Pledge Opportunity Pagelayout Enhancement 3 -Unchanged pagelayout&Validation Rule - JIRA (atlassian.net)

  2. [TAPSS-2144] Account Alternative Channel Update Issue - JIRA (atlassian.net)

  3. [TAPSS-2160] AQ Upgrade Plan B: Deactivate Campaign Influence and manually update in a sandbox - 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

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.

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.

laila.valterio seonah.choe rommel.ngo

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:

  1. TAPSS-2143 Default picklist value for Mailing Address Status on Contact/Account to "Active"

  2. TAPSS-2142 Activity Report field "Results" is a rich text box to be migrated to Salesforce Activity constraints

  3. TAPSS-1873 Gift/Pledge Opportunity page layout Enhancement

Decisions

#

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.

Actions 

#

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

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:

  1. TAPSS-2143 Default picklist value for Mailing Address Status on Contact/Account to "Active"

  2. TAPSS-2124 Prevent Receipt from being sent more than once

  3. TAPSS-2129 Notification to case owner when a case has been updated

  4. TAPSS-2132 Only the owner can submit a spend plan

  5. TAPSS-2142 Activity Report field "Results" is a rich text box to be migrated to Salesforce Activity constraints

Decisions

#

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.

Actions 

#

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

 

  • No labels