Previous Projects: Leyline Knights

Leyline Knights

• September 2020 - May 2021

• Leyline Interactive : Fourteen Person Team

• 30 week-long development cycle working towards vertical slice

• Launched on Steam Marketplace

• Created with Unreal Engine 4

• Genre: Roguelike Action Game

• Position: Producer

• Responsibilities

  • Managed teams' tasking through ClickUp: Every week I would create a sprint plan that distributed 15 hours worth of work to every team member. These 15 hours were the amount of hours expected of every team member every week. A team lead meeting would then occur where all estimates would be reviewed and any additional tasks would be added. After this meeting I created all tasks within ClickUp so the whole team would be able to track their work. Afterwards, myself and the leads, would follow up with team members to ensure that there were no issues with weekly tasking.

  • Here are some examples of ClickUp boards and tasks created throughout the project:

• Facilitating the Implementation of Scrum: All the way from the beginning of vertical slice to the completion of the project, I worked to Implement Scrum processes and artifacts to assist my team in productive ways. I created daily standup schedules that worked with all team members' schedules to raise attendance. I conducted weekly sprint planning meetings with team leads to modify and finalize weekly sprint plans. I incorporated sprint retrospective meetings to go over progress and field any questions about project direction from the team. On a bi-weekly basis I would conduct sprint retrospective with team members through a 1 on 1 format.

• Quality Assurance Organization and Feedback Collection: I was in charge of submitting builds for feedback from other teams in our cohort. These builds had corresponding google forms to collect data from playtesters. I then went through this data, along with the written feedback, and cataloged it to create new backlog items. These backlog items would be prioritized in terms of severity and distributed to team members every sprint.

• Updating the Team on Weekly Progress: Every day, I would update a weekly burndown chart. This chart would then be sent to the team detailing how many tasks were in each sub-section of the board. These charts also assisted me in seeing issues with work flow. For example: In the image below, you can see a large amount of tasks being marked as complete on the final day. This led to more frequent updates being sent to team leads for task reviews.