Scheduling Policies and Configuration Management Plans

UPI Study › Courses › Software Engineering › Free lessons › Lesson 14.3 Free with a free account

Scheduling Policies and Configuration Management Plans

Software Engineering · Chapter 14: Project Estimation, Configuration, and Change ControlSection 14.3 · lesson 88 of 1036 min · free with a free account

← Building Quality into Software Through Management SystemsNext lesson: Configuration Management Processes →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Controlling how and when change arrives, so the schedule stays meaningful.

  • Explain why schedules need configuration management policy
  • Describe what an SCM plan contains
  • Distinguish freeze periods, change windows, and escalating approval
  • Explain baselines as the meeting point of schedule and configuration

Transcript

Everything said in the video, section by section (842 words). Read along, or search it.

Project Estimation, Configuration, and Change Control

Scheduling Policies and Configuration Management Plans

An estimated schedule assumes a certain amount of stability in what is being built. But requirements, designs, and code keep changing anyway. This section covers how configuration management controls when that change gets incorporated, so an estimate stays meaningful.

A Moving Target

Why Schedules Need Change Policy

A schedule built from estimation techniques assumes that the target it was estimating stays reasonably stable. But requirements, designs, and code continue to change throughout a real project. Change itself is not the problem. Embracing change can be a genuine strength. The problem is change with no policy governing how, and when, it gets incorporated. If the target keeps shifting right up to the deadline, nobody can commit to a date. Configuration management supplies exactly that discipline.

The SCM Plan

What the Plan Establishes

A configuration management plan, or S C M plan, is a planning-level document. It is not a step-by-step procedure for handling any one change. It identifies which artifacts, like code, documentation, requirements, and test plans, are formally placed under configuration control. It defines who has the authority to approve which kinds of change. It establishes the general approach for how changes are requested, evaluated, and incorporated. And it sets the policy for when, relative to the schedule, different kinds of change are actually permitted.

Scheduling Policies

When Change Gets Allowed

A few recurring policy patterns govern what change is allowed, at any given point in the schedule. A change window designates specific points, between iterations or at a milestone, where less urgent changes are batched and reviewed together. A freeze period restricts changes to only the most critical ones, as a milestone or release approaches. That protects the stability the deadline depends on. And escalating approval requires increasingly senior sign-off for a change as a committed date nears. That is because the cost and risk of any change grows, the less time remains to absorb its consequences.

Figure 1

Restriction Tightens Toward the Deadline

Here is one schedule, running from project start to release, with three change policies. Early on, the schedule is open, and most changes are freely accepted. Then comes a change window, where changes are batched and reviewed together. Then a baseline is set, and the freeze begins. Only critical changes are allowed from there to the release. And all the way across, approval requirements escalate as the deadline gets closer.

Worth Noticing

The Cost of Change Isn't Constant

This connects to a point made about the sequential approach, at the start of this course. The cost of a change is not constant across a schedule. It grows the later the change arrives. Treating every change request as equally easy to accommodate, regardless of timing, ignores that reality. And that is precisely why scheduling policies exist.

Baselines

Where Schedule and Configuration Meet

A baseline is a formally reviewed, agreed-upon snapshot of a set of configuration items, at a specific point in time. It becomes the reference point for measuring any further change. Once something is baselined, changing it means going through the formal change process, rather than editing it freely. And baselines are typically set at points that align with the schedule, like the end of a phase, or a major milestone. That makes a baseline both a scheduled event, and a configuration management concept, at the same time.

Table 1

4 Policies and Their Timing

Here are the four policies, and when each one typically applies. A freeze period restricts changes to critical or high-priority ones, as a release or major milestone approaches. A change window batches and reviews less-urgent changes together, at defined points between milestones or iterations. Escalating approval requires broader sign-off for changes, increasing as a committed date nears. And a baseline formally locks a reviewed snapshot as the reference point, at the end of a phase or a major milestone.

Apply It

A Tweak 2 Weeks Before Release

Let's apply that. Two weeks before release, during the freeze, a stakeholder asks for a small, non-critical tweak to a screen. Because it is not critical, it is held for the next change window, where it is batched and reviewed with other requests. If it were genuinely critical, it could still go ahead. But it would need senior, escalated approval, and it would go through the formal change process against the baseline.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. An S C M plan is a planning-level document identifying what is under configuration control, who approves changes, and when changes are permitted. A configuration item is an artifact, like code, documentation, a requirement, or a test plan, that is formally placed under configuration control. A freeze period is a window of time, typically near a milestone or release, during which only critical changes are permitted. And a baseline is a formally reviewed snapshot of configuration items, serving as the reference point for all further change.

Key Takeaways

What to Carry Forward

To pull this together. Without a change policy, an estimated schedule quietly becomes fiction. An S C M plan sets what is under control, who approves changes, how changes are handled, and when they are permitted. Change windows batch less urgent changes. Freeze periods restrict change near a release. And approval escalates as deadlines near. All of this exists because the cost of a change grows as the deadline approaches. And a baseline is where schedule and configuration meet, as both a scheduled event and a configuration reference.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Scheduling Policies and Configuration Management Plans

What is a software configuration management plan?
A software configuration management (SCM) plan is a planning-level document that sets how change is controlled on a project. It identifies which artifacts, such as code, requirements, documentation, and test plans, are under configuration control, defines who can approve which kinds of change, outlines how changes are requested and evaluated, and sets when different kinds of change are permitted relative to the schedule.
What is the difference between a freeze period and a change window?
A freeze period restricts changes to only the most critical ones as a milestone or release approaches, while a change window is a designated point, such as between iterations, where less urgent changes are batched and reviewed together. Freezes protect the stability a deadline depends on. Change windows give non-urgent requests a predictable place to be considered.
Why does change approval get stricter as a release date approaches?
Approval escalates near a committed date because the cost and risk of a change grow as less time remains to absorb its consequences. Escalating approval therefore requires increasingly senior sign-off for changes late in the schedule. Treating every change request as equally easy regardless of timing ignores that reality, which is why scheduling policies exist.
How should a non-critical change request be handled during a code freeze?
A non-critical change requested during a freeze is usually held for the next change window, where it is batched and reviewed with other requests. A genuinely critical change can still proceed, but it typically needs escalated, senior approval and must go through the formal change process against the current baseline. This keeps the release stable without ignoring real problems.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →