Archive for December, 2010

Why Enterprise Engineers Need Great Communication Skills

December 31st, 2010


As the number of people or groups involved in a body of work increases, so does the complexity in communications between all parties. In other words, it gets harder to keep everybody up to date as the number of people involved in any given body of work increases.

If one was to model the number of relationships between bodies in a project then the formula would look like this; (n * (n-1))/2 where n is the number of people involved in the project.

So according to the formula if we have 3 people working together, the number of possible communications relationships is (3 * 2)/2 = 3. However, if we have double that number, 6 people or groups in a project, then the formula highlights a drastic increase in communications that need to be managed; (6 * 5)/2 = 15. When there are 100 people or groups involved then the result is a whopping 4950 relationships that need to be managed in order to keep everybody up to date with events!

As you can see, the higher the number of people or groups involved the more complex the communications get. Organizations have long understood this phenomenon and as a result processes exist in order to simplify and assist in the management of this difficult task.

This is why it is important for enterprise engineers to understand and comply with any existing processes in place to manage changes or projects. Not only will good communications keep the project members well informed, but it will also help you to voice concerns, milestones and announcements to relevant parties efficiently and without forgetting anybody.

So what are the basics in order for a technical person to achieve good communications levels in an enterprise environment? Here are our top 5 tips in no particular order;

1. Always put context around your messages. People may be involved with other tasks and projects and may not necessarily know what body of work you are referring to.

2. Deliver messages to the appropriate stakeholders. People directly and indirectly involved with the change need to know what is going on. For example, a network operations center may not be directly involved with the project or change but they may need to know of any scheduled downtime. Managers and support groups are also key groups to notify.

3. Adjust the language in your response to suit your target audience. This includes explaining an ‘english’ version of the proposed technical changes or outcomes.

4. Send messages in a timely manner. Sometimes it is appropriate to forewarn stakeholders of upcoming changes or events. It gives them an opportunity to consider the changes and to ask questions or voice concerns.

5. Be sure to understand the appropriate messaging system. You will notice that I have been cautious throughout the article to make sure not to specifically mention email or trouble tickets. Whatever the messaging system(s) your organization has in place is the appropriate tool to disperse the information.

Delivering great technical solutions is only half the battle for an enterprise engineer. The remainder is the communication with the teams and stakeholders to ensure that all levels of the organization have been well informed.

By: Andres Villalva

About the Author:
AIT-Pathways.com is dedicated to quality staffing in the Information Technology industry both through online learning articles such as this one and career development tools such as our IT Roles scatter diagram or our popular IT Skills Matrix.

IT-Pathways.com – Upgrade Yourself!



Implement the Benefit of Business Change with R-pM

December 30th, 2010


Conventional methods implement the costs of change and prevent benefits. Benefit from change through R-pM.

Many of us have participated in business change projects. I am sure that we share many experiences with the difficulties in gaining successful business change. We have read about many cases of problems and disasters. Why after all this experience and the many stories of unsuccessful business change, do we continue to have problems? For a start:

- We continue to employ bad methods for business change. No one has ever put forward a good method

- We do what everyone else is doing, to implement the same problems as everyone else

- We employ conventional wisdom, which automatically introduces bad decisions

- Our enterprise is not structured to plan and manage benefits, support new solutions in operation, or ensure good performance from the solution

Let’s go through business change step by step. What was the objective of business change? Likely, there is a nominal objective like increasing revenues, reducing costs, or improving customer service. What is the basis of this objective? Precisely how is the new solution to be used to produce benefits that add up to the nominal objectives and provide the return? This rarely is defined.

If the nominal objective is just words, what is the implementation team trying to do. Often they will say their objective is performance improvement. Should that be the objective? Conventional wisdom says yes, but how do you feel when someone tells you, you need to improve your performance or that consultants are coming in to improve our performance?

But, in the end, even performance improvement proves hard to define, so the objective comes down to something that every one involved can understand – - “solution implementation”.

Is solution implementation the proper objective? Conventional wisdom says it is, but I think most of us recognize that it is not. But, none of us is sure of what the objective should be.

Certainly, when consultants get involved, the objective is solution implementation. They likely proposed a methodology that they can employ to convert the business over to the new solution.

So, if consultants were involved, who ended up managing the day to day implementation – - the enterprise project manager or the consultant project manager? Likely it was up to the consultants because that is conventional wisdom and the enterprise does not have the capability or experience with business change. So, who was appointed enterprise project manager? Was it a manager involved in increasing revenues or improving customer service? Or, was it the administrative manager supporting the solution?

Likely, the administrative manager was appointed project manager, since that is the conventional wisdom. What was the role of the enterprise project manager? It likely boiled down to providing the solution requirements, which is what the consultant wants. The nominal consultant objective is to satisfy user requirements and to do what the customer wants, which conventional wisdom says are proper objectives.

