High-Speed Software Development Practices: What Works, What Doesn't
Guardat en:
| Publicat a: | IT Professional Magazine vol. 8, no. 4 (Jul/Aug 2006), p. 29 |
|---|---|
| Autor principal: | |
| Altres autors: | , , |
| Publicat: |
IEEE Computer Society
|
| Matèries: | |
| Accés en línia: | Citation/Abstract Full Text - PDF |
| Etiquetes: |
Sense etiquetes, Sigues el primer a etiquetar aquest registre!
|
MARC
| LEADER | 00000nab a2200000uu 4500 | ||
|---|---|---|---|
| 001 | 206330746 | ||
| 003 | UK-CbPIL | ||
| 022 | |a 1520-9202 | ||
| 024 | 7 | |a 10.1109/MITP.2006.86 |2 doi | |
| 035 | |a 206330746 | ||
| 045 | 2 | |b d20060701 |b d20060831 | |
| 084 | |a 70293 |2 nlm | ||
| 100 | 1 | |a Baskerville, Richard | |
| 245 | 1 | |a High-Speed Software Development Practices: What Works, What Doesn't | |
| 260 | |b IEEE Computer Society |c Jul/Aug 2006 | ||
| 513 | |a Feature | ||
| 520 | 3 | |a In the past decade, development cycles for such products have shrunk from a year or more to one to three months, to accommodate rapid and significant feature changes. Coincidentally, there is a growing interest in agile methodologies such as Extreme Programming and Scrum that are more formal than hacking and less formal than traditional methods. Although agile and plan-driven methods are likely to be successful in their home ground, in many projects a hybrid mix of these methods might be most appropriate. We believe it is critical for developers to understand the pros and cons of some of the more popular practices so that they can better balance quality, cost, and development speed, and avoid reinventing solutions. Beyond the work of highly visible leaders, such as Microsoft and Netscape, little is known about high-speed software development - the processes and steps to retaining quality in this accelerated cycle. To this end, we conducted an empirical study of high-speed software development practices in US companies. As the "Anatomy of an Empirical Study" sidebar explains, we first reviewed detailed case studies of Internet software development in 10 companies and then synthesized knowledge on best practices for quality and agility. | |
| 651 | 4 | |a United States--US | |
| 653 | |a Information technology | ||
| 653 | |a Software engineering | ||
| 653 | |a Competitive advantage | ||
| 653 | |a Product development | ||
| 653 | |a User training | ||
| 653 | |a Data collection | ||
| 653 | |a Internet | ||
| 653 | |a Methods | ||
| 653 | |a Teams | ||
| 653 | |a Qualitative research | ||
| 653 | |a Grounded theory | ||
| 653 | |a Case studies | ||
| 653 | |a Software | ||
| 653 | |a Software development | ||
| 700 | 1 | |a Balasubramaniam Ramesh | |
| 700 | 1 | |a Levine, Linda | |
| 700 | 1 | |a Pries-Heje, Jan | |
| 773 | 0 | |t IT Professional Magazine |g vol. 8, no. 4 (Jul/Aug 2006), p. 29 | |
| 786 | 0 | |d ProQuest |t ABI/INFORM Global | |
| 856 | 4 | 1 | |3 Citation/Abstract |u https://www.proquest.com/docview/206330746/abstract/embedded/H09TXR3UUZB2ISDL?source=fedsrch |
| 856 | 4 | 0 | |3 Full Text - PDF |u https://www.proquest.com/docview/206330746/fulltextPDF/embedded/H09TXR3UUZB2ISDL?source=fedsrch |