Tuesday, June 23, 2009

How to include SharePoint Document Version in your File ?

Since I started using SharePoint (MOSS & WSS), I wondered how I could include the version number provider by a SharePoint document library into the document itself, to ensure some cohesion help people to easily identify the latest version, particularly in the case of printed documents.

I discovered the following easy tip, which works for SharePoint 2007 and Office 2007.

  • In your documents list, go to Settings then Information management policy settings.

  • Under Specify a policy, select Define a policy and click OK.

  • In the labels section, enable labels and in the format field, enter something like: Version: {Version}.

  • Click ok.

Now go back to any of the documents of that library. Open it and edit it then go to insert, quick parts, document property and select Labels. Save your document, close it, then reopen it (in read only) and voilĂ , the SharePoint version will be included. For example, it will look like: Version: 1.4.

Note that it only works for Office 2007 documents (docx format for example) and MOSS.

Saturday, June 20, 2009

Ten ways to sink an IT project

During the recent Project Management Institute (PMI) congress from last May, Andre Chrome made an interesting show about ten ways to sink your project. And of course it applies perfectly to any IT project and I modified them sightly for this purpose.

  1. Be vague: Do not define any detailed scope that would force you to implement what you promised.

  2. Begin the execution ASAP. Why make a planning when you already know lots of changes will happen.

  3. Focus solely on your team. Clients will only interfere with your work.

  4. Forgot about code documentation and instead prefer mutual trust with your client.

  5. Go beyond your client expectations. As clients expect always more and fancy features, you will sign new contracts that will compensate for your losses and bugs.

  6. Risk management ? By definition, risk is uncertain. Why bother planning for risk.

  7. Quality is only important at the end of the project. The client will only look at the GUI anyway.

  8. Avoid bureaucracy. Paperwork is a waste of (your) time.

  9. Make sure your team works overtime. As IT project are overdue anyway, put pressure on your team from the start.

  10. Throw away paper documents when the project is over. Paper files takes place in your office and none ever read them.

Here is the video of this presentation:

Thursday, June 4, 2009

Server Fault: StackOverflow for Servers Issues

Jeff Atwood and Joel Spolsky have released the public beta of Server Fault. Based on their StackOverflow platform, it contains all existing features that made you love (or hate) StackOverflow.

While StackOverflow is oriented toward programmers, Server Fault aims to bring solutions to System, servers, and network administrators. Let's hope it will work as well. I cannot wait to see my first question answered.