• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
The agile cloud development scenario in ten acts
 

The agile cloud development scenario in ten acts

on

  • 3,123 views

The agile cloud development scenario in ten acts, TFSService

The agile cloud development scenario in ten acts, TFSService

Statistics

Views

Total Views
3,123
Views on SlideShare
2,267
Embed Views
856

Actions

Likes
1
Downloads
16
Comments
0

4 Embeds 856

http://www.clemensreijnen.nl 675
http://clemensreijnen.nl 136
http://feeds.feedburner.com 36
http://paper.li 9

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The agile cloud development scenario in ten acts The agile cloud development scenario in ten acts Presentation Transcript

    • The agileclouddevelopmentscenario in 10 acts
    • TFService ALM in the Cloudcrowd development and crowd testing, fast enabling ofteams with TFS service, master and teambacklogs, exploratory and automated testing, featurebranches with build quality and automatic deployment ofazure applications.
    • The agile cloud development scenario• TFS service,• master and team backlogs,• feature branches with build quality,• automatic deployment,• exploratory and automated testing. fast enabling of teams for crowd development and crowd testing
    • Team Foundation Service
    • Server vs. Service Server Service Work Items, Source Control, & Build Agile Product/Project Management Test Case Management Heterogeneous Development Near-zero setup and administration Collaborate with anyone, from anywhere Virtual Test Lab Management SharePoint Integration Data Warehouse & Reporting
    • Authentication Today: Windows Live ID Future: Corporate identity with Active Directory Federation Services, Google ID, Yahoo ID, Facebook Connect, etc.
    • Authentication Today: LiveID on corporate email, ping every month.
    • Clients
    • Act 1:connect to tfsservice 1. open TFS client 2. connect to https://clemens.tfspreview.com/ 3. use given LiveID or provide yours to the presenter
    • Teamshttps://tfspreview.com/_content/TeamHelp.htm By defining a group of people who work on your team projects, you can more easily organize, track, and facilitate the work that those people perform.
    • Teams A team project can one or more teams.
    • Teams A team contains one or more team project members
    • Teams A team project member doesn’t need to be in a team
    • Teams A team is responsible for an area
    • Teamshttp://www.clemensreijnen.nl/post/2011/10/09/Teams-in-VS11.aspx
    • Act 2:Browse the teamclient administrator designfunctional area functional area area <root> area
    • Iteration A team project has release / sprints
    • Iteration A team project is in a sprint
    • Iteration A team follows the team projects sprint cycle
    • Iteration A team contributes to an interation
    • product backlog A team has a product backlog for the area its responsible for
    • Teamshttp://www.clemensreijnen.nl/post/2011/10/10/Teams-in-Visual-Studio-11-feature-teams-and-backlogs.aspx
    • Act 3:Add backlog itemsadd backlog items for your team and prioritize
    • sprint backlog add backlog items to a sprint (current or future) commit backlog item add tasks to a backlog item
    • sprint backlog Team capacity per sprint
    • sprint backlog Team capacity planning
    • sprint backlog don’t play with the work items !!!
    • Act 4:plan the sprintselect sprint items and add tasks
    • board The task board contains tasks for an area for the current sprint.
    • board
    • Act 5:run the sprintput some tasks to todo
    • source
    • source
    • source
    • teams A team is responsible for an area
    • sourceVersion Control for Multiple Agile Teamshttp://www.infoq.com/articles/agile-version-control
    • Act 6:run the sprintget your branch and execute your tasks
    • break
    • builds Local Build Server
    • builds Cloud Build Server http://www.clemensreijnen.nl/post/2011/ 10/14/Build-Service-on-Azure-connected- with-Hosted-TFS-Service-on-Azure.aspx
    • builds
    • Act 7:check the qualityget your branch and execute your tasks
    • merge Relate merge check-in 2 bpi
    • sourceVersion Control for Multiple Agile Teamshttp://www.infoq.com/articles/agile-version-control
    • Act 8:merge the changesget your branch and execute your tasks
    • deploy
    • deploy http://blogs.msdn.com/b/tomholl/archive /2011/12/06/automated-build-and- deployment-with-windows-azure-sdk-1- 6.aspx
    • Act 9:deploy the bits kick off the deployment build
    • planned test
    • tests planned test tests test tests tests tests tests tests tests tests testsbuild build build build
    • planned test
    • exploritory test
    • exploritory test • Centered on customer value rather than spec compliance • Find bugs fast and early without overhead • Tests working software! http://channel9.msdn.com/Events/ALM- Summit/2011/Exploratory-Testing
    • the bug backlog
    • the bug backlog http://www.clemensreijnen.nl/post/2011/ http://blog.mountaingoatsoftware.com/b 10/12/Teams-in-Visual-Studio-11-CTP- ugs-on-the-product-backlog the-Bug-Backlog.aspx
    • Act 10:test the bitsget your branch and execute your tasks
    • use the system
    • dank