a) Outline the various software release strategies suggested within the ITIL guidance. Under what circumstances would each be appropriate.
12 Marks
b) How would an SC&D (Release) manager formally ascertain the effectiveness and efficiency of his/her function?
8 Marks
- Marking Guidelines
- Examinees may provide a straight listing of say, package release, delta release etc. However, full marks should be reserved for those phrasing the answer in terms of the following parameters:
Size (eg Module or whole Suite)
Urgency
Frequency (On-Demand vs Fixed Interval)
Individual systems vs Package Releases across systems
Suggest up to 7 marks for this type of discussion, with ½ marks only for a pure list. 5 marks for a good discussion of "circumstances" viz.
“Delta Release” - Urgent Change
“Package Release” - Requirement for periods of stability amongst a multi-system user base
“On-Demand” - Volatile Business Environment
Module vs Suite Release nature of build environment, ease of testing etc.
(Other issues to be accepted by the examiners if justified)
b) It would be necessary to obtain measures in the following areas (metrics better -before and after figures, rolling averages etc.)
1. Service time lost by SC+D activity
2. SC+D resource costs per release
3. No of builds rolled back after implementation
4. No of builds/distributions aborted during process
5. No of software changes made by SC±D team
6. No of times DSL misaligned with CMDB
7. No of instances of viruses in the environment
8. No of instances of unlicensed software in the environment
9. No of builds from other than DSL-managed versions
10. No of housekeeping activities carried out on the DSL
Up to 8 marks for a comprehensive list - no more than 4 if "metrics" not understood
| < Prev | Next > |
|---|
