The release of the Intranet

As I mentioned in one of the last posts, we released the first build of our Intranet site, built on Windows Sharepoint Services.

The release went very well. Mainly because of the preparation and planning on forehand. I am now (2 months down the line) seeing some things that could have gone a bit faster or differently.

We built and configured the server first, set up the outgoing mail settings, and the main structure of the site. After that we started setting up all the standard content for the sub sites, such as the calendars, some templates and so on.

When the main structure was set-up, we moved to the front page. We made a static block in which we added a lot of links to pages we believed would be either difficult to find or needed more attention. Also we created templates for the announcements from different departments.

When we where ready, we organised small sessions in which the team leaders could go, or send people from their teams to. Since we are mainly a call-center, it si hard to get people off the phone, so these sessions took about 30 minutes and spanned the whole day during 4 day’s. This, we believed, would give everybody interested the chance to have a look.

To remove administrative overhead, and also make sure the intranet will be used by the staff (of all levels) we decided to ask for volunteers in each team to administrate their account sites. This generated some quite positive feedback, and within a week, I had the team of administrators complete.

This created a small gap. I did not expect to have the team of admins ready that soon. Therefore, had no training material ready yet. The problem here is, that as soon as the site went online, the last think I want to think about now is writing How-To documents!  Therefore, be advised, make sure all documentation is ready before!

For the launch we started 3 competitions:

• The Naming competition, to get a name for our intranet, untill now we where still using the server name to access.
• The Logo or Template Design competition and a
• Bug Hunt. I hid images of little bugs in the site, and people had to find one, and accompany it’s location with a real Bug in the site.

The Bug hunt, really helped me a lot in the first day’s to get a list of all the little things I still had to work on/fix. To be honest I can really recommend something alike.

These competitions really helped to get most of the people online. That together with the Site-Admins, coming from all levels in the organisation and from all teams.

Aside from the standard set-up, I have also been creating some List templates, for things we know will be used in several Sites, and can be easily set-up this way. Examples are FAQ, Policies & Procedure Libraries, etc.

Resuming the first two months, I am very impressed by the capabilities of WSS, out of the box. Also about the manageability and ease with you can set up basic lists forms and such. Well, the fact of me, Solo, running an intranet for 350 employees divided in 25 teams while developing applications speaks for itself.

I am sure that my enthusiasm for this platform will diminish, as soon as I will try to customise a bit further than the help-file likes… after all, this is a Microsoft product

At the moment, I am looking into two different things. I am trying to find out how (if..?)  the custom workflows work, and trying to publish a .Net application I built in the sharepoint site as a webpart.

To be continued…!

Planning the Intranet IV

This morning I finished building the WSS Webserver we will use to build our intranet on. To be fair, it was very straight forward and did not gave me any issues aside form the speed, as I was working on a VM copy of the real server.

I made a virtual copy of the live server, to do a test run of the set-up. I used the VMware converter which is simple to use, and gives me an exact copy of the live server. I used this to complete the setup and configuration. This way, if any problems appear, I am aware of them and can prevent them from occurring on the live machine.

I did however encounter one small issue, which is completely my “fault”. I did not check in advance how to set up the email configuration for outgoing and incoming mail. The server is a standalone installation, not part of a farm, and I believe the WSS server, although standalone, should be able to benefit from the UK exchange environment for the mailing purposes.

Another thing I now have to have a look at is the way we will “upload” the custom applications we will be building. My best guess is that we will set up a site in IIS for each which we will link to from within the WSS site. However, I would have to have a look on how this can be done. Shared folder, Frontpage extensions, don’t know yet. We will be developing in wither visual studio, or on the VS Web developer express edition, and I’m not 100% sure what is the best way to publish the applications we build in there.

Planning the Intranet III

For about 5 years I have been working with IBM software. Mostly using Lotus Domino and Notes, designing applications. However I also looked at other technologies, like Websphere and DB2.

I have recently switched (well, I’m still switching) to comparable products from Microsoft. Mainly becasue the company I work for made the decision to stop using IBM for their internal mail and databases.

I do however believe that IBM, known as Big Blue, a big and slow organisation, was ahead of Microsoft concerning intranet software and ease of development back in the day’s they launched Websphere. I have been looking at an article on their website, that states that in 2006, their Intranet was listed in the Nielsen Norman Group Report: Intranet Design Annual 2006: Year’s Ten Best Intranets.

