Bridging On-site Practices and Design Principles for Service Development

The significance of collaboration between developers and operators has increased through service lifecycles, as they are expected to explore their clients' pains and co-create new ICT systems for their business opportunities through a number of trials. However, such agile development has caused conflicts with the conventional development management, which assumes waterfall development. This development process is administrated by the progress of documents statuses, such as created, reviewed, updated, and finalized, at development sites. This paper introduces a document-concern-design model to indicate developers their associated tasks to update specific sections of documents during their repetitive work between development and operation. The model incorporates three domains - document review process, concern, and design principle - with linking them one-by-one and form a single structure. This procedure enables to adapt any on-site local rule of design and development. Hence, the system can be introduced to any developers' site with little adaptation cost. Then, this mechanism can accelerate various collaborative activities between developers and operators and guide their deliverables.