Font Size: a A A

Research On Progress Management In Software Project F Based On Agile Software Development Methodology

Posted on:2023-09-02Degree:MasterType:Thesis
Country:ChinaCandidate:L Z HanFull Text:PDF
GTID:2558306914474084Subject:Project management
Abstract/Summary:PDF Full Text Request
With the impact of the epidemic since 2020,the development and growth rate of the whole software industry in China has been significantly affected.The software industry market is rapidly tilting towards the demander’s market.In order to reduce its own risks as much as possible when the project is implemented,the bid inviter of software projects will add a large number of flexible and fuzzy demands to the project at the beginning of project establishment.As a software enterprise,in order to survive in this rapidly evolving market pattern,in addition to the technology accumulation and team resources it must have.It also needs to think about what methodology to adopt and how to effectively control the project requirement risk,which is related to a number of development indicators such as enterprise cost investment,brand effect and enterprise benefit.This study takes CQZY project of CL Company as the research entity to study the requirement risk management of software development project.Firstly,the requirement risk in the project is identified through brainstorming and Delphi method,and finally the requirement risk factors of 22 projects are identified.Then,using the risk matrix analysis method,the identified requirement risks are quantitatively analyzed from the two dimensions of requirement risk occurrence probability and impact degree.According to the analysis results,the identified 22 requirement risks are divided into three levels:high,medium and low,including 5 high-level risks,11 medium-level risks and 6 low-level risks.For the high-level risk,this paper uses the game analysis method to analyze its requirement risk response strategy,studies the "Nash equilibrium" that may exist between Party A and Party B in the process of requirement risk game,and gives the equilibrium point that both parties may achieve a win-win situation according to the final research conclusion;For medium-level and low-level risks,risk mitigation,transfer,acceptance and other methods are used to formulate and implement response strategies.Finally,the risk tracking table is used to continuously track and monitor the changes after the requirement risk response.Through the research on the requirement risk of software development project,the conclusions are as follows:First of all,in the requirement risk identification stage,the combination of brainstorming method and Delphi method can better achieve the expectation of project requirement risk identification,and can quickly identify the requirement risk of software project.Secondly,in the stage of requirement risk assessment,the risk index of each risk factor can be obtained by using the risk evaluation matrix method,which is arranged in the order of risk factor index from high to low,so as to accurately distinguish the level of demand risk.Thirdly,in the requirement risk response stage,different response measures for high-level and low-level requirement risks can achieve better requirement risk response effect.Especially for high-level risks,using game analysis method can effectively guide the requirement risk response strategy of the project team and reduce the trial and error cost of Party A and Party B;For the middle-level and low-level requirement risk,the traditional countermeasures such as mitigation,avoidance and acceptance can be adopted,so as to better control the requirement risk of the project.Finally,in the requirement risk monitoring stage,the use of risk tracking table and other tools to regularly monitor,feed back and record the risk can effectively ensure the closed-loop management of requirement risk.
Keywords/Search Tags:software project, requirement risk management, game theory, risk matrix
PDF Full Text Request
Related items