Content Comparison

Objectives of the Workshop:

Items

• Values and Culture

  • What sort of team are we trying to build?

...

• How are we going to get there?

• Meeting Participants and cadence

  • Standups ( 2 per week)

  • ICT Daily

  • Refinement

  • Planning

• What is the process when a new requirement/request comes up?

  • Is Bug?

  • Is Request?

  • Is Valid?

    • Is Aligned?

    • Is fit for purpose/solvable?

  • Is Vendor Responsible?

...

• Adopt over Adapt - Structure business processes around “out of the box” functionality (bend the process to the system not the other way around)

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

Items

• Values and Culture

  • What sort of team are we trying to build?

...

• How are we going to get there?

• Meeting Participants and cadence

  • Standups ( 2 per week)

  • ICT Daily

  • Refinement

  • Planning

• What is the process when a new requirement/request comes up?

• Is Bug?

• Is Request?

• Is Valid?

  • Is Aligned?

  • Is fit for purpose/solvable?

Is Vendor Responsible?

Examples

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

...