2009
DOI: 10.1016/j.techfore.2008.03.018
|View full text |Cite
|
Sign up to set email alerts
|

An architectural framework for roadmapping: Towards visual strategy

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
197
0
6

Year Published

2015
2015
2024
2024

Publication Types

Select...
8
1

Relationship

1
8

Authors

Journals

citations
Cited by 252 publications
(203 citation statements)
references
References 7 publications
0
197
0
6
Order By: Relevance
“…Its emphasis shifts from the roadmap as a graphical product for the developing process of the roadmap [29]. In terms of the organization, communication work during the roadmapping process is usually a more important output than the final roadmap [26,27].…”
Section: Methodological Frameworkmentioning
confidence: 99%
See 1 more Smart Citation
“…Its emphasis shifts from the roadmap as a graphical product for the developing process of the roadmap [29]. In terms of the organization, communication work during the roadmapping process is usually a more important output than the final roadmap [26,27].…”
Section: Methodological Frameworkmentioning
confidence: 99%
“…[23]. Even though it is frequently used by a broad spectrum of firms and business sectors, the research in this field is relatively sparse [26]. Furthermore, it has not been widely applied to geographical issues and regional sustainability.…”
mentioning
confidence: 99%
“…The final phase of the foresight process involved the elaboration of operational plan for the implementation of the preferred R&D scenario with the use of technology roadmapping method (Phaal, Muller 2009). The plan in the form of a technology roadmap was developed during workshops by a group of internal experts supervised by the institute's foresight methodology team.…”
Section: Methodsmentioning
confidence: 99%
“…Nelson Sekitoleko [9] found that improved knowledge sharing between technical and managerial staff on different levels can significantly improve the ability to create a good plan that considers interdependencies between features and addresses both business and technical challenges. Robert Phaal and Gerrit Muller [10] discussed the value of having what they called "Linked analysis grids" that is used in directly linking business requirements with technological aspects of these requirements, then use a scoring technique that ranks product's backlog according to technical priority and complexity. Wojciech and Dorota [11] investigated the inherent risks in different agile methodologies, and concluded that a special risk mitigation process is mandatory.…”
Section: Related Workmentioning
confidence: 99%