O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
SharePoint project: DOs and DON’Ts
Natallia Makarevich, Lead Software Engineer
Raman Bakanovich, Business Analyst

Belarus...
Purpose?
Project success criteria:
 Skilled team
 Enough time
 Appropriate budget

Is it enough?

2
Customer and SharePoint
Are they the best match?

+

3
Customer and SharePoint
Reasons why SP projects fail:


Technology preferred by the customer



Technology already bough...
Customer and SharePoint
And why any projects fail:


Customer is not involved in the project



User adoption is skipped...
Speak as not SharePointee


Customer language is the only correct language
- Be on the same page with QA and BA
- Conside...
Learn OOB!


Customer – Know OOB SharePoint!



BA – Know OOB SharePoint!



QA – Know OOB SharePoint!



Dev – Know O...
If you're SharePoint
Developer


8

Knowing your domain is essential
- Sometimes BA may help. So read the requirements
- ...
Chimeras at SP project


3rd party components sometimes are
unreasonably added to the solution



The more chimeras, the...
Chimeras at SP project


Every technology has its applicability area



Chimeras can be created without 3rd party
soluti...
SharePoint Operations &
Maintenance


System administrators are our friends

Make sure you have one
in your team from the...
Do not test SharePoint!


QA should know SP – otherwise you’ll get
hundreds of bugs and will get drawn in disputes

Teach...
Do test SharePoint!


Quality assurance should be maintained on high
level anyway



Custom functionality often breaks O...
Follow SharePoint style


SharePoint as platform has its limitations, rules and
principles



BA, QA and DEV should be a...
SharePoint projects are
not special enough...


Plan architecture



Choose and follow a methodology



Maintain docume...
If you're SharePoint Project
Manager


Common PM practices are applicable



Project (as well as Sprint scope) should be...
Staff team with the right
people


SharePoint is technology



More .NET specialists won’t solve the problem quickly


...
If you're SharePoint
Architect

18

- Project timeframes may affect solution
architecture. Be prepared

- Estimate impleme...
SharePoint architecture...


Simple is the best!
- Follow Guidelines
- Make components reusable
- Make components less in...
If you're SharePoint
Business Analyst


They should become a SP expert



They should like SP



They should be trained...
If you're SharePoint
Business Analyst


They shouldn’t



provide poor requirements



miss requirements





commit...
Q&A – What do you think..
 ..about BA at SharePoint project?
 ..about QA?
 ..about PM?

22
Próximos SlideShares
Carregando em…5
×

SharePoint project: DOs and DON'Ts

847 visualizações

Publicada em

SharePoint User Group Belarus.

Publicada em: Tecnologia, Negócios
  • Entre para ver os comentários

SharePoint project: DOs and DON'Ts

  1. 1. SharePoint project: DOs and DON’Ts Natallia Makarevich, Lead Software Engineer Raman Bakanovich, Business Analyst Belarus SharePoint User Group November 2013
  2. 2. Purpose? Project success criteria:  Skilled team  Enough time  Appropriate budget Is it enough? 2
  3. 3. Customer and SharePoint Are they the best match? + 3
  4. 4. Customer and SharePoint Reasons why SP projects fail:  Technology preferred by the customer  Technology already bought by the customer  End-users’ religion is against SharePoint  SharePoint can’t solve customer’s problem 4
  5. 5. Customer and SharePoint And why any projects fail:  Customer is not involved in the project  User adoption is skipped  Incorrect or incomplete requirements are gathered  Low feedback from customer  Wrong deadlines  Technical debt is huge  And many many more.. 5
  6. 6. Speak as not SharePointee  Customer language is the only correct language - Be on the same page with QA and BA - Consider pros and cons of each solution: explain what is possible and what is not desired. 6
  7. 7. Learn OOB!  Customer – Know OOB SharePoint!  BA – Know OOB SharePoint!  QA – Know OOB SharePoint!  Dev – Know OOB SharePoint! Intensive communication and training are a must! 7
  8. 8. If you're SharePoint Developer  8 Knowing your domain is essential - Sometimes BA may help. So read the requirements - Keep learning! - Try different SP features - Create Accelerators, be rational
  9. 9. Chimeras at SP project  3rd party components sometimes are unreasonably added to the solution  The more chimeras, the more efforts to support - Conduct solution evaluation - Conduct impact analysis 9
  10. 10. Chimeras at SP project  Every technology has its applicability area  Chimeras can be created without 3rd party solutions When choosing a technology think about its purpose 10
  11. 11. SharePoint Operations & Maintenance  System administrators are our friends Make sure you have one in your team from the beginning of the project 11
  12. 12. Do not test SharePoint!  QA should know SP – otherwise you’ll get hundreds of bugs and will get drawn in disputes Teach your QA! 12
  13. 13. Do test SharePoint!  Quality assurance should be maintained on high level anyway  Custom functionality often breaks OOB features  QA will help you to identify missed requirements 13
  14. 14. Follow SharePoint style  SharePoint as platform has its limitations, rules and principles  BA, QA and DEV should be aware of them 14
  15. 15. SharePoint projects are not special enough...  Plan architecture  Choose and follow a methodology  Maintain documentation 15
  16. 16. If you're SharePoint Project Manager  Common PM practices are applicable  Project (as well as Sprint scope) should be managed to avoid stress within the team  Team with the right skills is important  Knowing SP is an advantage 16
  17. 17. Staff team with the right people  SharePoint is technology  More .NET specialists won’t solve the problem quickly  One should understand “technological background” - Document technical peculiarities - Communicate and explain! 17
  18. 18. If you're SharePoint Architect 18 - Project timeframes may affect solution architecture. Be prepared - Estimate implementing OOB featured carefully - Maintain proper environment for your team - Patterns are not a silver bullet. Be critical
  19. 19. SharePoint architecture...  Simple is the best! - Follow Guidelines - Make components reusable - Make components less interconnected - Maintain Knowledge Base! 19
  20. 20. If you're SharePoint Business Analyst  They should become a SP expert  They should like SP  They should be trained  They should document the requirements whatever methodology is used  They should be critical to customer’s wishes 20
  21. 21. If you're SharePoint Business Analyst  They shouldn’t   provide poor requirements  miss requirements   commit under deadlines without the team’s approval miss stakeholders You should be aware of Gold platting - Teach your BA - Ask questions as early as possible - Get feedback from BA as early as possible 21
  22. 22. Q&A – What do you think..  ..about BA at SharePoint project?  ..about QA?  ..about PM? 22

×