Publication

Abstract : It is very prevalent in IT sectors that the programmers want to do the best of the possible job to deliver the most desirable product to their customers, thus winning fame, fortune and more expanded offers. Once the programmers have configured the result that can grant all that it is expected to do far before the project timeframe, the customers and developers envisage additional capability that can be obtained from the solution which result needing additional engaging for the development. This will lead to an overly complex software product that caters for various requirements but are not simple and easy on the clients on usage of the solution. Unnecessary “little mores” that are added to make the software perfect actually brings about characteristic crawl, “Feature Creep. Uncontrolled featuritis might prompt growth creep known as "Scope creep"- extension for a task growth. This paper presents an approach to reduce feature creep to a certain extent as complete avoidance may not be reasonably expected. To ensure that those necessities which are highly required, we might select them by applying some selection strategies rather than by applying the conventional requirements freezing and code freezing approaches or any other follow up feature reduction methods. We have proposed a proactive technique that can be implemented along with the conventional SDLC processes of software development. This system deals with all those forms of creep that can occur in each of different phases of development cycle.