Vision and Scope to Story Trace

Traced Stories

V&S#	Activity	Area	Requirement	Jira
FEA01	Draft	SITS	As ASR user, we need to understand why certain data are being overwritten by SITS integration so that we can avoid scenarios where a newer data is being reverted back to an older data Note: 5 to 8 contact fields Changes required on : All the integration needs to be assessed. (eg., Swift integration/connector and SITS integration)	TASK: All the integration needs to be assessed Need discussion with each teams in TAP about Accounts and Contacts Structure (Gift admin, Plan giving (Alain, Harpreet, Demelza), Donor relations (Keri, Harriet), Events team (Miranda)
FEA02	Draft	Process	As ASR user, we need a standard procedure documentation for the following: Understanding of where data is coming from and the validity of data before it is being overwritten manually or by integration Clear definition of conditions of Matching records so that everyone is aligned on how to Match records. Understanding of information requirement from GA team to avoid delays in processing Understand and document the definition of friend so that we know if they are contactable or not Validate if unsubscribe from Swift are brought back into Jarvis	AVE-46 - Getting issue details... STATUS
FEA03	Draft	AQ	As general user, we need understanding/clarity on the use of Account Type on account and why it is a required field but not in the account create screen As general user, we need to understand the functionalities behind Primary and Secondary contacts so that we can build some workflows on it As community giving user, we need just to focus on legal credit as opposed to high end donors
FEA04	Draft	Data cleanliness	As general user, we need to clean up data specially for corporations migrated from Advance where a dummy contact is attached but no primary contact is recorded so that the whole process does not fail specially on receipting. As general user, we want to clean up and review data imported into Jarvis from Sensis and do the necessary so that they stay up to date. As general user, we need to clean data so that there no relationship that don’t make sense such as a solicitor in a household account
FEA05	Draft	Jarvis	As general user, we need to see soft credits on contacts instead of on accounts so that we can directly associate them when looking at the contact record. (rommel.ngo need to understand Why? What is expected?) Need discussion with +Affinaquest. As general user, we need efficiencies to be introduced on how to manage exclusion campaigns as they are quite challenging especially to newer staff member who are not familiar with the growing number of exclusion campaigns As general user, we need to understand what each of the contact types are for and clean up the list sot that they are not ambiguous to users As general user, we need more robust reports that take into consideration activities based on faculty and giving for instance so that we can better target our constituents	AVE-18 - Getting issue details... STATUS AVE-16 - Getting issue details... STATUS AVE-32 - Getting issue details... STATUS
FEA06	Draft	Disconnected data	As ASR user, we need to understand how we can ingest data coming from faculties so that we can stay upto date As ASR user, we need a way to manage updating RTS which is currently manual and tedious
FEA07	Draft	OGC	As ASR user, we need to laisse with OGC and establish Privacy statements so that we may reabsorb information from relevant sources.
		Gift Admin