Survey on Long-Term Product Planning and Requirements Prioritization to Customer Value Creation
Abstract
Software development projects are subject to risks like any other project. Software development is subject to unique risks which can be mitigated through effective risk management techniques. Risks are unavoidable and must be managed. Successfully managing risks assists developers in completing the project on time and on budget. Strategies selected to manage risk may result in a better product than originally anticipated. Identifying, analyzing, tracking, and managing software risk aids crucial decision making including release readiness. Software project suffers from many problems like high computational cost, higher delay time in designing the projects, not meeting the actual need of the user, and many systems are being unutilized. These problems are solved using the software risk management which helps the software developer to identify, analyze, and accordingly deal with software risks items.
Software risk management is also an attempt to define and formulate the risk oriented connection of success into a definite set of methods and techniques. Global Software development is learning and individuals escalated action. Individuals in such gatherings must work together, convey, and coordinate their work, which makes learning management a need. Point of the fact, little and stable associations where workers are inside an arm’s compass of one another can most likely make without information management. In any case, for associations that are huge and appropriated, whose environment is consistently changing, or have a high turnover, dealing with their information stakes are basic for survival.
This Paper focuses on a pilot survey carried out at small software firms and results of employees are recorded and analyzed with help of IBM SPSS.
Keywords
Download Options
Introduction
Project managers observe and aide the work of planners, designers and analyzes of software while now and again taking part in these exercises themselves. Where developer concentrates on code, construction modeling and execution, managers keep tabs on elevated amount concerns: the course of the project, allotment of assets, the list of capabilities, and the client experience. Supervisors work to synchronously fulfill stipulations imposed by clients, engineers, analyzers, maintainers and management.
Creating value for different customer segments is essential to the business of a company. Thus, software product development companies' ability to implement the most valuable requirements in their products has been seen as critical. The literature offers requirements prioritization methods for selecting requirements, but their suitability for solving practical challenges is not clear. The state of the practice in long-term product planning and requirements prioritization, and the practical challenges involved is not thoroughly analyzed. Therefore, the connection between the selection of product features and customer value creation is also an area that needs more investigation.
Conclusion
A positive relationship exists between Product and satisfaction of customer & Value of your product is directly proportional to satisfaction level of customer are accepted by the pilot survey conducted For researchers, this study shall provide a broad analysis of the practical challenges and characteristics of requirements prioritization and long-term planning in market-driven software development. Our results indicate that requirements prioritization in practice is a broader issue than just comparing a set of requirements at the same level of abstraction with each other, as is assumed in many existing prioritization methods. Our results shall provide implications to researchers about what should be taken into account when developing methods and practices for requirements prioritization and long-term planning. For example, the researchers in the field might benefit from understanding that the three main aspects (business, customer& users, and implementation) are used in practice in requirements prioritization.