# Project Organisation

# Previous Exam

## Major Milestones

What affects iterations?

### LCO = Lifecycle Objectives
**Inception phase**
Objectives
- Establish scope and boundary conditions
- Usecases and primary scenarios
- Demonstrate candidate architectures against primary scenarios
- Estimate cost & schedule
- Prep supporting env.

Eval Criteria
- Stakeholder concurrence on scope
- Shared understanding/agreement on requirements
- Agreement on cost, priorities risk and dev process
- All risks identified

### LCA = Lifecycle Architecture

**Elaboration phase**

LCA: Erläutern Sie folgende Kriterien und geben sie anhand des Projekts Beispiele an:

Objectives:
- establish baseline vision and architecture
- demonstrate architecture supports vision
- refine support env
- detailed plan for construction phase

Eval Criteria
- Product vision and requirements are stable
- Architecture is stable
- Key test and evaluation approach the problems and major risks are addressed and resolved
- Iteration plan for Construction phase are of sufficient detail and fidelity to allow work to product and are supported by credible estimates
- All stakeholders agree that the arranged vision can be met if the current plan is executed to develop the system

### IOC = Initial Operational Capability
**Construction phase**
Objectives:
- Complete software product
- Minimize dev cost
- Achieve adequate quality and useful versions quickly

Eval Criteria:
- Release stable and mature enough
- Stakeholders ready for transition to users
- Expenditures vs planned acceptable

### GA = Product release
**Transition phase**
Objectives:
- User self-supportability
- Stakeholder concurrence on completion of vision and baseline
- Reach final product baseline fast and cost effective

Eval Criteria:
- Are users sattisfied
- are resource expenditures accepatble

## Risiko

Q: Konkretes Entwicklungsrisiko definieren, Maßnahmen zur Reduktion von Wahrscheinlichkeit und Auswirkung definieren und was sollte unternommen werden, wenn das Problem schlagend wird

---

Risk Definition: Technical risks (Unproven technology), Resource risk (people, skills, ...), Business risk (Competition), Schedule risk (project dependencies)

Strategies: Risk avoidance, Risk transfer, Risk acceptance

Direct risk: the project has a large degree of control
Indirect risk – the project has little or no control

Risk Magnitude: Used for ranking risks.
Combines:
- probability of occurrence, and
- impact on the project (severity), e.g., project delays

---

**Beschreibung der Risiken mittels folgender Attribute**: -> See: PDF2:34
- Kurzbeschreibung
- Wahrscheinlichkeit (1..10)
- Auswirkung (1..10)
- Größe (=Wahrscheinlichkeit x Auswirkung)
- Maßnahmen zur Reduktion von Wahrscheinlichkeit und Auswirkung
- Schritte im Notfall des Eintretens

**Beispiel**:
- Risikobeschreibung: Fehlende Finanzierung
- Wahrscheinlichkeit (1..10): 2
- Auswirkung (1..10): 9
- Größe (Ws x Aw): 18
- Reduktionsmaßnahmen: Laufender Kontakt zu bestehenden Investoren und Akquisitionen weiterer Geldgeber.
- Notfallplan: Implementierung unwesentlicher Features zwischenzeitlich stoppen oder ganz abbrechen.

## IST-SOLL Analyse

Diskutieren Sie die Projekteigenschaften der vorgestellten Kriterien (Bedeutung, Umfang, Komplexität, Interdisziplinarität, Einmaligkeit, Endlichkeit, klare Ziele, Risiko)

Vervollständigen Sie die IST/SOLL Analyse für EINEN angeführten SOLL Zustand Ihrer Wahl:
IST:
- Problem
- Abgrenzung
- Bedeutung
- Ursache
- Lösung

SOLL:
- Art
- Ziele

### a) SMART

a) Diskutieren Sie für jedes der fünf SMART Kriterien, ob und warum die Zielbeschreibung erfüllt bzw. nicht erfüllt ist.

S: Specific - verständlich, eindeutig, stimmig mit anderen Zielen
M: Measurable - Zielerreichung muss messbar sein
A: Achievable - erreichbar, realistisch
R: Relevant - nur wesentliche Ziele formulieren
T: Time-based - es gibt einen Zeitpunkt an dem es erreicht sein muss

### b) Zielbeschreibung verbessern

b) Verbessern Sie die Formulierung der Zielbeschreibung so, dass alle Kriterien erfüllt sind, falls dies nicht bereits der Fall ist.

TODO: Kriterien

## OMG

a) OMG Essence zu Purpose, Issue, Object and Viewpoint definieren

**Purpose:** What shoud be achieved by measurement?
**Issue:** Which aspect should be measured?
- Strategy/Goals of org

**Object:** Wich product/process/resource will be assessed?
- Processes/Products of org

**Viewpoint:** From wich perspective is the goal defined?
- Model of org

b) Question und Metriken definieren

**Questions:** How to evalueate a goal
**Metrics:** Key figures to evaluate a question

**Example**
Goal: Improve the timeliness of change request proceeding from a project managers viewpoint.
Questions: Is the performance of the process improving?
Metric: (current cycle time)/(average cycle time)

### Bereiche
**Stakeholders:** peoplem, groups, orgas affecting/affected by project
1. Identification
2. How to involve them
3. Representatives actively involved/fulfilling responsibilities
4. Representatives in agreement
5. Minimal expectations achieved
6. Expectations met/exceeded

**Opportunities:** appropriate circumstances to develope/change a software system
1. Opportunity for software based solutions identified
2. Need for solution confirmed
3. Value of successful solution established
4. Agreement that cheap quick production is possible (viablility)
5. Solution for demonstration purposes is produced
6. Tangible benefits from using solution or sale

**Requirements:** how to satisfy stakeholders
1. Agree on need for system
2. Agree on purpose & theme of system
3. Establish requirements as consistent description for system characteristics
4. System described is acceptable for stakeholders
5. Requirements addressed staisfy the need for a system in an acceptable way
6. Requirements addressed fully satisfy stakeholders

**Software System:** system made up from software, hardware and data with primary value of software execution
1. Architecture addressing technical risks has been selected
2. Executable version for demonstration purposes which supports testing exists
3. System is usable
4. System is accepted for deployment
5. System is used in live env
6. System is no longer supported (retired)

**Team:** group of people engaging in development, delivery, maintenance and support of a system
1. Mission clear and know how needed in place
2. Enough committed people to start the mission
3. Members working as a unit
4. Effective efficient working
5. Team is no longer accountable for mission

**Work:** activity needing mental/physical effort to get result
1. Work has been requested
2. All preconditions are met
3. Work proceeds
4. Going well, risks under control, productivity sufficient
5. Work has concluded
6. Houskeeping tasks have been completed and work is closed

**Way of Working:** practices and tools supporting and guiding a team
1. Principles and constrains have been established
2. Key practices and tools are selected and ready
3. Adopted by some members
4. Adopted by all members
5. Way of working works well for team
6. Way of working no longer in use

## Netzplan

Vorwärts / Rückwärts Diagramm ausfüllen -> Netzplan

SAZ: spätester Anfangszeitpunkt
FAZ: frühester Anfangszeitpunkt
SEZ: spätester Endzeitpunkt
FEZ: frühester Endzeitpunkt

Vorwärts: FAZ FEZ und Dauer eintragen. Bei mehreren FEZ an einem Vorgangsknoten immmer den größten FEZ wählen. (FEZ_1 = 12, FEZ_2 = 13 -> FAZ_3 = 13)

Rückwärts: SEZ, SAZ und Puffer eintragen. Bei mehreren SAZ zu einem Vorgangsknoten wird immer der kleinste SAZ zum SEZ des aktuellen Knoten (SAZ_1 = 12, SAZ_2 = 13 -> SEZ_3 = 12). Der Puffer ist immer
SEZ-SAZ

Der Kritische Pfad ist der Pfad der keine Pufferzeiten enthält.

---

# Important concepts

## Ist Soll

**Ist-Analyse:**
- **Problem**: Begrifflich eindeutig definieren (inkl. Zuordnung zu einem Problembereich)
- **Abgrenzung**: Schranken von Zeit, Raum, Organisation, ...
- **Bedeutung**: Wirkungen des Problems quantitativ untersuchen auf (un-)mittelbare Auswirkungen (**Kosten, Zeit, Sonderleistungen, Ausschuss**, ...)
- **Ursachen**: Erkannte Ursachen können zur Problemlösung führen
- **Lösungen**: Mögliche Ideen und Alternativen, z.B.: "Einsatz/Nutzung von ..."

**Soll-Analyse:**
- Was soll als Projektergebnis vorhanden sein?
- Analyse der Lösungsalternativen
- **Verbesserungen**
- **Kernanforderungen**
- Wir wird es eingesetzt? (Szenarien)
- Alternativen ermitteln: Risikoanalysen, Machbarkeitsanalysen, ...

**Zielarten**:
- Inhalt: qualitativ, quantitativ
- Fokus:
- strategisch: langfristige Unternehmensziele
- taktisch: Einsparung von Zeit und Kosten
- operativ: papierarmes Tagesgeschäft
- Art:
- **project constraints** (Randbedingungen): naming conventions/definitions, relevant facts and constraints
- Vom Projektumfeld vorgegebene Bedingungen, die nicht beeinflussbar sind
- Technische (Materialeigenschaften, Klima, Technologieumgebung)
- Rechtliche (Normen, Vorschriften, Gesetze)
- Zeitliche (frühester Beginn, Deadlines) ▪ Ökonomische (Budgetvorgaben, Amortisationszeit)
- **functional** (Features): scope of the work/product, functional and data requirements
- Direkt messbare Eigenschaften eines Systems (Features)
- **non-functional** (Qualitätsanforderungen): Beziehen sich auf Entwicklung, Wartung und Betrieb
- **look and feel**: interface, style of the product
- **usability**: ease of use/learning, personalization, i18n, a11y
- **performance**: speed and latency, safety critical, precision, reliability, availability, capacity, scalability
- **operational**: expected physical/technological environment, partner applications, Productization requirement
- **maintainability and portability**: How easy must it be to maintain the product? Supportability, portability requirements
- **security**: access, integrity, privacy, audit
- **cultural and political**: Are there any special factors about the product that would make it unacceptable for some political reason?
- **legal**: Does the system need to uphold any laws? Are there standards that need to be complied with?

## GANTT

Start-Start: We can only start testing if developement already started
Finish-Finish: We can only finish documentation of a feature if its developement is finished
Start-Finish: We can only shutdown the old system if the new one is already started
Finish-Start: We can only go into production once testing is finished

## Requirements Engineering

## Resourcenplanung

- Auslastung / Überlastung der Ressourcen im zeitlichen Verlauf
- Gegenüberstellung der verfügbaren Ressourcen
- Berücksichtigung von Urlaub, Krankheit, Ausbildung, Kundenbetreuung
- **Zeitgetrieben**:
- Egal wie viele Resourcen man der Aufgabe zuordnet, sie wird immer gleich lange dauern
- Beispiel: Flug von Wien nach London
- **Ressourcengetrieben**:
- Je mehr Resourcen man zuordnet, desto schneller wird man fertig
- Beispiel: Mauer errichten
- Vorsicht geboten:
- Stunden- oder tagweise Planung ist zu genau (for most projects)
- Multiprojektplanung: Arbeiten an mehreren Projekten
- Mitarbeiter und andere Ressourcen nicht ueberlasten
- Anzahl der parallelen Aufgaben pro Mitarbeiter im Rahmen halten

Is des Requirements engineering? Wei donn ko am de headline do hin setzn
## Welche Arten von Anforderungen gibt es?

- **project drivers**: purpose of the product, client/customers/stakeholdres, users
- **project constraints** (Randbedingungen): naming conventions/definitions, relevant facts and constraints
- **functional requirements**: scope of the work/product, functional and data requirements
- **non-functional requirements** (Qualitätsanforderungen): Beziehen sich auf Entwicklung, Wartung und Betrieb
- **look and feel**: interface, style of the product
- **usability**: ease of use/learning, personalization, i18n, a11y
- **performance**: speed and latency, safety critical, precision, reliability, availability, capacity, scalability
- **operational**: expected physical/technological environment, partner applications, Productization requirement
- **maintainability and portability**: How easy must it be to maintain the product? Supportability, portability requirements
- **security**: access, integrity, privacy, audit
- **cultural and political**: Are there any special factors about the product that would make it unacceptable for some political reason?
- **legal**: Does the system need to uphold any laws? Are there standards that need to be complied with?
- **project issues**: open issues, new problems, tassks, risks, costs, user documentation, ...

# Flashcards

Flashcard 1

Q: What are the objectives of the Inception phase (LCO) in project management?

A:

Establish scope and boundary conditions
Use cases and primary scenarios
Demonstrate candidate architectures against primary scenarios
Estimate cost & schedule
Prepare supporting environment

Flashcard 2

Q: What are the evaluation criteria for the Inception phase (LCO)?

A:

Stakeholder concurrence on scope
Shared understanding/agreement on requirements
Agreement on cost, priorities, risk, and development process
All risks identified

Flashcard 3

Q: What are the objectives of the Elaboration phase (LCA) in project management?

A:

Establish baseline vision and architecture
Demonstrate architecture supports vision
Refine support environment
Create detailed plan for the construction phase

Flashcard 4

Q: What are the evaluation criteria for the Elaboration phase (LCA)?

A:

Product vision and requirements are stable
Architecture is stable
Key test and evaluation problems and major risks are addressed and resolved
Iteration plan for Construction phase is detailed and supported by credible estimates
All stakeholders agree the arranged vision can be met if the current plan is executed

Flashcard 5

Q: What are the objectives of the Construction phase (IOC)?

A:

Complete software product
Minimize development cost
Achieve adequate quality and useful versions quickly

Flashcard 6

Q: What are the evaluation criteria for the Construction phase (IOC)?

A:

Release stable and mature enough
Stakeholders ready for transition to users
Expenditures vs planned acceptable

Flashcard 7

Q: What are the objectives of the Transition phase (GA)?

A:

User self-supportability
Stakeholder concurrence on completion of vision and baseline
Reach final product baseline fast and cost-effectively

Flashcard 8

Q: What are the evaluation criteria for the Transition phase (GA)?

A:

Are users satisfied?
Are resource expenditures acceptable?

Flashcard 9

Q: What are the different types of project risks?

A:

Technical risks (Unproven technology)
Resource risk (people, skills, ...)
Business risk (Competition)
Schedule risk (project dependencies)

Flashcard 10

Q: What strategies can be used for risk management?

A:

Risk avoidance
Risk transfer
Risk acceptance

Flashcard 11

Q: How do you describe risks using specific attributes?

A:

Kurzbeschreibung (Short description)
Wahrscheinlichkeit (Probability: 1..10)
Auswirkung (Impact: 1..10)
Größe (Magnitude = Probability x Impact)
Maßnahmen zur Reduktion von Wahrscheinlichkeit und Auswirkung (Measures to reduce probability and impact)
Schritte im Notfall des Eintretens (Steps in case the problem occurs)

Flashcard 12

Q: What is an example of risk description?

A:

Risk description: Lack of funding
Probability (1..10): 2
Impact (1..10): 9
Magnitude: 18
Reduction measures: Ongoing contact with existing investors and acquisition of additional funders.
Contingency plan: Temporarily stop or cancel the implementation of non-essential features.

Flashcard 13

Q: What is an IST analysis in project management?

A:

Problem: Clearly define the problem and assign it to a problem area.
Abgrenzung (Boundaries): Define the boundaries of time, space, and organization.
Bedeutung (Importance): Quantitatively investigate the effects of the problem.
Ursachen (Causes): Identify causes that can lead to problem resolution.
Lösungen (Solutions): Possible ideas and alternatives.

Flashcard 14

Q: What is a SOLL analysis in project management?

A:

What should be available as the project result?
Analysis of solution alternatives:
Improvements
Core requirements
How it will be used (scenarios)
Identify alternatives: Risk analyses, feasibility analyses

Flashcard 15

Q: What are the SMART criteria for goal setting?

A:

Specific: Understandable, clear, consistent with other goals
Measurable: Goal achievement must be measurable
Achievable: Attainable, realistic
Relevant: Only formulate essential goals
Time-based: There is a specific time by which it must be achieved

Flashcard 16

Q: How can you improve goal descriptions to meet SMART criteria?

A: By ensuring goals are:

Specific: Clear and detailed
Measurable: Quantifiable
Achievable: Realistic and attainable
Relevant: Essential and aligned with overall objectives
Time-based: Set with a clear deadline

Flashcard 17

Q: What is the purpose of OMG Essence?

A:

Purpose: What should be achieved by measurement?
Issue: Which aspect should be measured?
Object: Which product/process/resource will be assessed?
Viewpoint: From which perspective is the goal defined?

Flashcard 18

Q: What are the elements of OMG Essence?

A:

Stakeholders: People, groups, organizations affecting/affected by the project
Opportunities: Circumstances to develop/change a software system
Requirements: How to satisfy stakeholders
Software System: System made up of software, hardware, and data
Team: Group of people engaging in development, delivery, maintenance, and support of a system
Work: Activity requiring mental/physical effort to achieve a result
Way of Working: Practices and tools supporting and guiding a team

Flashcard 19

Q: What are the key steps in project resource planning?

A:

Balancing the workload of resources over time
Comparing available resources with required ones
Considering vacations, illness, training, and customer support
Time-driven vs. resource-driven tasks
Avoiding overallocation of resources
Managing multiple projects and parallel tasks per resource

Flashcard 20

Q: What types of requirements exist in project management?

A:

Project drivers: Purpose of the product, stakeholders, users
Project constraints: Naming conventions, relevant facts, constraints
Functional requirements: Scope of the work/product, functional and data requirements
Non-functional requirements: Relating to development, maintenance, and operation, including:
Look and feel
Usability
Performance
Operational
Maintainability and portability
Security
Cultural and political
Legal
Project issues: Open issues, new problems, tasks, risks, costs, user documentation

Flashcard 21

Q: What are the different types of dependencies in a Gantt chart?

A:

Start-Start: One task can start if another task has already started.
Finish-Finish: One task can finish if another task is finished.
Start-Finish: One task can finish if another task has started.
Finish-Start: One task can start if another task is finished.

Flashcard 22

Q: How do you complete a forward/backward diagram in a network plan?

A:

Forward: Enter FAZ (earliest start time), FEZ (earliest end time), and duration. Choose the largest FEZ for multiple FEZ at a node.
Backward: Enter SEZ (latest end time), SAZ (latest start time), and buffer. Choose the smallest SAZ for multiple SAZ at a node. Buffer is SEZ - SAZ.
The critical path is the path with no buffer times.

Flashcard 23

Q: What are the steps involved in identifying and involving stakeholders in a project?

A:

Identification of stakeholders
Determining how to involve them
Ensuring representatives are actively involved and fulfilling responsibilities
Achieving agreement among representatives
Meeting minimal expectations of stakeholders
Exceeding stakeholder expectations

Flashcard 24

Q: What are the key considerations for identifying opportunities in software development?

A:

Identifying opportunities for software-based solutions
Confirming the need for a solution
Establishing the value of a successful solution
Agreeing that cheap, quick production is possible (viability)
Producing a solution for demonstration purposes
Realizing tangible benefits from using or selling the solution

