1

Managing SharePoint Projects with Agile and TFS

Andy Boyet, CISSPSharePoint Architect @ Sparkhound

andy.boyet@Sparkhound.comTwitter: @andrewboyet

LinkedIn: https://www.linkedin.com/in/andyboyet

2

IntroductionGoal: Empower each one of you to manage SharePoint and other projects in TFS using Agile

• Choosing a process• Planning• Execution• Review

3

Processes• Waterfall• Capability Maturity Model Integration CMMI• StageGate• Critical Chain• Scrum• Agile

4

No Process

5

Process TemplatesTFS ships with three process templates:• Agile• CMMI• Scrum

One shot, choose carefully

6

Process Templates Components• Work Item Types• Classifications and Mappings• Version Control• Builds• Security

7

Why Agile?• Agile methods assume that the projects they are

used for do not actually have a good definition of the requirements at the beginning of the project

• More predictable cadence• Tight feedback loops• Deliver more value• More sustainable• Flexible

8

Agile vs ScrumScrum

Agile

9

Roles in Agile• Product Owner• ScrumMaster• Team Member

10

PlanningAgile Planning Tools

• Product Backlog• Sprint Planning Session• Velocity• Work is chosen, not assigned

11

Product Backlog• Working set of requirements• Constantly prioritized by ScrumMaster with input

of Product Owner• Taken from the top

12

Capacity Planning

• Time off• Non Sprint related activities– Performance Reviews– Other Projects– Training– Support

• Max per person per day is 6 hours

13

Sprint Planning Session• ScrumMaster comes with top user stories• Team estimates effort using story points• Team organizes related work• Team chooses the stories to take on during the

sprint.

14

Sample Sprint Planning Session• 12:15–1:00 Determine upcoming time-away and

establish Team Capacity for the planned sprint • 1:00–2:00 Visioning (product owner presents:

Review OBT, discover Sprint Goals, discover Roles. Product owner presents each story in priority order)

• 2:00–4:00 Team reviews stories, creates estimated tasks for each

• 4:00–5:00 Team commits to chunk of stories to product owner, ready to start Daily Scrum tomorrow

15

Iterations aka SprintsCharacteristics of Sprints

• Fixed period of time• Usually 2 weeks• Primary container for work in Agile• Contains User stories, tasks, and bugs

16

AreasArea: Name for a related group of features

Examples:– Social Integration– Information Architecture– Infrastructure– System Integration– Dashboards– Customization

17

FeaturesCharacteristics of Features

• A feature is a small, client-valued function expressed in the form <action><result><object>

• Usually can be implemented within a few hours

ExampleDisplay order totals on product pagesDisplay product manager on product pages

18

User Stories• Basic building block of Agile• As a <<ROLE>> I would like to <<OBJECTIVE>> so that

<<BUSINESS VALUE>>• Story Points used for estimating

ExamplesAs a Product Manager I would like to have one site for all product informationAs an Intranet User, I would like to have a link have one site for all physical location information so that I will know how to prepare for business travel

19

Daily Stand Up3 questions to answer:• What did you do yesterday?• What are you doing today?• What is blocking you from progress?

Tasks to accomplish• “Burn down” hours• Update tasks

20

RetrospectiveQuestions to ask:• What went well?• What didn’t go well?• What should we start doing?• What should we stop doing?

Takeaway:Start – Stop – Continue

21

SharePoint and Agile• SharePoint Project Types– New Farm– Development– Migration– Integration– Consolidation– Upgrade

22

Project Relationships

• Team Project Collection/SharePoint Site Collection• Team Projects/SharePoint Site

23

Final ThoughtSprints, Iterations, Areas, Features, Product Backlogs, Search, Content Management, Social Integration, Retrospectives, Standups, Burndown, User Stories, Tasks, Bugs, Story Points, Capacity Planning, Web Pages, Lists, Libraries,

UGH!

24

What’s it all about?

Teamwork

25

Thanks to all our Sponsors!