Agile Content Migration for SharePoint
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Agile Content Migration for SharePoint

on

  • 1,607 views

Slides by Mark Hopkins, Tesoro. Presented to the San Antonio SharePoint User Group March 22nd, 2011

Slides by Mark Hopkins, Tesoro. Presented to the San Antonio SharePoint User Group March 22nd, 2011

Statistics

Views

Total Views
1,607
Views on SlideShare
1,607
Embed Views
0

Actions

Likes
0
Downloads
25
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Content Migration for SharePoint Presentation Transcript

  • 1. 0
    Sprinting to SharePoint
    An Agile method
    for SharePoint projects
    Mark Hopkins
  • 2. Scrum
    What is scrum?
    How does it work?
    Is it for my SharePoint projects?
    1
  • 3. What is scrum?
    • Grew out of Agile software development
    • 4. Solves especially complex problems
    • 5. Empowers small teams to manage their own fate
    • 6. Occurs in a 30-day ‘sprint’
    • 7. Delivers ‘shippable’ product at the end of the sprint
    • 8. Designates a scrum master to maintainscrum rules & protect the team
    2
  • 9. Pigs vs. Chickens
    Roles:
    • Product Owner
    • 10. Scrum Master
    • 11. Project Team
    3
  • 12. How does it work?
    4
    Product Backlog
    Sprint Backlog
    Product!
  • 13. Product Backlog
    5
  • 14. How does it work?
    6
    Product Backlog
    Sprint Backlog
    Product!
  • 15. Sprint Backlog
    7
  • 16. How does it work?
    8
    Product Backlog
    Sprint Backlog
    Product!
  • 17. 9
    Product Backlog
    Sprint Backlog
    Product!
  • 18. Is it for me?
    • Clear end goal (product)
    • 19. Ongoing requirements
    • 20. Complex or innovative solution
    • 21. Small, empowered team (4-7 people)
    • 22. Dedicated time available
    • 23. Trusting product owner
    • 24. Trusting manager
    10