Main Nav

Hi Renee - just wondering if you got any response you could share. Sam

Comments

Message from mgdaley@umich.edu

We have used a "Brick" model similar to what is used by the NIH and Gartner to define our technology roadmap. The categories are "Tactical", Strategic", "Emerging", "Containment", and "Retirement". We even color-coded them so visually many folks can understand the roadmap. It has grown from our original template in MS Word to now being lists within SharePoint. Our goal in moving to SharePoint was for the information to be more data centric and less static. This allows us to sort, query, etc. If we were to do it all over again, I'm not sure SharePoint would be our tool of choice, but at this point in our evolution it's getting the job done. Attached is an example of the word-based template. Let me know if you have any further questions and I'll be happy to help. -- ______________________________ Michael Daley Technical Infrastructure and Capacity Planning Manager Information & Technology Services - University of Michigan Arbor Lakes Bldg 1 - 2720 4251 Plymouth Rd. Ann Arbor, MI 48105-3640 734.647.9099
Michael,

If you were going to start from scratch today, what would choose from a tool perspective and why?  Wisconsin has a nice wiki-based approach, which I like because you don't have to click in when viewing from a website.  That said, there's no easy way to search/display targets at an abstract level, like "show me all the current retirement targets."

What are others doing?

Sharif



Hi Sharif,

Some of the semantic wiki schemes out there might be useful here...

Such as: semantic mediawiki, loki ( http://loki.ia.agh.edu.pl/about.php ) , or even the data or semanticdata plugins to dokuwiki.

I haven't worked with this myself, but they should allow you to metatag content and encode relations into pages that allow for structured querying later...

Wayde.
Wayde Nie <niew@mcmaster.ca>
McMaster University
Burke Science Building, Rm 233
1280 Main Street West
Hamilton, ON L8S 4L8
Canada

P: 905.525.9140 x23856
C: 905.906.1458
F: 905.524.5288
From: Sharif Nijim <snijim@ND.EDU>
Sender: The EDUCAUSE ITANA Constituent Group Listserv <ITANA@LISTSERV.EDUCAUSE.EDU>
Date: Thu, 23 Feb 2012 15:59:34 -0500
To: <ITANA@LISTSERV.EDUCAUSE.EDU>
ReplyTo: The EDUCAUSE ITANA Constituent Group Listserv <ITANA@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [ITANA] Technical architect roadmap

Michael,

If you were going to start from scratch today, what would choose from a tool perspective and why?  Wisconsin has a nice wiki-based approach, which I like because you don't have to click in when viewing from a website.  That said, there's no easy way to search/display targets at an abstract level, like "show me all the current retirement targets."

What are others doing?

Sharif



Message from mgdaley@umich.edu

Sharif,

We really haven't anything at this point that we would choose. We have looked at a couple different approaches, but they have either been too complicated for what we need at this level (Ex. Essential Project, Archimate) or not flexible enough. The SharePoint site is ok and provides good access for our customers, but just lacks in functionality. We are also suffering from a lack of resources to work on the problem (which is probably common).