LEADER 02601oam 2200409zu 450 001 9910873767103321 005 20241212220421.0 035 $a(CKB)3420000000000887 035 $a(SSID)ssj0000776639 035 $a(PQKBManifestationID)12281902 035 $a(PQKBTitleCode)TC0000776639 035 $a(PQKBWorkID)10745006 035 $a(PQKB)10931306 035 $a(NjHacI)993420000000000887 035 $a(EXLCZ)993420000000000887 100 $a20160829d2012 uy 101 0 $aeng 135 $aur||||||||||| 181 $ctxt 182 $cc 183 $acr 200 10$a2012 Agile Conference 210 31$a[Place of publication not identified]$cIEEE$d2012 215 $a1 online resource (xi, 204 pages) $cillustrations 300 $aBibliographic Level Mode of Issuance: Monograph 311 08$a9781467326223 311 08$a1467326224 330 $aAgile methods provide an organization or a team with the flexibility to adopt a selected subset of principles and practices based on their culture, their values, and the types of systems that they develop. More specifically, every organization or team implements a customized agile method, tailored to better accommodate its needs. However, the extent to which a customized method supports the organizational objectives, i.e. the `goodness' of that method, is questionable. Existing agile assessment approaches focus on comparative analyses, or are limited in scope and application. In this research, we propose a structured, systematic, and comprehensive approach to assessing the `goodness' of agile methods. We examine an agile method based on (1) its adequacy, (2) the capability of the organization to support the adopted principles and practices specified by the method, and (3) the method's effectiveness. We propose the Objectives, Principles and Practices (OPP) Framework to guide our assessment. The Framework identifies (1) objectives of the agile philosophy, (2) principles that support the objectives, (3) practices that are reflective of the principles, (4) linkages among the objectives, principles and practices, and (5) indicators for assessing the extent to which an organization supports the implementation and the effectiveness of that practice. In this paper, we discuss our solution approach, preliminary results, and future work. 606 $aAgile software development$vCongresses 615 0$aAgile software development 676 $a005.11 702 $aieee 801 0$bPQKB 906 $aPROCEEDING 912 $a9910873767103321 996 $a2012 Agile Conference$92507124 997 $aUNINA