Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview
Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview http://www.solvency2.lv/consulting/application-lifecycle-management-training/ 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
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (12)
Similar to Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview
Similar to Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview (20)
More from Mihails Galuška
More from Mihails Galuška (14)
Recently uploaded
Recently uploaded (20)
Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview
- 2. Valdis Iljučonoks Nexum Insurance Technologies, Chief Architect Microsoft MVP (Visual C#)
- 5. The reason we write business software is to turn business needs and opportunitiesinto business value.
- 6. Business Manager, Project Manager, PMO Decision Maker, Business Analyst, Architect, UX Team Members, Database Administrators, Developers, Testers, Operations and Maintenance Stuff
- 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 Software Development Lifecycle Software Development Lifecycle Analysis Management Descision Initial Requirements Initial Architeture Development Delivery Project Manager Business Analyst Developer UI Design DBA Operations
- 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
- 10. actually there is fourth element in the classical triangle – the quality with which deliver project on time Quality Time Functionality Resources
- 12. this is classical project development cycle every next step is performed only previous has been successfully completed
- 13. MSF process is iterative, never ending and never explicity starting. Project ends when customer has received a value
- 14. Project drivers
- 15. project is split into several iterations, every next iteration is performed as needed iteration contains concrete steps inside
- 16. every tiny check-in counts, which drives whole project, through daily builds those are consolidated into acceptance tests
- 17. Team Structure
- 19. Team Foundation ServerVisual Studio Team System
- 21. CIO PMO Architect Tester Developer ProjectManager Designer DB Pro Application Support Business Analyst Operations
- 22. TFS Architecture
- 23. TFS has 3 layer architecture with data storage, application and client tiers built on latest Microsoft platforms
- 25. process template is a set of all artefacts used and involved into your team project
Editor's Notes
- The reason we write business software is to turn business needs and opportunitiesinto business value.
- Business Manager, Project Manager, PMO Decision Maker, Business Analyst, Architect, UX Team Members, Database Administrators, Developers, Testers, Operations and Maintenance Stuff
- The SDLC Viewsomebody 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
- 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
- actually there is fourth element in the classical triangle – the quality with which deliver project on time
- this is classical project development cycle every next step is performed only previous has been successfully completed
- MSF process is iterative, never ending and never explicity starting. project ends when customer has a value
- project is split into several iterations, every next iteration is performed as needed. iteration contains concrete steps inside
- every tiny check-in counts, which drives whole project, through daily builds those are consolidated into acceptance tests
- TFS has 3 layer architecture with data storage, application and client tiers built on latest Microsoft platforms
- process template is a set of all artefacts used and involved into your team project