liveBook · Manning

Change request

A change request is a proposal to modify an existing system, requirement, service, process, or design, typically submitted for review or approval.

How 3 Manning books explain it

Shipping Go: Develop, deliver, discuss, design, and go again

An RFC is a written proposal for a software design or change that invites review and discussion before implementation.

How it is used
Prevents premature implementation by making designs reviewable before development.
How deep it goes
Explains the practice and repository placement but stops short of prescribing an RFC template or approval workflow.
Examples
Uses a rushed refactor and repository design documents as concrete examples.
What you can do after
Apply it by documenting a design in the repository and inviting discussion before writing the implementation.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains change request →

AI for Everyday IT

A change request is a formal IT document seeking approval to modify a system, service, or process.

How it is used
Uses change requests to seek approval for system or process updates and applies ChatGPT to speed up drafting.
How deep it goes
Defines the document and shows a prompt and structured draft, without detailing a complete approval or migration procedure.
Examples
Uses a proposed move of the DHCP role from a domain controller to a dedicated server, including expected client downtime.
What you can do after
Apply ChatGPT to draft a change request, then make small edits before submission.

Read how AI for Everyday IT explains change request →

Fundamentals of Cybersecurity

A request for change is a formal proposal describing a proposed system modification, its purpose, benefits, resources, risks, and rollback strategy.

How it is used
Starts the structured process for proposing and evaluating system changes.
How deep it goes
Specifies the proposal’s purpose, benefits, resources, risks, and rollback plan without prescribing a request format.
Examples
Uses patches for actively exploited vulnerabilities to illustrate emergency changes requiring documentation and review.
What you can do after
Apply it by documenting a proposed change, its rationale, resource needs, risks, and preliminary recovery strategy.

Read how Fundamentals of Cybersecurity explains change request →

Also covered in

What to know first

Related concepts

Questions about change request

What is change request?

A change request is a proposal to modify an existing system, requirement, service, process, or design, typically submitted for review or approval.

Which Manning books explain change request?

Shipping Go: Develop, deliver, discuss, design, and go again, AI for Everyday IT and Fundamentals of Cybersecurity.

What should I know before learning change request?

Manning books that teach change request usually introduce availability first.

What is change request a kind of?

Change request is a kind of design document. A design document is written material describing an intended software design, including its structure, technical decisions, rationale, constraints, or implementation considerations.

What is change request part of?

Change request is part of change management. Change management is the structured process of planning, guiding, coordinating, and controlling changes to organizations, systems, or processes.

What are the parts of change request?

Change request includes rollback plan.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.