Weekly IM Update.

 
 
 logo.jpg

861 Articles and Counting!

MIKE2.0 is being continually updated by the community. Why not dive in and add your insight to one of the information management problems or solutions that is being worked on by the community?

Below are some of our latest wiki articles:

We hope you find our new article additions of benefit and welcome any suggestions you may have to improve them.

Sincerely,

MIKE2.0 Community

 
Popular Content

Did you know that the following wiki articles are most popular on Google? Check them out, and feel free to edit or expand them!

What is MIKE2.0?
Deliverable Templates
The 5 Phases of MIKE2.0
Overall Task List
Business Assessment Blueprint
SAFE Architecture
Information Governance Solution

Contribute to MIKE:

Start a new article, help with articles under construction or look for other ways to contribute.

Update your personal profile to advertise yourself to the community and interact with other members.

Useful Links:
Home Page
Login
Content Model
FAQs
MIKE2.0 Governance

Join Us on
42.gif

Follow Us on
43 copy.jpg

 Join Us on images.jpg

 

 

This Week’s Blogs for Thought:

The Applification of the Enterprise: Part I

In early February of 2012, Halliburton, one of the world’s largest oilfield service companies, became the latest enterprise to abandon RIM’s BlackBerry. Halliburton’s new smartphone of choice: Apple’s iPhone.

Even two years ago, this would have been earth-shattering news. Companies of this size just didn’t buy Apple products. These days, however, announcements like these have almost become commonplace. That is, Halliburton is hardly alone in adopting the Apple’s iPhone throughout the company. In late 2011, Pfizer announced that it will purchase a rumored 37,000 iPads for its scientists and sales and manufacturing employees. In the same year, biotech giant Genentech announced that it had rolled out 30 company-specific apps in its own private app store.   

Read more.

How to Share Bad Project News

In the spirit of the holiday season, I just wanted to bring some levity to the blog. I’ll leave it to you as the reader to discern if there is any applicable value to you in how you communicate.

Email to the Divisional Vice President

Subject: Weekly Status Report on Project Thames

Alan,

This was not a good week for the project.

23 of our nodes failed and we learned that there are limitations to how much the 3-node failover processes work. We’re still trying to figure out what we’re missing. Once we do, we’ll be in a better position to know when we can recover our data. Hopefully it doesn’t happen again. We also learned that the patch we were expecting from the vendor has been backburnered to 2013.

Read more.
 

    The Last Resort: Custom Fields

For many years, I worked implementing different enterprise systems for organizations of all sizes. At some point during the project (hopefully earlier than later), someone would discover that the core application had no place to store a potentially key field. Against that backdrop, the team and I had a few choices .

Read more.

Forward to a Friend!

Know someone who might be interested in joining the Mike2.0 Community? Forward this to a friend 

Questions?

If you have any questions, please email us at mike2@openmethodology.org.

Category: Information Development
No Comments »