I never heard of that report before, and headed straight over for a look: http://www.nngroup.com/reports/intranet/design/. The report is for sale. 224$ and its yours. For me that is too expensive, and Im sure that my boss (who is likely to leave soon), would have a good laugh if I walk over to ask him for the money!

(reports from previous years still cost about 200$, which I still find very steep!)

However, it gave me a good impression what points to look at for our Intranet:

Some of the key areas for which best practices are presented in the report are:

• Company and industry news
• Integrating internal and external information sources
• Editorial control of the intranet homepage
• Keeping the intranet up-to-date
• CEO blogging
• Employee and department weblogs
• Onboarding of new employees
• Consistent navigation
• Multilingual intranets; supporting international employees
• Multimedia and video on intranets
• Data visualization
• Web 2.0 features on intranets
• Community
• Polls
• Collaboration tools and discussion boards
• Internal wikis
• Employee self service
• Search
• Governance
• Development process for intranet redesigns
• Web analytics for intranets
• Staffing of intranet teams; where they report in the organization
• Updating and maintaining standards and guidelines for intranet design
• Intranet branding
• Promoting new intranet features
• Staff directory and employee profile pages
• Corporate calendars
• Personalization
• Customization
• Alerts
• Working with external design agencies

These points are things (call them features) they look at when evaluating intranet sites. I believe this to be a very complete list, and I’m sure that in a company our size (just looking at our office in Spain, we are about 300 people) can and will have to remove some of the points. Either because of difficulty of implementation (read: cost), Irrelevance or plain Overkill.

It looks like we have a Feature Checklist, with which we can start planning!

Intranet budgets and staffing

Planning the Intranet I

As we are currently about to start implementing a sharepoint environment, this also implies that we will have to plan the Intranet.

Currently we do not have any. Well, we have the intranet site of our English company headquarters, but that is hardly used, and does not interact with us. Meaning that we cannot add our content, links to our tools, etc. The Sharepoint implementation will give us the possibility of having our own intranet site. This is, I believe, very important. Mainly because being an IT company with a lot of different teams, spread over different floors using only email as a way of “digital communication” is … say… a bit outdated (Heavy understatement). This is especially true if you know that most problems we experience internally are due to communication problems (either lack of, incorrect or simply non-existing).

The intranet could change that. Could, I say, because I believe that if not planned and managed correctly and across the board, an intranet can cause more problems than it was designed to resolve.

Management manages this company in a very typical style, you could really apply the machine metaphor to this one! Top-Down and in very linear streams. It is really hard here to make different dept. managers talk with each other and even more if they have to work together.

Lately there is a lot if buzz about 2.0 technologies, and how they can benefit communication outside work, but also in the office. Examples are company wiki’s, facebook-style people profiles etc.

I am now looking into planning the whole new environment. Not because I’m asked to, but because “I can see the cloud hanging above me, and don’t feel to wait till its raining”… Call it being pro-active (but I will dedicate another post to that;) ).

Personally I would like to make sure the intranet will give us these communication advantages and I believe that is also has to be future proof. My biggest fear is that the intranet ends up to be absorbed by “the Machine”, managed by a few upstairs who only care about their specific parts/departments or tools.

I see that the modern organisation is flat, as flat as possible without interfering with operations. If you look at these new communication technologies, you see that these are enablers for this. Maybe they even push organisations is this direction. The problem is: “how to apply modern tools in a company whose management thinks in an old-fashioned way”

Knowledge Management (KM)

As mentioned in the previous post, we are now looking into setting up a whole new knowledge management strategy for our office.

Currently this is dealt with per team. We have approx 250 people working in 15 account teams, giving IT support. Each of these accounts have their knowledge base and their knowledge management processes (if any). As you understand this is not an ideal situation. It is impossible to benefit from each others’ information, and there are a lot, really a lot of double, even triplicate documents. (after all most of us troubleshoot a printer in a similar way).

For a company that is trying to standardise all over the place, this is one of our worst areas.

According to many KM specialists, the first step in this whole plan should be to make sure we have senior management support. This to be honest is more difficult as it seemed. I was convinced that knowing the above, and actively trying to standardise, they would listen to a plan like this, but soon found out the “the idea is good, but it will be too expensive, or take you too long”. Yes, there will be a cost, and a considerable effort, but the return will be a very valuable asset; Knowledge! The work we do at service desks is for a huge part based on the knowledge we have at hand. An analyst can be great in troubleshooting and phone skills, but without documentation…. After all, none of us knows everything.

