Scrum and Kanban are popular agile methodologies used with Team Foundation Server (TFS). TFS supports agile practices through features like version control, work item tracking, build automation, and reporting. It allows teams to manage their backlogs, track work items like user stories and bugs, and gain visibility into project progress and metrics.
An overview of the Agile Manifesto and the principles and practices that define Agile software development. A comparison of Agile Development methodologies and an organisational culture that supports them
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
Ik gebruik deze checklist zelf als Scrum coach. De mindmap bevat een samenvatting van alle waarden rondom Scrum.
Door op deze waarden te letten, naast het eenvoudig kijken naar de "mechanica" van Scrum, ontstaat er een veel betere Scrum implementatie. Zo wordt Scrum "naar de geest" toegepast.
An overview of the Agile Manifesto and the principles and practices that define Agile software development. A comparison of Agile Development methodologies and an organisational culture that supports them
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
Ik gebruik deze checklist zelf als Scrum coach. De mindmap bevat een samenvatting van alle waarden rondom Scrum.
Door op deze waarden te letten, naast het eenvoudig kijken naar de "mechanica" van Scrum, ontstaat er een veel betere Scrum implementatie. Zo wordt Scrum "naar de geest" toegepast.
High Quality Software Development with Agile and ScrumLemi Orhan Ergin
Module 1. Born to fail
- Why projects are failing
- Waterfall & traditional software development
Module 2. Agile
Module 3. Scrum
Module 4. Writing high quality software with Agile
- XP
- How Google Write Software
Module 5. Do's and dont's
- How Scrum might fail
- Myths and realities
Module 6. How to kick off Scrum
Discover 12 principles for Agile Development created by @liquidconcept.
Liquid Concept is a swiss interactive communications agency. We share the values of our international clients: quality, user-friendliness, clarity and attention to detail
There you can find about definition of agile model.Working of agile model.You can also find where to use agile model.Examples of agile model is also given here.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
What are the Tools & Techniques in Agile Project Management?Tuan Yang
Organizations, teams and even project management software are increasingly responding to a demand for more adaptive and evolutionary processes. In a fast-changing business world that needs to respond to rapid market and technology shifts, Agile delivers. Agile project management provides numerous benefits to organizations, project teams, and products.
Learn more about:
» Set up an Agile project.
» Assign roles and responsibilities.
» Create a prioritized list of requirements.
» Define increments and timeboxes.
» Manage a Solution Development Team or Teams.
» Use Agile techniques such as Feature Driven Development.
» Present the benefits of Agile approaches to Senior Management.
Implementing distributed agile framework with
Scrum, XP & Effective Tools usage Dev ops. C. Padma presented this presentation during India Agile week 2015 - Bangalore
Las metodologías ágiles no son sólo una nueva forma de entender la gestión de los proyectos, si no también un cambio en la propia Organización. ¿Puede SCRUM ayudar a la educación de nuestros hijos? ¿A organizar más eficientemente la Administración Pública? ¿Se pueden fabricar coches con SCRUM?
High Quality Software Development with Agile and ScrumLemi Orhan Ergin
Module 1. Born to fail
- Why projects are failing
- Waterfall & traditional software development
Module 2. Agile
Module 3. Scrum
Module 4. Writing high quality software with Agile
- XP
- How Google Write Software
Module 5. Do's and dont's
- How Scrum might fail
- Myths and realities
Module 6. How to kick off Scrum
Discover 12 principles for Agile Development created by @liquidconcept.
Liquid Concept is a swiss interactive communications agency. We share the values of our international clients: quality, user-friendliness, clarity and attention to detail
There you can find about definition of agile model.Working of agile model.You can also find where to use agile model.Examples of agile model is also given here.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
What are the Tools & Techniques in Agile Project Management?Tuan Yang
Organizations, teams and even project management software are increasingly responding to a demand for more adaptive and evolutionary processes. In a fast-changing business world that needs to respond to rapid market and technology shifts, Agile delivers. Agile project management provides numerous benefits to organizations, project teams, and products.
Learn more about:
» Set up an Agile project.
» Assign roles and responsibilities.
» Create a prioritized list of requirements.
» Define increments and timeboxes.
» Manage a Solution Development Team or Teams.
» Use Agile techniques such as Feature Driven Development.
» Present the benefits of Agile approaches to Senior Management.
Implementing distributed agile framework with
Scrum, XP & Effective Tools usage Dev ops. C. Padma presented this presentation during India Agile week 2015 - Bangalore
Las metodologías ágiles no son sólo una nueva forma de entender la gestión de los proyectos, si no también un cambio en la propia Organización. ¿Puede SCRUM ayudar a la educación de nuestros hijos? ¿A organizar más eficientemente la Administración Pública? ¿Se pueden fabricar coches con SCRUM?
2013 Enterprise Track, Getting GIS done using the Scrum Methodology Jonathan ...GIS in the Rockies
We live in a world where limited resources is a constant battle. One of the biggest struggles is how to get work done and make sure that it brings the most value possible to our customer. Managing GIS work through Scrum provides a way to do this. In this presentation, I will explain the concepts around the Agile methodology and how it could be applied not only in the IT world, but to any GIS work that needs to be done.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
Safalta Digital marketing institute in Noida, provide complete applications that encompass a huge range of virtual advertising and marketing additives, which includes search engine optimization, virtual communication advertising, pay-per-click on marketing, content material advertising, internet analytics, and greater. These university courses are designed for students who possess a comprehensive understanding of virtual marketing strategies and attributes.Safalta Digital Marketing Institute in Noida is a first choice for young individuals or students who are looking to start their careers in the field of digital advertising. The institute gives specialized courses designed and certification.
for beginners, providing thorough training in areas such as SEO, digital communication marketing, and PPC training in Noida. After finishing the program, students receive the certifications recognised by top different universitie, setting a strong foundation for a successful career in digital marketing.
Normal Labour/ Stages of Labour/ Mechanism of LabourWasim Ak
Normal labor is also termed spontaneous labor, defined as the natural physiological process through which the fetus, placenta, and membranes are expelled from the uterus through the birth canal at term (37 to 42 weeks
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
MATATAG CURRICULUM: ASSESSING THE READINESS OF ELEM. PUBLIC SCHOOL TEACHERS I...NelTorrente
In this research, it concludes that while the readiness of teachers in Caloocan City to implement the MATATAG Curriculum is generally positive, targeted efforts in professional development, resource distribution, support networks, and comprehensive preparation can address the existing gaps and ensure successful curriculum implementation.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
3. I HAVE A DREAM
• My project
o In Time
o Within Budget
o Meet Requirements
• Members in my team
o Creative & responsive
o Not exhausted and not leave team
cuong@microsoft.com
5. Typical developer
• Personal interest is more than team interest
• Warm up time is long
• Good at patching but bad at designing
(problem solving style)
• Wait for thing happens but not make thing
happen
cuong@microsoft.com
12. Scrum is an Agile framework
Scrum is an iterative, incremental
framework for project management and
agile software development.
Agile … is a group of software
development methodologies based on
iterative and incremental development…
cuong@microsoft.com
13. Agile
Analysis Design Develop Test Deploy
cuong@microsoft.com
14. Agile
Analysis
Design Test
Develop Deploy Analysis
Design Test
Develop Deploy Analysis
Design Test
Develop Deploy
!
?
?
!
cuong@microsoft.com
15. Principles of Agile #1
• Deliver valuable software early &
continuously
• Accommodate changes
• Collaborate with customer or customer
proxy
• Motivate individuals Self-organizing
teams Self tuning
cuong@microsoft.com
16. Principles of Agile #2
• Enforce effective & transparent
communication
• Measure of progress by working
software delivered. Highlight amount of
work not done
• Maintain a development speed
• Promote technical excellent and good
design
cuong@microsoft.com
17. DIFFERENCES
Plan Driven Scrum
• Hierarchy team • Self organizing team
• Lot of document • Deliver features
• Follow plan • Response to change
• Structure • Flexible
• Gantt Chart • Burn down chart
cuong@microsoft.com
18. Roles in Scrum
Scrum Master Scrum Team
Product Owner
Stakeholders &
Users
cuong@microsoft.com
19. Product Owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the
product (ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as
needed
• Accept or reject work results
cuong@microsoft.com
20. The Scrum Master
• Manage project
• Enforce Scrum values and practices
• Help team to focus on tasks
• Enable close cooperation across all roles and
functions
• Shield the team from external interferences
cuong@microsoft.com
21. The team
• Typically 5-9 people
• Cross-functional:
– Programmers, testers, user experience designers, etc.
• Teams are self-organizing
– Ideally, no titles but rarely a possibility
• Membership should change only between sprints
cuong@microsoft.com
26. Product vs Sprint Backlog
Product BackLog Sprint BackLog
Level of detail Less detailed Very detailed
Item User Story Task
Estimation Units Story Points Hours
Doc owner Product Owner Team
Revised Weekly Daily
Duration Project Sprint
Workbook Product Backlog Iteration Backlog
cuong@microsoft.com
28. User Story
• Independent
• Negotiable User Story <StoryPoint>
• Valuable
Task 1 Task 2 Task 3
• Estimatable
• Small
• Testable
As a <USER> I need to <ACTION> In order to <REASON>
cuong@microsoft.com
29. User Story
• User Story == Use Case
• MosCow: Must – Should – Could – Wouldn’t
• Write non-functional requirements as user
stories
• Estimate Story Point
http://stackoverflow.com/questions/1232281/what-are-
estimate-points-story-points-and-how-to-measure-them-
in-scrum
cuong@microsoft.com
30. Meetings in SCRUM
Meeting Purpose Duration Frequency
Sprint Determine what work to do in 2 hours per Once per
Planning the coming sprint. week sprint
Daily Allow team members to 15 minutes Daily
Scrum commit, collaborate, and
communicate risks.
Sprint Show the customer and other 2 hours per Once per
Review stakeholders the work that the week sprint
team accomplished in the
sprint, and receive feedback.
Retrospect Identify and implement ideas 3 hours Once per
ive for process improvement. sprint
cuong@microsoft.com
31. Daily Scrum
• Daily, 15 minutes, whole team
• What did you do yesterday ?
• What will you do today ?
• What are impediments?
No need minutes meeting
Need a tool to keep track
user story, task, bug…
cuong@microsoft.com
32. Sprint Task Board
User Stories Not Done In Progress Done Deferred
Do this Do this Do this
As a user I and and and
want this to that. that. that.
do that.
Do this
and
that.
As a user I Do this Do this
and and
want this to
that. that.
do that.
As a user I Do this Do this
and and
want this to that. that.
do that.
Do this
and
that.
cuong@microsoft.com
33. “Music Store” web site
• Team : 1 PM - 1 dev – 1 ux designer
• Mission: Develop “Music Store” site in 3
months.
• Every 2 weeks must show customer progress
• Team work 5 days a week, 8 hours per day
(Utilize rate 75% ~ 6 hours per day)
cuong@microsoft.com
34. Example Solution
• Each Sprint takes 2 weeks
• 4 months 8 Sprints
• Each sprint, a person burns 5*2*6=60 hours.
A team burns 60*3=180 hours
Idle hours will not be counted
Hours which used to complete task
will be counted as burnt hours
cuong@microsoft.com
36. Product backlog
Story Point
Priority Backlog item
Estimate
1 User can see list of category 3
User clicks on a category, list of product under category will
2 5
show
3 At front page, user sees 20 suggested item 3
4 Registered user can rate, commend a item 8
5 Administrator can send message to registered user 8
6 Administrator can create new item 30
7 ….
cuong@microsoft.com
37. The sprint goal
A short statement of what the work will be
focused on during the sprint
UX Prototyping
Design static prototype web site Database Design
XHTML, CSS validation CodeFirst EF 4 to generate data
jQuery interaction Generate sample data
Performance
Tune render speed at client
Restaurant List Tune server response
Show top 20 restaurants Configure memcached caching
Personalize data per user
List restaurant by A-Z, styles, …
cuong@microsoft.com
38. Burn Down Chart
180 hrs. Learning Curve
Work Hours Remaining
Team speeds up
0 hrs.
Time 1 Sprint = 2 weeks
cuong@microsoft.com
39. What happen?
180 hrs.
Bugs happen
Work Hours Remaining
Urgent task
0 hrs.
Time 1 Sprint = 2 weeks
cuong@microsoft.com
44. SubVersion, CVS, GIT are SCM only
Bug Tracking Deployment
Project Management
Quality Control Report
SCM: Source Code Management
cuong@microsoft.com
45. Much more than a SCM
Developer Database
Designer
Professional
Architect
Tester
Business Project
Analyst Team Foundation Server Manager
cuong@microsoft.com
46. What TFS can do
Team Foundation Server
Process Focused
Version Control
Process
Templates Work Item Tracking
Integrated
SharePoint Check-in Build Automation
Manage work
Customizable Check-in
Bugs, Tasks, Reporting
Policies Continuous
Requirements, Integration
Shelving Stories, Risks, Decision
etc. Scheduled Support
Very Extensible Ad Hoc Track Project
Progress
cuong@microsoft.com
48. Building blocks
Client Interface Version Control Build
Proxy Environment
Visual
MS Excel Command Line
Studio Version
Control Build
Proxy Process
Service
MS Project Team Explorer TFS SDK
Application Tier
SQL Reporting Services Windows SharePoint Services Web Services
SQL Server
Version Data
Work Items Team Build
Control Warehouse
Data Tier
cuong@microsoft.com
49. Deployment
Business User Dev Team (Local)
Dev Team (Remote)
Build Server
Win 2008 Server
SQL Server 2008
IIS 7.0
Version Control
Active Directory Proxy (Remote)
HTTP / S
TCP/IP
Team Foundation Server
cuong@microsoft.com
51. Consolidate backend DB
Data Tier
TFS AT HR
Applications
Clustered SQL
Server
Scale (a little), SQL Consolidation
cuong@microsoft.com
52. Bigger
Network Load
Balancing
HR
TFS AT
Applications
Team Project
N Finance
Collection
VIP L TFS AT
Applications
B
Company
TFS AT Web site
Another SQL
Server
Isolation, Reliability, Scale
cuong@microsoft.com
53. More Bigger
HR TFS Build
TFS AT Farm
Applications
N Finance
Applications TFS
L TFS AT
Proxies
B
Company
TFS AT Web site
Test Rig
SharePoint Data Virtual
Project
Farm Warehouse Machine
Server
Manager
cuong@microsoft.com
54. VERSION CONTROL
Team Foundation Server
Process Focused
Version Control
Process
Templates Work Item Tracking
Integrated
SharePoint Check-in Build Automation
Manage work
Customizable Check-in
Bugs, Tasks, Reporting
Policies Continuous
Requirements, Integration
Shelving Stories, Risks, Decision
etc. Scheduled Support
Very Extensible Ad Hoc Track Project
Progress
cuong@microsoft.com
55. Workspaces: local working copy
Map Server to Per User, Per
Local Workstation
Changes in
Also Used for
Workspace create
Builds
“Pending Changes”
cuong@microsoft.com
56. Changesets
• Logical container of data related to check-in
– File and branch information
– Links to work items
– Check-in notes
– Check in Policy
– Metadata (date-time, user)
– Atomic checkin
• Uniquely identified
• Trace & query easilly
cuong@microsoft.com
57. Other terms of TFS version control
• Integrated Check-in
• Check-in policies
• Shelve
• Label
• Branch / Merge
More at
http://www.slideshare.net/stevenl/team-
foundation-server-2010-version-control
cuong@microsoft.com
58. Check-in Policies
• Soft requirements for check-in
• Extensible
• Can be overridden
cuong@microsoft.com
59. Client Server vs Distributed SCM
• Clients push-pull master Exchanging patches
repository. (change-sets) from
• A client hold only a working peer to peer
copy of a project tree
• Changes by client commits the
master repository before they
propagate to other users
cuong@microsoft.com
60. Client Server vs. Distributed
• TFS, CVS, SVN, Perforce, Vault are client-
server SCM
• Git, Mercurial are distributed SCM
• Distributed SCM:
o No canonical, reference copy of the codebase
exists by default; only working copies
o Basic operations (c-in, c-out) are fast
o Each working copy acts as remote backup
o Suitable for Open Source development but not
commercial development
cuong@microsoft.com
62. Visual Studio TFS
Visual Studio 2005
Team Foundation
Server 2010
Visual Studio 2008
Visual Studio 2010
Team Foundation
Server 2008
cuong@microsoft.com
63. With VB, VC++ 6.0, VS2003
• Upgrade to Service Pack 6
• Install Team Foundation Server MSSCCI
Provider
cuong@microsoft.com
66. Think TFS as web service provider
• Include these namespace
– Microsoft.TeamFoundation.Proxy;
– Microsoft.TeamFoundation.Client;
– Microsoft.TeamFoundation.Server;
– Microsoft.TeamFoundation.WorkItemTracking.Client
• Windows Form app connects to TFS
http://blogs.microsoft.co.il/blogs/shair/archiv
e/tags/TFS+API/default.aspx?PageIndex=2
cuong@microsoft.com
67. With SharePoint Server
• Install on SharePoint Foundation 2010
• Install on SharePoint Server 2010: full
features
• Connect to MS Project Server 2010
cuong@microsoft.com
68. For Non-.NET Development
• Team Explorer Everywhere
– Eclipse plug-in for TFS
– Rich client (Java-based)
– Command-Line
cuong@microsoft.com
70. Team Foundation Server
Process
Version Control
Process
Templates Work Item Tracking
Integrated
SharePoint Check-in Build Automation
Manage work
Customizable Check-in
Bugs, Tasks, Reporting
Policies Continuous
Requirements, Integration
Shelving Stories, Risks, Decision
etc. Scheduled Support
Very Extensible Ad Hoc Track Project
Progress
cuong@microsoft.com
71. Process Templates
CMMI 5.0 Agile 5.0 Default templates
SCRUM 1.0 MPT 1.0
Customed templates
X Y
cuong@microsoft.com
72. A Process Template
Process Guidance
User Story
Task
Bug Work Item
Process Template Issue
Test Case
Custom Work
Item
Reportings
cuong@microsoft.com
73. Work Item
Agile 5.0 CMMI 5.0
• User Story • Task
• Task • Bug
• Test Case • Change Request
• Bug • Test Case
• Issue • Requirement
• Review
• Shared Steps
• Issue
• Risk
• Shared Steps
cuong@microsoft.com
74. Work Item Tracking
• Create, Update, Change status
• Link
• Associate with changeset
• Query
cuong@microsoft.com
76. REPORTING
Process Focused
Version Control
Process
Templates Work Item Tracking
Integrated
SharePoint Check-in Build Automation
Manage work
Customizable Check-in
Bugs, Tasks, Reporting
Policies Continuous
Requirements, Integration
Shelving Stories, Risks, Decision
etc. Scheduled Support
Very Extensible Ad Hoc Track Project
Progress
cuong@microsoft.com
81. Automated Unit Test
• Write Once, Run Often
• Configurable Test Script
• Programmable Test Logic
• No human input
• Auto generate bug report
• Trigger action: build / notification
cuong@microsoft.com
86. CONTINOUS INTEGRATION
Team Foundation Server
Process Focused
Version Control
Process
Templates Work Item Tracking
Integrated
SharePoint Check-in Build Automation
Manage work
Customizable Check-in
Bugs, Tasks, Reporting
Policies Continuous
Requirements, Integration
Shelving Stories, Risks, Decision
etc. Scheduled Support
Very Extensible Ad Hoc Track Project
Progress
cuong@microsoft.com
88. Team Foundation Build
• Manual: run by team member
• Continous: queued by a check-in
• Rolling: accumulated until previous build
finishes
• Gated check in: Check-in is accepted only if
submitted changes merge and build
successfully
• Scheduled: run on a defined schedule
cuong@microsoft.com