Team Foundation Server or TFS is developed by Microsoft to manage the teams and the way they work. It is basically a management tool used in project management, reporting, requirements gathering and testing

1. Team Foundation server
Created by
Hesham ezzat

2. It is literally true that you can succeed best and quickest by helping
others to succeed.

3. 1
2
3
4
5
6
Table of
Contents
Introduction
TFS Session live
ALM TOOL
What is TFS?
Agile process in TFS
Implement in Makeen
3

4. Introduction
4
SDLC
software development life cycle is a
roadmap for working on a digital
solution. In other words, SDLC is a
blueprint designed for a team to
create, maintain, and fix
digital products.
SDLC

5. Introduction
5
ALM
is a superset which wraps together
the fragmented SDLC Management
as processes, and integrates them
ensuring delivery of end user value
and maintaining the same.
• Governance
• development
• operations
ALM

6. Introduction
6
SDLC
is the management of the processes
during the development stages only for
different modules/components of the
application.
ALM
is a superset which wraps together
the fragmented SDLC Management
as processes, and integrates them
ensuring delivery of end user value
and maintaining the same.
SDLC VS ALM

7. Introduction
7
.
SDLC VS ALM

8. ALM Tool
8
Idea of ALM Tool
Keys
• Requirements (CRS )
• Task (Dev – Design – DB)
• Test (QC )
• BUG (QC )
• Total Time (Estimation ) .

9. ALM Tool
9
TOPS ALM Tool

10. 10
Team Foundation Server or TFS is developed by Microsoft
to manage the teams and the way they work. It is basically a
management tool used in project management, reporting,
requirements gathering and testing This is a back-end
management system and uses Git to control the source code.
TFS
What is the TFS ?

11. What is the TFS ?
Basic
Choose Basic when your team wants the simplest
model that uses Issues, Tasks, and Epics to track
work. Note: Basic is currently in a selective Preview
for new users of Azure Boards only.
Scrum
Choose Scrum when your team practices Scrum. This
process works great if you want to track product
backlog items (PBIs) and bugs on the Kanban board,
or break PBIs and bugs down into tasks on the
taskboard.
Agile
Choose Agile when your team uses Agile planning
methods, including Scrum, and tracks development
and test activities separately. This process works
great if you want to track user stories and (optionally)
bugs on the Kanban board, or track bugs and tasks on
the taskboard.
CMMI
Choose CMMI when your team follows more formal
project methods that require a framework for process
improvement and an auditable record of decisions.
With this process, you can track requirements, change
requests, risks, and reviews.
11
Process in TFS

12. What is the TFS ?
12
Scrum vs Agile vs CMMI
Scrum :
"This template is for teams who follow the
Scrum methodology and use Scrum terminology."
Agile :
"This template is flexible and will work great for
most teams using Agile planning methods,
including those practicing Scrum."
CMMI :
"This template is for more formal projects
requiring a framework for process improvement
and an auditable record of decisions."

13. Agile Process in TFS ?
13
Agile process
Let’s Begin Now!
The Agile process provides several work item
types for example, user stories, tasks, bugs,
features, and epics among others—to plan and
track work. We recommend you start by
adding user stories like CR. If you need to
group them into a hierarchy, you can define
features. If you want to track additional details
of work, you can add tasks to a user story and
assign to specific member in other team .

14. Agile process in TFS?
14
Iteration vs Areas
Area paths allow you to group work items by
team, product, or feature area.
iteration paths allow you to group work into sprints,
milestones, or other event-specific or time-related
period.
Both these fields allow you to define a hierarchy of paths

15. Agile process in TFS?
15
Backlog
Backlog is a prioritized list of tasks that
teams need to work on within the scope of
a project management strategy. It is derived
from the requirements and roadmap of
the project. Important tasks in
the backlog are usually shown on top of the
list to let the team know which tasks they
need to deliver first.

16. Agile process in TFS
16
• User story name
• Area
• Iteration
• State
• Add comment
• Add tag
• Description
• Acceptance criteria
• Follow
• Tags
User story

17. Agile process in TFS
17
Tasks
• Efforts
• State cases
• Activity
• Related work
• Attachemrnts .
.

18. Agile process in TFS
18
Dashboard
.
•Dashboards are customizable interactive
signboards that provide real-time information.
Dashboards are associated with a team or a project
and display configurable charts and widgets.
•Charts are query-based status or trend charts
derived from a work item query or test results.
•Widgets display configurable information and
charts on dashboards. The widget catalog provides
brief descriptions of those widgets available to
you. In addition, you can add widgets provided
through

19. Implement in Makeen
19
Team leader vs Member
Member
• Update state of task
• Update work hours
• Write comments
Coordinator (coach)
• Add user story in PBL
• Assign tasks to Team
leader
• Update state of cr
• Follow task
• Sent mails to member
Team leader
• Assign tasks to member
• Write comments
• Follow task

20. Implement in Makeen
20
Task state
Update task state after adding complete
works (New – Removed )
Active updates the status to when they
start working on it
Closed state when the story has been
implemented according to the Acceptance
Criteria and acceptance tests pass.

21. Agile process in TFS
21
Tasks
Original : The amount of estimated work required
to complete a task. Typically, this field doesn't
change after it is assigned.
Remaining : The amount of work remaining to
complete a task. As work progresses
completed : The amount of work spent
implementing a task.
.

22. Agile process in TFS
22
Comments
• Use the Discussion section to add
and review comments made about
the work being performed.
• @ mention member
• # link work iteam
.

23. Agile process in TFS
23
History
Removed work items remain in the data store and can be
reactivated by changing the State.
With each update, changes are recorded in the History field
which you can view through the History tab.
.

24. TFS