The document discusses various important considerations for a SharePoint implementation project. It addresses questions that commonly arise, such as whether SharePoint can deliver the proposed solution out of the box or if additional development is required. It also compares the on-premises vs cloud options and factors like licensing costs and existing IT infrastructure that influence the decision. The document emphasizes that requirements gathering is key and that the goal should be a functional system rather than focusing on aesthetics. Information architecture and content types are discussed as important early components. Governance and various technical aspects like reporting, documentation and change management over the long term are also addressed.
IIBA OO - Is a business analyst required for SharePoint projects?John Calvert
SharePoint offers the promise of instant functionality for all sorts of business needs: collaboration, document management, Internet/intranet web content management, search, business intelligence, etc. In addition there are seemingly endless possibilities for configuration and customization, much of it easily accessible to business and power users. Do SharePoint deployments and customizations need formal requirements gathering, business modeling, and functional analysis as part of the project plan? Or is it all about the technical infrastructure and IT configuration? Let’s discuss some real-world project scenarios and share our experiences to answer this question.
SharePoint Survey 2011 Results: How are Businesses Using SharePoint?OpenText Global 360
Updated results of our "SharePoint in the Enterprise: Best Practices Survey" after an additional 820 SharePoint users responded. Go to http://www.global360.com/download/sharepoint-survey
to get your free survey results report.
IIBA OO - Is a business analyst required for SharePoint projects?John Calvert
SharePoint offers the promise of instant functionality for all sorts of business needs: collaboration, document management, Internet/intranet web content management, search, business intelligence, etc. In addition there are seemingly endless possibilities for configuration and customization, much of it easily accessible to business and power users. Do SharePoint deployments and customizations need formal requirements gathering, business modeling, and functional analysis as part of the project plan? Or is it all about the technical infrastructure and IT configuration? Let’s discuss some real-world project scenarios and share our experiences to answer this question.
SharePoint Survey 2011 Results: How are Businesses Using SharePoint?OpenText Global 360
Updated results of our "SharePoint in the Enterprise: Best Practices Survey" after an additional 820 SharePoint users responded. Go to http://www.global360.com/download/sharepoint-survey
to get your free survey results report.
When implementing SharePoint you might think that you are adding just another technology to your heterogeneous IT environment. But after a while you realize, that users are doing things with SharePoint that you did not expect them to do. This talk dives into the dynamics of adopting SharePoint as a platform, and shows you a how to setup an operational governance practice using a structured governance framework.
How to Write Amazing Functional Analysis Documents for your SharePoint Projects GSoft
In this session you will learn how to translate business requirements into usable SharePoint
specifications? How to accurately plan effort and scope for a SharePoint project?
How to prepare a clear, complete and concise document for the development team? If these
questions keep you up at night this session is for you!
The following topics will be covered during this presentation:
Requirements Definition
Information Architecture
Functional, and
Non-Functional Specifications
Analysis templates used in the presentation will be distributed to attendees.
Demystifying SharePoint Governance and User AdoptionWes Preston
Governance and User Adoption continue to be hot topics in the SharePoint community and are still adapting as the community matures. So, what do these buzzwords mean to you and your organization? In this session we'll explain what they mean, why they shouldn't be something to fear or over-think, and how to approach these topics as a part of your SharePoint planning, implementations and ongoing management.
Transforming your business with SharePoint Developmentseoquixtec
SharePoint provides a simple and easy-to-administer structure. The SharePoint admin can control who can view what in the environment. They can grant or revoke permission to the users.
Avoiding Failed Deployments Part 2 Interactive Discussion by Joel OlesonJoel Oleson
I had so much content I couldn't include in my keynote and so much I wanted to talk about. I put together a second deck to cover those further details around team forming, process to become a SharePoint Rockstar, and so on. The pictures helped encourage more stories and pull out customer experiences. (Best experienced with Joel)
When implementing SharePoint you might think that you are adding just another technology to your heterogeneous IT environment. But after a while you realize, that users are doing things with SharePoint that you did not expect them to do. This talk dives into the dynamics of adopting SharePoint as a platform, and shows you a how to setup an operational governance practice using a structured governance framework.
How to Write Amazing Functional Analysis Documents for your SharePoint Projects GSoft
In this session you will learn how to translate business requirements into usable SharePoint
specifications? How to accurately plan effort and scope for a SharePoint project?
How to prepare a clear, complete and concise document for the development team? If these
questions keep you up at night this session is for you!
The following topics will be covered during this presentation:
Requirements Definition
Information Architecture
Functional, and
Non-Functional Specifications
Analysis templates used in the presentation will be distributed to attendees.
Demystifying SharePoint Governance and User AdoptionWes Preston
Governance and User Adoption continue to be hot topics in the SharePoint community and are still adapting as the community matures. So, what do these buzzwords mean to you and your organization? In this session we'll explain what they mean, why they shouldn't be something to fear or over-think, and how to approach these topics as a part of your SharePoint planning, implementations and ongoing management.
Transforming your business with SharePoint Developmentseoquixtec
SharePoint provides a simple and easy-to-administer structure. The SharePoint admin can control who can view what in the environment. They can grant or revoke permission to the users.
Avoiding Failed Deployments Part 2 Interactive Discussion by Joel OlesonJoel Oleson
I had so much content I couldn't include in my keynote and so much I wanted to talk about. I put together a second deck to cover those further details around team forming, process to become a SharePoint Rockstar, and so on. The pictures helped encourage more stories and pull out customer experiences. (Best experienced with Joel)
Share Point Governance: 10 Steps to Successful Deployment by Joel Oleson Bes...Joel Oleson
Best of SharePoint Conference break out session on 10 Steps to successful deployment. This deck is focused on avoiding failed deployments and what is most important in to ensure successful deployments.
Sharepoint implementation quick points to graspNeha Rai
SharePoint Implementation- some key factors to be considered for successful results. #SharePoint
if you are looking for SharePoint new/ongoing development/maintenance where we can assist you. Please reach to us for getting experts assistance. Share your feedbacks on email: Neha.rai@adapt-india.com.
iStart - Sharepoint: Getting to the pointHayden McCall
Information overload. It defines the age we live in. Distraction,
clutter, and search angst are daily productivity killers causing
headaches and wasting hours.
Believe the disciples, and Microsoft’s SharePoint is on the
cusp of greatness, bringing order to clutter, collaboration to
fragmentation and timeliness to information and decision
making. But listen to the unconverted and it’s badly designed,
slow and another marketing snow job holding together the
Microsoft stack.
Your IT department probably already has the product, so iStart
canvassed a couple of experts on implementing SharePoint to
help you decide if it is a fit for wider use within your business…
This session will explore both the strategic and practical aspects of how the DBA role is impacted with the adoption of DevOps. Firsthand experiences from a DBA and the organizational learning gained during these transitions will be featured during the presentation.
Guiding a Successful SharePoint ImplementationRandy Williams
August 25 session
SharePoint is transforming the way organizations are connecting their people, business processes, and enterprise-wide information. In this exclusive two-part series on 23 & 25 August, led by SharePoint MVP Randy Williams, IT managers and SharePoint users will walk away with the blueprint they need to ensure they can successfully deploy SharePoint to meet their specific business needs.
In this session, learn the best practices and common pitfalls innate in implementing SharePoint in order to ensure your SharePoint service offering is right on the mark, the first time.
Is SharePoint working for you, or are you working for SharePoint..?
Why do many end users cringe when they hear the word 'SharePoint'? It's not because SharePoint is a bad platform (quite the contrary actually), it's because of their past experiences with SharePoint.
This webinar explored how you can make your users fall in Love with SharePoint and drive end user adoption in your organization!
Don't Just Migrate: Transform Your SharePoint Environment - DevConnections Or...Christian Buckley
SharePoint migration is as much about taking the opportunity to reorganize as it is about upgrading the platform and software. This presentation outlines some best practices for transforming your SharePoint.
How to go about your SAP Integration 2019, SAP PI, and cloudDaniel Graversen
Integration is a hot topic in all organizations. If you are an SAP customer the complexity of the integration is even higher.
In this rapport, I'm sharing the best ideas I have for how to make integration work in an SAP Landscape.
It covers topic like SAP PI/PO Migration, support. How to look at the SAP Cloud Integration (CPI) offerings.
3. SharePoint without purpose is pointless.
You are not actually installing SharePoint, you are
creating a system to do something functional and
SharePoint is the medium in which to achieve that goal.
The word SharePoint is generally banned during
Requirements Gathering workshops and Stakeholder
meetings and remember the client has all the answers,
they just do not realise it at the time.
4. Why are we changing the existing systems
Can SharePoint actually deliver the proposed solution
OOTB
Developing the additional features, do we really have
the skills on board
Development is generally a journey into the
unknown, how long it will it really take
GAP Analysis and what is really missing
Don’t talk about great looking sites, talk about really
functional Sites
5. We now have the choice between Cloud and On-
Premises but whatever the choice, licensing costs and
your existing IT and support infrastructure will be a
major influence on deciding the new Systems and
which Office 365 Plan to purchase.
On-Premises Requires
Servers
Client Access Licence
Application Software
Data Storage
Redundancy
Backup
Staging Farms
Development and Sandpit
Office 365 Includes
5 licences for Office Applications
SharePoint Enterprise
Office 365
Exchange
Lync
Access to Yammer (Requires Additional
Licence)
Federated Services
Disk Storage
6. Which or your sponsors are decision makers, find out
who you are dealing with and try to understand
what they expect from the project, why are they in
this role and how can you get the best out of them.
Find out from the Audience the role that best fits,
Decision Makers (Financial / Functional), Project
Managers, Team Sponsors, Developers, Product
Support, Application Support, Architecture, training
and documentation and discuss their input in a
SharePoint project.
7. Understand the Methodology in which the
Client team member is communicating and
how familiar are they with the process.
Prince (Projects in Controlled environments)
ITIL (Information Technology Infrastructure
Library)
Agile Unified Process (AUP); Dynamic Systems
Development Method (DSDM)
TOGAF The Open Group Architecture Framework
ISO (International Organization for Standardization)
8.
9.
10.
11.
12.
13. Information Architecture, one of the first words I
learnt at the beginning of my SharePoint journey.
Information Architecture will translate into Content
Types which are the building blocks for grouping
columns which are used in Libraries and Lists.
In reality you never create a column at the list or
library level you simply configure a content type and
add it to the List or Library
14. You can have a functional Layer (Getting it to
work) and the Business layer (the control
implied) where governance must be a part of
the requirements gathering and integrated into
the design.
Security
Auditing
Reliability
Usability
Supportability
15. An individual artefact cannot be described as
anything in particular but encapsulates everything as
the individual parts of your architectural design.
16. Pillar 1 - Corporate Strategy
Pillar 2 - Change Management Process
Pillar 3 - Back Office Administration
Pillar 4 - Training
Pillar 5 - Clear Ownership
Pillar 6 - Technical Development Process
Pillar 7 – Ongoing Maintenance Tasks
http://ezinearticles.com/?Seven-Pillars-of-
SharePoint&id=4672281
17. Once the Sites have been built the need for
reporting arises and the client has most likely
seen the promotional material outlining the
great reports that SharePoint provides but this
cannot be done on the fly.
Business Intelligence is a major topic which
baffles most IT technicians and requires the
enterprise version before you even start.
Reporting must be a part of your requirements
gathering process.
18. Installing SharePoint is a complex process and
you must be able to document and replay this
procedure exactly, you will also add servers
and change the topology as your Farm grows.
Two Codeplex tools which I use extensively
are AutoSPInstaller (Brian Lalancette /
Andrew Woodward) and
AutoSPInstallerGUI (Ivan Josipovic)
19. A SharePoint project will never close, it
just keeps going on and on which makes
sense, so remember you have started the
SharePoint Journey and at some point
you must Close the initial project and
move to a Change Management Process.
Why is this important?