Project Controlling/Monitoring Flashcards
Configuration Management (CM):
Concerned with the policies, processes and tools for controlling and managing assets or products.
Configuration Item (CI):
Any artefact that has been placed under configuration control, i.e. ensuring that versions are recorded and maintained and all versions are identified and stored for the lifetime
Configuration Version:
An instance of a configuration item that differs from other instances of that item. Versions always have a unique identifier, which is often composed of the configuration item name plus a version number
Configuration Version Management:
Keeping track of the multiple versions of assets/products and ensuring that changes made do not interfere with each other
Configuration Codeline:
A set of versions of a software component and other configuration items on which that component depends
Configuration Baseline:
A snapshot of the state of a product and any component products, frozen at a point in time for a particular purpose
Configuration Change Management:
Keeping track of requests for changes to the assets/products, working out the costs and impact of changes, deciding the changes should be implemented and track changes
Configuration System Building:
The process of assembling program components, data and libraries, to create an executable system
Configuration Release Management:
A release is a complete and consistent set of products, which forms a fixed reference point in the development of the end outcome
Change Management:
A process that manages change
Project Issues…
Typically captured in an Issue Log, are assessed to determine/plan actions and reviewed to monitor progress. Issues are also related to Risks
Control Schedule (ISO 21500):
Monitor schedule variances and take appropriate actions. Should focus on determining the current status of the project schedule and comparing to approved baseline schedule to determine any variance
Control Costs (ISO 21500):
Monitor cost variances and take appropriate actions. Determine the present project cost status, comparing to baseline costs to determine any variance
S-Curve Analysis - Pros and Cons:
Pros: Simple, clear and easy to update
Cons: May be misinterpreted and not tell the whole truth on project actual performance
Tracking Gantt Charts - Pros and Cons:
Pros: Easy to understand and update
Cons: Do not show underlying issues, do not easily allow for projections in the future
