Difference between Change Request Requirement vs. Business Rule / Functional requirements
I was trying to understand when to categorize a requirement under change control vs Business rule or Functional requirement. Seems like change control could fall into both business rules or functional requirements.
I'm including the training definitions below, but specifically between Change Control requirement and Functional requirement - aren't all change control requirements functional requirements?
I think the change control requirement would only be to manage additional scope after requirements are locked, but just wanted to confirm.
Business rule requirement identifies the rules that define, constrain, and enable organizational operations.
Change control requirement documents a modification needed for a Pega application. This modification may occur before or after release.
Functional requirement describes what a software system should do to meet the needs of the business.
Your third paragraph is actually correct :-) Although Change Control isn't always just additional scope, it could be a change/amendment in scope from what has been agreed as the baseline. Change controls can be any type of requirements (Functional, Non Functional etc). CR's are good practise within projects to ensure that you are tracking changes, have traceability and allow for a robust governance process (if changes were happening with no tracking, no-one would know what has changed, and there would be issues in testing/business acceptance testing). Usually each project would have a CR process, whereby when a CR is raised, it can be sent to the relevant impacted teams (may not just be Pega changes), to allow them to provide an impact assessment (ie time/cost/effort required for change).