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.
Entries in Best Practices (27)
Map Product Features to User Profiles
In attempting to make sense of the confusing Search Vendor landscape, I found some analyses that offered a guide to what product feature sets might be important.
In studying the literature, I found some good analysis of Search Usage Patterns – one analyst broke the user spectrum up as follows:
Larry Cone
in Best Practices, Case Studies
|
Post a Comment
Project Issues – Enterprise Search
We have resumed following my current Enterprise Search Implementation project for a Medical Publisher. I’m going to bring you back up to speed with a review of the project issues and status in Mid March.
Larry Cone
in Best Practices, Case Studies
|
Post a Comment
Punchlist for a “483” – Lessons Learned
Time to wrap up this project case study. Needless to say, the system successfully past the extensive QA process of Factory Acceptance Test, Installation Qualification Test, and Operational Qualification Test. Our voluminous documentation passed muster, too. The system was installed in good time, and for a fixed price. We used up our project contingency, but didn’t need much more than that.
Larry Cone
in Best Practices, Case Studies
|
Post a Comment
Punchlist for a “483” – Standing on the Rock
We are pushing toward the finish of this Incident Reporting System project. I’m working the Punchlist with my Client PM counterpart, and we are knocking items off faster than they are coming on.
Larry Cone
in Best Practices, Best of coneblog, Case Studies
|
Post a Comment
Punchlist for a “483” – No U Turns
I’m working the problems in this Incident Reporting System project. I’m using a Punchlist to try and define and manage the remaining scope on the one area that refused to Jell – the Reporting Requirements.
I’m having twice-weekly sessions with the Client to review the Punchlist, check off completed items, and add new ones. And I’m gaining ground, until some changes to a management report must be reversed back to the way they were originally.
Larry Cone
in Best Practices, Case Studies
|
Post a Comment