Yes, this sounds like like typical Enterprise software development. Actually it a sounds surprisingly competent compared to the average.<p>The biggest thing that's making your job boring is probably that your customer is doing most of what you would be expected to do. But this is a fantastic thing for the project - if someone who deeply understands and is embedded in the needs can write almost programmer ready specs then 50% of the project risk, confusion, and delays goes out the window.<p>Most enterprise software development is horribly slow, builds buggy, unusable products, and may never deliver.<p>The fact that your project many be over staffed, but still delivers repeatedly, actually makes makes management really happy.<p>Let me tell you about the best network engineer I've ever worked with. The guy did no apparent work. If you ever had any needs, he didn't even have to stop working on anything to give whatever you needed his full attention then and there. The reason he could do this was because had built everything to be scripted, monitored, and documented to the point that his stuff never broke. This have him time to script and monitor and plan for the future even more.<p>But the main takeaway was that even though he didn't do "work" everyday, he was worth a huge salary. His value to the company was the fact that the networks never went down, not that he ran around in a panic every day.<p>You worth to the company isn't that you are working hard - it's the output of your team. The fact that you aren't overloaded allows you to be responsive both inside the team and to the customer. This is way more valuable than you may think.<p>It sounds like you lucked into an unusually functioning project. If you want to stay in the Enterpise world, you aren't in a bad place.<p>(And yes, entprise programmers have an amazing ability to do only tiny amounts of work per day. It's incredible. I don't understand how many are employed)