1. SpiraTeam® - Product Information
Synchronizing Your Application Lifecycle

2. After viewing this presentation you will:
Objectives
After viewing this presentation you will:
Understand the challenges involved in managing the development and testing lifecycle of a project
Understand the challenges involved in planning and managing projects and why traditional waterfall methodologies have failed to deliver projects on-time and on-budget.
Have a strong grasp on the quality assurance and project management features provided by SpiraTeam
Have learned about the benefits of using SpiraTeam to plan, execute, test and manage your project

3. Agenda Quality Assurance & Project Management Challenges
SpiraTeam Overview
Feature Walkthrough
Requirements Management
Test Case Management
Release & Iteration Planning
Task Tracking
Incident / Defect Tracking
Source Code Integration
Integration / Migration Options
Use of automated testing tools
Integration with other systems
Synchronization with external bug-trackers

4. QA Testing Landscape
Traditionally, QA organizations use the following tools and systems to manage their testing:
Requirements stored in MS-Word documents or MS-Excel spreadsheets
Test scripts for user acceptance testing stored in MS-Word, MS-Excel with results recorded on paper and transcribed manually back into the spreadsheet
MS-Access, MS-Excel or standalone web-based bug-tracking system for tracking issues and defects
Automated testing is done with a variety of tools depending on the platform and language being tested (Java vs. .NET, web vs. client-server)

5. QA Testing Challenges This leads to the following challenges:
Processes are ad-hoc and not repeatable across projects
There is no visibility between test cases, requirements and defects. How do you know when you are truly ‘done’?
Measuring progress and productivity during testing is time consuming and difficult
It’s hard to share information across the project and get real-time metrics regarding the quality of the system being tested
There is no central repository of test results from all sources – both automated and manual
SpiraTeam is explicitly designed to address these issues and provide an integrated solution

6. Why Agile Methodologies?
Traditionally projects are delivered in a series of phases that are based on increasing levels of certainty around the system being built:
However this approach has some drawbacks:
It is not flexible to changes in customer requirements
Time is wasted building features that nobody needs
The end user cannot give feedback till it’s completed coded
You don’t know how stable the system is until the end
Traditional Waterfall Methodology
Requirements
Gathering
Business Design
Technical Design
Systems Development
Unit
Testing
Integration
Testing
Acceptance
Testing (UAT)
Release Complete

7. Traditional Waterfall Methodology
The Agile Approach
Instead of phases, projects are broken down into releases and iterations. At the end of each iteration you have a fully functioning system that could be released:
Traditional Waterfall Methodology
Requirements
Gathering
Business Design
Technical Design
Systems Development
Unit
Testing
Integration
Testing
Acceptance
Testing (UAT)
Release Complete
Agile Methodology
Limited Upfront Planning
Release #1
Release #2
Release #3
Release #4
It 1
It 2
It 3
It 4
It 5
It 6
It 7
It 8
It 9
It 10
It 11
It 12
Release Complete
Iteration N
Iteration Planning
Development, Continuous Integration, Unit Testing, Functional & Acceptance Testing

8. The Agile Approach (3)
The requirements for the project do not have to be codified upfront, instead they are prioritized and scheduled for each iteration:
The requirements are composed of ‘stories’ that can be scheduled into a particular release and iteration
Release Plan
Iteration
Tested,
Integrated
Working
System
Iteration
Scope
Iteration
Plan

9. The Agile Approach (3) There are several different agile methods:
Scrum
Extreme Programming (XP)
Agile Unified Process (AUP)
Dynamic Systems Development Method (DSDM)
They have specific features that make them better suited to different situations, but in general, they follow the same basic agile principles*:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
*Source: Agile Manifesto -

10. The Existing Project Management Toolkit
Traditionally, Software Development organizations use the following tools to manage their lifecycles:
Requirements stored in MS-Word documents, MS-Excel spreadsheets or expensive tools such a RequisitePro, Doors
High-level project plan (GANTT chart) developed in tools such as Microsoft Project, Primavera and printed out for reference
Project estimates prepared using a combination of the high-level project plan and specialized standalone MS-Excel spreadsheets
Detailed schedules maintained by individual team members using MS-Excel, Whiteboards or Groupware solutions
MS-Access, MS-Excel or standalone web-based bug-tracking system for tracking issues and defects

