Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview


Published on

Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview

2-day training course gives a deep insight into application life cycle phases, involved expertise, team layout and responsibility matrixes. Course touches various issues and problems each of the project team member must face with during application development process.

Microsoft Solutions Framework (MSF) guidelines developed by Microsoft internally with industry experts are used as basis for discussing various issues and challenges during application lifecycle.

Hands-on labs are available during course in order to touch the technology and help to get familiar with TFS server and various other involved software to access and work with TFS.

By completing course attendees get familiar with Microsoft TFS technologies, get ideas how to use these technologies to improve, boost, control and trace application lifecycle during all phases within the process.

What’s included:

Introduction to Application Lifecycle Management (ALM)
Involved members and responsibility matrix during project
Discussed 3 pillars of every project management must manipulate with
Introduction to Microsoft Solution Framework (MSF)
Classical waterfall and advanced spiral development processes
Major project drivers
Iterations of the application lifecycle
MSF project team model
TFS architecture and deployment
Project process template
Work item (WI) principles
Requirements categories and collection principles
Requirements management using TFS tools
Requirements management using partner tools
Development plan generation using TFS integration tools
Activities and challenges during development phase
Review of TFS source code repository and associated features
Source code branching and merging policies and general principles
Source code build system (MSBuild)
Tools used during testing phase
Traceability and manageability of the project using MS Office and Reporting tools

Published in: Technology, Business
  • Login to see the comments

Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview

  1. 1.
  2. 2. Valdis Iljučonoks<br />Nexum Insurance Technologies, Chief Architect<br />Microsoft MVP (Visual C#)<br />
  3. 3. MicrosoftTeam Foundation Server<br />
  4. 4. ALM Introduction<br />
  5. 5. The reason we write business software is to turn business needs and opportunitiesinto business value.<br />
  6. 6. Business Manager, Project Manager, PMO Decision Maker, Business Analyst, Architect, UX Team Members, Database Administrators, Developers, Testers, Operations and Maintenance Stuff<br />
  7. 7. somebody comes up with an idea based on an analysis of the business needs, project managerstarts gathering requirements with the help ofbusiness analysts, also startsplanning the project, the architect starts looking at how to realize the new system, the development starts, user interface (UI)designers, and DBAs, systemhas gone through acceptance testing, it is delivered to operations<br />Software Development Lifecycle<br />Software Development Lifecycle<br />Analysis<br />Management<br />Descision<br />Initial<br />Requirements<br />Initial<br />Architeture<br />Development<br />Delivery<br />Project Manager<br />Business Analyst<br />Developer<br />UI Design<br />DBA<br />Operations<br />
  8. 8. Three pillars<br />
  9. 9. within any project there are three pilars, human resources who is doing the job, required functionality to deliver, timeframe when required functionality must be delivered<br />
  10. 10. actually there is fourth element in the classical triangle – the quality with which deliver project on time<br />Quality<br />Time<br />Functionality<br />Resources<br />
  11. 11. Development process<br />
  12. 12. this is classical project development cycle every next step is performed only previous has been successfully completed<br />
  13. 13. MSF process is iterative, never ending and never explicity starting. Project ends when customer has received a value<br />
  14. 14. Project drivers<br />
  15. 15. project is split into several iterations,<br />every next iteration is performed as needed<br />iteration contains concrete steps inside<br />
  16. 16. every tiny check-in counts, which drives whole project, through daily builds those are consolidated into acceptance tests<br />
  17. 17. Team Structure<br />
  18. 18.
  19. 19. Team Foundation ServerVisual Studio Team System<br />
  20. 20.
  21. 21. CIO<br />PMO<br />Architect<br />Tester<br />Developer<br />ProjectManager<br />Designer<br />DB Pro<br />Application<br />Support<br />Business<br />Analyst<br />Operations<br />
  22. 22. TFS Architecture<br />
  23. 23. TFS has 3 layer architecture with data storage, application and client tiers built on latest Microsoft platforms<br />
  24. 24.
  25. 25. process template is a set of all artefacts used and involved into your team project<br />
  26. 26.<br />