Talk:Change control

Just passing through. I don't see any original research here. Many unsourced statements, no original research. I would suggest changing the "original research" template to some other variety of "unsourced statements". MaxEnt 17:15, 15 June 2006 (UTC)

I'll agree. I don't see any original research here. But it is obvious that there's no cited sources. DRogers 19:48, 29 September 2006 (UTC)

Agreed, I've checked through and there is no original research, just uncited sources. I've removed it. 83.100.174.241 01:17, 19 January 2007 (UTC)

Change control applies to all aspects of business documentation, especially engineering and not specifically or especially software.Snance 15:26, 17 March 2007 (UTC)

I see the term Change Control, while a sub-component of the broader Change Management process being distinguished as follows: The incremental level of managing change based on version, revision, or release levels which directly associate the instance of change to a specific content in the life of a software configuration item. These levels are then used to track the occurances of change as the software configuration items are delivered/deployed into and across run-time environments. Lloyd Morgan (talk) 22:02, 23 July 2009 (UTC)

Merge

There is a confusing degree of overlap between different articles on change management on Wikipedia. See also:

• Change management (engineering)
• Requirements management

yutsi (talk) 19:21, 1 January 2026 (UTC)

@Yutsi: did you mean this to be a case for merging Change impact analysis into this page, or something else? Klbrain (talk) 09:10, 3 March 2026 (UTC)

Yutsi, do you still believe a merger is appropriate? If there's no further activity on this, then they're unlikely to be merged. Thebiguglyalien (talk) 07:37, 21 March 2026 (UTC)

I've removed the merge tags since this discussion is inactive. Thebiguglyalien (talk) 23:41, 15 April 2026 (UTC)