project management - How to manage multiple products that share code -
The company I have just joined is a system of products that share a large percentage of their code base (Via shared link in Visual Source)). There are approximately 25 product types in this system as well as a PC interface.
Using proprietary protocols together, which are largely inappropriate. Historically, the method of maintaining this mess is that all the firmware and software has been released as a package. This certainly causes significant delays in the release schedule due to the necessary regression testing.
Are there any other ways to deal with this kind of issue? We are actually beat it up by the management (I honestly can not blame them for feeling like this).
My first idea is to try to isolate the device release in some other way, perhaps drag the shared functionality into the libraries, which are the versions. Then just update the devices that use changed libraries. I am getting problems with this version mismatch
This is an organizational question. I think how to keep the card house going through the tests and procedures, but I believe that the code base can have very good results in the better organization. Are there.
I appreciate the advice. Significant delays in release schedule due to necessary regression testing.
That's why people do a "".
On a daily basis usually involves a set of tests, which are sometimes called tests of smoke (where smoke is fired). These tests have been included to help in determining what could be broken due to changes made to the latest build. As part of the project, important part of this process is to include new and revised tests.
When the organization - as a whole - the daily work has to be maintained, then people change
Daily stand-up meeting becomes focused on such things That can break the build.
To prevent breaking down the individual developers building, you have to re-apply your code more carefully.
By breaking the build becomes an instantaneous, immediate indicator of what is going out of sync. Do not delay. If I break today's construction, then everyone will know in the morning tomorrow (or hoped) was not wasted (things that still work) We can immediately change the changes back, or apply changes to move forward can do.
Comments
Post a Comment