Out of the box RTC Reports

Report	Agile	Formal Lifecycle
Build
Build Health	Yes	No
Code Health	Yes	Yes
Frequent Test Failures	Yes	Yes
Frequent Test Regressions	Yes	Yes
Blocking Work Items	No	Yes
Planning
Planning Burndown	Yes	No
Planning Release Burndown	Yes	No
Planning Team Velocity	Yes	No
Source Control
Project Activity	Yes	Yes
Work Items
Actual as Percentage of Estimated Work	Yes	Yes
Advanced Release Burndown	Yes	No
Blocking Work Items	Yes	Yes
Burndown	Yes	Yes
Burnup	Yes	Yes
Closed Work Items Daily	Yes	Yes
Defect Backlog	Yes	Yes
Defect Backlog by Project Area	Yes	Yes
Defect Discovery Rate	Yes	Yes
Deferred Work Items	Yes	Yes
Estimate Changes	Yes	Yes
New Work Items by Severity	Yes	Yes
Open Work Items	Yes	No
Open Work Items by Type	Yes	Yes
Open vs Closed Work Items	Yes	Yes
Release Burndown	Yes	Yes
Team Velocity	Yes	Yes
Work Item Comparison	Yes	Yes
Work Item Comparison by Project Area	Yes	Yes
Work Items by Owner	Yes	Yes
Work Items by Priority	Yes	Yes
Work Items by Team Area	Yes	Yes
Story Points	Yes	NA
Story Points Progress	Yes	NA
Story Points Remaining	Yes	NA
Story Points by Iteration	Yes	NA
Estimated vs Actual Work	Yes	No
Open vs Closed Story Points by Iteration	Yes	NA
Risks by Exposure	NA	Yes
Cumulative Value Flow	No	Yes

Out of the box TFS Reports

Out of the box TFS Agile Reports
Build	Description
Build Quality Indicators	Helps you track how close the completed code is to release quality. Shows test coverage, code churn, and bug counts.
Build Success Over Time	Helps you track changes in the quality of the code that the team has checked in. Shows test results for the last build of each day.
Build Summary	Helps you determine the status of each build. Shows a list of builds with test results, test coverage, code churn, and quality notes.
Bugs
Bug Status	Helps you track the team's progress toward resolving bugs. Shows the number of bugs in each state over time, a breakdown of bugs by priority or severity, and the number of bugs that are assigned to each team member
Bug Trends	Helps you track the rate at which the team is discovering and resolving bugs. Shows a moving average of bugs discovered and resolved over time.
Reactivations	Helps you track how effectively the team is resolving bugs. Shows the number of bugs that the team resolved over time in relation to the number of bugs that the team resolved and later reactivated.
Dashboards
Burn Rate	Helps you track the team's progress toward completing the work for an iteration. Shows how many hours of work the team has completed, how many hours remain, the rate of progress, and the work assigned to each team member.
Burndown	Helps you track the team's progress toward completing the work for an iteration. Shows how many hours of work the team has completed, how many hours remain, the rate of progress, and the work assigned to each team member.
Project Management
Burndown and Burn rate	Helps you track the team's progress toward completing the work for an iteration. Shows how many hours of work the team has completed, how many hours remain, the rate of progress, and the work assigned to each team member.
Remaining Work	Helps you track the team's progress. Shows the total number of hours of work in an iteration and the team's progress toward completing it.
Status on All Iterations	Helps you track the team's performance over successive iterations. Shows each iteration's original estimates for the number of hours of work, the actual numbers of hours of work that the team completed, the number of hours of work that remain, and the number of bugs
Stories Overview	Helps you track how far each user story has been implemented. Shows each story's actual number of hours of work remaining and completed, its acceptance test results, and the number of bugs that are linked to each story.
Stories Progress	Helps you track recent progress for each user story. Shows each story's remaining, completed, and recently completed work.
Unplanned Work	How much unplanned work do we have?
Tests
Test Case Readiness	Helps you track how many test cases are ready to be run. Shows the number of test cases in each state of preparation.
Test Plan Progress	Helps you track the progress of your test plans. Shows the results of running the tests over time

Explaining Scrum in less than 120 seconds

Explaining Scrum in less than 120 seconds

Animated Stories

Ted the Developer Episode 1
Ted the Developer Episode 2
Ted the Developer Episode 3
Ted the Developer Episode 4
Ted the Developer Episode 5 
IBM's Rational Team Concert - http://jazz.net - makes team development more collaborative. It gives developers a platform for tracking code, enhancement requests, defects, and project status. It supports both Eclipse and Visual Studio clients.

RQM Videos

Lifecycle Quality Management with RQM

Rational Requirements Composer

A better way to define, collaborate, and manage requirements

Features and capabilities:

• Capture requirements
• Visually define
• Traceability
• Collaboration and review
• Reports
• Audit history

Capture requirements
Quickly define and organize requirements with convenient tools: UI mock-up, story boards, rich-text editors, and predefined templates

Visually define
Define requirements visually to quickly convey your project needs: Use cases, diagrams, and customized project content.

Traceability
Connect project requirements, scenarios, test artifacts, and development work items through traceability to identify gaps and change impact

Collaboration and review
Engage the experts from your team to collaborate and improve the quality of your project requirements

Reports
Generate documents, spreadsheets, or PDF reports that show project progress, traceability coverage, and overall status.

Audit history
Quickly identify what changes were made and who made them throughout the project's progress

Better requirements for better business outcome

High quality business requirements and good management practices in the development process (waterfall, iterative or agile) leads to the best outcomes. Engaging stakeholders - early and often - in defining and validating requirements improves the likelihood that projects will deliver what customers need. Using well defined requirements in an organized managed process allows business analysts, developers, and other team members to analyze the information to help drive key business decisions. Traceability across requirements can expose gaps and impact from change. Analysis features then give team members the power to discover key status, release, and value information during development based on good quality requirements.

