Download Improving software configuration management across multiple
Transcript
41 that the solution should be applied locally at the customer site and remain a customer specific customization. Defects or bugs might be assigned higher priority and are more likely to result in a hotfix than other issues. When the associated task is solved and is linked to a service request, the service request it updated manually. They try to be agile, so design and details might be specified on the fly. During this process and any modifications, they try to keep product documentation up to date at the same time. Recently Annata has started to conduct a list of new features they are adding to be able to describe functionality for new versions in a user friendly way. 3.5.1.2 To-Increase The existing routines at To-Increase are said to be documented by the interview subjects. However, these documents are not easily available or accessible and even though developers are aware of them no one can say how to retrieve the latest version. It seems that many efforts have been made but a formal companywide approved document describing the routines does not exist. They do however have informal routines and processes that they follow. The processes differ a bit depending on the product. IEM and RCM, the major products, have more ceremony associated with the new feature, bug and change request handling than smaller components. Requirements from a customer can be handled differently, depending on the need. There may be features needed to e.g. win a deal, such as prototypes, design, or a proof of concept. Some issues may be rush service requests (high priority issues) to solve emergencies at the customer site. In general, ideas for new features come from various sources such as product managers, customers, support or developers. The process for handling the new feature suggestions varies between different products. Some products are certified by Microsoft and thus require stricter handling before changes are introduced. Normally all these features should be documented and then handled properly, but that is not always the case. At To-Increase they do have good internal understanding of the processes, but not everything is done by the book; it is not a completely documented process and the current handling is described as “consistently inconsistent” to quote one of the interview subjects. To-Increase uses a website for support issues. The issues are validated and if they should be solved by means of code changes it should normally end up as a task associated to a component and version in Development Center. In the system,