To manage a large computerisation project, how many versions should I keep ?
Question:
I feel I need to keep hundreds of versions at any one time.
And I must keep every one of these versions as a historical record.
So it's potentially hundreds of fresh versions each year (or month, or week) for the life of the project.
Conceptually it's no different to a bank keeping accurate records of transactions.
I can't see the big deal. But how do I sell the idea.
A competing idea is to have one version, with teams defining "interface specs". What's that ?
Answer:
A project should have a "Version Control Manager" or "Configuration Manager". This is not always a full-time function but it could be.
As your project evolves new hardware, new system software, new program modules, new security, new user interface, and new database management modules are introduced.
Your test plans and quality control mechanisms should address changes to all these variables.
If you don't know when and how functionality is introduced it can be difficult or impossible to control the project.
Whether your are using ISO 900x or some other standard, this is import poopoo.
More Questions & Answers...