@wizz I do a kanban/scrum type thing. I’m the only tech person in a two team founder partnership. I’m a software engineer by trade. You have to understand why scrum exists to get benefits from it. It is meant to be a template, not doctrine, for your dev process. I personally like kanban better.
The daily scrum standup is meant to encourage communication amongst your team, and your team is meant to be comprised of many different roles. From SRE to infrastructure, DevOps, client support, devs and anyone else. A quick 2 sentence of what you are doing that might effect another discipline. Example if I’m updating the release pipeline, it might throw errors for the devs and tested bug fixes may not go out so I need to mentioned that to the rest of the team. Not what I’m changing in the pipeline or what I’m attempting to fix. That is a “parking lot” conversation for anyone who may want more intimate details of the changes I’m making. It’s not the babysitting that’s it’s turned into I. So many different orgs, but rather an FYI huddle.
Unless you are technical in nature and can talk the lingo, no t just the buzzwords, you may also need 2 devs not just one. Having someone tell you to not be an idiot and stop writing the code in a crappy way is a good thing. Though this is assuming you’ve already validated the idea and the MVP is successful enough that it is getting rebuilt.
If your MVP is successful, it needs to be rebuilt. It was done with the mindset of getting it out the door as fast a possible. It is a pile of technical debt to prototype features.