Date Range: 01/25-29/2019
Total Hours Spent: 9
Overview
This past week has been primarily focused on organizing information for the Design Document deliverable coming up on the 31st. Our team got together last week to delegate the sections of the Design Document among ourselves which made me responsible for the completing the Technical Requirements, Key Feature List / Scope, and High Level Development Plan sections. Aside from that, I've been doing some casual research into A-frame documentation to find any features or 3rd party components that will be useful for achieving some of our technical goals.
I've been making use of spreadsheet templates I developed during my year long coop term in 2018 to organize our project backlog and start developing a detailed sprint plan. The template will be an asset for completing the development plan section of the design document and will help our team maintain living copies of our backlog and sprint plans. As a result, we'll be able to make any scope or scheduling adjustments as they may be needed throughout the development of this project.
Given the limited period of time between this milestone and the last there hasn't been a lot of opportunity to make great strides in terms on tangible progress; I've been focused on confirming that the necessary preparations are in place so our team can hit the ground running once development kicks off.
Challenges & Successes
The thing I've been struggling with the most over the past few days has been defining our feature list and technical requirements. I've worked with A-frame during my Design Studio 1 but the scope/complexity of the project was extremely limited compared to what we're planning to achieve with Kendo Gakko. It's been challenging to plan out a detailed list of technical features and requirements without understanding the development or research effort involved. I've come across native components in A-Frame for integrating Oculus Rift controls and virtual hands which I originally assumed to be a pretty big chunk of effort to figure out. I would also make this as a bit of a success given the amount of time we'll save but the uncertainty still remains for other features we're looking at.
Despite trying to put together a development plan with a myriad of unknowns, I'm satisfied with the results I managed to pull together since our last milestone. I know there will be a lot that changes each week, let alone between now and the end of the project, but I'm confident that the information I've pulled together is a great started point for this project.
Next Steps
The next few days will be dedicated to completing the Design Document, at which point we'll be ready to start focusing on officially kicking off the development of Kendo Gakko. As the project manager, I'll need to make sure I vigilantly maintain our backlog and development plan to ensure we always have a realistic sense of our progress as we work. It'll will be important to stay aware of our rate of progress to ensure we can address any risks, dependencies, or potential alterations to our scope well in advance.
There is a lot of work ahead of the team but I am eager to dive in and see what kind of magic we can make together.
Comments