Publication: Assessing the status of a roadmap: When is the time to review?
dc.contributor.author | Ronald Vatananan | en_US |
dc.contributor.author | Nathasit Gerdsri | en_US |
dc.contributor.other | Mahidol University | en_US |
dc.date.accessioned | 2018-10-19T04:50:14Z | |
dc.date.available | 2018-10-19T04:50:14Z | |
dc.date.issued | 2013-12-26 | en_US |
dc.description.abstract | Maintaining a roadmap is a crucial part for any organization that wants to keep the roadmapping process alive after its development. However, it is not easy to maintain and review a roadmap, because an organization is exposed to constant changes in its business environment. An organization has to review its roadmap to include the changes that have a significant affect on the status of the roadmap. But, to determine when it is time to review a roadmap is a major challenge for any organization. As a result, most organizations maintain a roadmap on a predetermined regular basis. This paper proposes an analytical approach and evaluation model to determine the status of a roadmap. The proposed approach will assist an organization to decide when a review of its roadmap is necessary. A case example is presented to demonstrate the computational process and applicability of the proposed approach. © 2013 PICMET. | en_US |
dc.identifier.citation | 2013 Proceedings of PICMET 2013: Technology Management in the IT-Driven Services. (2013), 2200-2211 | en_US |
dc.identifier.other | 2-s2.0-84890842434 | en_US |
dc.identifier.uri | https://repository.li.mahidol.ac.th/handle/20.500.14594/31571 | |
dc.rights | Mahidol University | en_US |
dc.rights.holder | SCOPUS | en_US |
dc.source.uri | https://www.scopus.com/inward/record.uri?partnerID=HzOxMe3b&scp=84890842434&origin=inward | en_US |
dc.subject | Computer Science | en_US |
dc.title | Assessing the status of a roadmap: When is the time to review? | en_US |
dc.type | Conference Paper | en_US |
dspace.entity.type | Publication | |
mu.datasource.scopus | https://www.scopus.com/inward/record.uri?partnerID=HzOxMe3b&scp=84890842434&origin=inward | en_US |