Knowledge

Technology strategy

Source 📝

192:) is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document. The strategy includes the formal vision that guides the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives. 22: 114: 63: 288:
Process of IT Strategy is simplified with framework constituted of IT Service Management (ITSM), Enterprise Architecture Development (TOGAF) and Governance (COBIT). IT Strategy is modeled as vertical IT service applied to and supported by each horizontal layers of SOA architecture. For details, refer
506:
framework. Fundamentally, it is directed by a manager who oversees the process, which could include gaining targeted org. For instance, in the area of systematic exploration of emerging technologies, this approach help determine the relevance and opportunities offered by new technologies to business
235:
can be realized through technology and that technology investments are aligned with business. Some experts underscore the successful technology strategy is one that is integrated within the organization's overall business strategy not just to contribute to the mission and vision of the company but
762:
Essential strategy and enterprise architecture : strategy and enterprise architecture for business-aligned, SOA-based IT solution developed through different phases of preliminaries & foundation, business architecture, information system architecture, application & data architecture,
230:
A successful technology strategy involves the documentation of planning assumptions and the development of success metrics. These establish a mission-driven strategy, which ensures that initiatives are aligned with the organization's goals and objectives. This aspect underscores that the primary
271:
and sustain it, and how to compete in case that standards of technology is important. The final step is delivering the value, where firms define how to execute the strategy, make strategic decisions and take decisive actions. The Strategic Alignment Process is a step-by-step process that helps
239:
There are frameworks (e.g., ASSIMPLER) available that provide insights into the current and future business strategy, assess business-IT alignment on various parameters, identify gaps, and define technology roadmaps and budgets. These highlight key information, which include the following:
195:
Other generations of technology-related strategies primarily focus on: the efficiency of the company's spending on technology; how people, for example the organization's customers and employees, exploit technologies in ways that create value for the organization; on the full integration of
341:– An inventory of current projects being managed by the information technology department and their status. Note: It is not common to report current project status inside a future-looking strategy document. Show Return on Investment (ROI) and timeline for implementing each application. 211:(CTO) or equivalent. Accountability varies for an organization's strategies for other classes of technology. Although many companies write an overall business plan each year, a technology strategy may cover developments somewhere between three and five years into the future. 196:
technology-related decisions with the company's strategies and operating plans, such that no separate technology strategy exists other than the de facto strategic principle that the organization does not need or have a discrete 'technology strategy'.
262:
For a strategy to be effective, it should also answer questions of how to create value, deliver value, and capture value. In order to create value, one needs to trace back the technology and forecast on how the technology evolves, how the
478:
The IT strategy should also be presented or read by internal IT staff members. Many organizations will circulate prior year versions to internal IT department for feedback. The feedback is used to create new annual IT strategy plans.
474:
A technology strategy document is usually designed to be read by non-technical stakeholders involved in business planning within an organization. It should be free of technical jargon and information technology acronyms.
836:
Floyd, S.W. & Wolf, C. (2010) 'Technology Strategy' In: Narayanan, V.K. & O'Connor, G.C. (eds.) Encyclopedia of technology and innovation management. West Sussex: Wiley pp. 125–128.
207:. In the case of IT, the strategy is usually formulated by a group of representatives from both the business and from IT. Often the Information Technology Strategy is led by an organization's 502:
The implementation of technology strategy will likely follow the conventional procedure taken when implementing a business strategy or an organization's planned changes within the so-called
280:
Aligned with Statement Of Applicability (SOA) approach, IT strategy is composed of IT Capability Model (ITCM) and IT Operating Model (IT-OM) as proposed by Haloedscape IT Strategy Model.
631: 846:
Lawson, J (2006) "Delivering on Strategy: Those That Can...Do!! Those Who Simply Talk... Make Another Fine Mess", "Spectra – Journal of the MCA, June 2006"
199:
A technology strategy has traditionally been expressed in a document that explains how technology should be utilized as part of an organization's overall
743: 786: 876: 214:
The United States identified the need to implement a technology strategy in order to restore the country's competitive edge. In 1983
872:. This case study is widely quoted example how technology has large impacts an overall organization's overall business strategy. 770: 628: 35: 132: 124: 244:
The important components of information tech-strategy is information technology and strategic planning working together.
490:
to create an appropriate on-line presence. Large organizations frequently have complex web site requirements such as
863: 841: 699: 656: 613: 588: 168: 150: 49: 817: 727: 897: 554: 254:
The degree to which the IT mission, objectives, and plans support and are supported by the business mission,
692:
The Power of Convergence: Linking Business Strategies and Technology Decisions to Create Sustainable Success
435:
Description of disruptive forces that could cause the organization to become less profitable or competitive.
892: 549: 460:
List of monthly, quarterly or mid-year milestones and review dates to indicate if the strategy is on track.
337: 847: 544: 219: 396: 794: 208: 41: 344:
An catalog of existing applications supported, and the level of resources required to support them
516: 491: 248: 268: 84: 424: 8: 267:
changes, and how to organize effectively. Capturing value requires knowledge how to gain
877:"Strategic alignment: Leveraging information technology for transforming organizations" 510: 423:(faster processors, networks or storage at lower costs) will impact the organization's 389: 272:
managers stay focused on specific task in order to execute the task and deliver value.
264: 200: 507:
through its well-defined assessment mechanisms that can effectively justify adoption.
859: 837: 813: 766: 723: 695: 652: 609: 584: 539: 515:
A technology strategy document typically refers to but does not duplicate an overall
503: 232: 810:
The Strategic Management of Technology: A Guide for Library and Information Services
414:
Example: List of available Professional Service contractors for short term projects
869: 215: 483: 420: 886: 635: 357: 870:
The Human Capital Impact on e-Business: The Case of Encyclopædia Britannica
222:
program, was established to develop a national technology strategy policy.
204: 88: 690:
Hoque, Faisal; Walsh, Lawrence; Mirakaj, Diana; Bruckner, Jeffrey (2011).
526:
High-level view of physical architecture of information technology systems
523:
High-level view of logical architecture of information technology systems
411:
Description of new cost reduction or efficiency increase opportunities.
482:
One critical integration point is the interface with an organization's
347:
Architectural directions and methods for implementation of IT solutions
579:
Mistrik, Ivan; Tang, Antony; Bahsoon, Rami; Stafford, Judith (2012).
77: 511:
Relationship between strategy and enterprise technology architecture
231:
objective of designing technology strategy is to make sure that the
559: 487: 73: 292: 744:"ASSIMPLER EA Framework - Making Life Simpler for an Enterprise" 297:
The following are typically sections of a technology strategy:
388:
Example: Growth of high-quality web user interfaces driven by
787:"Definition: ITSM (IT Service Management) • Join Us! »" 647:
Donaldson, Scott; Siegel, Stanley; Donaldson, Gary (2012).
486:. The marketing plan frequently requires the support of a 255: 251:
functionality to both shape, and support business strategy.
578: 301:
Executive Summary – This is a summary of the IT strategy.
694:. New York: American Management association. p. 98. 689: 275: 646: 283: 606:
Information Technology Control and Audit, Third Edition
581:
Aligning Enterprise, System, and Software Architectures
382:
Summary of changes driven from outside the organization
720:
Management of Technology: Perception and opportunities
403:
List of new IT projects requested by the organization.
855:
The Business Value of Computers: An Executive's Guide
884: 293:Typical structure of a (IT) technology strategy 247:The IT strategy alignment is the capability of 603: 463:List milestone name, deliverables and metrics 812:. Oxford: Chandos Publishing. p. 214. 755: 753: 604:Senft, Sandra; Gallegos, Frederick (2010). 50:Learn how and when to remove these messages 852: 722:. London: Chapman & Hall. p. 70. 608:. Boca Raton, FL: CRC Press. p. 204. 446:IT organization roles and responsibilities 310:Approach and methodology of the engagement 879:. IBM research. Retrieved 7 November 2013 519:. The technology strategy may refer to: 443:IT Organization structure and Governance 313:Relationship to overall business strategy 169:Learn how and when to remove this message 151:Learn how and when to remove this message 750: 629:Information Technology Strategy Projects 583:. Hershey, PA: IGI Global. p. 17. 885: 763:platform & technology architecture 276:Meta-model of (IT) technology strategy 807: 765:. Middletown, DE: Haloedscape Haves. 759: 395:Example: Availability of open source 284:Framework of (IT) technology strategy 225: 875:J. C., Henderson; , N. Venkatraman. 717: 713: 711: 685: 683: 289:Haloedscape IT Strategy Framework. 107: 56: 15: 13: 304:High level organizational benefits 123:tone or style may not reflect the 14: 909: 708: 680: 671: 497: 31:This article has multiple issues. 857:, The Information Economic Press 438:Analysis IT usage by competition 374:Current IT department weaknesses 366:Current IT departments strengths 133:guide to writing better articles 112: 61: 20: 801: 779: 651:. New York: Apress. p. 9. 529:Technology rationalization plan 186:information technology strategy 39:or discuss these issues on the 736: 665: 640: 622: 597: 572: 76:format but may read better as 1: 830: 555:Second half of the chessboard 385:Rising expectations of users 853:Strassmann, Paul A. (1990), 550:Project portfolio management 338:project portfolio management 7: 545:Enterprise planning systems 533: 469: 397:learning management systems 307:Project objective and scope 236:also get support from it. 220:Defense Intelligence Agency 10: 914: 356:Includes a SWOT Analysis 565: 209:Chief Technology Officer 517:enterprise architecture 350:Current IT departmental 325:Summary of key projects 85:converting this article 760:Singh, Neeraj (2015). 492:web content management 332:Internal capabilities 808:Baker, David (2004). 269:competitive advantage 898:Strategic management 893:Technology strategy 791:servicemanagers.org 718:Lowe, Paul (1995). 449:IT role description 419:Description of how 182:Technology strategy 674:Strategy Execution 265:market penetration 226:Effective strategy 201:corporate strategy 87:, if appropriate. 848:See Article Here. 772:978-1-5078-4014-6 540:Business strategy 504:change management 316:Resource summary 233:business strategy 205:business strategy 179: 178: 171: 161: 160: 153: 127:used on Knowledge 125:encyclopedic tone 106: 105: 54: 905: 858: 824: 823: 805: 799: 798: 793:. Archived from 783: 777: 776: 757: 748: 747: 740: 734: 733: 715: 706: 705: 687: 678: 677: 669: 663: 662: 644: 638: 626: 620: 619: 601: 595: 594: 576: 379:External Forces 216:Project Socrates 174: 167: 156: 149: 145: 142: 136: 135:for suggestions. 131:See Knowledge's 116: 115: 108: 101: 98: 92: 83:You can help by 65: 64: 57: 46: 24: 23: 16: 913: 912: 908: 907: 906: 904: 903: 902: 883: 882: 833: 828: 827: 820: 806: 802: 785: 784: 780: 773: 758: 751: 742: 741: 737: 730: 716: 709: 702: 688: 681: 670: 666: 659: 645: 641: 627: 623: 616: 602: 598: 591: 577: 573: 568: 536: 513: 500: 472: 427:for technology. 295: 286: 278: 228: 175: 164: 163: 162: 157: 146: 140: 137: 130: 121:This article's 117: 113: 102: 96: 93: 82: 66: 62: 25: 21: 12: 11: 5: 911: 901: 900: 895: 881: 880: 873: 867: 850: 844: 832: 829: 826: 825: 818: 800: 797:on 2017-12-21. 778: 771: 749: 735: 728: 707: 700: 679: 672:Bernd, Bernd. 664: 657: 639: 634:2010-07-31 at 621: 614: 596: 589: 570: 569: 567: 564: 563: 562: 557: 552: 547: 542: 535: 532: 531: 530: 527: 524: 512: 509: 499: 498:Implementation 496: 484:marketing plan 471: 468: 467: 466: 465: 464: 461: 455: 454: 453: 450: 447: 441: 440: 439: 436: 430: 429: 428: 417: 416: 415: 408:Opportunities 406: 405: 404: 401: 400: 399: 393: 383: 377: 376: 375: 369: 368: 367: 354: 353: 352: 351: 348: 345: 342: 330: 329: 328: 327: 326: 323: 320: 314: 311: 308: 305: 294: 291: 285: 282: 277: 274: 260: 259: 252: 245: 227: 224: 177: 176: 159: 158: 120: 118: 111: 104: 103: 69: 67: 60: 55: 29: 28: 26: 19: 9: 6: 4: 3: 2: 910: 899: 896: 894: 891: 890: 888: 878: 874: 871: 868: 865: 864:0-9620413-2-7 861: 856: 851: 849: 845: 843: 842:1-4051-6049-7 839: 835: 834: 821: 815: 811: 804: 796: 792: 788: 782: 774: 768: 764: 756: 754: 745: 739: 731: 725: 721: 714: 712: 703: 701:9780814416952 697: 693: 686: 684: 675: 668: 660: 658:9781430235934 654: 650: 643: 637: 636:archive.today 633: 630: 625: 617: 615:9781420065503 611: 607: 600: 592: 590:9781466621992 586: 582: 575: 571: 561: 558: 556: 553: 551: 548: 546: 543: 541: 538: 537: 528: 525: 522: 521: 520: 518: 508: 505: 495: 493: 489: 485: 480: 476: 462: 459: 458: 456: 452:IT governance 451: 448: 445: 444: 442: 437: 434: 433: 431: 426: 422: 418: 413: 412: 410: 409: 407: 402: 398: 394: 391: 387: 386: 384: 381: 380: 378: 373: 372: 370: 365: 364: 362: 361: 360: 359: 358:SWOT analysis 349: 346: 343: 340: 339: 334: 333: 331: 324: 321: 318: 317: 315: 312: 309: 306: 303: 302: 300: 299: 298: 290: 281: 273: 270: 266: 257: 253: 250: 246: 243: 242: 241: 237: 234: 223: 221: 217: 212: 210: 206: 202: 197: 193: 191: 187: 183: 173: 170: 155: 152: 144: 134: 128: 126: 119: 110: 109: 100: 97:November 2016 91:is available. 90: 86: 80: 79: 75: 70:This article 68: 59: 58: 53: 51: 44: 43: 38: 37: 32: 27: 18: 17: 854: 809: 803: 795:the original 790: 781: 761: 738: 719: 691: 673: 667: 649:CTOs at Work 648: 642: 624: 605: 599: 580: 574: 514: 501: 481: 477: 473: 355: 335: 296: 287: 279: 261: 258:, and plans. 238: 229: 213: 198: 194: 189: 185: 181: 180: 165: 147: 138: 122: 94: 89:Editing help 71: 47: 40: 34: 33:Please help 30: 457:Milestones 421:Moore's law 371:Weaknesses 190:IT strategy 887:Categories 831:References 819:1843340429 729:0412643707 392:technology 363:Strengths 36:improve it 256:objective 203:and each 141:June 2017 42:talk page 632:Archived 560:Strategy 534:See also 488:web site 470:Audience 432:Threats 319:Staffing 322:Budgets 218:, a US 862:  840:  816:  769:  726:  698:  655:  612:  587:  72:is in 566:Notes 78:prose 860:ISBN 838:ISBN 814:ISBN 767:ISBN 724:ISBN 696:ISBN 653:ISBN 610:ISBN 585:ISBN 390:Ajax 74:list 425:ROI 336:IT 188:or 889:: 789:. 752:^ 710:^ 682:^ 494:. 249:IT 45:. 866:. 822:. 775:. 746:. 732:. 704:. 676:. 661:. 618:. 593:. 184:( 172:) 166:( 154:) 148:( 143:) 139:( 129:. 99:) 95:( 81:. 52:) 48:(

Index

improve it
talk page
Learn how and when to remove these messages
list
prose
converting this article
Editing help
encyclopedic tone
guide to writing better articles
Learn how and when to remove this message
Learn how and when to remove this message
corporate strategy
business strategy
Chief Technology Officer
Project Socrates
Defense Intelligence Agency
business strategy
IT
objective
market penetration
competitive advantage
project portfolio management
SWOT analysis
Ajax
learning management systems
Moore's law
ROI
marketing plan
web site
web content management

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.