We are now at the stage that the senior management team is interested in our plans, but we are still not getting a clear go-ahead. This causes us to have to work on the plan outside office hours…

We already have the main outline of the plan. We have the platform (wss) and bit by bit we start to get support. I’m sure that one of these day’s well get the “official” project request. Then we can start gathering people to set up a small project team, and present our plans to the different teams, to get their feedback.

Also, we made a SWOT analysis of the current tools we use, which will help a lot identifying the requirements once we reach the lower level of our plan, which is how the database design would look.

At the moment we are putting everything we’ve got in a high level project plan. Mainly to keep ourselves on track and focused on the parts that are important at the moment and not get in to too much detail (which is a common mistake techies make!). As soon as we have it ready, Ill post an update!

The Sharepoint Adventure – Part III

A while ago, I wrote about the plans we had in my office for the move from Lotus Domino to MS Share point as a database driven application platform.

This was quite a while back, but it looks like we will get some kind of approval soon.

This is great, especially after it took me about a year to have senior management listen to me. Up until now, that has been my greatest headache. Mainly because I believe that applications we build here are a vital part of the organisation. If you can have them developed in-house,  you save a lot of money and you are sure they are fit for pourpose!

Management, however could not see through the first layer, and somehow wanted applications to “just be there”. When I learnt how they thought about this, it was a lot easier to convince them. I spent the last months walking around, trying to sell applications that did not exist yet. Finally they saw want I meant.

I can see now that there is a huge gap to bridge, because all this time I have been running around selling my big plans… I did not have a lot of time to continue training myself in this platform.

o-oh!

My manager, who lately is finding out what I’m busy with, signed me up with the company training system to start the MS course Microsoft Certified Technology Specialist (MCTS): .NET Framework 2.0 Web Application. This, as it looks from the Lesson 1 viewpoint, will take me quite some time.

To give some more details on the environment we will be working with, here it is. Be aware, this is not the company’s main Share point server landscape, nor it is part of it. This is purely for our 300 person office.

We decided to go virtual, as the demands on the system where pretty low and the cost was a lot lower since we only pay for the licenses and had no hardware cost.

Finally well go for one Virtual 2003 Server, running IIS, ASP.Net and WSS (I did try to get the full MOSS, but the licence cost was a bit too high ) and a virtual SQL server.

To be honest I believe that this is fit for purpose, as the amount of usage (users / contents) will not be too high and if we exceed expectations the virtual servers can be upgraded quite easily.

The next step will be planning the contents. I already presented some in the plans I’ve put forward, but these now need to be worked on. A lot!

The most important plan is to re-design the Knowledge-management strategy within our office, and possibly within the whole company.  As I am also lecturing Knowledge Management internally, I really feel like being involved in this. I have been building the different knowledge bases we are using here, but this is a chance to setup the complete shop!

We already had a couple of meetings to look at how we are going to approach this. Still pretty high-level, as this is something we will  have to convince management…. Again! However, in the IT Support business, I believe the case is quickly made. Especially looking at our current KM organisation, in which every account team runs its own K Base and the teams do not comunicate with each other. I think this is where WSS can make the biggest difference!

Probably in one of my next posts, Ill explain a bit more about that!

Developping Distance

As promised in a previous post, Here is a shortlist of the first things I discovered when moving from Lotus Domino to ASP/SQL as an application Development platform.

Of course this is far from complete, but gives you an idea what its about. I will populate it over time. As I have just created one small app, I cannot list all the possible differences….. for the moment, the most obvious:

biggest differences between developing a simple database driven application on the Domino platform compared to the MS ASP.NET/SQL Environment
		DOMINO		ASP/SQL
Data Layer	No Intervention req. Using the Domino designer, only the fields need to be planned.		+	SQL Database needs to be planned and set up.	-
				Data connections need to be planned and set up.
