Jump to content


Why Approved Change Request Input For Control Scope, But Change Request Output For Control Schedule

Scope Management Time Management

  • Please log in to reply
No replies to this topic

#1 Kaushik Purohit

Kaushik Purohit

    New Member

  • Members
  • Pip
  • 2 posts

Posted 19 July 2015 - 09:10 PM

Why Approved Change request is input for Control scope process, but Change request is output for Control Schedule process


The only tool for Control scope is 'Variance Analysis'. As it compares the data with current scope baseline, it in effect does impact analysis of the scope change(variance), which can be an important input to whether to approve the change or not(correct me if I am wrong).


If so, this variance analysis should be an input to Integrated Change Control process. Instead this process is executed after the change request is approved. Anyhow the plans are to be updated, then what is the use of doing Variance analysis anyways? You will not be taking any decision based on this analysis?


I guess I am going big time wrong somewhere. Please correct me.

Also tagged with one or more of these keywords: Scope Management, Time Management

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users