A presentation by Adam Sandman.

1. Spira Concepts
How We Designed
Spira To Be Used
(aka Spira 101)
@Inflectra | #InflectraCon

2. Adam Sandman
Director, Inflectra
Programmer from the age of 10
Working in the IT industry for over 20 years
Adam lives in Washington, DC, USA
@adammarksandman

3. Session Objectives
We will walk through the overall workflow for using
Spira: creating products and programs, setting up a
product with artifacts and customizations.
The product configuration will cover the full
application lifecycle, including requirements, test
cases, tasks, releases, sprints, risks, and incidents.

4. SpiraPlan®
Agile Program & Portfolio Management
SpiraTeam®
Application Lifecycle Management (ALM)
The Inflectra® Product Suite
SpiraTest®
Requirements, Test Management
& Bug Tracking
KronoDesk®
IT Support & Help Desk Ticketing
Rapise®
Test Automation (Web, GUI, Services)
TaraVault® - Source Code Management

5. The Spira™ Platform
SpiraPlan®
Agile Program & Portfolio Management
SpiraTeam®
Application Lifecycle Management (ALM)
SpiraTest®
Requirements, Test Management
& Bug Tracking
KronoDesk®
IT Support & Help Desk Ticketing
Rapise®
Test Automation (Web, GUI, Services)
TaraVault® - Source Code Management

6. Philosophy of
Spira

7. Productivity from Day One
•Less Time Doing: •More Time Doing:
No plugins, customization or
configuration needed day one

8. If all you have is an ‘issue’ tracker…
Then everything is an issue…

9. Some Design Decisions
Unique artifacts (requirement, test case)
Default workflows and standard fields
Orchestration and workflow between
artifacts (vs. customizability)

10. 1. Getting Started

11. Approach to using Spira
1. Create Product
2. Add Users to Product (Membership)
3. Follow Product Workflow:
Requirements
Planning
Test
Planning
Sprint
Planning
Schedule &
Resourcing
Tracking &
Execution

12. Administration Menu

13. Administration – Add Product

14. Administration – Add User

15. Administration – Membership

16. 2. Requirements Planning
Requirements
Releases
Sprints

17. Artifact Relationships
ReleaseRequirements
Requirement Step
Requirement Step
Requirement Step
Sprint
Sprint
Sprint

18. Requirements Creation

19. Requirements Planning

20. 3. Test Planning
Test Cases
Test Steps

21. Artifact Relationships
Requirements Test Case
Test Step
Test Step
Test Step
Release

22. Test Case Management

23. Test Step / Script Creation

24. Test Coverage

25. 4. Sprint Planning
Requirements
Sprints
Tasks
Incidents

26. Artifact Relationships
ReleaseRequirements
Task
Task
Task
Sprint
Sprint
Sprint
Incident

27. Requirements – Task Elaboration

28. Sprint Planning

29. Sprint Planning

30. 5. Scheduling &
Resourcing
Tasks
Incidents
Test Sets

31. Artifact Relationships
ResourcesSprint
Test Set
Task
Incident
Resource
Resource
Resource

32. Test Scheduling – with Test Sets

33. Task Scheduling

34. Incident Scheduling

35. Resource Management

36. 6. Tracking &
Execution
Tasks
Incidents
Risks
Test Runs

37. Artifact Relationships
Resource
Test Run
Task
Incident
Risk
Requirements
Incident
Task

38. Test Execution

39. Task Tracking

40. Risk Management

41. Incident Tracking

42. Wrap Up

43. Key Takeaways
1. Spira has been designed to minimize
configuration time and maximize productivity
2. It has a range of specialized artifacts that
work together across the lifecycle
3. You should use the features of the system that
make sense for your project scope/size

44. Questions?