Application Layer	Formula language, very easy to learn. (ex. @mailsend(“Alex K”;”cc name”;”bcc name”;;”Subject”;”Mail Body text bla bla)		+	ASP / SQL Both not an easy language to learn. However not impossible either, depending on your capabilities.	-
	Lotus script, very similar to plain VBScript.		-/+	to create a simple application, no coding is required.	+
Presentation Layer	Domino Designer is not really made for developing for web clients. However, using css pages, and “render as HTML” make it possible to layout your site well. However This is not very straight-forward, and will take a bit to get a hang of.		-	The Microsoft VWD is clearly a web development tool. Layout and design are really easy.	+
Other	Access control easily managed, up to field level		+	Access control depends on set-up, Active Directory access makes things easier, while using roles in the asp.net user management console can be quite complex when managing multiple applications	-
Application: 1 database table 1 form for entering data 1 reporting view Access Control

The Idea, The Challenge…

Good, even though I am just starting to have a look at the development of web based applications I received a comment on one of my previous posts that maybe comparing Domino development against ASP/.NET could have interesting results.

I believe this to be a good Idea, but my only worry is that my lack of knowledge, as a .NET starter will bias the outcome of this “test” a bit. However, if I choose to make something really simple, this should not be that much of a problem.

I am looking into developing the same project twice. Once in Domino, and once in VWD (Visual Web Developer), the tool I am using at the moment to learn more about the development in ASP and SQL.

This is a bit of extra work, but I believe I can make the time to do this, and that it would  be very valuable, especially to see where major differences create delays, or make things slower (or faster, probably in rare occasions). Therefore I will try the following:

An application (I am thinking about one I have to make soon anyways, which will be an IT Asset Management Tool), Web based,containing:

* Standard Navigation
* 1 Form
* 1 View for reporting

There are a few things I cannot really test yet. For example, the (ASP/SQL)environment I use now @ work is purely local, and I cannot query Active Directory for user management. Therefore, Ill skip the whole access and security part (which usually takes quite a bit of planning and work), also, I cannot use Mail functionality, as our development environment does not have Domino, nor an Exchange server.

The aspects I will look at are:
- Time spent on each part
- Effort/Knowledge required to finish each part
- General Overview of differences/problems encountered

As mentioned before, I will have to find time for this, and I will probably post it all bit by bit, and join all bits together at the end. Stay posted!

Learning…..

lately I do not post that often. Well, to be honest Ive never been a very frequent poster. My problem is, if you can call it a problem, is that I prefer to do that to write about what I could be doing. Luckily enough, there are some gaps at work, in which I can dedicate some time to update this blog.

Last time I was excited about the speed in which it is possible to, from no knowledge whatsoever, build a decent database based web application. Now, a couple of weeks later, I started the Visual Web Developer again to see if I still manage.

The result is surprisingly Yes, I manage!! Still on a very basic level, but I had no time in the last two weeks to study, read or watch any of the training materials out there. I had to work on a couple of domino projects. To be fair, its very hard to work on both platforms simultaneously. I get too confused by the different terminologies etc.

Today, I will start to have a look at what I am capable of building without using the help or alike. This is a technique I often use to learn something and allows me to know exactly in what areas I still lack some knowledge. Also I would really like to know if there are any other Domino app designers that had to make this switch to MS. I guess there must be loads, mainly because in Europe I believe the businesses are more and more moving towards a non-domino environment. Soon I will explain my findings. However if there is anyone out there that can help me draw up my “road map to MS”, I welcome your comments/hints/help!

The Sharepoint Adventure – Part III

For a couple of weeks I did not have any spare time to look into the share-point Implementation project. Last week, however, I managed to get some days free to look into the plans.
I am working with another technical lead on this, and he is taking some pressure of our back, so we can really study this well.

Last Thursday, I decided to take a look at the technology behind it… ASP of course!

I used to (more that years ago) build websites as a freelancer. As a freelancer, my budget was limited (budget : = @Number(“0″) + @Text(“€”)!) and I learned to develop using PHP, ans MySQL. This worked more than fine for me. Also Learning PHP to a level you can use it to connect to databases, insert data, retrieve etc. is not too hard.
And the best of all… It´s all Free!!

Now however, in the office I am working, the price of legal software is not important anymore, and on top of that, we receive the Microsoft Action-pack, with new releases and training licences. This opened up all kind of experimentation with MS technologies.

Last Thursday I installed a copy of Microsoft Visual Web Developer 2008 Express, with SQL Server 2008. Biggest surprise of all… Its a Free download! Combining that with the standard IIS Server which comes free with most windows systems, you have a pretty nice Web development platform.

Since the interface confused me a bit, coming from Domino Designer, I started watching the MS Training videos , and over the weekend I followed a couple of tutorials.

I found myself building a complete application by Saturday! To be very honest, I have always been advocating Open Source and Free software. However It looks like Microsoft is taking care of their low budget developers and it works! There are quite some similarities with Domino Developer (v7), even though VWD looks much more web-facing and using the toolbox is a real joy! also the whole data-layer architecture, makes connections with databases something I understand!!

Well… Ill stop now, before I sound like an Uncle Bill add.