Tips for implementing Web content management

Bryan's picture
Submitted by Bryan on

Tony Pietrocola, Bridgeline Software, posted on their blog seven ways to "Avoid These Common Mistakes When Implementing WCM". Two of the tips he gives have been giving me trouble lately.

2. Have the requirements from all stakeholder groups been accounted for? One of the critical issues that sink CMS investments in the organization is missing all necessary input and buy-in.

3. Trying to solve too much from the very beginning and be all things to all people is a recipe for disaster. In order to be successful, work in manageable phases. Don’t be afraid to upset the apple cart and prioritize.

What do you do when all the stakeholders buy into the CMS but see everything on their laundry list as a priority for implementation? Sometimes having all the stakeholders involved is why tip #3 can be very difficult to do and maintaining a WCM can bring no joy. There is a lot of negotiation skills involved to make WCM implementation and maintenance happen. Unfortunately, not all IT project leaders are good at the negotiation table.

I will have to ponder on these issues a bit more...

Getting more work done through less innovation

Bryan's picture
Submitted by Bryan on
The biggest reward I get from working on IT projects is the opportunity to take new ideas and new strategies and piece them together into something that has never been done before.  Even when I'm not the one originating the new idea, I like helping other innovative people bring their ideas to the table.  I have ideas, dreams, and aspirations to help take my workplace to the next level of where it should be via innovative use of what I know best, information technology.  How could innovation and all these wonderful ideas I have in my head not be anything but a good thing for my organization?  A recent article in the Wall Street Journal answers just that question by saying that there are negatives for an organization that innovates too much.

In "How Innovation Can Be Too Much of a Good Thing", George Anders writes about how companies and business consultants are rediscovering that less innovation can produce better business results.  Companies that used to push the limit in efficiency are finding that they're "jamming too many new ideas into a product pipeline, without enough slack time to ensure that critical tasks stayed on schedule".

Similar insights have been standard wisdom on the manufacturing floor for decades. Factory managers learn about bottlenecks through the formal discipline of queuing theory. That teaches them to keep a little slack in the system to handle the unpredictable -- but inevitable -- crunch times.

pingVision: Project Management with Drupal

Bryan's picture
Submitted by Bryan on
"Two of the challenges faced in every project are the task of identifying milestones and distribution of work. Many systems and methodologies have been created to help address these issues but there is little information about using these practices in Drupal development. This post is an attempt to identify a methodology and tool set for managing the development of a Drupal based project."

Complete Story

Identifying Open Source Winners and Losers

Bryan's picture
Submitted by Bryan on
Very interesting article from InformationWeek, How to Tell the Open Source Winners from the Losers.
There are 139,834 open source projects under way on SourceForge, the popular open source hosting site. Five years from now, only a handful of those projects will be remembered for making lasting contributions--most will remain in niches, unnoticed by the rest of the world. For every Linux, Apache, or MySQL, dozens of other open source efforts fizzle out.

That's a dilemma for the many companies that are expanding their use of open source. Corporate developers and other IT professionals must get better at divining the winners and ignoring the losers. The wrong picks can lead companies down a rat hole of support problems and obsolete software.
Not sure if I agree with everything in the article.  For example, the 9-point checklist  of what is required for a successful open source project is surely up for debate.  However, the article is a very good starting point for companies and their IT managers to identify the more successful projects.   According to the article, some of the up-and-comers in open source include Alfresco (CMS), Subversion (version control), and Hyperic (system management).

It's funny though, I remember visiting SourceForge quite a bit years ago.  These days though, I seem to find the project directory through "word of mouth" via the blogs.  Amazing how blogging continues to change the IT landscape.