Kratka povijest SharePoint (Od relativno pridošlica perspektive)
Primijetiti: Ovaj članak je izvorno objavljen u www.endusersharepoint.com. Zaboravio sam to objaviti na svom blogu 🙂
SharePoint je evoluirala mnogo od svojih ranih dana, kao svojevrsno inkubacije tehnologije u Microsoftu –to je evoluirala gotovo kao horor filma, gdje je ludi znanstvenik kreacija se na vlastiti život, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 Objektni model je bogatiji i složeniji od 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, međutim, SharePoint evolucija je još značajniji.
U ranim danima, 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, to slijedi relativno tradicijski način za krajnjeg korisnika <-> IT relationship. A lot of End Users, komunikaciju i rad s vrlo malim brojem ljudi nje da dostavi rješenja koja rješavaju poslovne probleme:
Ukupna Problem domene za koje SharePoint je pogodna isporuku platforme je mala (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: definirati zahtjeve za IT, čekati za to rade svoj posao iza zavjese i uzeti isporuku finalnog proizvoda.
Kao SharePoint evoluirao 2.0 svijet (WSS 2.0 i SharePoint Portal Server), several things happened. Prvi, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Na primjer, ne bi previše razmišljati o provedbi ozbiljnu pretragu rješenje u SharePoint okoliš dok SPS (pa čak i onda, to nije bio tako dobar kao što je potrebno kako bi se). Istovremeno, Krajnji korisnici imaju neviđenu sposobnost ne samo definirati, but also implement their own solutions with little or no IT support.
The 3.0 platforma (WSS i MOSS) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platforma. Virtually every department in a company, u rasponu od proizvodnje zdravlja i sigurnosti odjela za marketing, od prodaje kontrole kvalitete - oni mogu naći dobro iskoristiti za SharePoint (a to nije slučaj gnječenje okrugli klin u rupu trgu). Istovremeno, 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, Krajnji korisnici su učinkovito sudac, porota i krvnik Poslovni analitičar, 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, razmotrimo slona u sobi.
Prodiranje u Crystal Ball
Kako će SharePoint 2010 utjecati na ovaj uzorak? Will it be incremental or revolutionary? Will more, manje ili približno isti broj krajnjih korisnika nađu ovlaštena za izgradnju rješenja u sustavu 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?
Ima dovoljno informacija "vani" za sigurno reći da general odgovor:
- The problem domain is going to dramatically expand.
- Krajnji korisnici će se naći još više ovlasti nego prije.
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.
Nema Bullsi u moju staklarni!
To zvuči odlično, , ali s moje točke gledišta kao SharePoint konzultant i ja stavljanjem u cipele IT menadžer, I see this vision. I own a China shop with beautiful plates, kristal, itd. (moj SharePoint okoliš). 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, ali u iščekivanju, 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 dva bulls and even a wolf. Then I notice that there are some sheep. Sheep are tako loše, , ali su oni možda prikriveno vukove? I don’t want bulls in my china shop!
To se pogoršava! When I rented the space, I couldn’t believe how nice it was. Wide and open, nevjerojatan pogodnosti, very reasonable price. Međutim, sad sam shvatio da prostranstvima i ogromna vrata je upravo savršeno veličine za bika doći lutanja i položiti otpada na moj Kini.
Ja sam gura ovu analogiju predaleko, naravno. End Users are not bulls (većina ih, u svakom slučaju) i IT odjeli ne (ili sigurno ne bi) view their user community with that kind of suspicion. Međutim, postoji ova vrsta savršen sudara odvija već u 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.
To je super i sve, , ali činjenica je da je još uvijek vrlo tehnički proizvod i dalje poziva na kakve energične poslovne zahtjeve analize, 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 će se promijeniti igru malo i to će se igrati drugačije i usporeno kao tvrtke razvaljajte svoju SP 2010 Rješenja više 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, for instance. They need to understand fundamental concepts like CRUD (stvoriti, ažuriranje i brisanje), dev / test / K / prod okruženja i kako koristiti tu infrastrukturu kako bi ispravno implementirati rješenja koja žive lijepo dugo vremena i iskrivi (Ne provaliti) kao odgovor na promjene u organizaciji.
U narednim tjednima, Planiram probati i dati neke svoje nove ideje, , kao i link na velikom djelu učinio mnogo drugih autora (na www.endusersharepoint.com i drugdje) so that interested End Users can learn that old time IT religion. Keep tuned.
</kraj>
Slijedite me na Twitter-u http://www.twitter.com/pagalvin