Inicio Nosotros Búsquedas
Buscar en nuestra Base de Datos:     
Autor: Tiwana, Amrit (Comienzo)
2 registros cumplieron la condición especificada en la base de información BIBCYT. ()
Registro 1 de 2, Base de información BIBCYT
Publicación seriada
Referencias AnalíticasReferencias Analíticas
Autor: Tiwana, Amrit atiwana@bus.emory.edu
Oprima aquí para enviar un correo electrónico a esta dirección
Título: Beyond the Black Box: Knowledge Overlaps in Software Outsourcing
Páginas/Colación: pp. 51-58
Url: Ir a http://doi.ieeecomputersociety.org/10.1109/MS.2004.1331302http://doi.ieeecomputersociety.org/10.1109/MS.2004.1331302
IEEE Software Vol. 21, no. 5 Sept/Oct 2004
Información de existenciaInformación de existencia

Palabras Claves: Palabras: BLACK-BOX DEVELOPMENT BLACK-BOX DEVELOPMENT, Palabras: CONGRUENCE FRAMEWORK CONGRUENCE FRAMEWORK, Palabras: KNOWLEDGE MANAGEMENT KNOWLEDGE MANAGEMENT, Palabras: OUTSOURCING OUTSOURCING, Palabras: SOFTWARE DEVELOPMENT SOFTWARE DEVELOPMENT, Palabras: SOFTWARE PROJECT RISK SOFTWARE PROJECT RISK

Resumen
RESUMEN

RESUMEN

 

The well-known black-box model of software development outsourcing is typically effective. The approach assumes that the vendor can successfully solve a client organization's business problem without either organization having to deeply understand the other’s domain. This article reports on a field study of 209 global projects that explored the black-box approach’s limits as well as potential solutions to those limits. The study’s key finding is that the black-box approach usually works well in routine projects but fails in projects involving novelty. Novel projects require careful deviations from the black-box model depending on novelty type. Conceptually novel projects require the vendor to deeply understand the client’s business whereas projects involving novel development processes require deeper technical expertise on the client’s part. The article also presents insights into the effectiveness of capability maturity, intense architecture design effort, and development coordination tools. A knowledge congruence framework is offered to apply the findings to software development practice.

 

Registro 2 de 2, Base de información BIBCYT
Publicación seriada
Referencias AnalíticasReferencias Analíticas
Autor: Tiwana, Amrit atiwana@bus.emory.edu
Oprima aquí para enviar un correo electrónico a esta dirección ; Keil, Mark mkeil@gsu.edu
Oprima aquí para enviar un correo electrónico a esta dirección
Título: THE ONE-MINUTE RISK ASSESSMENT TOOL.
Páginas/Colación: pp. 73-77; 28 cm. ; il
Communications of the ACM Vol. 47, no. 11 November 2004
Información de existenciaInformación de existencia

Resumen
The article discusses the use of one-minute risk assessment tool in guiding managers how to reduce software project risk. The tool can also be given to each of the key stakeholders in a project, allowing the project manager to bring out differences in perception or conflicting views that may create trouble later on if they are not resolved. Only risk that is underappreciated and unmanaged has the power to surprise. While in any given situation, some risk drivers may be more controllable than others; most of the risk drivers fall within the project manager's sphere of influence. The most important drivers are ones over which managers can clearly exercise some control. Recognizing which risk drivers are amenable to managerial control and which are not is the key to walking the tightrope between calculated risks and outright gambling. Careful project planning and partitioning of attention can mitigate the former but rarely the latter. An understanding of the factors that drive risk and which ones can be influenced in a given situation can empower managers to have the serenity to accept the risks they cannot change, the courage to manage the risks they can control and the wisdom to know the difference. INSET: How the Study was Conducted.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno

Generados por el servidor 'bibcyt.ucla.edu.ve' (18.227.24.11)
Adaptive Server Anywhere (07.00.0000)
ODBC
Sesión="" Sesión anterior=""
ejecutando Back-end Alejandría BE 7.0.7b0 ** * *
18.227.24.11 (NTM) bajo el ambiente Apache/2.2.4 (Win32) PHP/5.2.2.
usando una conexión ODBC (RowCount) al manejador de bases de datos..
Versión de la base de información BIBCYT: 7.0.0 (con listas invertidas [2.0])

Cliente: 18.227.24.11
Salida con Javascript


** Back-end Alejandría BE 7.0.7b0 *