GXD Progress.
THE CONSULTING
ORGANISATION, ENCODED.
THE CONSULTING
ORGANISATION, ENCODED.
THE CONSULTING
ORGANISATION, ENCODED.
GXD Progress is designed to connect requirements, specialist delivery work and validation in one system. Each stage has a clear responsibility, a defined output and a review before work moves on.
GXD Progress is designed to connect requirements, specialist delivery work and validation in one system. Each stage has a clear responsibility, a defined output and a review before work moves on.
01 / THE DELIVERY MODEL
01 / THE DELIVERY MODEL
SPECIALIST WORK. CONNECTED.
SPECIALIST WORK. CONNECTED.
SPECIALIST WORK. CONNECTED.
A business requirement is the starting point. Specialist capabilities develop the context, requirements, design, implementation and evidence needed to deliver it.
A business requirement is the starting point. Specialist capabilities develop the context, requirements, design, implementation and evidence needed to deliver it.
ILLUSTRATIVE DELIVERY MODEL · NOT A LIVE PROJECT RUN
ILLUSTRATIVE DELIVERY MODEL · NOT A LIVE PROJECT RUN
The model is designed to combine specialist synthetic-intelligence capabilities with senior human review. The roles below describe responsibilities and intended outputs.
The model is designed to combine specialist synthetic-intelligence capabilities with senior human review. The roles below describe responsibilities and intended outputs.
SPECIALIST CAPABILITY
RESPONSIBILITY
OUTPUT
DOMAIN EXPERT
DOMAIN EXPERT
Understand the organisation, its industry and the context of the requirement.
Understand the organisation, its industry and the context of the requirement.
A source-backed context brief, terminology, relevant constraints and open questions.
A source-backed context brief, terminology, relevant constraints and open questions.
Verified information is distinguished from assumptions. Public research does not establish the client’s internal processes or final compliance requirements.
Verified information is distinguished from assumptions. Public research does not establish the client’s internal processes or final compliance requirements.
BUSINESS ANALYST
BUSINESS ANALYST
Turn the business request into clear requirements.
Turn the business request into clear requirements.
Process requirements, business rules, acceptance criteria and unresolved questions.
Process requirements, business rules, acceptance criteria and unresolved questions.
CONSULTANT
CONSULTANT
Assess the requirement against available Salesforce capabilities.
Assess the requirement against available Salesforce capabilities.
A functional approach, standard-capability assessment and options requiring a decision.
A functional approach, standard-capability assessment and options requiring a decision.
ENTERPRISE ARCHITECT
ENTERPRISE ARCHITECT
Check how the change fits the wider technology landscape.
Check how the change fits the wider technology landscape.
System boundaries, data ownership, integration dependencies and enterprise-level decisions.
System boundaries, data ownership, integration dependencies and enterprise-level decisions.
UX/UI
UX/UI
Examine how people will use the proposed solution.
Examine how people will use the proposed solution.
User journeys, interaction requirements and usability considerations.
User journeys, interaction requirements and usability considerations.
SALESFORCE ARCHITECT
SALESFORCE ARCHITECT
Translate the agreed requirements into a coherent Salesforce design.
Translate the agreed requirements into a coherent Salesforce design.
Data, access, automation and integration design, with recorded technical decisions.
Data, access, automation and integration design, with recorded technical decisions.
BUILDER
BUILDER
Implement against the approved design.
Implement against the approved design.
Implementation changes and the information needed to review and release them.
Implementation changes and the information needed to review and release them.
Production deployment requires the appropriate review and approval; it is not represented as autonomous.
Production deployment requires the appropriate review and approval; it is not represented as autonomous.
TESTER
TESTER
Check the implementation against the original requirement and acceptance criteria.
Check the implementation against the original requirement and acceptance criteria.
Test cases, recorded execution results where available, defects and outstanding validation.
Test cases, recorded execution results where available, defects and outstanding validation.
A proposed test is not an executed test. Generated test cases are not evidence of a passing implementation.
A proposed test is not an executed test. Generated test cases are not evidence of a passing implementation.
02 / FOLLOW ONE REQUIREMENT
02 / FOLLOW ONE REQUIREMENT
SEE WHAT THE HANDOFFS PRODUCE.
SEE WHAT THE HANDOFFS PRODUCE.
SEE WHAT THE HANDOFFS PRODUCE.
ILLUSTRATIVE WORKFLOW
ILLUSTRATIVE WORKFLOW
Not a live project run.
Not a live project run.
“Assign new enquiries to the appropriate admissions team and make routing exceptions visible.”
“Assign new enquiries to the appropriate admissions team and make routing exceptions visible.”
“Assign new enquiries to the appropriate admissions team and make routing exceptions visible.”
A / REQUIREMENT
A / REQUIREMENT
Starting point for design
Starting point for design
BUSINESS RULE
BUSINESS RULE
Use the enquiry’s selected school to determine the responsible admissions team.
Use the enquiry’s selected school to determine the responsible admissions team.
ACCEPTANCE CRITERION
ACCEPTANCE CRITERION
If no valid routing match exists, record an exception rather than silently assigning an unrelated team.
If no valid routing match exists, record an exception rather than silently assigning an unrelated team.
OPEN QUESTION
OPEN QUESTION
Who owns the exception queue?
Who owns the exception queue?
B / DESIGN REVIEW
B / DESIGN REVIEW
Decision open · not approved
Decision open · not approved
REVIEW CONSIDERATIONS
REVIEW CONSIDERATIONS
Where the school-to-team mapping is maintained.
Who can change that mapping.
What happens when a team is inactive.
How exceptions are recorded and reviewed.
Where the school-to-team mapping is maintained.
Who can change that mapping.
What happens when a team is inactive.
How exceptions are recorded and reviewed.
UNRESOLVED DECISION
UNRESOLVED DECISION
Exception queue ownership remains open.
Exception queue ownership remains open.
C / REVIEW AND REWORK
C / REVIEW AND REWORK
Return to design review
Return to design review
ILLUSTRATIVE FINDING
ILLUSTRATIVE FINDING
“The proposed default assignment conflicts with the agreed exception rule.”
“The proposed default assignment conflicts with the agreed exception rule.”
REQUIRED RESPONSE
REQUIRED RESPONSE
Revise the design before implementation proceeds.
Revise the design before implementation proceeds.
D / VALIDATION
D / VALIDATION
Planned. Not executed.
Planned. Not executed.
PLANNED CHECKS
PLANNED CHECKS
A valid routing match.
A missing routing match.
An inactive destination team.
A duplicate submission.
An unauthorised attempt to change routing.
Multiple enquiries processed together.
A valid routing match.
A missing routing match.
An inactive destination team.
A duplicate submission.
An unauthorised attempt to change routing.
Multiple enquiries processed together.
03 / OVERSIGHT THROUGHOUT DELIVERY
03 / OVERSIGHT THROUGHOUT DELIVERY
THE WORK MOVES.
THE CONTROLS STAY WITH IT.
THE WORK MOVES.
THE CONTROLS STAY WITH IT.
THE WORK MOVES.
THE CONTROLS STAY WITH IT.
PROGRAMME MANAGEMENT
PROGRAMME MANAGEMENT
Programme Management follows the work across stages, dependencies and decisions. Daily reporting should reflect recorded progress and unresolved issues, not an optimistic summary.
Programme Management follows the work across stages, dependencies and decisions. Daily reporting should reflect recorded progress and unresolved issues, not an optimistic summary.
REPORT CATEGORIES
REPORT CATEGORIES
What moved.
What is blocked.
Which decisions are needed.
What failed review.
What happens next.
What moved.
What is blocked.
Which decisions are needed.
What failed review.
What happens next.
SECURITY & COMPLIANCE
SECURITY & COMPLIANCE
Security & Compliance reviews requirements, designs and changes against applicable client controls. Findings remain attached to the work until they are resolved or an exception is approved.
Security & Compliance reviews requirements, designs and changes against applicable client controls. Findings remain attached to the work until they are resolved or an exception is approved.
AREAS CONSIDERED
AREAS CONSIDERED
Access.
Data handling.
Privacy.
Client standards.
Required approvals.
Recorded exceptions.
Access.
Data handling.
Privacy.
Client standards.
Required approvals.
Recorded exceptions.
04 / THE DELIVERY RECORD
04 / THE DELIVERY RECORD
FROM THE ORIGINAL REQUEST
TO THE ACCEPTANCE EVIDENCE.
FROM THE ORIGINAL REQUEST
TO THE ACCEPTANCE EVIDENCE.
FROM THE ORIGINAL REQUEST
TO THE ACCEPTANCE EVIDENCE.
The intended result is a connected delivery record: what was requested, what was decided, what changed and how it was checked.
The intended result is a connected delivery record: what was requested, what was decided, what changed and how it was checked.
REQUIREMENTS
REQUIREMENTS
Original request, business rules and agreed acceptance criteria.
Original request, business rules and agreed acceptance criteria.
DESIGN
DESIGN
Reviewed approach, dependencies and decision records.
Reviewed approach, dependencies and decision records.
IMPLEMENTATION
IMPLEMENTATION
Changes made, their relationship to the design and any outstanding exceptions.
Changes made, their relationship to the design and any outstanding exceptions.
VALIDATION
VALIDATION
Tests performed, actual results, defects and remaining acceptance work.
Tests performed, actual results, defects and remaining acceptance work.
05 / CONTINUITY INTO GXD GUARDIAN
05 / CONTINUITY INTO GXD GUARDIAN
KEEP THE KNOWLEDGE USEFUL.
KEEP THE KNOWLEDGE USEFUL.
KEEP THE KNOWLEDGE USEFUL.
The requirements, decisions and validation record remain useful after delivery. The GXD model connects that delivery context with Librarian, the knowledge core within GXD Guardian, to support subsequent change.
The requirements, decisions and validation record remain useful after delivery. The GXD model connects that delivery context with Librarian, the knowledge core within GXD Guardian, to support subsequent change.
This is the intended relationship between the products; automatic synchronisation has not been established.
This is the intended relationship between the products; automatic synchronisation has not been established.
06 / LET’S TALK
06 / LET’S TALK
WHAT OUTCOME ARE YOU TRYING TO ACHIEVE?
WHAT OUTCOME ARE YOU TRYING TO ACHIEVE?
WHAT OUTCOME ARE YOU TRYING TO ACHIEVE?
TECHNOLOGY
CONSULTING.
REBUILT.
TECHNOLOGY
CONSULTING.
REBUILT.