Typical result of Agile code first approach
Doing a code review today involving a project to remove functionality that is not longer used by 3rd parties. Someone posted a comment in the review, "So I know it would be a large work effort addition, but have we discussed removing <columnName> from the table? It is only used for <business function being removed>" This is typical for what I have seen of Agile development (by supposed experienced agile developers) in that they start something, start coding, then as they hit issues their scope expands because the didn't have a correct design to start with.
The answer to the question that was asked, was yes we need to remove all of the functionality supporting the business function being removed, not just the user interface for it. Their reply was that scope change tripled or quadrupled the work they need to do. If you have ever worked on a system with a percentage of its code associated with no-longer in use functionality, you know they answer they received. "You need to pull all of the code and columns exclusive to <business function>." Identify it, remove it, and supply QA with the information to test the remaining functionality that is touched by these changes.
posted by MrPopman @ 4:28 PM
0 Comments:
Post a Comment
<< Home