I came to my current place of employment as an contracted IT support technician of the most generic variety about a year ago. I had only an associates degree to my name and most of what I knew both as a support technician, and as a tech professional in general, was self taught. In short time, I showed myself to be useful enough to warrant hiring, and further more, worthy of more duties. I soon found myself working as a DevOps / Automation Engineer. Lot's of scripting.
Not to long after this transition I was tasked to build a web application for the enterprise that, in the long run, would serve as a central hub for day to day IT operations, with a focus on automation. Even without knowing the complete ins and outs of designing, prototyping, building, and maintaining a project of such scale, I knew this would be a lot for one person, but did not want to throw up the white flag just yet.
I am apart of a dev team of just three people, one of which has their own monolithic project, though not quite as large as my own, and the other who doesn't know enough about the technologies we use to adequately help us. I am approaching the UAT phase and have a growing backlog. Part of me wants to pack a bag and disappear to a place without electricity. More rationally though, I am thinking about talking to my boss about the workload and my struggle to carry it.
What would be best way to approach this situation to relieve the stress/pressure levels?
Edit: I realized I forgot to mention a key part of our development cycle. We have 3 week iterations (sprints) with catchups / demos at the end. We did not always have this in place. At the start, I was developing in a bubble with little to no feedback.