eLifeMagz.Com » 10 Keys To A Successful Portal Project

Home > Business > 10 Keys To A Successful Portal Project

10 Keys To A Successful Portal Project

November 15th, 2010 elifemagz Leave a comment Go to comments

Before you look at the factors that can lead to success, let’sattempt to conclude it. A small investigate in to plan success rates shows thatthere are no unprejudiced census data is to final decade. There are lots thatclaim to be, but a small digging always resulted in a leading grant tothe figures being from a firm that increase from assisting you be successful.There is nothing incorrect with these companies compelling themselves in thismanner, it usually leaves the trustworthiness of the figures in questions. So you willleave census data out of our definition.

The figures on success differ widely depending on what factors areconsidered to conclude success. Was the plan inside of budget? Were thestakeholders satisfied? Did the plan total on time? Oddly, the onecriteria not found was user satisfaction. Does this meant that if it was withinbudget, on time, and stakeholders (rarely users) were contented but no a usedthe program it was still a success?

For the role of this article, you will conclude success solely asreturn on investment. ROI may be completed by increased increase and operationalsavings, possibly inclusively or exclusively. My experience has been that theonly certain way to accomplish a positive ROI on a portal plan is for users towillingly use the portal. Time and responsibility are unquestionably vital factors,too, and are deliberate in any of these 10 keys.

Someone once mentioned (and has been plagiarized on this often) that “theonly stipulations to achieving success are time and resources”. There are a few projects that are programmed bystarting with the limitations. Other projects are programmed ignoring thementirely. You shouldn’t need a expert to discuss it you that any impassioned is goingto lead to at least dissatisfaction if not total failure. And you shouldn’tbelieve any person that tells you that they have the absolutely best approach. Whatis draft here is to beginning without stipulations to prevent having them, well,limit you.

The primary formulation should be really pie-in-the-sky, and preferablyfacilitated by someone who can both bring out the creativity of the planninggroup, remind them kindly that they may not obtain all that they can imagine, andartfully evasion the unavoidable requests for functional stipulations before it istime to request them, that is after all attractive attributes have beenexpressed. There are two ways to know that your organisation has completed expressingtheir total list of possibilities. The first way is when the final dozenideas are deliberate unreal or invalid by the most of the group. Thesecond is when reality re-enters the formulation event and you have run out oftime. And you have to confine time to prevent the dangers of analysisparalysis.

With infinite time and resources, the honest amid us will admitthat they would never broach anything. Still, it is incredibly familiar forprojects to endeavor to “fill a 5 bruise bag with 10 pounds” as a projectmanager frequently described his job. If a portal were to obviously broach all ofthe features listed in the infinite formulation event it would possibly do manythings so feeble that no a would ever wish to use it, or take over theplanet. The usually sites that advance shut to receiving over the world started as reallysimple with really paltry features and functionality, so you can safely assumethat not as big is better.

With your list of desirables as long as possible, it is time to onceagain kindly remind the team that stipulations are something you all live with.Many projects that beginning off with the pie-in-the-sky underline draw close narrowtheir choices by presenting them to the technical teams to review. This canoccasionally work out good if the technical team has built many portals for thesame stakeholders and users. However, even these mental condition teams can gain fromanother draw close to dwindling the range to something that may be deliveredsuccessfully (remembering that our clarification of success is ROI). That approachis to order the full list.

Hopefully the wish list is considerable sufficient where the first greeting maybe “that will take forever”. It doesn’t have to, if you break it down intostages. The first theatre is to divide the features in to 3 groups ofdesirability: High, intermediate and low (similar to the MoSCoW method). The easiest way I have seenthis done is to put all of the features on sticky-notes, then have any memberof the team as a organisation spot the records with their ranking. Total the votes andyou right away have 3 lists. Put the low list away, and then order the remainingtwo. Usually during this final ranking a few of the highs and mediums will getdropped to a low. The outcome is a prioritized list of features the team agreeswill be useful.

While I would be cheerful to give a decisive product in thissection that will make your plan a success (in box you haven’t guessed,that would be WebLogic Portal) that would be the a certain way to accomplish theopposite outcome in a few cases.

There are many (though fewer than as small as 5 years ago)portal products. Some are specialized for definite portal types, such ascollaboration or ecommerce. Others are broad purpose. Your prioritizedrequirements will slight the list from all portal products to a few smalleramount. If you confine yourself to Oracle products, you should be able to findsomething that suits your definite needs.

Portal products are moreover differentiated formed on programminglanguage. This may or may not be a leading reason in choosing, depending on yourtraining bill and timeline. Do keep in thoughts that if your technical team ishighly skilled in a particular denunciation that the extra savings in practice should becarefully weighed against functionality and features that encounter yourrequirements. If a considerable most of your mandate may be filled usingout-of-the-box features from a product in a denunciation where your team needstraining, the product advantages may transcend the practice costs.

