application lifecycle management with team foundation server
DESCRIPTION
Application Lifecycle Management with Team Foundation ServerTRANSCRIPT
APPLICATION LIFECYCLE
MANAGEMENT WITH MICROSOFT
TEAM FOUNDATION SERVER
JOZUA VELLE
APPLICATION LIFECYCLE MANAGEMENT (ALM)
Introductie
APPLICATION LIFECYCLE MANAGEMENT (ALM)
• Application lifecycle management is the concept of managing your software development project throughout all phases of its life.
APPLICATION LIFECYCLE MANAGEMENT (ALM)
• Governance– Manage to assure that the software brings what the business needs
APPLICATION LIFECYCLE MANAGEMENT (ALM)
• Development– One or more Software Development LifeCycles (SDLC’s)– Each SDLC contains requirements definition, analyses, design,
development and testing– Deployment after first SDLC
APPLICATION LIFECYCLE MANAGEMENT (ALM)
• Development:– Incremental approach (agile) withinSDLC:
WAT IS APPLICATION LIFECYCLE MANAGEMENT (ALM)? (5)
• Operations– Deployment and monitoring of the software
APPLICATION LIFECYCLE MANAGEMENT (ALM)
• All roles in a development organization are involved in ALM process
MICROSOFT TEAM FOUNDATION SERVER (TFS)
Introductie
MICROSOFT TEAM FOUNDATION SERVER (TFS)
• Tooling evolution
• Team development tools– 1st generation (<2008): best of breed– 2nd generation (>2008): end-to-end flow
• Hard to adopt– Impacts multiple roles – Impacts development proces
MICROSOFT TEAM FOUNDATION SERVER (TFS)
MICROSOFT TEAM FOUNDATION SERVER (TFS)
AGILE SOFTWARE DEVELOPMENTThe real world (in Centric Belgium – Retail)…
AGILE SOFTWARE DEVELOPMENT
• Manage/minimize impact of projects risks:– Work in small Scrum team: 4 - 8 FTE– Build product incrementaly during 3 week Sprints (iterations)– Split-up scope in small User Stories (work items)– React to change by organizing a planning, review and retrospective
meeting during each Sprint (iteration)
1 day
3 weeksSprint
BacklogCompleted
Work
Daily Scrum
Iteration Planning Meeting
Iteration Retrospective
Meeting
Iteration ReviewMeeting
Scrum of scrums
AGILE SOFTWARE DEVELOPMENT
• Continuous delivery– Why do continuous delivery?
• Developers work on their local machine• Integration of local changes is (often) difficult• Integration should be done as soon as possible• Early feedback is valuable
– How do we do continuous delivery?• Code repository• Build automation• Test automation• Easily deployable
MICROSOFT TEAM FOUNDATION SERVER (TFS)
