Tag Archives: Anailís Ghnó

BrightStarr US Ag féachaint do SharePoint Anailísí

Fág freagra

Mo cuideachta, BrightStarr, Tá iarratais á lorg anailísí gnó SharePoint.  Is é ár gcuspóir a bheith ag obair le duine a:

  • Tuigeann sé an t-ardán go han-mhaith
  • Tá smaoineamh maith ar cad a réiteach SharePoint cliste i gcomparáid le teach cobbled le chéile de chártaí
  • Taitneamh ag obair go díreach do chliaint, cuid acu a thuiscint cad is SharePoint ar fad faoi agus roinnt a bhfuil ach smaoineamh vague go bhféadfadh SharePoint cabhrú leo ach nach bhfuil cinnte go cruinn conas
  • An féidir scríobh go han-mhaith
  • Is féidir le cumarsáid a dhéanamh i ndáiríre go maith le foireann bheag
  • An bhfuil go maith ag taitneamh agus il-tasking.  Ní hé seo an timpeallacht próiseas-tiomáinte mór (ní mór dúinn a phróiseáil go leor chun rudaí a dhéanamh ar bhealach eagraithe, ach tá muid thar a bheith go tapa ar ár chosa, nimble agus go léir go stuif maith).

Ní suíomh forbróir Tá sé seo cé go má tá tú ina chomhairleoir-forbróir ag lorg chun díriú níos mó nó dul i gcomhairle agus níos lú ar fhorbairt, D'fhéadfadh sé seo a bheith ina chéim maith agat.

Má tá suim agat, ping dom ar Twitter nó ríomhphost chugam!

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin

An féidir "An bhfuil” versus "Ar chóir Ná” i dTionscadail SharePoint

8 Freagraí

Sílim go bhfuil a lán againn i láthair ó am go chéile le, d'easpa frása níos fearr, riachtanais óg-leanbh.  An t-úsáideoir deiridh i ndáiríre, an-dona mian le breathnú sonracha áirithe agus mothú, nó struchtúr sórtáil an-sonrach nó a ghearradh amach cliceáil amháin nó rogha roghchlár chun maolú ar loingseoireacht nó [insert passionately held belief that happens to be wrong].  As SharePoint pro’s, we can generally meet almost any kind of requirement with the platform, but for some of them, we know in our hearts that:

  • They are going to take a disproportionate amount of time to implement (and therefore cost more)
  • They are going to be highly custom and therefore difficult to maintain and troubleshoot
  • There is is some easy SharePoint approach that meets 80% or more of the requirement (i.e. meets the sprit of the requirement, but not the letter of the requirement)

Bottom line, we know that the “requirement” is really just a nice to have or even legitimate in some sense, but something that people should live with rather than spend a lot of time trying to “solve.”

I think of these as “young child” requirements because I’ve seen this pattern many times before.  Kids will pine away and nag you for some new toy for weeks at a time.  You get them the toy, they play with it for a few hours or days and then put it down, never to pick it up ever again.  Nó, you don’t get the toy, the nagging stops and the kid moves on to become President of the free world.   I’ve seen this happen in SharePoint projects.  Decision makers either get what they want and it becomes an unused or underused function or they don’t get what they want and the project still succeeds anyway.

I was reminded of that today in a forum post and I liked how Clayton Cobb tried to get the forum poster to push back on one of these kinds of requirements: http://social.msdn.microsoft.com/Forums/en-US/sharepointinfopath/thread/af8a1941-92ad-4f1a-b1bf-875e28ea79b7/

I’m really curious how people view this topic and how you deal with it.  Am I missing the point?  Do you have strategies to steer decisions makers away from overinvesting in trivial requirements?  Please leave a comment.

</deireadh>

Liostáil le mo bhlag.

Lean mé ar Twitter ag http://www.twitter.com/pagalvin