11. Project Management Toolkit Challenges
As the static project plan with its discrete phases has become replaced by the more flexible agile approach, the old set of tools no longer works:
The project requirements and scope are not locked-down so the schedule of releases and iterations needs to be connected to the requirements backlog in real-time
The project schedule is constantly evolving, with stories being reallocated to different iterations and team members re-estimating the number of stories they can complete (velocity)
Defects and stories need to be managed in the same environment, with the project estimates and schedules taking account of both at all times
SpiraTeam is explicitly designed to address these issues and provide an integrated solution

12. SpiraTeam® Overview

13. Product Overview
Instead of having to buy separate requirements management, quality assurance and project management solutions, SpiraTeam provides a complete Lifecycle Management solution in one package.
SpiraTeam manages your project's requirements, tests, stories, release plans, iteration plans, tasks and bugs/issues in one environment. Since it’s web based, teams can collaborate in real time and have up to the minute visibility of the project’s status.

14. Why Choose SpiraTeam?
The top reasons that our customers choose SpiraTeam over other solutions are:
It is a complete solution that includes requirements management, test case management, release planning, iteration planning, task estimation and defect tracking all fully integrated from day one.
Highly intuitive web application that provides a complete picture of a project’s status and health yet requires only a web-browser.
Methodology Agnostic – SpiraTeam can be used equally web for any agile methodology – including Scrum, AUP, XP, DSDM
Ability to leverage your existing technology investments. SpiraTeam integrates with many automated testing solutions, software configuration management (SCM) and third-party defect-management systems.
In addition, we provide superb technical support that ensures that enquiries and questions are dealt with in a timely and professional manner.

15. Feature Snapshot
Listed below are some of the many great features that makes SpiraTeam the leading choice of ALM solution for companies and organizations worldwide:
Develop high-level requirements with initial estimates
Create, edit and execute test-cases
Track bugs, enhancements, risks and issues
Map tests to requirements to track coverage
Prioritize and schedule requirements for each release
Determine resourcing levels to deliver required features
Link bugs to test steps during test execution
Drill down from requirements to tests and incidents
Load-balance project resources to maximize project velocity
Track issues and defects against project schedule
Personalized dashboards and customizable reporting
Integrated web-based document management.

16. Competitive Landscape
We believe that SpiraTeam offers an unbeatable combination of capability and affordability:
Source: Inflectra Corporation, 2010
Niche Players
Challengers
SpiraTeam
XPlanner
Mingle
ScrumWorks
CollabNet Team Forge
AcuNote
Affordability
TargetProcess
Version One
Rally Enterprise
Uncompetitive
Incumbents
Breadth of Features / Capability

17. Representative Customers
The following are some of the organizations who are using SpiraTeam to manage their application development lifecycles:
Energy & Industrial
Financial & Business Services
Government
Information Technology
Healthcare & Bio-Technology
Telecommunications
Retail & Consumer Goods
Transportation & Hospitality

18. Testimonials
"... Great features, such as integration into JIRA and Bugzilla, for issue tracking. Clean layout. Great price for the product and great customer support. I really recommend SpiraTeam. I have tested it thoroughly and found it to be just what our company was looking for. ...“ - Zeb Anderson - Mortenson Construction
“…I really love this tool it does exactly what I need as a QA manager and gives me a lot of flexability. The best part is the service. From the phone support to the responsiveness of the development team I could not be happier with this purchase. This is the first application I have ever used that I could say that about. If you are looking for a tool to track Requirements, Releases, Test Cases, and Defects this is what you are looking for.
For me I look for a tool that allows me to get my job done faster and still provide me the data I need. This tool does that and with the enhancements that are planed it will actually be very valuable for other portions of our company. The other thing I look for is a responsive customer & tech support team. Inflectra has hands down the best support teams I have ever worked with. Makes all the difference when you can tell them what you need to product to do and the actually address your needs...“ - Daniel Hauser of RegEd

