Reply to thread

Message

<blockquote data-quote="Umbran" data-source="post: 4682717" data-attributes="member: 177">It is easy to provide quality products (digital or otherwise) in a timely manner if you're doing repetitive, well-known and well-understood tasks in a well-known, well-understood situation.Unfortunately, most software development isn't like that.&nbsp; &nbsp;Ask someone who does house construction.&nbsp; When you have a set of plans, the first house you build with it runs over schedule, over budget, and has problems.&nbsp; As they build more houses from the same set of plans, what they have learned from previous work applies, and improves performance.In general, in software development, you're always working on the first house.&nbsp; Nobody wants a copy of old software, they want new software, new features, new UI, all cutting edge.&nbsp; The programmer typically doesn't have enough information to give really solid estimates at the start of a project.&nbsp;There are techniques for manage this, but don't make it sound easy.&nbsp; You need above standard managers and programmers to get things to come in on a timeline set early in the project.&nbsp; That's the nature of the work, not a failing onf hte programmers.</blockquote>

[QUOTE="Umbran, post: 4682717, member: 177"] It is easy to provide quality products (digital or otherwise) in a timely manner if you're doing repetitive, well-known and well-understood tasks in a well-known, well-understood situation. Unfortunately, most software development isn't like that. Ask someone who does house construction. When you have a set of plans, the first house you build with it runs over schedule, over budget, and has problems. As they build more houses from the same set of plans, what they have learned from previous work applies, and improves performance. In general, in software development, you're always working on the first house. Nobody wants a copy of old software, they want new software, new features, new UI, all cutting edge. The programmer typically doesn't have enough information to give really solid estimates at the start of a project. There are techniques for manage this, but don't make it sound easy. You need [i]above standard[/i] managers and programmers to get things to come in on a timeline set early in the project. That's the nature of the work, not a failing onf hte programmers. [/QUOTE]

Verification