Zeiss Application Lab
Contribution
- Supporting the team during work breakdown & estimation process
- Budgeting, milestone planning, creating and updating roadmaps
- Preparing and continually updating the project JIRA board
- Escalating issues regarding technical constraints and initiating a revision of the project vision and scope
- Integrating bug catalog grooming and code reviews into the workflow
- Facilitating SCRUM rituals and best practices
- Tracking scope and budget using JIRA structures
- Prioritizing feedback and managing feedback scope
- External client delivery
Obstacles
During pre-production the engineers defined that all application lab device experiences would be contained within one UE4 project and scene. When the project entered production more senior engineers were brought in, who identified that this was not a scaleable solution. This was a critical issue as the client planned to commission up to one hundred experiences. We escalated this issue to the production and engineering leads and identified the need for a scope change to restructure the architecture of the experience. I took responsibility for facilitating this process and getting the scope change approved by leads and management. The final experience contains a lobby which allows users to browse through the available devices using a tablet interface, preview them at full scale, and transport to the corresponding device experience which is contained in it’s own separate UE4 project.
Lessons Learned
By going through this process I learned the importance of a proper lead review and approval process during pre-production. I also learned how to properly escalate issues to leads and management. As well as how to balance quality, budget and time considerations when proposing a potential scope change.