19. Approach for Using SpiraTeam (1)
The first step is to define the high-level project requirements:
This is a hierarchical list of all the features that the system needs to fulfill (in some methodologies these are called user stories)
They can be entered by hand, imported from Excel, or loaded from other tools like Jama Contour or Enterprise Architect
The next step is to create the project’s high-level schedule:
Include the major releases, minor releases and optionally builds and iterations depending on desired granularity
You can now assign the different lower-level requirements to each of the iterations so that it is possible to start planning the features that will be developed in each iteration
Requirements & Release Plan

20. Approach for Using SpiraTeam (2)
Now you can create the test plan
This consists of a hierarchical list of test cases organized into folders. Each test case can have multiple test steps.
Each test case can be mapped to one or more requirements – this is used to specify the test coverage of the various requirements.
Any requirements that have no covering tests are a project risk and additional covering tests should now be written
The tests can be entered by hand or imported from Excel.
Finally you can also map the test cases to the releases to provide regression testing capability
Requirements & Release Plan
Test Plan
Creation

21. Approach for Using SpiraTeam (3)
Now you start the iteration planning:
Decompose the requirements into detailed project tasks that can be prioritized and individually estimated. These estimates can be then compared against the top-down requirement estimate
Potentially re-assign the requirements and tasks to different iterations, if there is not enough time/resources to support the planned functionality
Assign any defects that were raised in the previous release/iteration into the current iteration for resolution
In some methodologies (Scrum) this is called ‘sprint planning’
Requirements & Release Plan
Test Plan
Creation
Iteration Planning

22. Approach for Using SpiraTeam (4)
Now you can schedule the team members and load balance the task resourcing allocation:
Assign the discrete project tasks and defects to the members of the development team staffed to the iteration
Create and assign test sets to the various testers. Each test set contains a group of test cases that need to be executed.
Team members view their individual schedule and task assignments to determine if they can perform all the tasks
The detailed task schedule is updated by the team members, with the release/iteration schedule reflecting the updates so that the management can make changes to the master schedule
Requirements & Release Plan
Test Plan
Creation
Iteration Planning
Schedule & Resourcing

23. Approach for Using SpiraTeam (5)
Real-time status of the progress of the iteration and release is visible by the management during development and testing:
The team members update the status and actual effort values for their assigned test sets, tasks and incidents.
When tasks and tests are completed, or if exception conditions occur (late starting tasks, late finishing tasks, overruns, etc.), the status of the overall iteration and release is updated to give early indication of needed management intervention
During the test runs, test failures can be used to automatically generate new defects that are managed by the incident tracker
Requirements & Release Plan
Test Plan
Creation
Iteration Planning
Schedule & Resourcing
Tracking & Testing

24. Feature Walkthrough

25. Personalized ‘My Page’
Upon login to SpiraTeam, you are presented with a personalized ‘dashboard’ of all your key information.
This provides a consolidated view of all the artifacts that are of interest to you with information to let you know what action needs to be taken.
RSS Feeds of your information are available.

26. Project Home Page
Each project has a dashboard home-page that summarizes all of the information regarding the project into a comprehensive, easily digestible form.
It provides a “one-stop-shop” for people interested in understanding the overall status and health of the project at a glance.

27. Project Portfolio Management
Projects in SpiraTeam can be organized into Project Groups that belong to a common organization, customer or division. This allows you to view a summary project group dashboard that lets you view the aggregate status of the group as whole as well as compare the relative health of the different projects in the group:

28. Requirements Management
You have the ability to create and manage project requirements, user stories and use cases in a hierarchical organization. Requirements can be prioritized, estimated and also associated with a specific release. Each requirement is displayed with its associated test coverage and task progress.

29. Requirements Test Coverage
Each requirement is mapped to one or more test cases that can be used to validate that the functionality works as expected.

30. Requirements Elaboration (Tasks)
Each requirement can then be decomposed into its low-level assignable work items called ‘tasks’. Each can be separately estimated to validate the overall high-level requirement estimate.

31. Test Case Management
SpiraTeam provides the ability to create, edit and delete project test cases that are stored in a hierarchical folder structure. You can move, copy and filter the test cases according to a variety of criteria.

32. Manual Test Cases - Editing
Each test case consists of a set of test steps that represent the individual actions a user must take to complete the test.
You can include other template test cases as steps within your test case. This allows you to build a library of reusable test components.

33. Manual Test Cases - Execution
You can execute groups of test cases - along with their test steps – so that the testers can follow the instructions and determine if the system being tested behaves as expected. Optionally a new incident can be raised in the system – linked to the test step failure

34. Automated Testing – Test Scripts
You can attached test automation scripts to test cases in SpiraTeam.
SpiraTeam supports a wide variety of test automation engines (both commercial and open-source) including Rapise, QTP, Squish, LoadRunner TestComplete and Selenium.

35. Automated Testing – Test Hosts
The automated test scripts managed in SpiraTeam can be either executed on the local machine or scheduled for execution on a series of remote hosts.
Using Inflectra’s RemoteLaunch™ technology, you can manage an entire global test lab from a central SpiraTeam server, with test sets being executed using a variety of different automation technologies 24/7.

36. Test Set Organization
To make it easier to assign and track the execution of test cases, SpiraTeam allows you to optionally group the test cases into test sets that can be assigned as a ‘package’ to individual testers or automation hosts.
Each test set can be associated with a particular release for testing, and you can quickly see the execution status of each test set in one consolidated view.

37. Test Run Tracking
Every time you execute a test case, SpiraTeam records every pass / failure as well as the associated incidents generated as a ‘Test Run’. These archived Test Runs can be viewed to determine if changes to the system have introduced failures to previously working functionality.

38. Release Planning
You have the ability to create a master release schedule containing all the major milestone releases together with the individual iterations – smaller releases of the system delivered every 4-6 weeks.

39. Product Backlog Planning
The list of user stories, requirements, defects and features is called the Product Backlog. SpiraTeam lets you organize the backlog by component, package or priority. You can order and categorize them by simple drag and drop editing. This is called backlog grooming.

40. Sprint / Iteration Planning
The requirements (user stories), tasks, test cases and outstanding incidents (bugs, issues) can be scheduled against the different iterations / sprints in the release.
The system will calculate the available effort as requirements are added.

41. Kanban & Scrum Agile Planning Boards
The Planning Board allows teams to view the story cards by iteration, status or person for a given release or iteration. The allows you to manage the number of backlog items at each stage of the process and also load-balance the members of the project team.

42. Task Progress Tracking
SpiraTeam provides the ability to track the progress of the tasks in the system and determine if tasks are suffering from schedule overrun or misestimation. In addition you can compare actuals for continuous process improvement.

43. Build Management
SpiraTeam provides the ability to integrate with continuous integration build servers such as Hudson and CruiseControl so that the status of builds can be recorded in SpiraTeam and linked to source code revisions, incidents and test runs. This provides traceability for each build, so that you can see what was changed in each build, what was tested and what was fixed.

44. Resource Tracking
Once the requirements, tasks and incidents have been scheduled against the iteration plan, you can use the Resource Tracking screens to view the total assigned workload for the members of the project and determine the resource assignments and perform load balancing if necessary.

45. Bug / Issue Tracking
The system provides the ability to create, edit, assign, track, manage and close incidents (i.e. bugs, issues, risks, defects, enhancements) that are raised during the testing of the software system under development.

46. Incident Traceability
Unlike a standalone bug tracking tool, you can trace the defects back to the test case and the underlying requirement that generated them, giving the project manager unprecedented power in analyzing the “in-process” quality of a system during its lifecycle.

47. Document Management
All documents and web links uploaded to the system are available in the integrated document management system. This allows you to organize the documents into folders, categorize by document types and associate with meta-tags. Once uploaded, users can search, sort and filter the documents as well as find dynamically related items through the meta-tag hyperlinks.

48. Document Version Tracking
Once uploaded to the central knowledge repository, revisions to the documents can be uploaded so that there is complete audit trail of all changes made to artifacts and associated documentation in the project.

49. Instant Messaging & Collaboration
SpiraTeam includes an integrated instant-messenger that lets users collaborate and communicate in real-time regardless of geographic location. The discussions can be codified and tagged against specific artifacts in the system, so that they become part of the artifact discussion thread.

50. Software Configuration Management (SCM)
SpiraTeam allows you to link your existing software configuration management (SCM) repositories to a particular project. When this is done, you can browse the contents of the repository (folders, files and revisions) directly in the SpiraTeam web interface.

51. Source Code Integration
In addition to being able to view the source code repository, using SpiraTeam you can link artifacts to specific source code revisions. This allows you to associate requirements, tasks or defects/incidents with the corresponding code changes. This provides end-to-end traceability from requirements to working software code.

52. Attachments & Screenshot Capture
You can upload document attachments and web links to all artifacts (requirements, test cases, tasks, incidents, etc.) in the system. Each of these artifacts includes an attachment view that allows users to view the existing attachments, delete an existing attachment and upload new documents from their workstation.
In addition, there is a built-in screen capture utility for quickly adding screenshots to a test execution or incident report

53. Customizable Reporting Dashboard
SpiraTeam includes an extensive reports library that can display information such as Requirements Traceability, Test Case Execution, Release Notes, Task Progress and Incident Status.
SpiraTeam allows you to build a customized reporting dashboard featuring your frequently-used graphs, charts and reports.
The graphs available include: Requirements Coverage, Test Run Progress, Incident Discovery, Project Velocity, Task Burndown and Burnup.
Supported formats include HTML, XML, Word, Excel.

54. Change History Tracking
All of the changes made to a particular artifact in the system are tracked by SpiraTeam, so that at any time you can view the complete audit trail of all the changes made to an artifact, including the date of the change, who made the change, and what information was changed.
SpiraTeam features full version-control capabilities that allow you to rollback specific changes and revert the artifact back to a prior revision.

55. Timecard Submission
SpiraTeam includes a built-in timecard entry system that lets developers quickly and easily enter the time spent each day on their assigned tasks and incidents.

56. Custom Properties
In addition to the built-in fields that are associated with each type of artifact, you can also define custom properties for each type of artifact in the system.
The system supports a variety of different field types including: text, rich-text, dropdown lists, user selectors, and date-fields

57. Customizable Incident Fields
You can customize each of the fields used in the Incident tracking module to suit your own business needs - including incident type, status, priority and severity. You can even associate your own color schemes with the different priorities and severities.

58. Customizable Workflows & Notifications
Different types of incident, requirement and task can follow their own customized workflow. This allows you to tailor SpiraTeam to the business processes used by your organization. Each workflow consists of a customizable set of steps and transitions.
In addition each transition can be used to send notifications to the detector, owner or users in a certain project group.

59. Artifact Associations
Each artifact can be linked to an unlimited number of other requirements, incidents and source code revisions, providing traceability between related artifacts. For example a change request incident that turns into a new requirement can be associated to preserve the pedigree of the requirement.

60. Support for Mobile Devices
SpiraTeam provides a mobile web interface that allows users of smartphones, tablets and other mobile devices to view their dashboard of assigned test cases and execute their tests using the mobile device.
During test execution, you can attach screenshots to failed tests using the device’s built-in camera, providing additional context.

61. Integration
SpiraTeam has a built-in notification engine that lets you define custom templates and notification events. This enables the system to send out notifications when specific events occur (e.g. user is assigned a test case, the priority of a requirement changes, etc.).
In addition, SpiraTeam can connect to your system and retrieve users’ comments and attach them to the appropriate artifact in the system. It can also create new incidents directly from s, saving users’ time.

62. Visual Studio & Eclipse IDE Integration
Developers can work on assigned requirements, tasks and incidents directly inside their Integrated Development Environment (IDE).
SpiraTeam has plug-ins available for both Eclipse and Visual Studio.
Research has shown that allowing developers to use the same tool to develop their code and manage their workload enhances efficiency and improves data accuracy.

63. Integration / Migration Options

64. Software Configuration Management
Integration Overview
SpiraTeam has a very flexible architecture and has been integrated with a variety of external tools and systems:
SpiraTeam
Requirements
Test Cases
Releases
Iterations
Defects
Tasks
Various Tools
Requirements
Defect/Issue Tracking Tools Bugzilla, TFS,
FogBugz, JIRA,
Mantis, etc.
Software Configuration Management
Subversion,
CVS, Git,
TFS, VSS
MS-Office
Legacy Data
Automated Testing Systems
xUnit
Unit Testing
Rapise
Functional Testing
Various Tools
Functional Testing
Various Tools
Performance & Load Testing

65. Automated Functional & Load Testing Tools
Functional testing tools:
Inflectra Rapise® functional testing system
HP QuickTest Pro™ functional testing system
Selenium IDE and WebDriver functional testing framework
TestComplete™ and Soap-UI from SmartBear
Squish® multi-platform test automation system
SmarteScript™ functional testing system
Ranorex functional testing system
Rational Functional Tester (RFT)
FitNesse open-source testing framework
Load/Performance testing tools:
HP LoadRunner load-testing system
Neotys NeoLoad load testing system
JMeter open-source Load Testing System

66. Automated Unit Testing Tools
SpiraTeam can integrate with a variety of automated unit testing tools and frameworks:
NUnit and MS-Test frameworks for .NET
JUnit & TestNG frameworks for Java
PyUnit framework for Python
TAP framework for Perl
PHPUnit framework for PHP
Test::Unit framework for Ruby

67. Integration with Build Servers
SpiraTeam® is able to connect to your continuous integration (CI) build server to link tests and defects with continuous builds:
Currently Available:
Hudson
Jenkins
Planned:
CruiseControl
TeamCity
Atlassian Bamboo

68. Integration with Bug-Tracking Systems
SpiraTeam® is able to leverage your existing investments in bug / issue tracking systems:
Current
Synchronize incidents with Atlassian JIRA
Synchronize incidents with Bugzilla
Synchronize incidents with FogBugz
Synchronize incidents with Mantis
Synchronize incidents with Microsoft Team Foundation Server
Synchronize incidents with AxoSoft OnTime
Synchronize incidents with IBM Rational ClearQuest and RTC

69. Integration with Requirements Mgt Systems
SpiraTeam® is able to leverage your existing investments in requirements management and UML modeling systems:
Synchronize requirements with IBM Rational RequisitePro
Synchronize requirements with Sparx Enterprise Architect
Synchronize requirements with Jama Contour
Synchronize requirements with IBM DOORS
Synchronize user stories with Version One

70. Integration with SCM Systems
SpiraTeam® is able to leverage your existing investments in Software Configuration Management (SCM) systems:
Current:
Integration with Subversion repositories
Integration with CVS repositories
Integration with Microsoft TFS repositories
Integration with Microsoft VSS repositories
Integration with Mercurial distributed repositories
Integration with GIT distributed repositories
Integration with Perforce repositories
Planned
Integration with Rational ClearCase repositories
Integration with StarTeam repositories

71. Integration with Developer IDEs
SpiraTeam® is able to integrate with your developers’ Integrated Development Environment (IDE):
Ability to manage requirements, tasks and incidents inside Microsoft Visual Studio
Ability to manage requirements, tasks and incidents inside the Eclipse IDE

72. Data Migration Options
SpiraTeam makes it easy to import data from a variety of existing legacy data sources:
Import requirements, test cases, incidents and test runs from any software package capable of exported in MS-Excel, MS-Word or MS-Project formats
Import requirements, test cases, incidents and test runs from HP QualityCenter and Mercury TestDirector.

73. Please contact sales@inflectra.com if you have additional questions.

74. Legal Notices
DISCLAIMER: All product comparison diagrams have been made on the basis of information available on respective product websites. The analysis and views expressed in the diagrams and the information made available are purely those of Inflectra Corporation.  It is possible that competing products have additional features not mentioned on the product websites.