SharePoint project planning

3,122 views

Published on

Slide deck from SPTechCon Boston

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,122
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SharePoint project planning

  1. 1. Planning your SharePoint project Joshua Haebets
  2. 2.  Melbourne, Australia  @jhaebets on Twitter  www.linkedin.com/in/jhaebets  Blog - www.robotsdottxt.com
  3. 3. SharePoint is different SharePoint needs to be built the same way it is going to be used, collaboratively
  4. 4. Your organisation’s requirements are unique v’s
  5. 5. You cant insert CD and click next…
  6. 6. So what steps do you need to take? Define Implement Educate
  7. 7. to determine or fix the boundaries to make clear the outline from dictionary.com
  8. 8. Why are you implementing SharePoint?
  9. 9. It’s a big pie
  10. 10. The first rule of problem solving, make sure you are solving the right one
  11. 11. What does your organisation really need It is very difficult for those inside a box to think outside of it Management f-laws
  12. 12. What does success look like?
  13. 13. Who do you want as stakeholders? What do they need to know? Who are your stakeholders?
  14. 14. to put into effect according to or by means of a definite plan or procedure. from dictionary.com
  15. 15. Are you heading straight to nirvana? Take small steps, there is no harm in delivering in phases
  16. 16. Functionality You have the requirements, now use them as a checkpoint during build
  17. 17. Who is on the build team Admin Developer Content writer Project Manager Business Analyst
  18. 18. Technical Farm InfoPath Solutions Features Content Database WSP Site Collections Web Web Applications MySite
  19. 19. What will the Farm look like
  20. 20. What will the Farm look like
  21. 21. Will it be big enough If you have poor performance you will have trouble getting people on board Load test before the big day
  22. 22. Governance…..who owns what
  23. 23. Simple governance model Consumer works with the system Administrator Keeps it running, publishes new content. Does development work Owner Is the go to person for functionality requests. They make the final call
  24. 24. to develop the faculties and powers of (a person) by teaching, instruction, or schooling. from dictionary.com
  25. 25. Change
  26. 26. Things are going to be different
  27. 27. Communication Before During After
  28. 28. Let everyone know
  29. 29. User engagement and training
  30. 30. Transition to support
  31. 31. Where do we go for help?
  32. 32. So you want all the pie Cut it up into bite size pieces
  33. 33. Repeat the process
  34. 34. Questions
  35. 35. Contact Contact Joshua.haebets@evolve-is.com.au Slideshare http://www.slideshare.net/jhaebets www.linkedin.com/in/jhaebets

×