All in Project Management

I was interviewed yesterday by a Forrester Research staff member about how CIO’s (Chief information Officers) should approach the implementation of collaboration tools (click here for a list of blog posts related to “collaboration”). We talked about the usual adoption issues related to “web 2.0” applications within the enterprise.

Project Management, Social Media, and Defining "Community"

As a continuation of our Conversation about Project Management and Social Media, Lee White in his recent post Project Community states the following: The point here is not that Social Media, as discussed in earlier posts, directly drives efficiencies, but that it can create a community of project stakeholders that are passionate about the successful completion of a project.
CIO.com's Seven Reasons for Your Company to Start an Internal Blog lists the following: 1. Your enterprise e-mail applications are not easy to search. 2. Your e-mail is lost in the eye of the “cc storm.” 3. Ex-employees can take it with them. 4. Too much wasted time checking in with colleagues. 5. With blogs, the humble and the egotist both win. 6. Organizational openness and accountability. 7. People might already be using them.
Earlier this month in my post What is the Minimum Information You Need to Describe Your IT Projects? I mentioned that a “RACI” statement is a useful way to communicate project responsibilities: * Who has ultimate Responsibility, who has Authority to make decisions, who must be Consulted about major actions or decisions, and who must be Informed about major actions or decisions.
One blog I read is the Microsoft Knowledge Network Team Blog (registration required). It describes development and features of the "Knowledge Network" product that will accompany Microsoft's upcoming Microsoft Office SharePoint Server 2007 which is also in Beta status.
When considering the potential system integration costs of an enterprise web 2.0 project, one of the first things to do is to identify potential system-related “ripple effects” (if any) of introducing an enterprise web 2.0 system into the organization. We also need to consider the cost implications of addressing and managing these ripple effects over time.