FI-AE 02 Projektmanagement-Grundlagen (EN)

FI-AE 02 Project Management Fundamentals

In this module, you will learn the fundamentals of agile and traditional project management methods. You will understand the differences between Scrum, Waterfall, and Kanban, and know the associated roles, artifacts, and ceremonies. You can apply these methods and know which model is most suitable for a project.

The content forms the basis for effective project management in software development and helps you to systematically plan, execute, and successfully complete projects.

Concepts and Background

Project Management

The systematic planning, control, and monitoring of projects to achieve defined objectives within given constraints (time, cost, quality).

Waterfall Model

Linear, sequential approach with clearly defined phases (requirements, planning, design, implementation, testing, maintenance). Each phase must be completed before the next begins.

Scrum

Agile framework for complex product development with defined roles (Product Owner, Scrum Master, Development Team), artifacts (Product Backlog, Sprint Backlog, Product Increment), and ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective).

Kanban

Visual work management system that visualizes workflow and optimizes lead times. It is based on the principles of visualization, limitation, workflow management, and explicit rules.

Agility

Project management approach focused on iterative development, adaptability, and continuous improvement. Unlike the Waterfall model, requirements are flexibly adjusted during the project.

Architecture Diagram

The following graphic illustrates the typical workflow of an agile project according to Scrum:

flowchart LR
    A[Product Vision] --> B(Product Backlog)
    B --> C[Sprint Planning]
    C --> D[Sprint Backlog]
    D --> E[Daily Scrum]
    E --> F[Work on Sprint Backlog]
    F --> G[Sprint Review]
    G --> H[Sprint Retrospective]
    H --> I[New Sprint Planning]
    I --> D
    G --> B

Practical Steps

1. Clearly define the project scope and objectives. This forms the basis for all further planning and ensures that all stakeholders have the same expectations.
2. Choose the appropriate project management model based on project requirements, team size, and complexity. For stable requirements with clear specifications, Waterfall is suitable; for dynamic projects, Scrum or Kanban.
3. Create a Product Backlog with prioritized user stories. Each story should describe a clear benefit for the end user and include acceptance criteria.
4. Plan the sprints and determine the sprint duration (typically 1-4 weeks). A shorter sprint enables faster feedback loops, while a longer one provides more continuity.
5. Conduct daily stand-up meetings to discuss the current status, identify blockers, and find solutions. Each meeting should last a maximum of 15 minutes.
6. Implement a Kanban board to visualize the workflow. It should contain columns for "To Do", "In Progress", "In Review", and "Done" to make progress transparent.
7. Document project progress and keep a sprint log. This serves as proof of progress and as a basis for later analysis and learning processes.
8. Organize regular retrospectives to continuously improve the process. Discuss what went well, what can be improved, and what concrete steps will be taken.

Common Pitfalls

Further Resources

• Official Scrum Guide from Scrum.org
• Scrum Resources from Atlassian
• Kanban Resources from Kanbanize
• PMI Project Management Fundamentals
• Waterfall Model Explanation from projektmanagement.de

Knowledge Check

Four questions for self-assessment. Click on each question to see the correct answer and explanation.

What is a main characteristic of the Waterfall model compared to agile methods?

• A) Iterative development with short cycles
• B) Linear, sequential approach with clearly defined phases
• C) Flexible adjustment of requirements during the project
• D) Visualization of the workflow

Correct Answer: B. The Waterfall model is characterized by its linear, sequential approach with clearly defined phases, while agile methods are iterative and flexible.

Which element is not an official artifact in the Scrum framework?

• A) Product Backlog
• B) Sprint Backlog
• C) Project Plan
• D) Product Increment

Correct Answer: C. The Project Plan is not an official Scrum artifact. Instead, Product Backlog, Sprint Backlog, and Product Increment are used as artifacts.

What is a fundamental principle of the Kanban system?

• A) Fixed sprint lengths of 2-4 weeks
• B) Limitation of work in progress
• C) Obligation to daily stand-up meetings
• D) Predefined roles like Product Owner

Correct Answer: B. Limiting work in progress (WIP) is a core principle of Kanban, while fixed sprint lengths and daily stand-ups are typical for Scrum.

What is the main difference between agile methods and the traditional project approach?

• A) Strict adherence to initial plans
• B) Sequential execution of phases
• C) Emphasis on documentation and formal processes
• D) Flexibility and adaptability to change

Correct Answer: D. The main difference is that agile methods emphasize flexibility and adaptability to change, while traditional approaches focus on strict planning and sequential execution.