Since a few years I execute the job of SharePoint consultant. SharePoint seems to be one of the most successful product, maybe even the most successful product Microsoft has launched. Then why should a guy like me complain about that Microsoft is wrong in their bring to market? They probably earn billion$ with SharePoint. And they should, because it is a great product! But at the end of this post, in the quote you can see my worry.

During the SharePoint Evolution conference SPEVO held in April of this year, my memory was refreshed of something that was said during one of the analyst sessions in the SharePoint Conference 2009 (SPC09) in Las Vegas.
The SPEVO was actually the SharePoint Best Practices Europe Conference, but because of the launch of a new version called SharePoint 2010 there were not a lot best practices to share on SharePoint 2010. BUT the organizers of this conference really got the message I’ll talk about in this blog post. They organized a IW (Information Worker stream) In fact, they organized even 2 parallel streams. Well done Steve Smith!

During a session from Symon Garfield, he explained why 70% of all projects fail. There are several reason, like unclear requirements, scope changes. If you take £SharePoint,  one of the main reasons is that a SharePoint project can’t be driven only by IT. SharePoint is a business driven product. IT can install, deploy and support it, but it can not solely drive it toward long term success.
You also need to have a good user adoption plan, and some corporate guidelines (let’s call them governance) to make sure that when people really start using SharePoint, it doesn’t get a maze where you can’t do or find anything. If you take a look at the Microsoft Press books, about 99% of the SharePoint books are technically focused. There is a lack of business side books. (Thank you Michael Samspon for representing this 1%)

During that analyst panel session at SPC09 there was a discussion about having a third pillar next to the Developers  and IT PRO’s. The name was not specified, but lets call this group Functional people, or Functionals.  For me, but also for all SharePoint projects in general, I thought that was good, no even great news.

But until now, nothing has changed. From Microsoft’s opinion you are or a developer, or an IT PRO.There is no new group. Or you write code, or you have access to Central Admin.

Take for example the Ignite Sessions. They are organized for IT Professionals and Developers, but not for Functionals. Even with such a huge release of  SharePoint 2010, where a lot extra power is provided to PowerUsers, and it very important to have that link between Business and IT.

Or the Microsoft SharePoint 2010: Developer and IT Professional Learning Plan.

In my first conversation with Karine Bosch (a Belgian SharePoint MVP) right after a BIWUG session  we were talking about what we did in the SharePoint world. When she explained what she does I replied, “Oh, you’re a code sh|tter”, without being disrespectful. That’s good because we need SharePoint code writers (you can also read developers)  to cover non ‘Out Of The Box’ functionality , When I explained what I do, I summarized it with “I’m a document sh|tter”. And We also need them (I guess). Actually that’s also what Karine confirmed.

That’s why (I would say) in my humble opinion that Microsoft is acting wrong. Until now, they don’t provide any special documentation or support for these Functionals.  Besides some sales and marketing information on how SharePoint will make your organization more productive, there is no specific information for the Functionals. They are just twilights.
And they should pay attention to this, because otherwise SharePoint might become one of these “Oooh darn, it’s a SharePoint” applications.

That’s also why I am so happy that guys like Michael Samspon, the author of Seamless Teamwork, a book on using SharePoint from a business perspective, Raymond Dux Sy , the author of SharePoint for Project Management: How to Create a Project Management Information System (PMIS) and Paul Culmsee take a different approach on SharePoint. I will do my best to provide useful information like these guys do in their blogs, webcasts, … That will be my way to contribute to the grey twilight zone that Microsoft can’t fill.

On the other hand, I must admit that I know a few, but just a few guys that are good at coding, have a good knowledge of the the Out Of The Box functionality of SharePoint and are able to talk to the business and translate their requirements to SharePoint functionality. These are the golden egg chickens…

But to conclude, what I’m also trying to explain is that Microsoft, and the Microsoft partners will be judged by their clients (the business) based on the return SharePoint gives to the business, not on it’s nice technical gracefulness.