Another visit preference indicate for portal products is vendorsupport. Again, an Oracle product will give an value here.

Finally, you may moreover ponder something completely custom. This isseldom the best choice, but occasionally does not meant never. I evidently stop aseries of several portals built for a leading curative firm by aboutique formation firm that someone after that mentioned could have been done for amuch descend cost from scratch. At the time, I agreed. A year subsequent to thatstatement most of those portals were amalgamated in to a singular portal application.That would have been an massive endeavour if they had been built it on acustom platform rsther than than the WebLogic Portal, that done it a fairlystraight-forward plan draw close to mix them all together.

The most successful portal projects I have worked on started with a”clickable demo”. If you have already gritty your portal platform, by allmeans erect it the demo inside of the platform. Otherwise, you should still beable to reuse ample of your demo HTML in a final product.

While I mentioned in the foreword to this essay that reliablestatistics were tough to locate, a reason was sincerely consistent. A keyrisk reason of web-based projects is varying requirements. From experience,requirements most frequently change when a great treat of bid has been put forthto broach and then the stakeholders look at the results and change their mind.This could be since the mandate weren’t clear, but it is just as oftenfrom the realized mandate leading to new understandings or needs.

While it is great to be in a room with meddlesome and creativepeople formulation what they want, there is no replacement for being able to actually”see and touch” something that represents what looks good on paper. Once aclickable demo is available, stakeholders can see what their prophesy will looklike. This is moreover an glorious time to actions usability tests with actualusers, bringing out key success criteria beneath investigation before creation a outrageous investment.Good HTML work takes talent, but it may be altered ample faster than a completedend-to-end focus where it is detected that the underline is not what theuser longed for or needs a few leading change before it will be something that theuser will wish to use.

Ok, so during our Plan Big theatre you mentioned that it was critical tonot discuss technical stipulations until the right time. Now is the right time.

This key theatre in a successful plan can (and usually should) berun in together with office building the clickable demo. If a underline is identified asimpractical previous to presenting it with a look and feel it will save a lot offrustration to all by stealing it from the demo before someone sees it andthinks it’s cool. While the cold reason can lead to success, with our keysuccess criteria as ROI, cold may a reduction to success.

Taking the list that the mandate team prioritized (but with theprioritization private to prevent prejudice), it is right away time is to technicalteam to give their ratings. While the technical team may have their own(correct or not) notions of what is useful, they must put that in reserve and solelyrate any underline with a danger and an bid level, once again using the High,Medium, Low scale. Features that have both a High rating in both should then becompared with the appropriateness ratings, dropping those that are low on the wishlist.

The residue of the list should then be reviewed between both therequirements and technical teams to finalize what may be delivered with thebest expectancy of success. It is rarely endorsed that this bargain bearbitrated by an unprejudiced celebration that moreover has a good understanding of both thebusiness needs and technical considerations. In all honesty, this is probablythe most tough success reason to achieve, that moreover creates it really high onthe inestimable scale.

Project teams are normally fluid. They change to a few grade witheach project. For a portal project, it is critical to have a good mix ofspecialists and generalists. Generalists are vital to keep an eye on thebig picture. These are the people that will grasp the discrepancies that occurwhen a organisation finds a answer to a complaint and adopts the “if you have ahammer in your hand, all resembles a nail” mindset. They can moreover seewhere not similar mandate or approaches are possibly jointly disdainful orpresent a ample aloft effort/risk value when amalgamated than they do separately.

The need for specialists is a matter of practicality. There arefewer generalists than specialists, and far fewer generalists that are highlyskilled in the specifics of more than a few of disciplines they have knowledgeof. A good generalist knows when they need more sum from a specialist, anda good dilettante has an premonition when they need submit from a generalist, evenif the submit is usually is to generalist to experience in a deliberation acrossspecialists to accomplish the best approach.

For the areas where a generalist is rarely skilled in the specificsof role or technology, the top luck for success is to have a specialiston the team who can hoop the job as well. This is since the generalist willoften be entangled in “fire fighting” a few aspect of the plan using usually oneof their skills, leaving gaps in the plan course that will must be befilled by others.

There are many specialists that are multi-disciplined, nonetheless still notgeneralists, and many generalists that have no particular specialty. The key isto have a generalist and a dilettante for any role. This isn’t to say thatthere must be two people per role per project, usually that the team should becomprise of members who can encouragement any other. One e.g. would be a projectthat requires 10 roles. A singular generalist may hoop the generalist segment ofthe team, and 5 specialists any with two specialties. Any multiple isfine, so long as there is cranky encouragement for any role.

