R
Ronald S. Cook
We are about to undertake a an app dev project at our company. The overall
project has a name (let's say "DBD - Digital Business Design"). Within the
scope of the project will be several applications, some interdependent, some
stand-alone).
How should we document and version things?
Should it be DBD 1.0 which consists of App1 1.0, App2 1.0, App3 1.0? If we
have just a "DBD 1.0 Vision/Scope" document (covering the apps within it),
that would work I suppose. But then what about after its all deployed?
What if a change is warranted in App2 1.1. If that was scoped and developed
separately than DBD 1.0 is now obsolete.
Just looking for best practices.
Thanks,
Ron
project has a name (let's say "DBD - Digital Business Design"). Within the
scope of the project will be several applications, some interdependent, some
stand-alone).
How should we document and version things?
Should it be DBD 1.0 which consists of App1 1.0, App2 1.0, App3 1.0? If we
have just a "DBD 1.0 Vision/Scope" document (covering the apps within it),
that would work I suppose. But then what about after its all deployed?
What if a change is warranted in App2 1.1. If that was scoped and developed
separately than DBD 1.0 is now obsolete.
Just looking for best practices.
Thanks,
Ron