You are part of that 3/4. A proof of concept or mockup to verify that you've correctly captured requirements? Sounds like planning to me. Determining which te

You are part of that 3/4. A proof of concept or mockup to verify that you've correctly captured requirements? Sounds like planning to me. Determining which technology stack is best, including building (to be clear, I mean coding) some basic systems to test out if your assumptions about performance and writing the pieces are correct? That's planning. And so on. Hours spent writing code are not mutually exclusive to hours spent planning for the success of a software project.