It isn't all about the code?
This is the coneblog journal and related categorized archives. You can read the blog as written back to front, or browse the categorized archives at right - check out the about categories for guidance on that is where. For a quick overview of the types of content you might run into, check out the Best of coneblog - some of my personal favorites.
Structure-Function
We left the Analyst in front of the white board, drawing circles and arrows. She was engaged in the primal act – Creation. Out of the formless Requirements Void was emerging the Light of a Solution, an Architecture.


Magic Happens
We have been interviewing customers, users and management for about eight weeks now on the way to defining our Content Management System requirements. We have inventoried the content areas involved, and created Use Cases and Benefits Analyses from the interview contents. We have come to one of the most interesting parts of the project – where “Magic Happens”.


Content: Inventories of Content
This project, like many others, will be successful when a bunch of “stuff” that is now in an old place, will be accessible in a new place, and in a new way. In this case the “stuff” is medical content documents. The new way is accessible through improved cross-silo search capabilities. So, knowing facts about the “stuff” – how many, what format, where – is important to the success of the project.
Content: It’s All About the Interface
As you may recall, I’m the PM for a project to install a content management system for a medical publisher. We have worked hard at understanding and documenting the benefits of the system, but that’s not what people really want to talk about.


Content: Project Benefits: A Trail through the Swamp
Benefits are the reason for any IT project. Too often, a benefits analysis is an important part of getting the money, but is soon forgotten in the day-to-day alligator wrestling that makes up most IT projects.

