Being agile with SharePoint

Uploaded on

How can you remain agile while adopting SharePoint technologies? Even though the platform provides incredible value out of the box for businesses, many still rely on custom development to complement …

How can you remain agile while adopting SharePoint technologies? Even though the platform provides incredible value out of the box for businesses, many still rely on custom development to complement the built-in features. The path to successful SharePoint development is filled with traps, and typical projects can stretch on for months without any value being provided to the stakeholders.

Don't this steer you towards a monolithic, linear development process. Despite these issues, you can embrace agile methodologies and gain a competitive advantage by decreasing your turnaround time in implementing new and changing requirements. With techniques such as Scrum and XP, your clients become more involved in the project, the transfer of knowledge (a particular important point in SharePoint governance) happens seamlessly and, most importantly, your client see results they want fast.

Sebastien will share with you the lessons learned from applying agile methods to a mid-scale SharePoint portal project. He will present what tools enable faster development, unit testing, continuous integration and deployment, in a SharePoint context.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • RED / GREEN / REFACTORFirst thing to do is to write new testsNext, we’re running the testsFix those who are failingRefactor


  • 1. Being Agile with SharePoint
    Sébastien Leduc
    Vice-President, GSoft Group
  • 2. 2
    GSoft Group & Me
    GSoft Group
    Based in Montreal
    Agile software development and consulting firm
    Expertise in Microsoft .NET and SharePoint technologies
    Vice-President of GSoft Group
    Working with SharePoint and Microsoft Technologies since 2003
    I’m a SharePoint trainer
    Information architecture planning
    SharePoint governance plan
    Development team setup
    Product owner of sharegate
  • 3. 3
    Being Agile with SharePoint
    Business Case
    How we estimate the project
    Introduction to Scrum
    What’s a sprint
    Sprint planning
    Sprint review
    Sprint retrospective
    eXtreme Programming (XP)
    Unit testing
    Iterative development
    Agile SharePoint development
    Pain points
  • 4. 4
    Being Agile with SharePoint
    Lack of customer understanding
    New technology
    Peoples knowledge (development team and client)
    Changing requirements
    Achieve a lot using Out of the Box
    Platform allows rapid deployment
    Platform allows you to deploy in modular pieces
    Use your solution as soon as possible
  • 5. 5
    Business Case
    Fédération des médecinsomnipraticiens du Québec
    CMS Website using Windows SharePoint Service 3.0
    320 pages
    14 associations
    8000 members
    200 000 visits / month
    Estimated time : 6 month
    1 Product Owner
    1 Scrum master
    3 GSoft developers
    1 FMOQ developer
    1 FMOQ QA
    1 webmaster
  • 6. 6
    Business Case –
    Fédération des médecinsomnipraticiens du Québec
  • 7. 7
    We break down the specifications into user story
    End user : Member of the FMOQ that have access to modify the website content
    Member : Member of the FMOQ website
  • 8. 8
    Sprint 0
    Pass through the checklist
    Build the first security grid
    Defining the “Done Done”
  • 9. 9
    With a story
    With a sprint
  • 10. 10
    What’s the Scrumprocess?
    Product backlog
    Sprint planning
    Daily Scrum
    Sprint review meeting
  • 11. 11
    Sprint planning
    Product owner describes the highest priority features
    Define a sprint goal
    Define the conditions of success
  • 12. 12
    FMOQ – Sprint 1 – Sprint planning
    It was really important for the FMOQ to see the president’s blog
    Sprint goal : post on a blog and write a comment on it
  • 13. 13
    FMOQ – Sprint 1 – Sprint review
    How does it work?
    Success or not?
    Live demo!
  • 14. 14
    FMOQ – Sprint 1 – Sprint retrospective
    What went well during the sprint?
    What went wrong during the sprint?
    Define an action plan
    There should be a lot of interaction during the retro
    Example of a retrospective activity :
  • 15. 15
    FMOQ – Sprint 2 – Sprint planning
    The FMOQ wanted to be able to recognized their members on the web site
    Sprint goal : Login and manage online profile
  • 16. 16
    FMOQ – Sprint 2 – Sprint review
    Success or not?
    Live demo!
  • 17. 17
    FMOQ – Sprint 3
    The next step was to put the content management system in place with the approval workflow
  • 18. 18
    FMOQ – Sprint 4
    We finally have a design and the navigation is working!
  • 19. 19
    FMOQ – Sprint 5
    Access to external site (authentication)
  • 20. 20
    FMOQ – Sprint 6
    Site content types
  • 21. 21
    FMOQ – Sprint 7
    Union activities calendar
    Admin dashboard
  • 22. 22
    FMOQ – Sprint 8
  • 23. 23
    FMOQ – Sprint 9
    Advanced search
  • 24. 24
    FMOQ – Sprint
  • 25. 25
    FMOQ – Sprint 7 – Unit testing
    Sprint 7
    Change 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. 26
  • 27. Red, Green, Refactor
  • 28. 28
    Iterativedevelopment in SharePoint
    Advantages of a iterative development in SharePoint
    Potentially Shippable pieces of codes
    Face tough challenge early and often
    Early visibility
    Ability to change every sprint
    Inspect and adapt to customers needs
  • 29. 29
    Agile SharePoint Development
    When is it a good idea?
    You have management and customer buy in
    You understand that Agile won’t magically make your project work
    Your team is committed
    Start small
    Inspect and adapt
    When is it a bad idea?
    Don’t start on high risk projects
    Don’t start without management buy in
    Don’t start without customer engagement
    Although agile can help rescue failing projects
    Don’t start if the team doesn’t want to
  • 30. 30
    Pain points
    Unit testing - Impossible
    Automating Integration and acceptance testing
    Continuous build and automatic deployment
    Used as an excuse not to be Agile
  • 31. 31
    Agile SharePoint development and unit testing
    Introduction to scrum
    Unit testing with TypeMock
    SharePoint development with Unit testing
  • 32. 32