All portals require maintenance. What is startling is how seldomthe continuance mandate are identified before production. As mentionedearlier, plan teams lend towards to be fluid, nonetheless so many portal projects obtain allthe way to prolongation with the unstated premise that the growth teamwill be existing for maintenance. A more realistic plan is to pick out membersof the growth team who will passing from one to another to the continuance team immediatelyupon release. Depending on the size of the project, their time post productionmay be widely separated between continuance and new development. This is obviously highlydesirable as it provides a good way for those entrusted with continuance tokeep sensitive on what future features they will be accountable for.

Another draw close is to have a completely well-defined continuance team.This is frequently functional for really considerable portals (though, as mentionedoccasionally in progressing sections, a really considerable portal for a first let go isusually not favorable to success). When the continuance team is well-defined fromthe growth team, it is critical that the growth team have thoroughdocumentation. The continuance team must be fabricated far sufficient in advance ofrelease so that they can examination the record with the growth team forgap analysis. It is moreover fitting for this sort of continuance team toparticipate in QA, to give them early bearing to problems that may happen inproduction.

Just as demise and taxes are deliberate unavoidable (though a few of usstill grip out hope for that to change) a portal that is successful on releasemust develop to go on being successful. If the success key of Deliver Smallis followed, you should have a list of desires nonetheless to be fulfilled. Once theportal is in the hands of users, that list should develop as well, since usersare your best source for ideas on how to upgrade the success of your portal.

A growth strategy for a portal is another a of those areas (likethe selection of portal products) where usually suggestions may be given rsther than thanabsolutes. Identifying members of the primary team to expand permanent rolesrelated to the portal is a strategic approach. Another draw close is to obtaina bill for expansion, even if that bill must be fit by requirementsthat were delayed whilst knowing those may not be the mandate implementedin the next iteration.

The UI pattern should take growth in to account. The navigation needsto be adjustable so that it may be stretched without leading changes. There are fewthings more frustrating to a user to have new features introduced that make itdifficult to fix up the features they were already using.

The network architecture should expect growth without leading toa considerable bid to perform future needs now. Taking a pluggable draw close tocomponent formation is the best way to pave the way for growth withoutspending a considerable amount of time and bid office building something to supportfunctionality that may after that be deserted for something else.

Remember our list of risks and effort? It is flattering familiar that thislist will be a bit more confident than it should be. Developers by inlet areoptimistic, that is why most of them work long hours. One way to alleviate thisoptimism (which is a good thing and why the technology continues to blossom inleaps and bounds) is to conclude anything that your team hasn’t privately doneas intermediate to high risk. If it is something that is good documented and examplesare straightforwardly available, it may be rated medium; instead it should be considerhigh risk.

There have been many projects where the danger was rated as well lowbecause product record settled that a underline was supported, where it waslater detected that there is a considerable hole between “supported” and “easilyimplemented”. If ROI is as highly-user driven as you are presumption (well, I am,at least), there are few things more user-vicious than to guarantee a underline andnot give it.

Any piece that is high danger should given a functional test, ordeveloped as a entirely functional proof-of-concept before committing todelivering it. The POC will give a improved understanding of both danger andeffort, and upgrade ROI since a underline that fails to work as expectedrequires extra work on the segment of QA staff, growth staff, and analysts. Thesaying “there is never sufficient time to do it right but always sufficient time to fixit” leaves out a critical factor: it expenses more to fix it than to do itright.

While roughly all developers lend towards to be optimistic, they are prettydivided on their preference of possibly reusing what already exists or buildingeverything new. They moreover lend towards to follow this preference single-mindedly. Asmany growth managers were once developers, their tendencies frequently becomethe culture. This is not always a bad thing, since such cultures frequently evolveto where they can broach consistently with their selected preference. If thedelivery is not consistent, it is critical to develop an draw close forevaluating existing properties for any plan and make a unfeeling decisionwhether reuse or replacement will server the plan best. While thedevelopment team must be segment of this preference process, it is best to have itfacilitated by someone outward the team, preferably someone who doesn’t have theirown tendencies in this area.

One familiar thesis of all “Ten-Keys_to-Success” presentations is thatthe user’s needs must advance first. Ifyou wish the user to need something for your distinction or extra savings it must beprovided in a way that gives the user a benefit.

Creativity is moreover critical to a successful portal project. Itshould be fostered from the earliest stages of the plan and speedy ateach stage. Creativity is not paltry to forthcoming up with features to deliver, itcan (and should) moreover be applied to creation compromises between business needs,technical considerations, and usability.

Finally, more than a key to success is evidently a matter of findingwhat functions for your particular plan rsther than than a cure-all trail to portalproject perfection. This moreover means that actively seeking for more than tenkeys is the eleventh key to success.