Technical PM-competences (Subject) / 1.03 Project requirements and objectives (Lesson)

This lesson was created by Steurich.

Learn lesson

This lesson is not released for learning.

back  |  next 1 / 1

• Project Targets arise from the strategic and operational targets of the company, are detailed into specific, measurable project objectives
• Project strategy Concept of top management how the project will be achieved
• Project objectives Objective provide the agreed end result, within the specified timeframe, within the agreed budget and acceptabel risk parameters They should be SMART, must be prioritised (acc. importance for the project owner) and the connection of objectives must be checked (are the conflicting objectives?) In the context of the different project phases Clealy and precisely defined objectives are identiefied in the project defintion phase and confirmed by the project owner Project objectives are not changed during the control phase (or only in the context of change mangement) The fulfillment of the project objecitves is evaluated and confirmed by the project owner in the close-out phase
• Project objectives have to fullfill important target functions Control functions: taget achievement Guidline functions: "where the journey is going" Connective and motivation functions: joint objevtives connect project team Selective functions: faciliate prioritised decison
• Scope of services and deliverables Agreed upon by project manager and porject owner DIN 69901-5:2009: "Totality of products and services, that must be presented as the end-result of the project's task" 
• Deliverables Tangibale results that are presented at the end of the project(documents, technical facilities/ buildings, organisational structure/ processes)
• Scope of services Include for example, the requirmenet specification sheet, the functional specification and the technical specification (the later especially for investment projects)
• Requirement specification sheet Describes the project results from the perspective of the project owner (project owner's responsibility) Specification or feature that a system or compoment must show to comply Problem is usually the quality of the requirement's description(identifiable, comprehensive, certain, detectable, measurable)
• Functional specification A description how the system will operate Developed by the project manager
• Technical specification Description of the system environment, technical features, norms etc. Description of the finished system
• Advertisement
• Four steps to define project objectives Identify and categories (time/performance/cost objectives) Comply with SMART(specific, measurable, attractive, realistic and timed) Prioritised (MUST-, SHOULD-, COULD- and NONE objectives) Check connection of objectives (contradicting, competing, neutral, complementary and identic)
• SMART objectives Specific: phrased clearly and specifically Measurabel: checkable and measurable Attractive: positive and motivating Realistic: attianble but still ambitious Timed: clear deadline
• Summary project objectives be precise, understandable, positive and darfted with an "exit criterion" be qualifiable have an objective size be divisable in single components be examined wheter they are necessary be summarized in one place (for necessary checks and updates) be accepted by all concerned

back  |  next 1 / 1