![]() And good configuration management practices allow the team to reconstruct accurately any previous baseline and all its components. Typically, a baseline is also given a unique name so that all the project participants can refer to it unambiguously. ![]() That planned functionality is the baseline. Once the project team establishes a requirements baseline, the team should follow a pragmatic change control process to make good business and technical decisions about adding newly-requested functionality and altering or deleting existing requirements.Ī change control process is not about stifling change it’s about providing decision-makers with the information that will let them make timely and appropriate decisions to modify the planned functionality. When stakeholders “sign-off” on requirements, what they’re really doing is agreeing and committing to a specific requirements baseline (whether they think of it in those terms or not). That “release” could be a complete delivered product or any interim development increment of the product. ![]() A requirements baseline is a snapshot in time that represents an agreed-upon, reviewed, and approved set of requirements that have been committed to a specific product release.
0 Comments
Leave a Reply. |