44
Agile SharePoint Development with Scrum DEV338 Andrew Woodward, MOSS MVP
| Date post: | 20-Aug-2015 |
| Category: |
Technology |
| Upload: | andrew-woodward |
| View: | 13,042 times |
| Download: | 1 times |
Agile SharePoint Development with Scrum
DEV338
Andrew Woodward, MOSS MVP
Andrew Woodward, MVP Principal Consultant 21apps Email [email protected] Twitter @AndrewWoody Blog www.andrewwoody.com/blog Agile developer, recent white paper:
Unit Testing SharePoint – Getting into the Object Model
Agenda
Introduction to Scrum Being Agile with SharePoint
Iterative Development Expect Change Upgrades Environments
Product Backlog
Burndown Chart
Sprint
Product
Product Backlog
Roles
Product Owner
Release Planning
Release 1
Release 2
Release 3
Sprint
----5----10----15----20----25----30
Estimating
Release 15 8 3 2 8 13
8 21 5 2 5 8
HoursStory
Points
Bananas
Days
Priority
Release 11 2 3 4 5 6
7 8 9 10 11 12
Sprints
Release 1
Potentially Shippable
What is done?
Sprint
Burndown Chart
Work to do
Sprint duration in days
Burndown Chart
Work to do
Sprint duration in days
Velocity
Release Planning
Work to do
Go Live Date
Required Velocity
Release Planning
Work to do
Release Planning
Work to do
Move Go Live Date
Release Planning
Work to do
Reduce features
Burndown Chart
Work to do
Early visibility
Daily Scrum
What I did yesterday?What I’m
doing today
Any problems I
have.
Scrum Master
Product Backlog
Bugs
Bugs – Defect Backlog
Create Defect Log Plan to do a couple
of defect sprints
Bugs - Fixed in Sprint
Directly related to task fix in Sprint
Being Agile with SharePoint
Iterative Development
Sprint Potentially Shippable Face tough challenges early and often Ability to change every Sprint
Continuous Builds and QA/TestingContinuous Builds and QA/Testing
Proving / StagingProving / Staging
ProductionProduction
Change
Expect Change Design for change
– Features and Feature Stapling over Site Templates
Tool Up– Upgrade helper utilities
Upgrade
SharePoint is a long term proposition More complex than traditional ASP.Net
Deal with early in manageable pieces Attend DEV372 with Robert Bogue
Environments
Developer Automate refresh / consistent
Continuous / QA / Demo Daily validation and Testing Continuous customer access
Staging Mirror Live, prove upgrades
Production
Best Practice – Why?
Expect Change Face tough challenges early Know what is done Visibility early and always
Best Practice – When?
You have management buy in You have customer buy in You understand Why Your team are committed Start small
Inspect and adapt
Best Practice – When its not?
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 don’t want to
Question?
Thank you for attending!
Please be sure to fill out your session evaluation!
Thank you for attending!
Post conference DVD with all slide decks
Sponsored bySponsored by
