Provide an introduction to Agile development using Scrum and discuss how the iterative approach to development helps the customer to get the solution they want. Look at how this approach works when applied to SharePoint projects, how it helps leverage more of the core platform and focuses effort on the biggest value areas. We will look at the challenges this brings to your development team by doing early integration, dealing with upgrades and changes and understand how addressing the hard things early is the right approach. We will also discuss how Scrum gives visibility of the project and brings both good and bad news. How getting customer engagement is the primary challenge and how the flexible approach is often at odds with the way work is contracted.

1. Agile SharePoint Development with Scrum DEV338 Andrew Woodward, MOSS MVP

4. Product Backlog

5. Burndown Chart

6. Sprint

7. Product

8. Product Backlog

9. Roles

10. Product Owner

11. Release Planning Release 1 Release 2 Release 3

12. Sprint ----5----10----15----20----25----30

13. Estimating 5 8 3 2 8 13 8 21 5 2 5 8 Hours Story Points Bananas Days Release 1

14. Priority 1 2 3 4 5 6 7 8 9 10 11 12 Release 1

15. Sprints Release 1

16. Potentially Shippable What is done?

17. Sprint

18. Burndown Chart Work to do Sprint duration in days

19. Burndown Chart Work to do Sprint duration in days

20. Velocity

21. Release Planning Work to do Required Velocity Go Live Date

22. Release Planning Work to do

23. Release Planning Work to do Move Go Live Date

24. Release Planning Work to do Reduce features

25. Burndown Chart Work to do Early visibility

26. Daily Scrum What I did yesterday? What I’m doing today Any problems I have.

27. Scrum Master

28. Product Backlog

29. Bugs

32. Being Agile with SharePoint

34. Continuous Builds and QA/Testing Proving / Staging Production

41. Question?

42. Thank you for attending! Please be sure to fill out your session evaluation!