About IT management, cloud, Arduino, and other stuff

This article from the PMI Knowledge Shelf explains the rationale behind the creation of an in-house, customized project management methodology, iMAP, at a rapidly growing pharmaceutical company. The authors also describe the priorities that were selected to start with its implementation: a solid project initiation, a clear project life cycle, a special attention to risk management, a first step in reporting standardization, and specific attention to the activities necessary for the transition to operations. They provide an overview of their approach to IT project governance and how a defined project management methodology is the key for its success. https://docs.google.com/file/d/0B40T8ZW4GEUJNmYxMTJhY2YtODY3Mi00NWEwLWExZDMtMmNlMGNiZTUyZWEw/edit

When discussing around me about Google Docs in the corporate world, I'm very often surprised to see the difference between the people who use it -and generally love it-, and the people who have never used it -and have tons of reasons for not doing so-. Here are the 10 justifications I'm earing the most: 1. Google Spreadsheets do not support complex data analysis: wrong, the function list contains hundreds of functions for Math, Date, Financial, Statistical, and Engineering Analysis. The database functions even allow Google Spreadsheets to query and process data from other databases. It can be fully customized using Google Apps Scripts, based on Javascript. You can create charts in a spreadsheet and publish them on an intranet webpage, so they get updated every time you update the data, in real time. 2. You can’t send a Google Document easily as an attachment in another format: wrong, you can export a document by selecting “Email as attachment...” and select the document...