log 229: schedule

management

One of the hardest tasks I’ve dealt with since starting out with the programming team is scheduling. It’s always been difficult to manage my expectations because I want to keep pushing for more. I’m a big believer in “if you want it done right, do it yourself.” So the entire duration of building the MVP for Kynetik was a learning experience. However, after a couple of months I’ve learned to really appreciate my unique position and how I am privileged enough to hire a team of developers. Most issues are multifactorial, and this one definitely is. For someone like me, who isn’t established, $5,000 a month is a lot of money and I always want to keep pushing to get the most out of every cent. This is why I felt like my team fell short of my expectations. However, it was the complete opposite. They did things much faster than I expected. The issues only came when I realised that my guidelines were incomplete and we needed something extra. Or when I received feedback or a new idea and I wanted to change the plan slightly. This is what caused the speed bumps. This is also what distracted me when I was the only one working on previous versions. So I’ve come to learn that the $5,000 a month saves me an incredible amount of time and effort because there is absolutely no chance that I would have been able to do it myself. So, all of that learning was just project management. This past month I set specific requirements, submission dates, and the final publish date. I tried my best to delay or void quick new ideas to now mess up the flow. Instead I added it to the backlog. This turned out to be much better. The team was able to get things done on time and we were able to publish the version 1.3.0 of Kynetik with no hiccups. This is where all the fun is starting to happen. It’s all about innovating from now on and I need to create solid scheduling to make sure that we are always on track.