| Summary: | 碩士 === 輔仁大學 === 資訊管理學系碩士在職專班 === 107 === Wang(2012) suggests that when adopted an agile development methodology, usually an outsourced project will fix time and price but leave the scope of the project flexible. This will cause the failure of an outsourced project. This study investigated how can an outsourced project successfully adopted agile development methodology.
This study conducts an action research on a public sector outsourcing project. Initially seven problems were identified: "a huge requirement gap between both sides", "no team spirit", "poor communication", "the progress of the project is seriously behind and the management is not transparent", "test without standardized criteria", "lack of a version control process", and "deploy system without quality control". Eight improvement objectives were established: "bridging the gap between both sides", "building agile team spirit and protocols to work together", "establishing communication mechanisms", "keep up with the project progress" , "making management more transparent", "developing standardized criteria for testing", "establishing a version control process", and "controlling quality before deployment". Afterwards, seven action plans were carried out and all the details for these actions were recorded.
This study found that in outsourcing projects the Product Owner is the key role to the success for Scrum projects. When the Product Owner doesn’t play his/her role, the project will be carried out based on contract without any flexibility. When there is a need to change requirements in a short period of time or in a large scale, the development team will refuse to accept all the requirement changes. There is no benefit to adopt an agile development methodology.
This study also found that under fixed contract, both the contractor and outsourcer have to form a consensus to work together. Otherwise, the project may not be able to success.
Finally, this study found that when adopting agile development methodology, the team should focus on a main objective: establishing a common agile team spirit and values and establishing communication mechanisms based on team and project characteristics. When speeding up and getting productive, the development team will eventually adopt appropriate tools and practices for software quality.
|
|---|
