SharePoint historia laburra (Relative Wazemank baten ikuspuntutik)
Kontuan izan: Artikulu hau, jatorriz etan www.endusersharepoint.com. I forgot to post it to my own blog 🙂
SharePoint handia bilakaera izan du bere hastapenetan, eta geroztik, Microsoft teknologia inkubazio sort –beldurrezko film bat bezala da ia eboluzionatu, non zientzilari ero en sorkuntza bere bizitza bat hartzen du, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 objektu eredua da, aberatsagoa eta konplexuagoa WSS baino 2.0, which was itself an improvement over earlier versions. The next version will no doubt show tremendous improvement over 3.0. From an End User’s perspective, Hala ere,, SharePoint bilakaera da, are gehiago esanguratsua.
Hasieran egunetan, SharePoint didn’t offer much to End Users. They would have their usual functionality requirements, work with IT to define them well and implement a solution. IT would use SharePoint to solve the problem. The product wasn’t very accessible to End Users. I’ve thought threw a few analogies, but I decided to stick Venn Diagrams to show what I mean. When Microsoft first released SharePoint to the world as a commercial offering, Azken erabiltzailearen eredua nahiko tradizionala ondoren <-> IT relationship. A lot of End Users, komunikatzeko eta bertan jende kopuru oso txiki batekin irtenbide enpresa arazoak konpontzeko emateko lanean:
Globalaren arazoa domeinu diren SharePoint egokia entrega plataforma da txiki (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: define eskakizunak IT, itxaron egin lana oihala atzean eta azken produktuaren entrega hartu.
SharePoint to eboluzionatu gisa 2.0 mundu (WSS 2.0 eta SharePoint Portal Server), several things happened. Lehen, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Esate baterako, ez duzu uste gehiegi gogorra larri bat bilatu beste irtenbide ezartzeko SharePoint ingurune batean buruz SPS arte (eta, nahiz eta, ondoren,, ez zen ona behar da izan). Aldi berean,, Amaiera Erabiltzaileek aurrekaririk gabeko ahalmena ez da bakarrik definitzeko, but also implement their own solutions with little or no IT support.
The 3.0 plataforma (WSS eta MOSS) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 plataforma. Virtually every department in a company, fabrikazio-, osasun-eta segurtasun-sailetako marketing artekoak, kalitate-kontrola salmenta - SharePoint erabilera ona aurkituko dute (eta ez da Kopako bat Peg mashing karratu zulo sartu kasu bat). Aldi berean,, the platform empowers even more End Users to implement their own business solutions. I try to capture that with this diagram:
This has proven to be both a potent and frustrating mixture. The 3.0 platform turns previously stable roles on their heads. Suddenly, Amaiera, erabiltzaileak modu eraginkorrean epaile, epaimahaiak eta Ejecutor enpresa analista, application architect and developer for their own business solutions. This gets to the heart of the problem I’m writing about. But before I dive into that, dezagun kontuan hartu aretoan elefantea.
Crystal Ball sartu Peering
Nola izango SharePoint 2010 eragina duten patroi hau? Will it be incremental or revolutionary? Will more, gutxiago edo amaiera erabiltzaile kopuru berean buruz aurkitu konponbideak eraikitzeko SharePoint-en ahalmena beraiek 2010? Will SharePoint 2010’s problem domain expand even further or will it just refine and streamline what it already offers in WSS 3.0 / Moss?
Ez dago informazio nahikoa da "hor kanpoan" segurtasunez esan, orokorrean erantzuna dela:
- The problem domain is going to dramatically expand.
- Azken erabiltzaileek beraiek aurkituko are gehiago ahalmena baino.
The Venn Diagram would be larger than this page and cause some IT Pros and CxO’s to reach for their Pepto.
I believe it’s going to be a tremendous opportunity for companies to do some truly transformational things.
Nire Txina Denda Zezenak No!
Dirudi handia, baina nire SharePoint aholkulari gisa ikuspuntutik eta ni jarriz IT kudeatzailea zapatak sartu, I see this vision. I own a China shop with beautiful plates, kristal, etc (nire SharePoint ingurumena). I’ve rented a space, I’ve purchased my inventory and laid it all out the way I like it. I’m not quite ready to open, baina aurrea hartzeko, I look at the door to see if my customers are lining up and I notice an actual bull out there. I look more closely and I actually see bi bulls and even a wolf. Then I notice that there are some sheep. Sheep are beraz, bad, but are they maybe disguised wolves? I don’t want bulls in my china shop!
It gets worse! When I rented the space, I couldn’t believe how nice it was. Wide and open, terrific amenities, very reasonable price. Hala eta guztiz ere, now I’m realizing that the wide open spaces and the huge door is just perfectly sized for a bull to come wandering in and lay waste to my china.
I’m pushing this analogy too far, jakina. End Users are not bulls (most of them, hala ere) and IT departments don’t (ziur aski, edo behar ez) view their user community with that kind of suspicion. Hala eta guztiz ere, han egiten ari da dagoeneko dagoen talka perfektua moduko hori 3.0 platform that I expect will only get worse in SP 2010. SharePoint already empowers and encourages End Users to define and implement their own solutions.
Hori da, handia eta guztiak, baina kontua da hori, oraindik ere oso teknikoa, produktu bat, eta oraindik enpresa indartsua eskakizunak analisi mota eskatzen, design and general planning and management that technical projects require to be successful. These are not the kind of skills that a lot of End Users have in their bag of tricks, especially when the focus is on a technical product like SharePoint.
I’ve given this a lot of thought over the last year or so and I don’t see any easy answer. It really boils down to education and training. I think that SP 2010 da jokoa aldatzeko pixka bat joan eta play ezberdinean eta mugimendu motela hasi da joan enpresa roll out beren SP 2010 konponbideak baino gehiago 2010 and beyond. In order to succeed, End Users will need to transform themselves and get a little IT religion. They’ll need to learn a little bit about proper requirements
analysis. They will need some design documentation that clearly identifies business process workflow, adibidez. They need to understand fundamental concepts like CRUD (sortu, eguneratu eta ezabatu), dev / test / qa / prod inguruneak eta nola azpiegitura hori erabiltzeko behar bezala zabaldu irtenbideak bizi polit bat denbora luzean eta bihurgune (ez hausteko) Erakunde baten aldaketak erantzunez.
Datozen asteetan, Eta saiatu ematen nire ideiak batzuk egiteko asmoa dut, baita lan handia lotura beste askotan egileek egin (an www.endusersharepoint.com eta beste nonbait) so that interested End Users can learn that old time IT religion. Keep tuned.
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin