This document discusses managing SharePoint projects using Agile and Team Foundation Server (TFS). It introduces Agile project management processes like Scrum and compares them to traditional waterfall processes. It describes setting up process templates in TFS, including the Agile and Scrum templates. It then covers various Agile concepts like product backlogs, sprints, stand-up meetings, and retrospectives and how they relate to planning and executing SharePoint projects in TFS.
Htf2014 managing share point projects with agile and tfs andy
1. Managing SharePoint
Projects with Agile
and TFS
Andy Boyet, CISSP
SharePoint Architect @ Sparkhound
andy.boyet@Sparkhound.com
Twitter: @andrewboyet
LinkedIn: https://www.linkedin.com/in/andyboyet
0
2. Introduction
Goal: Empower each one of you to manage
SharePoint and other projects in TFS using Agile
1
• Choosing a process
• Planning
• Execution
• Review
5. Process Templates
TFS ships with three process templates:
• Agile
• CMMI
• Scrum
One shot, choose carefully
4
6. Process Templates Components
• Work Item Types
• Classifications and Mappings
• Version Control
• Builds
• Security
5
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
6
9. Roles in Agile
8
• Product Owner
• ScrumMaster
• Team Member
10. Planning
9
Agile 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
10
12. Capacity Planning
• Time off
• Non Sprint related activities
11
– 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.
12
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
13
15. Iterations aka Sprints
14
Characteristics of Sprints
• Fixed period of time
• Usually 2 weeks
• Primary container for work in Agile
• Contains User stories, tasks, and bugs
16. Areas
Area: Name for a related group of features
15
Examples:
– Social Integration
– Information Architecture
– Infrastructure
– System Integration
– Dashboards
– Customization
17. Features
Characteristics 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
Example
Display order totals on product pages
Display product manager on product pages
16
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
Examples
As a Product Manager I would like to have one site for
all product information
As 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
17
19. Daily Stand Up
3 questions to answer:
• What did you do yesterday?
• What are you doing today?
• What is blocking you from progress?
18
Tasks to accomplish
• “Burn down” hours
• Update tasks
20. Retrospective
Questions to ask:
• What went well?
• What didn’t go well?
• What should we start doing?
• What should we stop doing?
19
Takeaway:
Start – Stop – Continue
21. SharePoint and Agile
• SharePoint Project Types
20
– New Farm
– Development
– Migration
– Integration
– Consolidation
– Upgrade
22. Project Relationships
• Team Project Collection/SharePoint Site Collection
• Team Projects/SharePoint Site
21
23. Final Thought
Sprints, 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!
22
Mention the goal to empower each member of the audience to manage SharePoint and other projects in TFS using Agile
Brief explanation of all steps
Has anyone been on a project where the requirements changed?
Specific reasons or personal examples
Sustainability examples: Past performance isn’t the best indicator, Stock market, Burnout, personnel changes, technology changes, no two projects are alike
Flexible: Use it at home with your kids
Scrum.org, Agile Alliance
The main difference is how bugs are managed
Product Owner: The product owner is a role in scrum development of the person who represents the business or user community.
ScrumMaster role: A scrum master is the facilitator for a product development team that uses scrum, a rugby analogy for a development methodology that allows a team to self-organize and make changes quickly. The scrum master manages the process for how information is exchanged.
No direct authority, Influence oriented,
Team Member:
Benefits: Allows for constant prioritization of requirements. Keeps the nice to haves in check.
Taken from Scrum Alliance.org
Not all slots are necessary.
1-2 is goal oriented, what user stories are we going to accomplish? Bring extra user stories
Think of this as the same broad areas that SharePoint covers.
See more at: http://www.agilemodeling.com/artifacts/feature.htm#sthash.zrllb8Fn.dpuf