Thursday, 30 May 2013

Project Server 2013 Installation - Issues with AppFabric Pre-Req.

Aaaaargg!!! Microsoft AppFabric !!! Took me a whole morning to get the Pre-Req's Installed on an Offline 2012 Server. (Offline meaning not connected to internet to download the Pre-Req's as part of the Install of SharePoint 2013)

So with Project Server 2010 all we needed to do was to download all the Pre-Req's and install them one by one. This always worked. Now with SP 2013 this does not seem to be the case with all the items, especially AppFabric, as there are configuration that should be done as part of the Install of the Appfabric Pre-Req. Managed to eventually find a Script by Craig Lussier (http://craiglussier.com) to help me to get the Pre-Req's for SharePoint 2013 installed. Find these scripts here.

Please note: I do not own these scripts. Please have a look at the Authors blog, quite a bit of valuable resources on there.

Monday, 13 May 2013

So many times i have been asked the question : Why do some Project Server implementations fails at a client ? or why did it only last a few months before it became a white elephant ?

We have had support calls from clients where they wish to "resurrect" the implementation, that was done a year or two again. Just to come on-site to find out someone has formatted the server and re-allocated it to another application ! Which I'm sure it's normal IT practice but, no one new about it for about a year that the server is off. Only when a new person started in the PMO he wanted to use a tool, but the tool was not there.

I have a done a bit of research on why Project Server Implementations fails and have spoken to may people that i work with on what caused things to go south. I will try to highlight them below in a manner that makes sense to all.

Scoping of the Project not done properly, when requirement workshops starts everybody is amazed at how much work is actually involved

Buy in from Senior Stakeholders is a key success factor for a successful deployment. How do you drive the adoption of a new tool from the bottom up?? That will simply not work. I have dealt with clients where executives had come to a point, after numerous change management processes, training, begging and pleading, came to a point where the users KPA's and KPI's are influenced by participation of the system. Unfortunate, but a reality. But today 8 years on Project Server works like a dream in the same said organization, having upgraded from 2003 to 2007 and then to 2010.

Buy in from "the rest of the community" In some cases too little focus is on the general community and too much focus on executives and Senior Personnel. By not letting them know the benefits and how it can make their work better, you actually just aggravates them. I have had Project Managers tell me that this new system will not be used and that they will use "Offline" scheduling to plan and track their projects, as they feel the "Visibility" makes them vulnerable.

Change Management - So many organisations thinks by telling resources to use a new system is classified as change management. User training is NOT the only aspect of change management. In some cases management seem to think that change is driven from the bottom up and not from the Top downwards. This tool as with any other Enterprise tool requires an amount of change management.

Thinking the Tool will define a process. The tool is supposed to support a properly defined process, not the other way around. If there is no governance or processes in place, many clients think this tool will now "Make it all better"

Overestimating Maturity. Many organisations when asked the question "On a scale of 1-5, how mature are you. The general response is: "We are at least a 4!" In 95% of these cases a 2 on that same scale is an overkill. Once you are a in workshop and you start asking about base-lining procedures and the response is "We don't set baselines on schedules" but they are still trying to manage things like "Planned vs. Actual" and in some or other way try to actually report against that!!

Over complication of the Configured Solution. Many clients wants to have a solution that is so complex and can do so many things that the basics are forgotten about. Having a large complex solution that no one understands just adds to the end user frustration.

People overestimating the Project Professional skills. So many people think they know Microsoft Project, having worked in a stand alone environment for years. Once a Project Server is installed that picture changes significantly. There are added complexities, and a heap of new functions to use.

Customers don't follow advice. Most reputable implementation partners have done this for a number of years and all of them have "War Stories" to tell. Clients take that lightly and does not listen to advise or suggestions given. We have a very good idea of what will and what wont work!! Trust us.

Cutting Training. Allot of clients think by cutting training from the deployment they will save time and money, when in fact what happens is is costs more and the learning and adoption curve is so much longer. In my humble opinion this is one of the most dangerous things to do. And i am sure some implementation partners will hang me for saying, that some Partners Allow clients to cut training so that they still get the business.

Infrastructure cost and or complexity. Allot of the smaller clients tend to underestimate the complexity of n proper designed Infrastructure. Most of them do not want nor understand the need of a Development environment.

Tuesday, 8 January 2013

TPG PSLink is a SAP-certified product
for a bidirectional data exchange between Microsoft Project and SAP. Its
extensive checking mechanisms ensure the complete consistency of all data
shared between the two systems at all times. The product is very flexible for
use in a range of different scenarios with extensive configuration options,
which offer you an unrivaled rapid implementation time – even if the SAP PS
module has not been implemented.

A difference analysis shows you the changes in the data before
they are written to the other system – and only these changes are transferred.
This is what makes TPG PSLink so unique, compared to other solutions.

So i am sure some of you have started playing around with Project Server 2013 or will be looking at it in the near future. One of the most interesting things for me is that Microsoft has decided to move the "Server Settings" (As known in Project Server 2010).

The new Navigation bar does not display the "Server Settings" section any more. What has happened is that some settings are now managed under the contexts of Central admin for the farm. The Managed items : Queue and Database Administration, Operational Policies and Workflow & Project Detail Pages are all managed from Central Admin. Some of these items below these topics are managed here.

The rest of the Traditional "Server Settings" can be found under the "Site Settings Menu" of the PWA site that was created.

Note the "Project Web App Settings" at the bottom of the list. This is where you will find the remainder of the "Settings" for the PWA environment.

Interestingly enough the "Personal Settings" is now also listed under the Site menu. Obviously these items are permission driven, so depending on your role in the Environment you might or might not have access to everything.

Thursday, 3 January 2013

I would like to wish all my readers a Prosperous New Year , may the best of 2012 be the worst of 2013 !!

I am really excited about this year and the new Project 2013 as well as SharePoint and Project Server 2013. I hope to enlighten you with some of the info i pick up as i start deploying to clients "Playpen" environments.

If you have any questions or comments please ask i will assist when and where i can.