Just for the record, here are my my questions to Microsoft.

What are your intentions to this issue? (When)Are you planning to setup a functional stream?

A fellow consultant and blogger Michael Sampson @collabguy organized a survey on Site Closure.

Michael is the author of the book  Seamless Teamwork: Using Microsoft SharePoint Technologies to Collaborate, Innovate, and Drive Business in New Ways, which I recently received from Combined Knowledge (many many thanks for that Zoé and Steve). I would recommend this book for everybody who is interested in empowering people and team with SharePoint.

But I don’t post this just to talk about this book. The reason I write this post is because Michael has launched a survey on Site Closure. And The survey will close on friday July 9th. So this is yet another last minute post…

His next book, SharePoint Roadmap Governance Themes, greatly expands on the governance chapter in SharePoint Roadmap for Collaboration. Two themes have been explored to date — Site Creation Rights, and User Adoption Strategies — and there are reports available on both of those. The third theme for investigation is Site Closure Policy. In other words, what do you do with SharePoint sites when their useful life is at an end, however you define that?

As with the previous two reports, there’s a survey. If you have involvement in setting governance decisions for SharePoint at your organization, please take the survey now.

Respondents who complete the survey will receive a free copy of the research report, due for publication in July 2010.

The survey closes on Friday July 9 … so please do it now!! Thanks.

Onze verontschuldigingen, dit bericht is alleen beschikbaar in English.

As you probably know there are different kinds of Lists and Libraries available in SharePoint (WSS 3.0 or MOSS 2007). This overview shows the available lists and libraries for MOSS 2007 Enterprise.

You can easily reuse a List or Library, with or without its content. For instance, you have created a survey and you would like to re-use that survey (maybe several times a year, but this doesn’t really matter, you just want to reuse it) without having to input all questions and eventually branching again. The same thing may apply when you Webcast want to reuse a Document Library or a List with several columns.

It’s quite easy to reuse a list. In the following procedure you will see some screenshot how you can do that. I have also created a Webcast.

LINK HERE

This is my initial setup:

I have a survey called: Users satisfaction.

In this survey there are several questions, and some questions are branched. (This means that depending on your answer, you well go to a specific question instead of the next question)

• The first thing you need to do is save the List/Library as a template

• To create a new List/Library based on this template: Click on View all Site Content and then create and select your Template.

Recently I had to configure a SharePoint workflow where an item had to be copied to another list when the Approval Workflow status is approved. It was ok to start the workflow manually. The workflow had to be created in SharePoint Designer 2007, since no other specialized workflow software is/was available.

The problem I had was that when I assigned a condition that would check if the Approval Status equals Approved. But this doesn’t work when you use this condition, it will be skipped, because internally SharePoint uses a number for the workflow status.

Also, if you Edit in Datasheet (your list or Library) you can see the numbers is stead of the text.

Here is an overview:

So, I need to modify my workflow like : If Approval Status Equals 16, ….

The same policy applies when you would like to have a view where you display items based on their Approval Workflow Status.

This list is partially copied from David Wise blog

Yes, my ticket for Sunday to travel with the Eurostar from Brussels to London is booked. I called the Belgian call center this morning at 09:00 and they confirmed that there were no more places available to leave on Sunday. The operator I talked to yesterday confirmed me that at 10:00 Eurostar will announce extra trains, and they can book them as soon as they are announced. What I don’t understand is that the operator this morning didn’t provided/knew this information, even when I specifically asked for it.

Anyway, I called back at 10:00 and this operator was aware of the extra scheduled procedure and I managed to buy a ticket to leave tomorrow at 12:59. SharePoint Evolutions (and definitely a big SharePint with lots of travel stories) here I come. I hope other people will get there safely and on time.

Oh yes, my flight from Antwerp -> London city with Cityjet was cancelled yesterday, and I called there call center just a few minutes ago. They cancelled my flight back and will refund it to my credit card.

