00:01
Let's go through each statement one at a time.
00:04
So the statement, in the traditional way of software development, once the requirements are baselined, further changes should undergo a heavy change control process.
00:13
This is generally correct.
00:32
In traditional software development methodologies like the waterfall model, once requirements are finalized and baseline, making changes can be challenging and typically requires a formal change control process to ensure that changes are well documented, assessed for impact and approved.
00:49
The second statement, changes are acceptable until design, but once development starts, any further change should be rejected is not a typical practice in modern software development.
00:59
In many development methodologies, including agile, changes can be accommodated even after development has started.
01:06
Agile methodologies prioritize flexibility and responsiveness to changes in customer requirements...