In this blog post we take a look over the shoulders of our project manager Tobias Gollinger and discuss topics such as quality, time and budget.
Tobias Gollinger has been working for eggs unimedia as a Senior Project Manager for over 3 years in which time he has been involved in numerous projects. Martin Brösamle conducted an interview with him to discuss the tasks involved..
Martin Brösamle (MB): Tobias, when does your work as a PM begin?
Tobias Golinger (TG): My activities already start during the presales phase. In this phase, in coordination with the sales and development team, I carry out estimates based on customer requirements. This ensures that we incorporate our experience from past projects into the estimates. This is important because the optimal composition of the project team depends on the often very different project requirements and the teams can therefore differ from project to project. It also happens that we do not exactly understand the requirements or objectives of an inquiry, which may have different reasons. Then we specifically ask until we get a coherent picture. In addition, during this phase we already check which know-how and which colleagues are needed in the project and "reserve" these at an early stage.
MB: How does a project start respectively what is the typical Project Life Cycle?
TG: Years ago, we defined a PM process that goes through various steps and is continuously improved. After receiving the customer order, we start with the project planning as soon as possible. First, in consultation with our colleagues, we name a Tech Lead for the project, define the team and explain the project goal in a kick-off. Ideally, the kick-off should take place at the customer's site and, if possible, with all project participants. Before work on the project begins, I also make sure that all the information required for the project is available. This includes contact details of all project participants, access to all required systems, etc.
MB: What happens next?
TG: Once the business and technical requirements have been clarified, the development cycle can begin. If not, there will be a requirements phase at the beginning in which technical and functional requirements are clarified. This is followed by the UX / Design phase, which forms the foundation for the subsequent implementation. Upon successful completion the project ends with the so-called "Closing", in which we carry out a Lessons Learned within the team and partly also with the customer and afterwards finish the project. During the Lessons Learned, we note down the experiences and knowledge which can improved as well as the ones which need no improvement, so that these can be taken into account for future projects. This is what we call Continuous Improvement.
MB: How do you work?
TG: Basically, we work very transparently and thus ensure that the customer has an insight into the progress of the project at all times. Depending on the size of the project, all available information is documented in Confluence. We use Jira for task management. Coordination with customers takes place either through regular telephone calls (Jour-Fixe, Daily) and/or directly via Confluence and Jira. During a project, the customer receives time sheets and status reports at regular intervals.