Reference

JANE reference material

Detail that sits outside the core learning flow: governance, the full field list, filters and dashboards, and the glossary.

Statuses

Statuses in JANE with their meaning
#	Status	Meaning
1	New	When a Change Request has been created by a Business Owner (or SPOC).
2a	Form Incomplete	The Change Request is not complete and action from the BO is required.
2b	Ready for Intake	The information on the Change Request is complete.
3	Intake Ongoing	After the Change Intake Forum (CIF), the value and cost need to be validated.
4	Analysis	The Business Analyst (or Product Owner) is analysing the Change Request.
5	Planning	The Change Request is being planned by the driver.
6	Design	The driver designs the solution.
7	Development	The developing partner is currently developing the solution.
8	Post go-live	The solution is monitored during hypercare.

Governance detail

Standard Change (Medium or Large)

Transformation resources drive the change and involve Product Owners when relevant.
Transformation resources allocated.
Formal governance with Core project meeting, validation at Domain SteerCo’s and prioritisation at the QBR.

Examples: Integrate Tracy; Ticketing system; SLA Pro & Premium.

Small Change

The Product Owner drives the change.
No transformation resources allocated.
Limited governance; regular alignments between BO and PO are sufficient.

Examples: add a flag in Marlin; backend changes to a dashboard; add an additional validation step in a build process.

Criteria for lighter governance

No material analysis effort needed to clarify business requirements and solution design.
No need to consolidate feasibility from multiple Product Owners.
No project plan to elaborate.
No formal training and communication to be foreseen.
Limited number of stakeholders to manage.

IT definition for a small change (8 criteria, with TSS)

Formally logged — Measuring provides insight; to ensure quality and properly manage expectations, even minor requests must be formally logged.
Limited scope — Single application impact, no new applications, no new or updated IT integrations between systems.
Small size and fast delivery — Epic size XS or S, deliverable within a single month.
Limited stakeholder and coordination impact — Fully managed by PO/BO; no Partners, Servco's or cross-team dependencies.
Single team impact — Affects only one team; no consolidation of feasibility across multiple Product Owners.
No significant process or training impact — No training, communication or BPV testing required; validated by the Business Owner.
Reduced or no risk — No complex deployment; not linked to ongoing or funnel Demand Cockpit items; no multiple smalls for the same topic or application.
Business-approved solution — Impact and solution validated by the business before intake.

Forums and validation

For all Change Requests, Small or Standard, the Business Owner (or a designated Business SPOC) has the responsibility to request the Change Request. The Domain SteerCo validates the problem statement of the Business Owner and can optionally validate the implementation plan. The SLT selects the list of Change Requests to be started, and the Transformation Lead allocates the most appropriate resources.

Roles at a glance

Business Owner

Requesting the Change Request — for both Small and Standard Changes.

SPOC

Business SPOC

Logging the Change Request when the Business Owner delegates it.

Product Owner

Product impact on the organisation, roadmap management, change implementation and testing.

Business Analyst

Analysing the Change Request during the Analysis status.

Project Manager

Planning product changes and validating the implementation plan.

Implementation Manager

Supporting the implementation of the change during Development, together with the Product Owner and Project Manager.

Transformation Lead

Allocating the most appropriate resources (PM, BA, …) to the selected Change Requests.

Domain Expert

Contributing domain knowledge during Intake and Analysis.

Key fields in a Change Request

Key JANE fields, who fills them in and when
Field	When	Who	In the form	Requirement	Context
Summary	Logging	BO	Yes	Mandatory	Title of the Change Request.
Description	Logging	BO	Yes	Mandatory	Context and information of the Change Request.
Desired outcome of the Change Request	Logging	BO	Yes	Mandatory	Requested TO BE state.
Approval Domain SteerCo?	Logging	BO	Yes	Mandatory	Domain SteerCo approval is mandatory for logging, unless sponsored by SLT.
SLT Sponsor	Logging	BO	Yes	Mandatory if SLT Sponsor	Used when the Change Request was not approved by the Domain SteerCo.
Business Owner	Logging	BO	Yes	Mandatory	The Business Owner adds their own name.
Business SPOC	Logging	BO	Yes	Mandatory	If there is no SPOC, the BO is the SPOC.
Change for the WHS Customer	Logging	BO	Yes	Mandatory	Which WHS Customer is impacted.
Origin of the Change Request	Logging	BO	Yes	Mandatory	Internal, regulator or WHS Customer.
Risks and dependencies	Logging	BO	Yes	Mandatory	Risks if the change is not done, and risks to consider if it is.
Values 1–5 (EBITDA, CAPEX, customer satisfaction, penalties, FTTH CP delivery)	Logging	BO	Yes	Mandatory	Are these KPIs impacted? A motivation is required where there is impact.
Requested timeline + justification	Logging	BO	Yes	Optional	When delivery is requested and why.
Product Owner	During the lifecycle	Driver	Yes	Mandatory for Small Change	Which Product Owner(s) are involved.
Status	During the lifecycle	Driver	No	—	Updated throughout the lifecycle to indicate where the Change Request is.
Assignee	After QBR	Driver	No	—	The driver is the assignee of the Change Request.
Status context	During the lifecycle	Driver	No	—	RAG status: why is this Change Request Red, Amber or Green?
Budget forecast / actual budget	During the lifecycle	Driver	No	—	Used for KPI tracking.
Forecast / actual delivery date	During the lifecycle	Driver	No	—	Used for KPI tracking.
Deliverables (and per quarter)	During the lifecycle	Driver	No	—	List of deliverables during the lifecycle and per quarter.

Filters and dashboards

The project navigation contains Backlog, Change Req Board, List, Forms, Components, Releases and Reports.
Filter on any field in the Change Request ticket — for example the SLT Member — and combine filters.
Saved filters are available on the right side of the screen; you can also save the current filter there.
Useful dashboard gadgets: Filter Results, Pie Chart / Two-Dimensional Statistics, and Created vs. Resolved.
Share dashboards with your team via Share in the top-right corner.

Filter guideline

IS / IS NOT — Check whether a field is empty or has a value, for example assignee is not EMPTY.
= — Exact match on a single value.
IN — Match any value from a list.
AND / OR — Combine filters into one query.

Glossary

BO: Business Owner — requests and logs the Change Request.
SPOC: Business SPOC — colleague designated by the BO to log the Change Request.
PO: Product Owner — responsible for a product; drives Small Changes.
BA: Business Analyst — analyses the Change Request; can be the driver.
PM: Project Manager — plans and steers implementation; can be the driver.
IM: Implementation Manager — supports implementation during Development.
TL: Transformation Lead — allocates PM, BA and other resources to selected Change Requests.
DE: Domain Expert — provides domain input; validation leads to the validated value score.
SLT: Senior Leadership Team — selects Change Requests to be started; an SLT Sponsor can sponsor a request.
TCE: Abbreviation used in the Wyre source deck. Meaning not defined in the source — flagged for review by the Transformation Team.
PMO: Project Management Office. Its exact remit is not defined in the source deck — flagged for review.
CRQ: Unique Change Request number of a ticket in JANE.
CIF: Change Intake Forum — after the CIF, value and cost need to be validated.
QBR: Quarterly Business Review — where Change Requests are prioritised and selected.
SteerCo: Domain Steering Committee — validates the problem statement of the Business Owner and approves Change Request logging.
TSS: Technology and shared services landscape that JANE integrates with; TSS co-defined the 8 IT criteria for a small change.
WHS: Wholesale customer of Wyre, impacted by many Change Requests.
RAG: Red / Amber / Green status context on a Change Request.
SiD: The tool used to request access to JANE.