Collecting of requirements
Status | DECIDED |
|---|---|
Stakeholders | @Soren.Pedersen@esv.se (Unlicensed) |
Outcome | Team will not initiate proactive gathering of requirements but can by consensus agree to support new requirements. |
Due date | Feb 14, 2018 |
Owner | @Georg Birgisson (Unlicensed) |
Background
Shall the BIS3 project team engage in proactive collection of requirements from PEPPOL members or limit its scope to adopting requirements handed to it by CMB.
Action items
Comments
Mar 7, 2018
CMB meeting on 2018-03-07 decided that; the project team proposal that it does not proactively engage in collecting requirements for change but as a starting point base the work on rfc's transferred from the spring maintenance release to the BIS3 upgrade project. Normal review cycle will be kept. (See https://openpeppol.atlassian.net/projects/PB30/issues/PB30-16?filter=allissues). This is to prevent scope creep. The project team can by consensus approve support for additional business requirements.