So what are the requirements of the administrative project manager? Does the administrative manager know what is needed to improve revenues or customer service? Is the administrative manager interested in really reducing costs, when it means reducing their own staff? Who developed the old solution or gains a technical authority from the old solution? So, chances are the requirements boiled down to one – - “no change”.

So then, the project went through the steps of the methodology. Acquire the solution, set up the solution, train on the solution, implement the solution, accept solution, and operate the solution. But, all these steps just incur costs. Where are the steps for planning and achieving benefit?
During all this, what happened if there was an exception, advanced need, or a problem that was not addressed? These likely were put off to the future or left “up to the users”, since the objective is implementation.

What happens when it comes to acceptance? Well, the main requirement of the administrative project manager was met. And, the manager would look bad if delays or controversies were introduced. So implementation is signed off and the project is complete.
But what remains:

- Were advanced or future period features ever implemented?

- Was the old solution completely removed, or is it still operated to handle the exceptions?

- Is the new solution utilized to increase revenues, reduce costs, or improve customer service? Does anyone understand how to use the new solution to do more than what was done before?

- Was a responsibility established to ensure that the new solution is utilized to produce benefit?

- Was a capability established to support and improve the solution?

- Was a method established to track and measure the return on the investment in the new solution?

- How many old performance problems were implemented as part of the new solution? What is the cost of change now?

- Are the users who face the customer, enthusiastic about the new solution?

Many enterprises have had implementations where they implemented the cost of business change and received, at the most, marginal benefit.

Even if the enterprise follows an implementation or conventional business change method the best that it can, it will still be implementing the cost of business change. Conventional methods manage change and development through contrived entities rather than business reality. No conventional method can enable the methodical development of the benefit of business change, since enterprises are not structured to plan, manage, and track the benefits. Until they are structured properly to manage business reality, enterprises will continue to implement the cost of business change.

This problem is eliminated by Result-performance Management (R-pM), a new management breakthrough now being launched. R-pM provides the answer by structuring enterprise results and performance to enable result-performance development. The benefits of the investment come from result development; the costs of investment come from performance development. The payback from investments come from the increase in result value-added (result value less performance costs) compared to the result value-added with no investment, over the payback period.

So, stop implementing the cost of business change. Implement the benefit of business change by becoming a 21st century enterprise with R-pM.

By: H. Greene

About the Author:
Harry is the President of Result-performance Management Ltd. and posts information on R-pM at result-performance-management.com (http://www.result-performance-management.com/) the home site for the R-pM community. E-mail: harry@result-performance-management.com



Requirements For MCTIP Certification

December 29th, 2010


Microsoft certified Information Technology Professional is the acronym for MCITP. This certification validates the comprehensive skills that are necessary for performing a particular job specialization role which includes enterprise messaging administration or database administration. MCITP certification also builds up technical proficient that are measured in the Microsoft certification informational technology professional. Hence, candidate can obtain more MCITP certifications to earn credentials in this certifications.

Successful candidates who are holding their MCITP certification will be capable of designing, deploying, building, optimizing as well as operating technologies of a particular specialized job role. Successful candidates will also design and make decisions regarding the technology in an effective way to bring successful technology implementation of projects.

MCITP Certification Examination:

In order to obtain the this certificate, candidate has to take up the examination and score a minimum scaled points. The following are the examinations for the MCITP certification.

Windows client:

1) 70-680 or enterprise desktop administration 7.
2) 70-686 or enterprise desktop administration 7.
3) 70-620 or consumer support technician
4) 70-623 or consumer support technician
5) 70-620 or enterprise support technician
6) 70-622 or enterprise support technician

Windows server:

1) 70-640 MCITP or enterprise administration
2) 70-642
3) 70-643
4) 70-624 or exam 70-620 and exam 70-647
5) 70-640 MCITP or server administrator
6) 70-642
7) 70-646

Microsoft SQL server:

1) 70-432 or database administrator 2008
2) 70-450
3) 70-433 or database developer 2008
4) 70-451
5) 70-448 or business intelligence developer 2008
6) 70-452
7) 70-431 or database administrator
8) 70-443
9) 70-444
10) 70-445 or business intelligence developer.
11) 70-446

Microsoft Office Project Server:

1) 70-632 or enterprise project management with MS office server 2007.
2) 70-633
3) 70-634

Microsoft exchange server:

1) 70-236 or enterprise messaging administration
2) 70-237
3) 238

All these above examinations are required to take part by the candidates to obtain the certification and they can be taken part in any order.

By: Alina Michael

About the Author:
Alina Michael is CCNA and CCNP and MCITP Certified professional and currently working as Senior Network Engineer in London. She has helped thousands of IT professionals to get MCITP Certified via MCITP Certification practice exams with money back passing guarantee. You may like to visit Certification Preparation by ExamsExpert for complete details about all certifications training products and prices.