Our business requirements are broken out into POL (Policy) and PRO (Procedure) documents. A policy is a requirement as to what must be done, and a procedure is how it must be done. You could combine those as a PPRD or get creative if you want and figure out how to create some word out of it. Catchy acronyms are popular with managers. Another alternative would be a BR&O (Business Requirements and Objectives) similar to DR&O for design.
We typically use Functional Requirements or Business Objectives in-place of the BRD.
...
1 reply by NITIN MITTAL
Oct 30, 2019 8:26 PM
NITIN MITTAL
...
Thanks, Corey
Saving Changes...
NITIN MITTALSr. Project Manager - Professional Services| USADenver, Co, United States
Oct 30, 2019 4:42 PM
Replying to Kiron Bondale
...
Requirements package is something my current client came up with when they merged their old BRD with their system requirements specification.
You could also call it a requirements baseline or (if you were following an adaptive lifecycle) your product backlog.
Kiron
Thanks, Kiron!!!! Saving Changes...
NITIN MITTALSr. Project Manager - Professional Services| USADenver, Co, United States
Oct 30, 2019 5:32 PM
Replying to Keith Novak
...
Our business requirements are broken out into POL (Policy) and PRO (Procedure) documents. A policy is a requirement as to what must be done, and a procedure is how it must be done. You could combine those as a PPRD or get creative if you want and figure out how to create some word out of it. Catchy acronyms are popular with managers. Another alternative would be a BR&O (Business Requirements and Objectives) similar to DR&O for design.
Thanks, Keith!!!! Saving Changes...
NITIN MITTALSr. Project Manager - Professional Services| USADenver, Co, United States
Oct 30, 2019 5:45 PM
Replying to Corey Gill
...
We typically use Functional Requirements or Business Objectives in-place of the BRD.
Thanks, Corey Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
User Requirements Specification (URS) , User Stories Backlog (USB) , Requirements Specification (RS) , Requirements Documentation (RD)
...
1 reply by NITIN MITTAL
Oct 30, 2019 11:13 PM
NITIN MITTAL
...
Thanks Deepesh.
Saving Changes...
NITIN MITTALSr. Project Manager - Professional Services| USADenver, Co, United States
Oct 30, 2019 10:52 PM
Replying to Deepesh Rammoorthy
...
User Requirements Specification (URS) , User Stories Backlog (USB) , Requirements Specification (RS) , Requirements Documentation (RD)
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I fully recommend do not revinvent the wheel. Go to IEEE Std 828 ConOps (Concept of Operations) or go to IEEE Std 1233 SysReqs (where system is not software system) which is a boarder document. Inisde the standard you will find the template and the proposed process to get the template done, including it examples.On the other side, while is not an standard, search for Vision document. Just to remember: project manager is on charge of project requirements not product requirements. Saving Changes...