Flashcard 25

Q: What are the stages of agreeing on requirements to satisfy stakeholders?

A:

Agree on the need for a system
Agree on the purpose and theme of the system
Establish requirements as a consistent description of system characteristics
Ensure the system described is acceptable to stakeholders
Address requirements to satisfy the need for a system in an acceptable way
Fully satisfy stakeholders with addressed requirements

Flashcard 26

Q: What are the stages in the development of a software system?

A:

Selecting an architecture that addresses technical risks
Creating an executable version for demonstration purposes to support testing
Ensuring the system is usable
Getting the system accepted for deployment
Deploying the system in a live environment
Retiring the system when it is no longer supported

Flashcard 27

Q: What are the stages of forming and developing a project team?

A:

Clear mission and necessary knowledge in place
Sufficient committed people to start the mission
Members working as a unit
Achieving effective and efficient working
Completing the mission
Team is no longer accountable for the mission

Flashcard 28

Q: What are the stages of completing work in a project?

A:

Requesting work
Ensuring all preconditions are met
Proceeding with the work
Monitoring work progress, controlling risks, ensuring sufficient productivity
Concluding the work
Completing housekeeping tasks and closing the work

Flashcard 29

Q: What are the stages of establishing and adopting a way of working in a project?

A:

Establishing principles and constraints
Selecting and preparing key practices and tools
Adoption by some team members
Adoption by all team members
Ensuring the way of working is effective for the team
Retiring the way of working when it is no longer used

Flashcard 30

Q: What factors affect project iterations?

A:

Scope changes
Stakeholder feedback
Risk management activities
Resource availability
Schedule adjustments
Technical issues and solutions
Quality assurance results

Flashcard 31

Q: What are the major milestones in a project lifecycle?

A:

Lifecycle Objectives (LCO)
Lifecycle Architecture (LCA)
Initial Operational Capability (IOC)
Product release (GA)

Flashcard 32

Q: What is the importance of conducting an IST-SOLL analysis?

A:

IST (Current State): Identifying the problem, its boundaries, importance, causes, and potential solutions.
SOLL (Desired State): Defining the desired project outcomes, analyzing solution alternatives, and determining improvements, core requirements, and usage scenarios.

Flashcard 33

Q: What are the types of project constraints?

A:

Technical (material properties, climate, technology environment)
Legal (norms, regulations, laws)
Temporal (earliest start, deadlines)
Economic (budget guidelines, amortization period)

Flashcard 34

Q: What are the types of project goals based on their focus?

A:

Strategic: Long-term organizational goals
Tactical: Saving time and costs
Operational: Daily operations, e.g., paperless work

Flashcard 35

Q: What are non-functional requirements in project management?

A:

Look and Feel: Interface, style of the product
Usability: Ease of use/learning, personalization, internationalization, accessibility
Performance: Speed and latency, safety-critical aspects, precision, reliability, availability, scalability
Operational: Expected physical/technological environment, partner applications, productization requirements
Maintainability and Portability: Ease of maintenance, supportability, portability requirements
Security: Access control, integrity, privacy, audit
Cultural and Political: Factors making the product acceptable/unacceptable
Legal: Compliance with laws and standards

Flashcard 36

Q: What are functional requirements in project management?

A:

Scope of the work/product
Functional and data requirements that define what the system should do

Flashcard 37

Q: What are the project drivers in requirements engineering?

A:

Purpose of the product
Clients/customers/stakeholders
Users of the product

Flashcard 38

Q: What are project issues in requirements engineering?

A:

Open issues
New problems
Tasks
Risks
Costs
User documentation

Flashcard 39

Q: What is the critical path in a network plan?

A: The path in a project network diagram that has no buffer times and determines the shortest possible project duration.

Flashcard 40

Q: What is the purpose of a Gantt chart in project management?

A:

Visualize project schedule
Show dependencies between tasks
Track progress of tasks
Identify critical path and potential delays