Specifications are added to an existing specification project via plan review

[waynebeaton]

The process bits in the EFSP are built around a notion of projects being at the center of all things. That is, things like reviews are project level things. According to the EDP, a project may release only parts, so the notion of a single specification project that's used to develop multiple specifications engaging in a release review to create a Final Specification for just one of their specifications is fully supported.

It's the same for creation reviews. Creation reviews are used to create projects. Adding a new specification to an existing specification project is essentially the same as adding new functionality to an existing software project: that is... you're not creating a new project, you're just adding something to an existing one.

When an existing project team decides to start working on a new specification, the specification committee would have to be informed of that intention via a plan review at the beginning of a development cycle.

I don't think that anything in the specification process itself needs to change. But this is a subtlety that will need to be documented in the operations guide.