May 24, 2018 at 7:56 am
Hello,
I'm asking a more broad question other than just SQL Server but we are tasked to redesign our entire system into a new DB and a new coding language. We are having conflicts with our customer on level of effort numbers. They 1) don't like our LOE cause its long and 2) say we aren't approaching the LOE properly.
Just wondering if anyone has suggestions on methodologies on how to come up with an LOE for a system redesign in a logical and detailed manner. One way we have been asked to do it is to physically go through 1,000's of code pages and identify any business rules, queries etc inside the code. The system is old and a lot of stuff isn't greatly documented. So, for us to go through every code page and do what they want is just ridiculous.
So, just wondering what approach everyone else would take to provide a realistic estimate or something you have actually done? We can count pages, count lines of code, count DB objects etc... and use some low, medium and high categorizations but they don't seem to be receptive.
Any thoughts, ideas or examples of LOE analyses any of you have done would be super helpful just for brainstorming...
Thanks!
June 22, 2018 at 1:17 pm
Wow, this is a scary question. My first thought is to run for the door. I've become very accustomed to working in an Agile environment and this sounds much different. What is the nature of the customer relationship? Is this a full-time employee position or are you contracted with this customer? Just curious...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply