Aligning Technology with Business

CIO/CTO Update

Subscribe to CIO/CTO Update: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get CIO/CTO Update: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

CIO/CTO Update Authors: Andy Thurai, Thanh Tran, Lori MacVittie, Adrian Bridgwater, Reza Koohrang

Related Topics: Enterprise Architecture, CIO, CTO Journal, Enterprise Application Performance, CTOvision Journal, CIO/CTO Update

CIO: Blog Feed Post

Planning a Project – The TOGAF Way

Stakeholder analysis

If you have no intention of adopting TOGAF then does it make any sense for you to understand how TOGAF recommends planning a project? I think the answer is yes if somebody can explain it in simple terms. Since TOGAF is flexible and it recommends many techniques which you might find useful and apply in isolation, it may make sense for you to glance through these series of posts. (In this post I am talking about a technique of Stakeholder Analysis)

As we had seen earlier, the heart of the “TOGAF – ADM” is how you define the work that needs to be done. It is done from “Phase A” to “Phase F” in a top-down manor. (See my earlier post – What is TOGAF – without jargon for an overview)

In the last post we had seen that TOGAF – ADM consists of 4 major steps. I had grouped 6 phases of ADM to call it the second step. Now let me logically break this step into 3 sub steps.

  1. Tailor TOGAF to suit your need
  2. Define scope of work and prepare plan for rollout
    1. Define the scope and get approval from the sponsor
    2. Define requirement in terms of how the business process will change, what data, application and technical infrastructure is required for accomplishing the work – this step consists of 3 distinct phases (see this for detailed discussion)
    3. Select a suitable solution and make the implementation plan – this step is also made of 2 ADM phases
  3. Oversee development and implementation
  4. Manage post-implementation change

Define scope and get approval
[Phase A: Architecture Vision]

“…defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals…”

Architecture Vision” means a description of where we want to be. It is to be used, among others things, to help the sponsor to sell the project to stakeholders and decision-makers.

“…it describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented…”

New capability” in this context means whatever the enterprise will be able to do after the project is implemented which is not possible today.

More Stories By Udayan Banerjee

Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world. The focus is mostly on...

  • Keep the hype out and project a realistic picture
  • Uncover trends not very apparent
  • Draw conclusion from real life experience
  • Point out fallacy & discrepancy when I see them
  • Talk about trends which I find interesting