Being agile with SharePoint
- 1. Being Agile with SharePointSébastien LeducVice-President, GSoft Groupsebastien.leduc@gsoft-group.com
- 2. 2GSoft Group & MeGSoft GroupBased in MontrealAgile software development and consulting firmExpertise in Microsoft .NET and SharePoint technologiesMeVice-President of GSoft GroupWorking with SharePoint and Microsoft Technologies since 2003I’m a SharePoint trainerConsultingInformation architecture planningSharePoint governance planDevelopment team setupProduct owner of sharegate
- 3. 3IntroductionBeing Agile with SharePointBusiness CaseHow we estimate the projectIntroduction to ScrumWhat’s a sprintSprint planningSprint reviewSprint retrospectiveeXtreme Programming (XP)Unit testingIterative developmentAgile SharePoint developmentPain points
- 4. 4Being Agile with SharePointLack of customer understandingNew technologyPeoples knowledge (development team and client)Changing requirementsAchieve a lot using Out of the BoxPlatform allows rapid deploymentPlatform allows you to deploy in modular piecesUse your solution as soon as possible
- 5. 5Business CaseFédération des médecinsomnipraticiens du QuébecProject CMS Website using Windows SharePoint Service 3.0320 pages14 associations8000 members200 000 visits / monthEstimated time : 6 monthTeam1 Product Owner1 Scrum master3 GSoft developers1 FMOQ developer1 FMOQ QA1 webmaster
- 6. 6Business Case – www.fmoq.orgFédération des médecinsomnipraticiens du Québec
- 7. 7SpecificationsWe break down the specifications into user storyEnd user : Member of the FMOQ that have access to modify the website contentMember : Member of the FMOQ website
- 8. 8Sprint 0Pass through the checklistBuild the first security gridDefining the “Done Done”Checklist
- 9. 9DoneDonelistWith a storyWith a sprint
- 10. 10What’s the Scrumprocess?Product backlogSprint planningDaily ScrumSprint review meetingRetrospectivewww.mountaingoatsoftware.com
- 11. 11Sprint planningProduct owner describes the highest priority featuresDefine a sprint goalDefine the conditions of success
- 12. 12FMOQ – Sprint 1 – Sprint planningIt was really important for the FMOQ to see the president’s blogSprint goal : post on a blog and write a comment on it
- 13. 13FMOQ – Sprint 1 – Sprint reviewHow does it work?Success or not?Live demo!
- 14. 14FMOQ – Sprint 1 – Sprint retrospectiveWhat went well during the sprint?What went wrong during the sprint?Define an action planThere should be a lot of interaction during the retroExample of a retrospective activity :
- 15. 15FMOQ – Sprint 2 – Sprint planningThe FMOQ wanted to be able to recognized their members on the web siteSprint goal : Login and manage online profile
- 16. 16FMOQ – Sprint 2 – Sprint reviewSuccess or not?Live demo!
- 17. 17FMOQ – Sprint 3The next step was to put the content management system in place with the approval workflow
- 18. 18FMOQ – Sprint 4We finally have a design and the navigation is working!
- 19. 19FMOQ – Sprint 5Access to external site (authentication)Articles
- 20. 20FMOQ – Sprint 6Site content typesHierarchy
- 21. 21FMOQ – Sprint 7Union activities calendarAdmin dashboard
- 22. 22FMOQ – Sprint 8Security
- 23. 23FMOQ – Sprint 9Advanced search
- 24. 24FMOQ – Sprint
- 25. 25FMOQ – Sprint 7 – Unit testingSprint 7Change the authentication method to use an email Something need to be change but how can we make sure we don’t break anything? Answer : Unit Testing
- 26. 26TypeMock
- 27. Red, Green, Refactor27REDGREEN
- 28. 28Iterativedevelopment in SharePointAdvantages of a iterative development in SharePointPotentially Shippable pieces of codesFace tough challenge early and oftenEarly visibilityAbility to change every sprintInspect and adapt to customers needs
- 29. 29Agile SharePoint DevelopmentWhen is it a good idea?You have management and customer buy inYou understand that Agile won’t magically make your project workYour team is committedStart smallInspect and adaptWhen is it a bad idea?Don’t start on high risk projectsDon’t start without management buy inDon’t start without customer engagementAlthough agile can help rescue failing projectsDon’t start if the team doesn’t want to
- 30. 30Pain pointsUnit testing - ImpossibleAutomating Integration and acceptance testingContinuous build and automatic deploymentDeploymentUsed as an excuse not to be Agile
- 31. 31ReferencesAgile SharePoint development and unit testinghttp://www.21apps.com/Introduction to scrumhttp://www.mountaingoatsoftware.com/topics/scrumUnit testing with TypeMockhttp://www.typemock.comSharePoint development with Unit testinghttp://www.sharepointdevwiki.com
Editor's Notes
- #28: RED / GREEN / REFACTORFirst thing to do is to write new testsNext, we’re running the testsFix those who are failingRefactor