Vasilios Alexandros F.

Product Owner

9 years
Frankfurt, GERMANY
Contact us for this profile

My experience


Private Energy ProviderSeptember 2018 - Present

Product Owner.
  • Defining the product vision.
  • Product backlog, stakeholders and time management.
  • Estimating priorities and determining team velocity for the product release.
  • Analyzing the data and feedback gathered from the client and the team.
  • Creating effective user stories.


Business Analyst.
  • Understanding systems engineering concepts.
  • Business case development.
  • Use of modeling techniques and methods.
  • Translating and simplifying requirements.
  • Analyzing different mobile ad formats and creating business proposals based on the results.

Energy Data Management SpecialistJune 2017 - May 2018

Business Analyst.
  • Travelling to customer premises to insure the correct installation and use of the application.
  • Meeting moderation: discussions with people from business and management departments (in order to understand the needs and translate them into specifications), discussions with the development team (in order to find technical solutions for the user's needs).
  • Analysis of the existing applications and proposal of improvements.
  • Writing specifications and use cases.
  • Data assessment and mapping.
  • Creation and analysis of data flow diagrams.

XeroxAugust 2012 - May 2017

Systems Analyst within a business processing outsourcing and document technology company.

Business analysis on IT systems.
  • Assessing client requirements: assistance during the elicitation process in determining the client needs and the best way to integrate those needs into the company's internal processes.
  • Prioritizing implementation tasks in an organic workflow: by understanding the platform's capabilities one can come up with an efficient way of implementing those requirements on the web platform.
  • Attending client calls, especially handovers; communicating with the client's internal team to establish timelines.
  • Translating the system possibilities and limitations from a technical language to one the client or other non-technical parties can understand easily.
  • Creating wireframes to help define the features of the software to be developed.
  • Tracking project progress using Jira and Redmine.
  • Managing system documentation with Confluence.
  • Establishing potential issues (both technical and administrative): the current platform encompasses a number of people doing different tasks. There is a mix of technical and non-technical people (and of course the client) which need to communicate effectively; in that regard a high degree of adaptability has been required.
  • Assessing change requests, their impact on the platform, timelines, resources.
  • Creating functional specification documents relating to the change requests - this refers to the internal documentation describing how the system behavior/function will change when a change is applied, as the platform the team uses has not been developed in house.
  • Dealing with last minute changes on a regular basis.
  • Taking part in UAT and applying fixes/workarounds.

Software testing and implementation.
  • Implementation: having low detail system knowledge which was exploited for the implementation of the system requirements.
  • Testing: involvement in the development of test plans; managing bugs/defects and fixing them on the platform.
  • Content implementation: having whatever content the client needs made available to employees through the platform; this has at times included HTML manipulation, CSS, etc.
  • BAU activities: maintenance, clearing certain types of items from the backlog.

My education and trainings

Studies in European Law, Faculty of Liberal Arts and Sciences - University of Tilburg, The Netherlands. 2011 - 2012