It was a stressful experience to arrange transport to London, but eventually I turned out pretty good for me.

Happy and save travels to all other #SPEVO attendees

I was so happy that I could go to the #SPEVO SharePoint Evolutions Conference next week. I reserved an airplane ticket from Antwerp to London, but due to volcanic ash my flight was cancelled. Like many other people in the SharePoint community I have an issue to get to London.

So today I’ll try to book one of the (hopefully) extra scheduled Eurostar trains from Brussels to London. The call center opens at 09:00, so I still have to wait about 20 minutes.

Some people start to do roadtrips like @zimmergren, @mariannerd or @billbither .

I wish al travelers to #SPEVO good luck and safe travels and hopefully we can SharePint together in London

Yesterday Jeff Teper announced on the SharePoint Team blog some great news

–quote–

Today we reached an exciting engineering milestone- the release-to-manufacturing (RTM) for Office 2010, SharePoint 2010, Visio 2010 and Project 2010!

RTM is the final engineering milestone and a major achievement for all of the internal teams who worked so hard to get to this point. As tirelessly as our engineering teams worked, we would never have reached this milestone without incredibly active participation from our customers and partners. More than 5,000 organizations and partners have worked with us on rapid deployment and testing of the products, and the feedback that we’ve received from all these programs has shaped a fantastic set of products that I’m sure our customers will love.

Our Volume License customers with active Software Assurance (SA) on these products will be one of the first to receive the 2010 set of products. They will be able to download the product in English, French, Spanish, German, Russian, and Dutch via the Volume Licensing Service Center starting April 27. Other languages will be available on a rolling timeline. Customers without SA will be able to purchase the new products through Volume Licensing from Microsoft partners starting May 1.

–End Quote–

Full article can be read via this link

Microsoft® heeft een whitepaper uitgebracht over Business productiviteit voor  SharePoint® met Office.

Dit document toont aan hoe 2 producten , Microsoft ® Office and Microsoft SharePoint ®, samenwerken aan het krachtige design dat Microsoft Business Productivity Infrastructure (BPI) noemt.

De BPI benadering suggereert dat enkel door te denken op een gebruikerswens (bvb. “Wat willen de gebruikers doen?”) en door het toevoegen van de juiste aspecten van het vermogen van Client, Servers en Services, de desktopapplicaties kunnen ontwikeld worden die ook een rijke omgeving ter beschikking kan stellen voor de Information Workers.

Dit document beschrijft hoe de 2010, 2007, and 2003 versies van Office samenwerken met de 2010, 2007, and 2003 versies van SharePoint. Hoewel we een overzicht wordt aangeboden van de manier waarop Office en SharePoint samenwerken in oudere versies, richt dit document richt zich op de integratie van functies van Microsoft Office 2010 met Microsoft SharePoint 2010.

De scenarios in dit document tonen voorbeelden over hoe SharePoint 2010 en Office 2010 waarde kunnen toevoegen op volgende gebieden:

• Samenwerken zonder compromis,
• Ideëen tot leven brengen,
• Toegang tot alles van overal,
• Het practische IT platform

Download dit document op http://go.microsoft.com/?linkid=9690494

Het is een mooie dag vandaag. 2 dagen eerder dan verwacht is de SharePoint 2010 BETA gereleased. Je kan ze downloaden op de MSDN website (op voorwaarde dat je een MSDN abonnement hebt)

Dus, als je een MSDN abo hebt, kan je SharePoint 2010 downloaden via deze link https://msdn.microsoft.com/en-gb/subscriptions/securedownloads/default.aspx

SharePoint Designer 2010 BETA , SharePoint Foundations 2010 BETA (WSS 4.0) en Office 2010 BETA zijn ook gereleased. Happy downloading and experimenting!

Ohja.. Er zijn toch wel wat probleempjes. Voorlopig geen Win2k8 R2 installatie mogelijk
lees vooral http://bit.ly/2rNgl8 voor je je in dit avontuur stort