Medieninformatik HTW Berlin
Fachbereich 4
Internationaler Bachelor Studiengang
Internationale Medieninformatik (Bachelor)
Informatik 3
Winter Term 2023/24

 
HTW Berlin

Info 3: Informatik III
Modern Software Engineering
 

Lab 7: Project Planning and Risk Analysis

Project Planning

Let's think back to when we were starting to plan your shopping cart apps. Normally, before we start, we put together a project plan. But that is really hard to do if you don't know what such a project entails. But now you know, and some of you actually followed my suggestion that you keep track of how much time you really needed. That will help you now.

We recently heard about how to calculate the amount of person-months that will be needed for a project, and the TDev that will be necessary. You are then to work your way through to Gantt chart. Maybe read a bit more about it before the lab. Then complete the following exercises, assuming that you are using a waterfall process:

1. Calculate PM and TDev for your app. Assume that you do not yet have the requirements specified, but you have been asked by the shopping cart company to produce an app that will help deal with the problem of stray shopping carts. Explain why you chose which model.

2. The next step is the definition of milestones for your project. You will probably have about 3 or 4, but there can be more.

3. What will your deliverables be? Remember that documentation is legally necessary in Germany.

4. Using PM and TDev prepare a Gantt chart for your project. Assume that you will begin the project on April 1, 2024. When do you expect to be finished? Are there any external factors that might influence your plan?

5. With the Gantt chart and making educated guesses about the needed overhead: What will it cost to develop (not maintain!) your app?

Risk Analysis

Before you begin working on a project, you should undertake a risk analysis. And you should review your analysis regularly.

  1. What are the risks inherent in your project plan?
  2. What is the probability of these risks happening?
  3. How serious are the risks?
  4. What can you do to mitigate the risks?

Prepare a risk analysis for your project and finish up with a longish reflection by each team member on what they learned about constructing a software system in this semester.

Your report is due the night after the exam, February 7, 2024 at 22:00. You can hand in earlier if you wish!
Please post the report in the Moodle area for each team member. Please include a reflection on how easy or how difficult these exercises were.


Copyright Prof. Dr. Debora Weber-Wulff
Questions or comments: <weberwu@htw-berlin.de>
Some rights reserved. CC-BY-NC-SA - Copyright and Warranty