A Tentative Framework for Managing Software Product Development in Small Companies

Authors:
K. Rautianen;C. Lassenius;J. Vähäniitty;M. Pyhäjärvi;J. Vanhanen
Affiliations:
-;-;-;-;-
Venue:
HICSS '02 Proceedings of the 35th Annual Hawaii International Conference on System Sciences (HICSS'02)-Volume 8 - Volume 8
Year:
2002

Citing 0
Cited 6

OUTLINING A MODEL OF A RELEASE MANAGEMENT PROCESS

Journal of Integrated Design & Process Science
Information systems success factors in software SMEs: a research agenda

International Journal of Business Information Systems
The influence of the best practices of information system development on software SMEs: a research scope

International Journal of Business Information Systems
Information system development approach: facts from IT SMEs in India

International Journal of Business Information Systems
An information systems design product theory for the class of integrated requirements and release management systems

Journal of Software Maintenance and Evolution: Research and Practice
A case study on the success of introducing general non-construction activities for project management and planning improvement

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement

Quantified Score

Hi-index	0.00

Visualization

Abstract

Deploying an appropriate software process can improve the effectiveness of software engineering. Still, small companies find it hard to allocate resources to software process improvement and tailor existing process models for their needs. In this paper we present a tentative framework for managing software product development in small companies. The framework combines business and process management through four cycles of control: (1) Strategic release management provides the interface between business management and product development. (2) Release project management handles the development of individual product versions. (3) Iteration management deals with the incremental development of product functionality within release projects, and (4) Mini-milestones are used to get an indication of system status during development.