'N Kort geskiedenis van SharePoint (Uit 'n relatiewe nuweling se perspektief)
Let daarop: Hierdie artikel is oorspronklik gepos word aan www.endusersharepoint.com. I forgot to post it to my own blog 🙂
SharePoint ontwikkel het 'n groot deel sedert sy vroeĂ« dae as 'n soort van 'n inkubasie tegnologie by Microsoft –dit ontwikkel het amper soos 'n horror movie, waar die mal wetenskaplike se skepping neem op 'n lewe van sy eie, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 voorwerp model is ryker en meer kompleks as WSS 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, egter, SharePoint se evolusie is selfs nog meer betekenisvol.
In die vroeë dae, 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, Dit volg op 'n betreklik tradisionele patroon van eindgebruiker <-> IT relationship. A lot of End Users, kommunikeer en werk met 'n baie klein aantal mense Dit oplossings vir probleme op te lewer:
Die algehele probleem domein waarvoor SharePoint is 'n geskikte aflewering platform is 'n klein (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: definieer vereistes IT, wag vir dit doen nie hul werk agter die gordyn en neem lewering van die finale produk.
As SharePoint ontwikkel om die 2.0 wêreld (WSS 2.0 en SharePoint Portal Server), several things happened. Eerste, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Byvoorbeeld, sou jy nie dink te hard oor die implementering van 'n ernstige soek oplossing in 'n SharePoint omgewing tot SPS (en selfs dan, dit was nie so goed soos dit nodig is om te wees). Op dieselfde tyd, Einde gebruikers het 'n ongekende vermoë om nie net te definieer, but also implement their own solutions with little or no IT support.
Die 3.0 platform (WSS en mos) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platform. Virtually every department in a company, wat wissel van die vervaardiging van gesondheid en veiligheid departemente tot bemarking, uit verkope aan gehaltebeheer - hulle kan vind 'n goeie gebruik vir SharePoint (en dit is nie 'n geval van Mais Chen 'n ronde pen in 'n vierkantige gat). Op dieselfde tyd, 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. Die 3.0 platform turns previously stable roles on their heads. Suddenly, Einde gebruikers is effektief regter, jurie en laksman sake-ontleder, 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, Kom ons kyk na die olifant in die kamer.
Loer na die Crystal Ball
Hoe sal SharePoint 2010 invloed op hierdie patroon? Will it be incremental or revolutionary? Will more, minder of ongeveer dieselfde aantal End gebruikers hulself bemagtig om oplossings te bou in SharePoint 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?
Daar is genoeg inligting "daar buite" om veilig te sĂŞ dat die algemene antwoord is:
- The problem domain is going to dramatically expand.
- Einde gebruikers sal vind dat hulle selfs meer bemagtig as ooit tevore.
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.
Geen Bulls in China, My Shop!
Dit klink baie, maar uit my oogpunt as 'n SharePoint konsultant en om myself in die skoene van 'n IT-bestuurder, I see this vision. I own a China shop with beautiful plates, kristal, ens. (my SharePoint omgewing). 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, maar in afwagting, 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 twee bulls and even a wolf. Then I notice that there are some sheep. Sheep are so slegte, maar hulle is dalk verbloem wolwe? I don’t want bulls in my china shop!
Dit raak erger! When I rented the space, I couldn’t believe how nice it was. Wide and open, geweldige geriewe, very reasonable price. Egter, nou is ek besef dat die wye oop ruimtes en die groot deur is net perfek grootte vir 'n bul te kom dwaal in en afval te lê na my China.
Ek is besig om hierdie beeld te ver, natuurlik. End Users are not bulls (die meeste van hulle, in elk geval) en IT-afdelings nie (of sekerlik moet nie) view their user community with that kind of suspicion. Egter, daar is hierdie soort van volmaakte botsing plaasvind reeds in die die 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.
Dit is groot en al, maar die feit is dat dit nog 'n baie tegniese produk en nog steeds oproepe vir die aard van die kragtige besigheid vereistes analise, 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 gaan die spel verander 'n bietjie en dit gaan om te speel anders en in slow motion as maatskappye uitrol hul SP 2010 oplossings oor 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, byvoorbeeld. They need to understand fundamental concepts like CRUD (skep, werk en te verwyder), dev / toets / QA / prod omgewings en hoe om daardie infrastruktuur te gebruik om behoorlik ontplooi oplossings wat leef 'n lekker lang tyd en draai (nie breek) in reaksie op veranderinge in 'n organisasie.
In die komende weke, Ek is van plan om te probeer en 'n paar van my eie nuwe idees, sowel as skakel na die groot werk wat gedoen word deur baie ander skrywers (op www.endusersharepoint.com en elders) so that interested End Users can learn that old time IT religion. Keep tuned.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin