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

Ways of Working/Framework Placeholder

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 8 Next »

Example Stories

TAPSS-1660 - Getting issue details... STATUS

TAPSS-1663 - Getting issue details... STATUS

1

Five Dysfunctions of a team

https://learning.oreilly.com/library/view/overcoming-the-five/9780787976378/

2

Empathy Triangle (Love/Power/Truth)

https://www.youtube.com/watch?v=F8swPODqGGg

Items

  • Meeting Participants and cadence

  • Values and Culture

  • Approach to Design

    • Adopt over Adapt - Structure business processes around “out of the box” functionality

    • Clicks over Code - Exhaust declarative configuration options before attempting programmatic customisation

    • Reuse and Simplify - Think of the system as a whole and understand where repeated functionality can be avoided

    • Optimise data - Establish the right database structure and relationships using standard objects before custom

    • Integrate efficiently - Transform and orchestrate in the integration layer

    • Code well - Design with efficiency, minimisation and reuse in mind; robustly test and deploy. Ensure good practices such as abstraction and avoidance of tight-coupling components.

    • Don’t over-engineer -Don’t ask the platform to perform beyond its capabilities by building complex processes using tools and features not designed for it.

  • Overarching Principles

    • Stabilise: The platform to reduce technical debt

    • Simplify and Standardise: The Processes and Technology

    • Scale: Build capability to enable growth and value

Examples

  • Example of a record with the same phone number in seven different fields

  • Example validation rules on the opportunity object

  • Lightning Utilities

Laila Thoughts/Handover Process

  • Triage process

  • Tracking of ‘stops and starts on projects’ i.e timesheets impact to efficiency and dollar value

  • Who is are contact point if something has changed and how will communicate changes e.g. Tina personal folders in Jarvis (the ones that Pat set up when you start)

  • Etiquette around escalations (The ticket owner should be aware - transparency and visibility)

  • When there is agreement on work e.g q4 need to receive a ‘report’ that shows division of work. Whether this is extracted from Jira or elsewhere I need to show the business where the tickets are coming from. e.g opps definition but which tickets went through that quarter under what classification. Not broad specific. Did the CS have the most tickets for example.

  • No labels