• Requirements are expressed in many different forms visually and textually and they can come from many sources and tools: spreadsheets, presentations, whiteboard snapshots, etc. Requirements Composer will bring these "information islands" together and connect them with traceability to expose them to the broader development team for collaboration and analysis.

• Requirements Composer helps project teams define what the business needs to accomplish, structure their ideas as text, stories, use cases, process diagrams, work items and tests.

• Analysts and others who author documents have all of these tools and features available, with similar user interfaces, in one location, using a common repository.

• Impact and requirement gaps in project information can be viewed and exposed using built in traceability viewers to show how changed requirement will affect the down/up stream for development.

• Project team members will be able use standard reporting views that include attributes, filters, sorts, traceability and other critical information for development decisions.

Using the Stakeholder Collaboration Strategy with Rational Requirements Composer:
Part 1. The Audience
Part 2. Organizing the project and repository space
Part 3. Linking strategy
Part 4. Collaboration approach

RTC Pointers

e-Kit :

https://www14.software.ibm.com/iwm/web/cc/imc/sdp/agile/thankyou.shtml

Agile thought leadership:

Being agile while still being compliant -

http://www.ibm.com/developerworks/rational/library/compliant-agile-medical-device/index.html?ca=drs-

Top 5 lessons learned about scaling Agile from a leading insurance provider

-

http://www.ibm.com/developerworks/rational/agile/lessons-learned-insurance/index.html?ca=drs-

Lessons from the Agile trenches -

http://www.ibm.com/developerworks/agile/library/a-agiletrenches/index.html?ca=drs-

Progressive refinement of user stories in the Product Backlog -

http://www.ibm.com/developerworks/rational/library/user-stories-product-backlog/index.html?ca=drs-

Best practices for effective velocity tracking -

http://www.ibm.com/developerworks/agile/library/a-vt/index.html?ca=drs-

Pragmatic architecture for agile application lifecycle management -

http://www.ibm.com/developerworks/rational/library/agile-application-lifecycle-management/index.html?ca=drs-

The true value of agile process maturity -

http://www.ibm.com/developerworks/rational/library/agile-process-maturity/index.html?ca=drs-

IBM Rational Agile Product Guidance

Effective Planning with Rational Team Concert 4.0 -

https://jazz.net/library/article/594

Using scrum methods with Rational Team Concert Version 4: Part 1. Set up the project, team area, and Product Backlog -

http://www.ibm.com/developerworks/rational/library/scrum-methods-rational-team-concert-v4-1/index.html?ca=drs-

Hitting nails on the head: Scrum and Rational Team Concert - https://jazz.net/blog/index.php/2010/03/08/hitting-nails-on-the-head-scrum-and-rational-team-concert/

Progress Bars, Load Bars, and the importance of estimating your work in Rational Team Concert 4.0 - https://jazz.net/library/article/586

Document and automate processes with Rational Method Composer and Jazz:

Part 1. The value of methods in an agile world -

http://www.ibm.com/developerworks/rational/library/automate-software-development-processes/index.html?ca=drs-

IBM z/OS application continuous integration: Part 1. Building continuous integration with Rational Team Concert -

http://www.ibm.com/developerworks/rational/library/ibm-zos-application-continuous-integration-1/index.html?ca=drs-

TFS Links

What's New for Application Lifecycle Management in Visual Studio 2012

TFS Video Links

Visual Studio Premium and Ultimate 2012:
Coordinate your team with agile project management
Visualize the impact of a change
Managing lab environments for testing
Using Code Review to Improve Quality
Using layer diagrams to design and validate your architecture
Collecting and analyzing data in production
Easily reproducing issues through manual testing
How to multi-task with My Work
Learnings:

• Seamless creation of task,
• updation of task progress (new to InProgress to Closed (Resolved)) in Team explorer window, 
• suspending current work (marking it/creating snapshot) to work on other prioritized task, resuming to suspended work etc.,
• Within TFS, code compare features without using 3rd party tools like beyond compare etc., 

Load testing applications in Visual Studio
Understand your code dependencies through visualization
Upgrading to Team Foundation Server 11: Process Templates
A Lap Around Microsoft Visual Studio and Team Foundation Server 2010

Team Foundation Server - Slide Share presentation links

Team Foundation Server: Planning, Tracking and Reporting
Team Foundation Server 2012: Reporting capabilities

Creating Reports for Team Foundation Server 2010

Creating Reports for Team Foundation Server 2010

Out of the box reports in TFS

Out of the box reports in TFS
Report area	MSF for Agile Software Development	MSF for CMMI Process Improvement
Project Management	• Burndown • Issue Trends • Task Progress (trend) • User Story Progress (trend)	• Burndown • Issue Trends • Task Progress (trend) • Requirements Progress (trend)
Bug Management	Bugs by Assignment Bugs by Priority Bug Progress (trend) Bug Reactivations (trend) Bug Trends (trend)	Bugs by Assignment Bugs by Priority Bug Progress (trend) Bug Reactivations (trend) Bug Trends (trend)
Test Management	Test Management Reports Test Case Readiness (trend) Test Plan Progress (trend) Manual Test Activity (trend) Failure Analysis (trend) User Story Test Status (trend)	Test Management Reports Test Case Readiness (trend) Test Plan Progress (trend) Manual Test Activity (trend) Failure Analysis (trend) Requirements Test Status (trend)
Software Quality and Release Management	Build Quality (trend) Code Churn (trend) Code Coverage (trend)	Build Quality (trend) Code Churn (trend) Code Coverage (trend)

Scaling Agile with C/ALM

A Scenario - based approach for overcoming the challenges of team collaboration