Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview
Download as PPTX, PDF5 likes2,493 views
The document discusses the software development lifecycle and the collaborative roles involved in transforming business needs into software solutions. It outlines an iterative project development process governed by key pillars such as human resources, functionality, timeframe, and quality. Additionally, it mentions the Team Foundation Server architecture and its relevance in managing project artefacts and iterations.
Application Lifecycle Management using Microsoft Team Foundation Server Training Course Overview
- 2. Valdis IljučonoksNexum Insurance Technologies, Chief ArchitectMicrosoft 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 operationsSoftware Development LifecycleSoftware Development LifecycleAnalysisManagementDescisionInitialRequirementsInitialArchitetureDevelopmentDeliveryProject ManagerBusiness AnalystDeveloperUI DesignDBAOperations
- 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 timeQualityTimeFunctionalityResources
- 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 needediteration 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
- 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
- #6: The reason we write business software is to turn business needs and opportunitiesinto business value.
- #7: Business Manager, Project Manager, PMO Decision Maker, Business Analyst, Architect, UX Team Members, Database Administrators, Developers, Testers, Operations and Maintenance Stuff
- #8: 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
- #10: 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
- #11: actually there is fourth element in the classical triangle – the quality with which deliver project on time
- #13: this is classical project development cycle every next step is performed only previous has been successfully completed
- #14: MSF process is iterative, never ending and never explicity starting. project ends when customer has a value
- #16: project is split into several iterations, every next iteration is performed as needed. iteration contains concrete steps inside
- #17: every tiny check-in counts, which drives whole project, through daily builds those are consolidated into acceptance tests
- #24: TFS has 3 layer architecture with data storage, application and client tiers built on latest Microsoft platforms
- #26: process template is a set of all artefacts used and involved into your team project