Tfs 2013 Process Template Overview

Comprehensive presentation detailing reporting and tracking capabilities of Team Foundation Server. Focuses on Excel workbooks and Reporting Services, but touches on other technologies as well.

Until now there have been two camps for Application Quality Management (AQM) systems. Traditional Tools like HP QC that have proved inflexible for agile developments and maintenance heavy, or new agile tools from Version One or Rally Software, which are agile specific tools and not suitable for use outside agile environments or corporate-wide where teams are using a mix of processes. With many organisations moving to or experimenting with Agile, Original Software has been acclaimed by the analyst community as the best solution for supporting Agile. [Original Software nominated Agile Best Tool Award] Just as improvements in developer's software tools and methods have enabled a shift in development approaches, next generation technology for test automation is similarly reframing the opportunities for testers to automate earlier in the delivery cycle without incurring the heavy burden of script maintenance so often associated with traditional automation tools. This means that not only can an agile environment be adopted, application quality is maintained and the total testing time reduced. - See more at: http://www.origsoft.com/solutions/agile-software-testing/

The PPT is about scaling agile across various non-cross-functional teams and the various experiments that were done before arriving at a methodology that worked for the teams.

This document discusses automated acceptance testing and continuous delivery. It describes how consistent, predictable, high-quality software can be delivered through every iteration using automated testing and continuous delivery practices. These practices include writing specifications and scenarios in a Given/When/Then format to define requirements and tests, automating the testing process, and setting up continuous delivery pipelines to deploy changes quickly and reliably.

An overview of the reporting capabilities in Team Foundation Server 2012. Includes explanation of Data warehouse architecture, included reports (SSRS and Excel), and customization.

The document provides an overview of agile testing concepts and approaches. It discusses key aspects of agile testing including testing terminology, mindset, challenges, common approaches, strategies, and metrics. The agenda includes recapping agile principles, describing testing roles in agile, discussing test planning and execution in each sprint, and highlighting problems and lessons learned from projects.

Introduction to Agile software testing - The 5th seminar in public seminar series from KMS Technology which have been delivering from 2011 in every two months

The document discusses test management in Scrum and outlines the main testing documentation and artifacts like test strategies, test plans, test cases, and defect reports. It also covers tools, approaches to test management, and how to plan testing sprints by dividing QA tasks among testers and ensuring time estimated is less than time available.

The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.

How Does IBM Do Agile presentation that I presented at the Software Development Conference in Wellington, New Zealand at 22 March 2011.

This document discusses best practices for using agile product development for hardware projects. It provides differences between hardware and software development such as hardware being more difficult to change after manufacturing. It recommends using scrum with a focus on technical stories for hardware. An example project at Thermo Fisher Scientific developing analytical chemistry equipment is described that successfully used scrum. Key lessons learned include the product owner also being a team member, most deliverables being behind the scenes technical work rather than user-facing, and estimation and velocity being more challenging for hardware projects.

The document discusses Agile Scrum, including: - The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan. - Scrum roles like Product Owner, Scrum Master, and cross-functional team members. - Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. - User stories, epics, and conditions of satisfaction to define work in the product backlog. - The goal of each sprint is to produce potentially shippable increments of functionality.

The document discusses how adopting Agile practices can help reduce costs and increase project success rates. It provides an overview of the Agile manifesto and techniques like iterative development, improved communication, and leverage existing investments. Adopting Agile can lead to reduced inventory, quick turnaround focusing on required functionality, minimizing costs, and delivering working software sooner to generate savings and quicker time to market. This allows for a focus on ROI and increased project success rates through improved quality, productivity, visibility for customers, and alignment between business and technology needs.

Overview of TFS Reports, comparing what is available between different Process Templates. This is a WIP, and will be updated soon with additional info on customizing reports.

Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.

The document discusses agile testing approaches. It defines testing as executing software with test cases to find failures and demonstrate correct execution. It then discusses key aspects of agile testing including: running tests iteratively throughout development rather than just at the end; automating tests wherever practical; and having testers work collaboratively as part of development teams. It outlines success factors like focusing on delivering customer value and continually improving testing practices. The document advocates for automating a large portion of testing to provide rapid feedback and free up resources while balancing automation costs.

Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.

This document provides an overview of Team Foundation Server (TFS) by Phase 2 International, including: 1. TFS is an advanced source control and software development lifecycle (SDLC) management tool that includes work item tracking, project management, document management, and reporting capabilities. 2. TFS requires Windows Server 2003 or 2008 and SQL Server 2005 or 2008 to be installed on a dedicated server. 3. TFS includes features like version control, build automation, a project portal, and add-ons like Team Explorer and integration with Visual Studio and Microsoft Project.

TFS est la plateforme de collaboration qui se trouve au coeur de la solution de gestion du cycle de vie des applications (ALM) de Microsoft. Pour de petites équipes de développement (5 users), TFS est disponible online et gratuitement. Lors de cette session, principalement à base d'exemples pratiques, nous aborderons les modules Source Controle, Collaborate (gestion des tâches et des bugs) et Automatic Builds (compilations et déploiements automatisés).

An introduction to process templates, an overview of the Microsoft Process Template, and new process template features shipping in Team Foundation Server 2010.

This document provides an overview of administering a Team Foundation Server (TFS) application. It covers the operational architecture including databases and services, backup and restore processes, application administration such as managing users and groups, creating team projects, setting permissions, and other administrative functions. It also discusses maintenance plans for SQL databases, adding and removing users, and data migration from external version control and defect tracking systems.

The document discusses communicating agile project status to executive managers. It provides tips for establishing trust between management and agile teams. It also outlines appropriate roles for executives, managers, and teams in an agile environment. The document recommends focusing reporting on working software demonstrations and metrics like burn down charts and velocity, rather than intensive intra-sprint reporting.

The document discusses 5 common mistakes that companies make with their IT departments that cause them to lose money. It describes each mistake in more detail and provides statistics on the financial impacts. The mistakes include miscommunication between business and IT, implementing IT projects as standalone systems rather than integrated platforms, limiting IT's role to only automation, designing IT systems without standardized architecture blueprints, and treating IT projects as expenses rather than investments. The document then presents examples of how to avoid these mistakes by taking an enterprise architecture approach that integrates business and IT strategy and ensures IT projects deliver measurable returns on investment and business value.