You will join an active project team where you truly become part of the team. Here, we teach you the tricks of the trade by working on various ongoing projects in a team setting. 

What can you expect on a day-to-day basis?

• You work in an agile environment
• You participate in the morning stand-ups
• You take part in the bi-weekly sprint planning
• You join every retrospective related to the project you are involved in
• You get to work independently
• You receive daily guidance and support from your internship mentor

During an internship as a functional analyst/product owner at PHPro, your skills will be tested in areas such as all-round problem-solving, administrative strengths, and visualizing problems and solutions. As an intern, you will have the opportunity to analyze potential issues within active projects, develop solutions for them, and implement them yourself.

In this internship, we provide the opportunity to develop all competencies associated with the role of a functional analyst: problem-solving, administrative strength, strategy, and planning.

• You will work closely with one of our product owners and analysts, collaborating on wireframes, analyses, and more.
• You will have direct contact with clients.
• You will translate requirements into user stories for developers.
• You will monitor the development process by validating the developments in the QA process and providing feedback.

You will document the assignment in Confluence and also prepare everything in a PowerPoint, Keynote, or Google Slides presentation to present to the team of analysts at the end of your internship.

The assignment consists of three parts: discovery phase, deliverables, and real live analysis.

Discovery 

You will set up a discovery workshop for one of our clients or for PHPro itself. A discovery process aims to map out everything that could potentially impact the project:

• You create discovery stories
• You compile a list of discovery questions
• You compile a list of possible assumptions
• You answer the 5 core questions: Who, What, Where, Why, When, and How
  • Determine stakeholders (Who needs the software?)
  • Set a goal for the webshop/website/... (Why is the webshop/software needed?)
  • Provide a high-level overview of the project (What is the scope of the project?)
  • Deadline/Roadmap (When)
  • Agreements on working methods (Where is the work done, where is the documentation stored? - Where)
  • How do we serve our target audience? (e.g., Shopware vs Magento Open-Source vs Magento Cloud, ...)

Deliverables 

Once the discovery phase is completed, we expect the goals of this process to be visualized and compiled through various deliverables:

• You create a document to record the functional requirements
• You draft a high-level project plan (mapping out the project's scope)
• You create a context diagram that shows all the integrations in the project
• You create a work breakdown structure to frame the project (main activities/sub-activities)

Real Live Analysis

• You will present your discovery findings to the client along with the accompanying functional analyst.
• You will analyze real-time questions from the client within the ongoing project and deliver solutions.