The agile cloud development scenario in ten acts

Post on 21-Oct-2014

3.328 views 0 download

Tags:

description

The agile cloud development scenario in ten acts, TFSService

Transcript of The agile cloud development scenario in ten acts

The agile cloud development scenario

in 10 acts

TFServiceALM in the Cloud

crowd development and crowd testing, fast enabling of teams with TFS service, master and team backlogs, exploratory and automated testing, feature branches with build quality and automatic deployment of azure 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

Agile Product/Project Management

Test Case Management

Heterogeneous Development

Virtual Test Lab Management

SharePoint Integration

Data Warehouse & Reporting

Work Items, Source Control, & Build

Collaborate with anyone, from anywhere

Near-zero setup and administration

Today: Windows Live IDFuture: Corporate identity with Active Directory Federation Services, Google ID, Yahoo ID, Facebook Connect, etc.

Authentication

Today: LiveID on corporate email, ping every month.

Authentication

Clients

Act 1:

connect to tfsservice

1. open TFS client 2. connect to

3. use given LiveID or provide yours to the presenter

https://clemens.tfspreview.com/

Teams

https://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

Act 2: Browse the team

client functional area

administratorfunctional area

designarea

<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

Act 3: Add backlog items

add backlog items for your team and prioritize

sprint backlog

add backlog items to a sprint (current or future)commit backlog itemadd tasks to a backlog item

sprint backlog

Team capacity per sprint

sprint backlog

Team capacityplanning

sprint backlog

don’t play with the work items !!!

Act 4: plan the sprint

select sprint items and add tasks

board

The task board contains tasks for an area for the current sprint.

board

Act 5: run the sprint

put some tasks to todo

source

source

source

teams

A team is responsible for an area

RECAP

source

Version Control for Multiple Agile Teams

http://www.infoq.com/articles/agile-version-control

Act 6: run the sprint

get your branch and execute your tasks

break

builds

Local Build Server

builds

Act 7: check the quality

get your branch and execute your tasks

merge

Relate merge check-in 2 bpi

source

Version Control for Multiple Agile Teams

http://www.infoq.com/articles/agile-version-control

RECAP

Act 8: merge the changes

get your branch and execute your tasks

deploy

Act 9: deploy the bits

kick off the deployment build

planned test

build

build

build

build

test

tests

tests

tests

tests

tests

tests

tests

tests

tests

tests

planned test

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

Act 10: test the bits

get your branch and execute your tasks

use the system

dank