Inflectra News Feed: BlogPost

Responsible AI Starts with Respect for Customer Data

2026-04-20T13:47:57-04:00

Inflectra’s Position Is Clear: Customer Data Should Not Be Repurposed for Shared Model Training

At Inflectra, we believe AI should help customers work faster, test smarter, and reduce risk without turning their operational data into shared training fuel. Our Responsible Artificial Intelligence Statement is explicit: we prioritize ethical standards, privacy, and security. In addition, our policy protects user data in accordance with applicable laws and regional restrictions; encrypts data at rest and in transit; and does not use user input or processed data for base AI model training. Our policy also states that strict internal controls are in place so sensitive, confidential, and personally identifiable information is not stored in AI systems in ways that expose it to misuse or unauthorized access.

Why This Distinction Matters for Enterprise Teams

For many organizations, project artifacts are not generic content. They are roadmaps, requirements, defects, release discussions, internal priorities, customer commitments, test evidence, and audit-sensitive records. Even when vendors describe contributed data as de-identified or aggregated, many enterprises still see governance, sovereignty, contractual, and trust issues whenever customer activity is repurposed to improve services for everyone else. As a comparison, Atlassian’s published materials say contributed data may include both metadata and in-app data, and that some contributed data may be retained for up to seven years.

AI Value Should Not Come at the Cost of Data Control

Our position is simpler: your data should be used to serve you, not mined to improve a shared model for the broader market. Our approach to AI is grounded in transparency, access control, privacy protection, and accountable governance. We use AI to enhance customer outcomes, but we do not believe customers should have to trade away control of their data to receive those benefits.

The Right Questions to Ask Any AI Software Vendor

This is especially important for organizations operating in regulated, security-conscious, or IP-sensitive environments. When teams evaluate AI-enabled application lifecycle management, testing, and quality platforms, they should be asking more than whether a feature is impressive. They should ask:

What data is being collected?
What is the default setting?
Can it be fully disabled?
How long is it retained?
Is it used for model training?
And who ultimately benefits from that use?

Atlassian’s new policy makes those questions impossible to ignore.

Inflectra’s Commitment to Responsible AI

At Inflectra, our answer is clear. We are committed to responsible AI that strengthens quality, compliance, and productivity without compromising customer trust. We believe AI should be powerful, practical, and privacy-respecting. Customers should get the benefits of innovation without wondering whether their own data is quietly being repurposed behind the scenes.

That is the standard we believe enterprise software vendors should meet. And it is the standard Inflectra intends to keep.

XXXspiraplandemoXXX

The Missing Guardrail for Non-Deterministic AI: Highlights from the SureWire™ Beta Unveiling

2026-04-17T12:24:44-04:00

The Silent Revolution: Building Without Validating

A major theme of the launch was the conspicuous silence in the industry regarding AI safety. While every organization is currently fixated on how to construct AI agents, there is a widespread lack of discussion regarding the rigorous validation required to ensure they perform exactly as designed.

Organizations are racing to deploy these digital workforces, yet the infrastructure to verify their performance has been largely missing. We have entered an era where agents collaborate on complex tasks; however, since these agents operate probabilistically, standard static test scripts are no longer sufficient to ensure reliability. Deploying unverified agents isn't just a technical oversight—it’s a massive organizational liability.

The Unregulated Frontier of AI Agents: The High Cost of Settling

Adam Sandman described the current AI revolution as a transformative journey similar to the birth of the web browser in the 1990s. To illustrate the potential consequences of inaction, Adam shared sobering real-world examples of what happens when agents are released without proper oversight—scenarios that could easily impact your organization if your agents are not tested:

Unauthorized Actions: An airline was legally forced to honor a fictitious refund policy invented by its chatbot.
Data Leakage: A major health insurer suffered a massive breach when a chatbot leaked sensitive personal and medical records.
Legal Disruption: A law firm faced disbarment and sanctions after an agent cited court cases that did not exist.
Financial & Reputational Ruin: From support bots accidentally causing customer churn to AI systems making prejudiced remarks in public.

Without dynamic testing, your organization remains exposed to adversarial risks, behavioral drift, and the unpredictable nature of non-deterministic reasoning.

Introducing SureWire™ Beta: Testing AI Like the Real World

SureWire was built to close the reliability deficit by deploying specialized AI testing agents to audit your AI. Core platform capabilities include:

Feature	Description
Bespoke Testing Agents	Dynamically probes your AI based on specific requests to surface hidden vulnerabilities.
Judge Agents	Applies probabilistic evaluation to create repeatable metrics for response quality.
Domain Specialists	(Coming Soon) Expert agents specialized in tone, security, and behavioral drift for regulated industries.

The Workflow: Users describe their AI agent and their specific concerns. SureWire then creates a detailed plan, generates diverse test data, executes the probes, and delivers a clear, actionable report on quality and risk.

Hands-On with SureWire™ Beta: A Look at the Beta Platform

During the live demonstration, Simon Bor showcased how SureWire provides the documented evidence required for industries where a simple confirmation of completion isn't enough.

Pre-Built Scenarios: Users can test flawed templates, such as The Overconfident Agent, which highlights how bots can provide dangerously incorrect information with complete certainty.
Custom Demo Chatbot: Define a System Prompt to set a specific personality and then describe exactly what needs to be validated, such as tone consistency.
Test Your Own Chatbot: Direct integration via a public API Endpoint allows builders to execute dynamic testing plans against their live production or staging environments.

Your Spot in the Early Access Program is Free—The Risk of Skipping it Isn't

The SureWire™ Early Access Program is officially live. Inflectra is inviting engineers, QA leads, and AI builders to get ahead of the reliability challenge before it becomes a crisis.

Early Access Benefits:

Free Access for the full beta period—no credit card required.
Preferred Pricing once General Availability is reached.
Founding Member Recognition with an Early Access badge.

Ready to secure your agents? Visit beta.surewire.ai to join the program today.

13 Things Traditional QA Can’t Catch (But SureWire™ Can)

2026-04-17T12:25:00-04:00

Core Capabilities & Testing Scope

What types of AI agents can SureWire test? In the current beta, SureWire beta is designed to test chatbots and conversational AI agents — either via your own public API endpoint or using Inflectra's built-in demo agents. Future versions will expand support to a broader range of agentic systems and deployment models.
Can SureWire detect PII leakage? Yes, PII detection is one of SureWire's supported use cases in the current beta. PII is relatively well-defined and structured, making it a strong candidate for automated detection. SureWire can flag when an agent appears to be leaking personally identifiable information during testing, allowing teams to address it before production deployment.
Can SureWire compare different AI models side by side? Yes — with some configuration. In the beta, you can connect two separate API endpoints (each using a different foundation model) and run the same test against both. This allows meaningful model comparisons. More streamlined, built-in model comparison features are planned for future releases.
Is testing done entirely via prompting? Yes. You write a natural-language test plan, SureWire deconstructs it into an internal testing strategy, generates prompts to send to your agent, and evaluates the responses. The entire workflow is designed to be accessible to non-technical users, while still producing rigorous, repeatable results.
Can SureWire be used to analyze documents not created by AI? SureWire is currently optimized for testing AI agents, not static document analysis. For requirements analysis and intelligent document processing, Inflectra's SpiraTest platform (including the recently announced Inflectra AI roadmap for Spira) may be a better fit.

Understanding Scoring & Metrics

How does the Quality Score work? SureWire uses a qualitative scale of 0 to 100, where 100 represents excellent performance and 0 represents complete failure. Importantly, what "quality" means is specific to each test run — it's based entirely on what you ask SureWire to evaluate. Testing for refund policy accuracy will produce a different quality result than testing for polite tone, even against the same agent.
How is the Confidence Score calculated? The confidence score reflects the variance across individual test outputs. If results are highly consistent — whether the agent consistently passes or consistently fails — confidence will be higher. A lower confidence score typically indicates a small sample size or mixed results. In the beta, the default number of test runs is limited, but increasing the volume of test executions will improve confidence levels.

Data Integrity, Privacy & Security

Will SureWire get smarter over time with use? The team is actively exploring personalized learning capabilities, where SureWire can adapt its assessment weighting based on familiarity with your specific agents and testing patterns. However, data privacy and security are top priorities, and any such capability will be implemented carefully to ensure your data remains fully protected.
Can SureWire validate agent responses against a database or document? Not in the current beta. This capability requires SureWire to have access to your data sources — raising important questions about security, data residency, and trust boundaries. The team is actively designing architectures that would allow this safely, potentially including deployment models where SureWire runs within your own protected environment.
Does SureWire comply with specific AI risk or quality standards? The beta uses an internal quality model developed by the Inflectra team. Support for established regulatory frameworks and standards — as well as the ability to define your own risk criteria or integrate your organization's policy documents — is planned for future releases.

The Roadmap: Future Features & Scalability

Does SureWire detect hallucinations? Hallucination detection is on the roadmap but is not yet available in the beta. Accurately detecting hallucinations requires grounding data — information SureWire can use to validate whether an agent's response is accurate. Expanding this capability is a key priority for the path to General Availability.
Can I run multiple test scenarios in parallel? Not yet in the beta, but this is a planned capability. Future versions will support parallel test execution with weighted results feeding into an aggregated quality report.
What's on the roadmap? The team has an ambitious vision for SureWire's first year and beyond, including: integration with CI/CD workflows, MCP server support for developer tooling (such as Kiro, Cursor and Claude Code), red teaming for security vulnerabilities, specialist agents for industry-specific risk frameworks, and more dynamic, iterative testing sessions that go deeper when problem areas are identified — similar to how a human red team would operate.

Ready to get started? Visit surewire.ai to join the beta and help shape the future of AI agent quality assurance. If you have any questions, do not hesitate to contact us.

Inflectra at AWS BOX Riyadh 2026: Securing the MENA Region's Applied AI Future

2026-04-01T11:58:47-04:00

Having a physical presence on the ground in KSA is no longer optional for tech leaders—it is absolutely crucial. With AWS announcing a massive $5.3 billion investment in the new 2026 KSA Region and a $5B+ joint "AI Zone" investment with HUMAIN, the infrastructure is scaling at breakneck speed. Furthermore, an incredible 98% of organizations surveyed in the UAE and KSA are planning to invest heavily in AI. The region is skipping legacy hurdles and building the future from scratch. Inflectra is proud to be on the ground, helping to secure the foundation of this massive digital acceleration.

As regional leaders and top-tier AWS partners gathered in Riyadh, the BOX program conversations confirmed exactly why Inflectra’s application lifecycle management (ALM) and quality assurance platforms are mandatory for this new era:

The "Agentic AI" Era Demands Uncompromising QA: We are moving rapidly past basic generative AI. By 2028, 33% of enterprise software applications will include agentic AI, and 15% of day-to-day work decisions will be made autonomously. When AI agents are autonomously executing tasks and making decisions, traditional testing is not enough. You need absolute traceability, rigorous compliance, and advanced lifecycle management to ensure these autonomous systems do not introduce catastrophic risks. Inflectra provides the guardrails that make Agentic AI safe for the enterprise.
The Shift to Line-of-Business (LoB) Buyers: The cloud conversation has moved out of the IT basement and into the boardroom. Today, 60% of all IT spend comes from Line of Business budgets. LoB executives—CEOs, CFOs, and Operations Heads—do not buy technology; they buy guaranteed business outcomes. AWS is driving this through the "Power of 3," uniting consulting, distribution, and technology partners. By integrating Inflectra into these multi-partner SaaS solutions, we ensure that the business outcomes promised to LoB buyers are delivered flawlessly, without bugs, delays, or compliance failures.
High-Stakes Verticals Require Absolute Resilience: The specialized industry tracks in Riyadh highlighted the staggering scale of modernization. In the GCC Energy sector alone, we are tracking a $68B+ digital transformation, heavily relying on advanced AI and the Industrial Internet of Things (IIoT). Meanwhile, the Financial Services sector is deploying AI for highly sensitive use cases like fraud prevention, credit decisioning, and regulatory compliance. In these highly regulated, mission-critical environments, software failure is not an option. Inflectra’s platforms ensure that as these industries adopt rapid SaaS models, they maintain bulletproof operational resilience.

The future of enterprise technology is being architected right now in the MENA region. Through strategic partnerships and a deep commitment to the area, Inflectra is perfectly positioned to ensure that the AI-driven, SaaS-first solutions of tomorrow are built on a foundation of absolute quality and trust.

Let’s Secure Your AI Future Together

Ready to lead the next generation of digital transformation in the MENA region? Whether you are navigating the shift to Agentic AI or managing high-stakes digital modernization in the Energy or Finance sectors, we are here to help.

Don’t let legacy hurdles or compliance risks slow down your acceleration. Contact our team to learn how our platforms can guarantee the business outcomes your organization demands.

Maximize Your Success: Leverage Inflectra’s Complimentary Worldclass Expert Support Services

2026-03-26T18:36:38-04:00

At Inflectra, we believe that world-class software deserves world-class support. Whether you are a long-time license holder or currently evaluating our solutions through a Free Trial Proof of Concept (POC), our mission is to ensure your ecosystem operates at peak efficiency. To help you achieve this, we invite you to take full advantage of our complimentary support services available at support@inflectra.com.

Expert Guidance for Complex Environments

In today’s fast-paced development landscape, maintaining a "single source of truth" is critical. We have customers using Rapise (self-healing codeless test automation) and Spira (SpiraPlan, SpiraTeam, SpiraTest) fo SDLC with integrations across 80+ commonly used software tools to ensure data integrity across their entire lifecycle. However, we understand that configuring these connections to meet specific business rules can be complex. For instance, if you are challenged in making the Jira-Spira data sync work exactly the way you want, you don’t have to navigate it alone.

Our Support Engineers are experts in fine-tuning synchronization patterns, ensuring that your requirements, tasks, and defects flow seamlessly between platforms. Or if you want Spira to connect to PowerBI for additional reports, your ServiceNow tickets, Azure DevOps (ADO), GitHub, GitLab code repositories. Let us know. Here is a list of all the free plug-ins to help you maintain always auditable single source of truth. You can even make enhancement suggestions that are considered during product roadmap meetings via this channel, attach screen grabs for tickets etc.

This help desk responds within 24 business hours and is backed by the very people who build and upgrade the solutions. For screen share services with an expert, check out our Premium Support packages or service accelerators.

Hear From Our Customers

Don't just take our word for it—our users consistently highlight the responsiveness and expertise of our team*:

"Best Customer Support in my 30-year career": "This is by far the best customer support I have ever experienced in my 30-year career in IT!" — Stephan Luik, Sr. Firmware Engineer, Ascom Wireless Solutions.
"Exceptional and Prompt": "I have found the support to be exceptional, with all of my queries being automatically logged pretty instantly and answers provided within 24 hours without exception." — Recent Testimonial from SpiraTest User.
"Top Notch Technical Service": "Their technical service is top notch—always responsive and spot-on in resolving any issues." — Testimonial from SpiraPlan User.
"They don’t stop until giving you the right answer": "Customer Service is great, they don't stop till giving you the right answer. I advise everybody to use SpiraTest." — Recent Testimonial from Automated Testing User. [see more Testimonals and Case Studies via www.inflectra.com]

Why Contact Our Support Team?

When you reach out to support@inflectra.com, you aren't just opening a ticket; you are gaining access to a team of product specialists dedicated to your success.

Zero Cost, High Value: This is a free service for all active license holders and those conducting a trial.
Technical Excellence: Our team possesses deep architectural knowledge of Spira and its 80+ integrations, helping you eliminate data silos and manual entry. We will handhold your journey to cloud migration to connect competitor products.
Tailored Solutions: We don't just provide generic answers; we work to understand your specific workflow challenges and Customised Reports to provide a bespoke path forward.

Your Single Source of Truth Awaits

Don't let a configuration hurdle slow your momentum. Whether you are syncing with Jira, automating with Rapise, or connecting to a DevOps pipeline, our experts are ready to assist you.

By leveraging our team, you ensure that your Inflectra Platform instance remains the robust, interconnected heart of your operations. We encourage you to reach out today at support@inflectra.com and let us help you optimize your integration, migration, or configuration needs. In addition, please connect with your account manager if you would like an introduction to an on the ground partner.

*Source: https://www.inflectra.com : https://www.g2.com

What Rapise 9.0 Self-Healing Looks Like in the Real World

2026-03-23T14:44:26-04:00

The test scenario

The scenario itself was intentionally simple: record a test that creates a new book in the original ASP.NET application, then see what happens when that exact same test is executed against the React implementation. Normally, this kind of migration is exactly where UI automation becomes fragile. Even when the business flow is identical, the underlying application structure is often completely different:

Control hierarchies change
HTML changes
IDs and classes change
and the object repository that worked perfectly in the first version no longer maps cleanly to the second.

That is the maintenance burden Rapise 9.0 is designed to reduce. This version introduces SmartActions as a self-healing layer that combines object descriptions with action intent expressed in natural language, then uses AI-based visual recognition and contextual analysis when the web locators fail.

This recovery process is multi-level:

Rapise first tries standard repository lookup
then AI-based recovery, and finally deeper intelligent resolution
after which it can generate patch files to update the repository for future runs.

Why this example matters

This is a useful example because the move from the ASP.NET version to the React version is not just a minor cosmetic update. It represents a front-end technology shift. From an automation perspective, that is usually where recorded tests become expensive to maintain. The user journey may still be “log in, go to books, add a new book, save,” but the UI implementation underneath can be radically different.

For example, the application shown above, looks completely different when it was modernized to React:

In older test automation models, that would usually mean going back into the test, relearning objects, editing locators, and repairing the repository by hand. In Rapise 9.0, the self-healing flow changes that experience. Because the recorded actions carry descriptive intent, the test has more context about what it is actually trying to do, not just which technical object it originally found.

For example, the login button has the following intent:

What happened during playback

When the recorded ASP.NET test was played back against the React version, Rapise was able to continue execution using self-healing. That is the important point. The test was not tied so rigidly to the original implementation that it simply failed at the first UI mismatch. Instead, Rapise used the SmartActions approach to interpret the action, inspect the changed interface, locate the equivalent elements in the React UI, and continue the scenario.

From an end-user perspective, this is where the feature becomes much easier to understand. Self-healing is not magic and it is not random guesswork. Rapise still begins with the normal learned objects and repository references. But when those no longer line up with the current application, it has another layer to fall back on. That fallback uses visual and contextual analysis to identify the correct element when the UI has changed.

In practical terms, that means a test step such as creating a book is no longer understood only as “click this exact stored object.” It can also be understood as “perform this action on the control that now corresponds to the original intent.”. That is what allows Rapise to adjust dynamically to changes in the UI - it knows what was the original intent of the user.

From healing to permanent maintenance reduction

The second half of the story is just as important as the first. After Rapise successfully played the test using self-healing, I was then able to apply the detected changes. Once those updates were accepted, the test could play back against the React application again without needing AI recovery. The updates are presented to the user in a simple to understand format where you can Approve or Reject them either individually or in bulk:

That is a critical part of the value proposition. Self-healing is not only about rescuing one execution. It is also about shortening the path back to stable deterministic automation. When SmartActions successfully recovers an object, Rapise can generate patch files that update the repository so future runs benefit from the healing without repeated AI intervention. A sample patch file is shows above.

For teams maintaining large automation suites, that is exactly the difference between a helpful demo and a genuinely useful feature. If AI only helps during one run but leaves the suite in a permanently fuzzy state, maintenance is still a problem. But if AI helps bridge the change, surfaces the updates, and lets the team convert those discoveries into an updated repository, then the test suite becomes stable again on the new UI.

Why this is different from traditional self-healing claims

A lot of test automation tools talk about self-healing, but many of those approaches are still heavily locator-centric. They may retry similar attributes or search for nearby DOM patterns, but they remain narrowly tied to the original technical structure. Rapise 9.0 takes a broader approach by combining object information with natural language action intent and AI-based visual recognition. That means it is not just asking, “What selector is close to the old selector?” It is also asking, “What is this step trying to accomplish on the screen?”

That distinction matters more as teams modernize applications. When organizations move from legacy web stacks to newer front-end frameworks, they often want to preserve their regression coverage without rebuilding every test from scratch. The ASP.NET-to-React Library Information System example shows how Rapise can help make that transition more manageable.

A better model for UI automation maintenance

What this example ultimately demonstrates is a better maintenance model for UI automation. First, record and run the test in the normal way. Second, when the UI evolves, let Rapise use self-healing to identify the equivalent controls in the updated application. Third, review and apply the resulting changes so the repository reflects the new implementation. Finally, return to normal playback without ongoing AI dependency. For example, in our application, the original playback took about 15 seconds, playback with AI took about 2 minutes, and after self-healing, the tests went back to taking about 15-20 seconds again:

That workflow is important because it keeps AI in the right role. It is there to help teams adapt to change, not to replace test engineering discipline altogether. In the Library Information System example, the AI layer provided the bridge between two materially different implementations of the same workflow. Once the changes were accepted, the test became stable again on the new version.

Why this self-healing is different?

The jump from the ASP.NET Library Information System to the React version is a strong illustration of what Rapise 9.0 self-healing is really for. It is not just about recovering from a renamed button or a moved field. It is about preserving the value of your test assets when the application underneath them evolves. By combining stored object knowledge, natural language action descriptions, AI-driven visual recovery, and repository patching, Rapise gives teams a practical way to carry automated tests forward through UI change instead of repeatedly starting over. The result is less manual maintenance, faster adaptation to redesigned applications, and a clearer path from AI-assisted recovery back to stable automated playback.

As companies start to use agentic AI development tools like Claude Code or Amazon Kiro, the rate of change of the underlying application is only going to increase, making this problem even more important to solve than before!

XXXrapisedemoXXX

The Agent Leader: Shifting from Static to non Static Autonomous Innovation

2026-03-31T17:09:43-04:00

The Era of Agentic AI

The floor isn't just shifting; it's being redesigned in real-time. For years, AI was a tool we "used." Today, we are entering the era of Agentic AI: a world where AI doesn't just suggest; it acts, reasons, evolves and manages other agents as well as human teams.

The latest "explosion" is best personified by Miro Fish, a swarm intelligence engine that hit #1 on GitHub in March 2026. Unlike traditional models that treat the world as a static equation, Miro Fish spawns thousands of autonomous agents, each with its own memory and personality to simulate complex, messy human social dynamics.

When one AI agent can update all others, the question for CIOs, CTOs, Product, Engineering and QA Heads is simple: Is this a scary loss of control, or the "sacred" key to solving humanity’s greatest challenges?

The Dual Reality: Scary vs. Sacred

The "Floor Shifting" Fear: Trust in fully autonomous agents has dropped from 43% to 27% in just a year. The "scary" part isn't just the speed; it's the probabilistic nature of AI. Traditional software is deterministic (if X, then Y). Agentic AI is behavioral. It can drift, "hallucinate," or make rogue decisions.
The "Sacred" Potential: In non-technical disciplines like medicine, these swarms act as a "digital reality rehearsal". They can simulate how a new drug interacts with a population or how public health policy impacts social behavior before a single real-world life is at risk. Imagine the cure of Parkinson's disease or Type 1 Diabetes with the help of AI reducing clinical trials from years down to weeks.

Engineering Reliability: The Inflectra Blueprint

We have gone from playing catch-up on how to test chat bots to now managing agentic ai systems of systems outside or any box and open. To move from "unpredictable liability" to "defendable delivery," engineering leaders must treat AI behavior as a testable property. Here is how to use the Inflectra Platform to anchor your agentic workflows:

SureWire.ai: The "Agent Control Tower"
- Proactive Probing: SureWire is a new category of AI Quality Assurance. It uses "Judge Agents" to actively probe your AI for failure, identifying prompt injections or fabricated outputs before they reach production.
- Behavioral Audits: It provides documented artifacts and repeatable metrics for governance, essential for regulated industries like healthcare and finance.
SpiraPlan: Adaptive Lifecycle Intelligence as your Standard Operating Platform (basically the floor that doesn't shift under your feet)
- Risk Prediction: Report across inflProgram, Portfolio and Products useing AI-driven analytics to generate Requirements, Tests, Tasks, Incidents, Release Analysis, forecast risks across the entire delivery lifecycle, highlighting likely problem areas before they impact a release.
- Full Traceability: links requirements/tech specs/parameters directly to AI-generated, test cases, tasks, releases analysis and risk prioritisation ensuring that even as agents evolve, they remain aligned with accountable business objectives.
Rapise: Self-Healing Automation
- Codeless Evolution: Rapise transforms manual test descriptions into executable code from images not just words to test across multiple environments simultaneously.
- Autonomous Maintenance: Its agentic orchestration includes "self-healing" scripts that adapt when application UIs change, reducing the maintenance burden that typically kills high-speed AI projects.

Together as the Inflectra Platform, you as Leadership can:

Define "Safety Gates": Use Inflectra.ai to generate risk predictions directly from your requirements beyond our human cognitive capacity
Continuous Validation: Integrate SureWire.ai into your CI/CD pipeline to monitor for non deterministic "behavioral drift" in real-time.
Human-AI Collaboration: Manage "blended teams." By 2028, 38% of organisations will have AI agents as core team members. Already in Japan, if a business unit needs to hire resources, they can request this via HR and HR to decide if this is an ai agent or Full Time Employee. Your job is to ensure those members are reliable, capable, predictable, and above all defendable.

Watch the recording of Inflectra's recent Asia Pacific Strategy Session to learn what is needed to prepare for a future of technology that is no longer just built; it’s simulated in safe "sandbox" environments, rehearsed, and refined by swarms like Miro Fish and tested by SureWire.ai. With the right QA framework i.e.: the Inflectra Platform, your experience of this shift will not be a blindsided shock, rather it's your superpower!

Dystopia and the Boardroom

2026-03-18T02:56:36-04:00

Whether you take the dystopian view of Netflix's "Mother/Android" theme where: (spoiler alert) Servant humaoid droids take over humanity in the aim to kill off our species or the utopian view I hold where robotics will assist us in solving parts of our aged care crisis, AI is here to stay and evolve rapidly for now anyway.

And while we are figuring out policies, guardrails, ethical disclosure and use along with re-imagining Intellectual Property, from content, creativity, to PhDs and engineering from the death of coding to the death by deep fakes to even reevaluating the worth of GDP and the economy at large (e.g. universal basic income and who will pay taxes) - your competition is already using that latest LLMs to replace coders and create new roles, drive unimaginable scale in delivery while mitigating most risks before they become such.

Conversation in boardrooms across Singapore, Sydney, to Silicon Valley has shifted from "Should we use AI?" to "How do we control the chaos AI creates?"

Because here is the hard truth about the Asia-Pacific market right now: Speed is no longer your competitive advantage. Controlled scale and speed with safety is!

The "Shadow AI" Epidemic in APAC

Let’s look at the facts. In the last 12 months, we’ve seen a surge in "Shadow AI" especially in Asia Pacific compared to rest of the world. Development teams in high-pressure hubs from Bangalore, Ho Chi Minh City, and Manila, empowered by AI coding assistants, are generating code 40-50% faster than last year. That sounds great for economies of scale right? Wrong.

A recent survey by a major APAC tech consortium found that while code volume is up, code visibility is down by an alarming margin. We are entering an era of "Invisible Complexity." You have junior engineers using LLMs to generate libraries they don't fully understand. You have product teams pushing features at a velocity that security and risk teams cannot physically audit. All while breach liability now is CxO and Board accountability.

This is where the dystopian view meets the boardroom. If you don't harness these agentic workflows, the Droids *do* take over - not by killing us, but by creating a tangled, untestable web of dependencies that collapses under the weight of its own technical debt. You in fact reach the law of diminishing returns if your software/application lifecycle can not be:

understood
defendable
traceable
and auditable

The Engineers Dilemma: Scale vs. Sanity

To my fellow Engineering and Product Leaders: We understand you are being pulled in two polar opposite directions:

"The Demand": Deliver faster. Beat the competitor in Jakarta. Capture the market in Tokyo.
"The Reality": Your toolchain is fragmenting. Jira holds the tickets, GitHub stores the AI-generated code, but no one has the "truth".

How do you practice Continuous Quality Assurance when the code is being rewritten by an Agentic AI every night minute? How do you manage risk when the "creator" of the code is the very Agentic AI in a "black box"?

You don't do it by working harder. You do it by unifying the entire lifecycle. When failure isn't an option, Inflectra helps you deliver. And prove it with SpiraPlan as your "Kill Switch" for Chaos. This isn't just another project management tool. This is the central nervous system for the AI-augmented enterprise.

If your AI agents are the engine, SpiraPlan is the steering wheel, the brakes, and the heads-up display.

For the C suite leaders The Visionaries):

You are looking at the bottom line and the risk register. In the next 24 months, the companies that win in APAC won't be the ones with the most AI agents; they will be the ones with the most auditable AI agents managing AI systems.

Governance: SpiraPlan provides the guardrails we are all trying to figure out. It gives you a single source of truth. When a regulator asks, "How did this feature get built?", you don't point to a chat log with an AI. You point to a traceable, immutable path from Requirements to Test to Release.
ROI: We are currently helping organizations in the region reduce their risk exposure by over 60% simply by catching "Ghost Code" before it hits production. Anticipate what is next.

For the Engineering & Product Leads (The Architects):

You live in the trenches. You know that "unimaginable scale" means nothing if the quality is trash.

Visibility: Imagine seeing, in real-time, how AI-generated code impacts your existing requirements. Imagine your test cases being automatically updated when an Agentic AI changes a function. Inflectra doesn't just track your human team; it tracks the *output* of your digital workforce.
Moving from "shift-left" to "shift-everywhere." With Inflectra's SpiraPlan, risks are flagged the microsecond they emerge—whether that's a scope creep from a product marketer or end customer vulnerability written by an LLM.

For the Project & Program Lead (The Orchestrator):

You are responsible for delivery. You are tired of the silos and lagging reporting.

Unification: Marketing uses different tools. Dev uses different tools. Ops uses different tools. SpiraPlan sits above the fray, integrating with your entire ecosystem (yes, including Jira and GitHub) to give you a unified view.
Prediction of risks allows you to forecast with accuracy and make decisions in real time that positively shape the future.

The Utopic Reality

My utopian view isn't just about robots helping the elderly; it's about software helping us manage the complexity we create.

The droids/bots/agents are writing code and self managing. Are you going to let them run wild, or are you going to put them to work in a disciplined, managed environment where their speed becomes your strength and their output becomes your competitive scale?

Don't let your organisation become the next dystopian headline.

XXXinflectraaitrialXXX

See how we turn the chaos of Agentic AI into the symphony of controlled delivery. Let your competition worry about the speed of playing catch-up while you focus on perfecting this evolution.

AI Testing Has Entered a New Era: Adam Sandman on TestGuild Discusses Non-Deterministic Systems and SureWire

2026-03-15T11:22:52-04:00

For decades, software testing has largely depended on a stable assumption: if the same input is given under the same conditions, the system should return the same output every time. That assumption still holds for deterministic software, and it remains essential for testing traditional application layers such as user interfaces, APIs, business logic, and databases. But AI systems are different. As discussed on the podcast, non-deterministic systems can produce different responses to the same prompt or input, even when the environment appears unchanged.

That means QA teams can no longer rely exclusively on binary notions of “pass” and “fail” when evaluating AI-powered workflows.

What Makes Non-Deterministic Systems So Hard to Validate

One of the core points is that AI is not just another feature layer. It changes the validation model itself. In deterministic testing, you can define a single expected result and compare actual versus expected. In non-deterministic testing, the same prompt may generate multiple acceptable responses, different quality levels, or even responses that stay within policy but vary in tone, specificity, or usefulness.

That changes how teams define success. The right question is often no longer, “Did it match exactly?” but instead, “Did it behave within acceptable boundaries?” Those boundaries may include safety, relevance, accuracy, harmful content controls, policy compliance, brand appropriateness, or task completion quality. The more critical the application, the more carefully those thresholds need to be defined.

Why Pass/Fail Testing Is No Longer Enough for AI QA

A major theme is that QA teams need to move beyond a purely binary concept of success when evaluating AI systems: because 100% testability is impossible in non-deterministic environments, quality teams need to shift from traditional pass/fail metrics toward identifying an acceptable level of risk for the use case. The episode also notes that the right threshold depends heavily on context, whether the application is an e-commerce chatbot or something safety-critical like air traffic control.

This is one of the most important mindset shifts for the industry:

AI quality is not just about correctness in the narrowest sense.
It is about bounded risk.
It is about confidence.
It is about being able to say, with evidence, that a system behaves well enough for the scenario in which it will be deployed.

For software leaders, that is a much more realistic and much more valuable framing. It aligns testing to real-world consequences instead of forcing a probabilistic system into a deterministic rubric that does not reflect how the system actually behaves.

The Growing Gap Between AI Development Speed and QA Capacity

Another critical issue discussed in the episode is the pressure that AI is putting on quality teams. We have known for a while that AI-generated code is raising the stakes for QA while budgets stay flat. That means teams are being asked to validate more software, more quickly, while also developing entirely new methods for testing AI-driven features such as chatbots, copilots, and agentic workflows.

This is where many organizations are feeling strain. AI can help teams produce more functionality faster, but quality does not happen automatically. In fact, the faster the pace of development, the greater the risk that fragile assumptions, incomplete evaluation criteria, or unmeasured AI behaviors will make their way into production.

That is why QA leaders need better tooling and better frameworks, not just more optimism about AI.

If development accelerates but testing remains stuck in yesterday’s model, the gap between shipping and trust will only widen.

SureWire and the Need for a New Category of AI Quality Assurance

That gap is exactly why we created SureWire, built specifically for agentic AI and designed to help teams know whether their AI agents are safe, reliable, and effective. SureWire acts like an experienced test manager, designing and implementing dynamic tests using collections of bespoke testing agents. The workflow is organized around three steps:

Teams describe their AI agent and concerns
SureWire assesses the system dynamically
Then the platform helps them improve through a report highlighting strengths, weaknesses, risks, and quality concerns.

That structure matters because it translates a difficult technical problem into an operational one. Instead of asking teams to manually invent everything from scratch, it gives them a path to define concerns, execute assessment, and interpret results in a more scalable way.

Many AI systems look promising in demos, prototypes, and controlled environments. But enterprise teams need something more than promising. They need repeatable evidence that a system performs acceptably under pressure, across variation, and within the constraints of the real business environment.

The challenge is not whether AI can produce impressive results. We already know it can. The challenge is whether those results can be trusted consistently enough for production use in environments where quality, compliance, and customer confidence matter.

It is not about replacing all existing QA practices. It is about filling the specific gap that appears when deterministic test models meet non-deterministic behavior.

What Still Remains Deterministic in an AI Application

Another useful point from the TestGuild episode is that teams should decompose their applications instead of treating the whole stack as non-deterministic. When testing AI-enabled systems, teams should still apply traditional deterministic testing to areas like the web UI and data layers, while using new statistical or agent-based testing approaches for the non-deterministic AI components.

This is important because it gives organizations a practical adoption path. You do not have to throw out everything you know about quality engineering. You still need regression suites, integration tests, API validation, requirements traceability, access control verification, and release discipline. What changes is that you now need an additional quality layer for the parts of the system that can vary meaningfully in behavior from one interaction to the next.

That decomposition is one of the most practical ways to think about AI QA. It keeps the discipline grounded while making room for new methods where they are actually needed.

AI Testing Is Really About Risk Thresholds

Perhaps the most important takeaway from the episode is that testing non-deterministic systems is fundamentally about risk management. In the episode Adam and Joe discuss how the acceptable risk thresholds vary depending on the context and consequences of failure. A consumer support bot and a mission-critical control system should not be evaluated with the same tolerance model.

That idea should shape how organizations build their AI quality strategies. Every team needs to answer questions like:

What kinds of failure are unacceptable?
How much variability is tolerable?
What dimensions matter most — accuracy, safety, consistency, policy compliance, or something else?
How should those dimensions be weighted?
What evidence is required before release?
Those are governance questions as much as technical ones. And that is why AI testing is becoming such a strategic function inside engineering organizations. It is no longer just about defect detection. It is about defining operational trust.

Watch the TestGuild Episode

If your team is working through how to test AI-enabled applications, this TestGuild conversation is a useful place to start. It covers why the old rules are breaking down, how non-deterministic systems require a different QA mindset, and why tools like SureWire are emerging as part of a new discipline for enterprise AI reliability. TestGuild’s episode summary also highlights related themes including the difference between deterministic and non-deterministic systems, the pressure AI places on QA budgets, and why testers who embrace AI as a tool will be better positioned to lead going forward.

As AI changes how software is built, it will also change how software is trusted. The organizations that adapt their quality practices early will be the ones best positioned to scale AI with confidence.

Interested in learning more about SureWire?

SureWire is Inflectra’s upcoming AI quality assurance platform built to help teams assess non-deterministic and agentic AI systems for safety, reliability, and effectiveness.
Join the waitlist to get early access and follow the latest product updates from Inflectra.

Recap | Breaking Free from Forced Cloud Migrations: Why Enterprise Teams are Moving to SpiraPlan

2026-03-10T11:17:21-04:00

Proactive Planning for the Atlassian Transition

While 2029 feels far away, the restrictions on the Jira ecosystem begin much sooner.

February 2026: New subscriptions and applications can no longer be purchased.
March 2028: You will be restricted to your existing user counts and plugins with no ability to expand.
March 2029: The software ceases to function for active work, moving into a permanent state of restricted access.

For large enterprises with millions of records, a migration of this magnitude typically takes years to organize, carry out, and verify.

Recording

Why SpiraPlan is the Leading Jira Alternative

Switching to SpiraPlan isn't just about finding a new home for your data; it’s about gaining capabilities that Jira requires expensive add-ons to achieve.

1. True Ownership of Your Hosting

While Atlassian is pushing users toward a multi-tenant cloud, Inflectra remains flexible regarding deployment.

Self-Hosting & Air-Gapping: You can run SpiraPlan on physical hardware in completely isolated environments for maximum security.
Private Cloud: Deploy on your own Azure, AWS, or GCP instance to maintain total control over your encryption keys and database access.
SaaS with Data Residency: If you choose Inflectra’s cloud, your data stays in your region—whether that’s the US, Canada, Europe, or Asia-Pacific.

2. Native Power vs. Add-on Bloat

In Jira, everything is a generic task. To get professional test management or risk management, you must buy and maintain third-party extensions like X-Ray or Zephyr.

Built-in Excellence: SpiraPlan includes enterprise-grade requirements, test management, and risk management as standard components.
One Vendor for Support: You no longer have to navigate disputes between different extension providers when a system update disrupts your workflow.

3. The Concurrent Licensing Advantage

Jira charges for every individual user, meaning you pay for every person regardless of how often they access the system.

Pay for Usage, Not Names: SpiraPlan uses a model based on simultaneous users. You can have 1,000 registered users in the system, but if only 50 are active at once, you only pay for those 50 licenses. This is ideal for stakeholders who only log in occasionally to view reports.

4. Total SDLC Traceability

SpiraPlan offers a unified foundation that Jira struggles to match without significant manual effort.

Code-Level Visibility: See exactly which code commits fixed a specific bug or fulfilled a requirement directly within the interface, with syntax highlighting included—no extra plugins required.
Flexible Methodologies: Seamlessly manage Waterfall Gantt charts, Scrum boards, and Kanban work-in-progress limits in the same program.

Migration Made Simple

Moving your data doesn't have to be a chaotic experience. Inflectra provides a dedicated migration assistant that pulls requirements, tasks, incidents, and even X-Ray test artifacts directly from Jira into SpiraPlan. For teams needing extra help, partners like Merito provide comprehensive support to clean data and ensure your compliance needs are met during the transition.

Don't wait until your Jira instance is restricted.

Experience SpiraPlan firsthand and dive into the full power of built-in traceability and integrated test management by starting a free 30-day trial. Our trials are 100% unlocked, with no credit card required and no obligation, giving you access to every enterprise feature.

If you are not sure where to begin, reach out to the experts at Merito for a complimentary SDLC micro-assessment. They will help you evaluate your current Jira environment and map out a strategic, stress-free path to SpiraPlan that aligns with your future roadmap.

Rapise vs. Cucumber in the Age of Agentic AI

2026-03-04T12:07:05-05:00

Strengths of Cucumber

Cucumber’s strength is clear: it lets teams write acceptance tests in plain language, using Gherkin, so business and technical stakeholders can share a readable source of truth. The project explicitly describes itself as a tool for running automated acceptance tests written in plain language, and its documentation shows that execution depends on matching those Gherkin steps to step definitions implemented in code. In practice, that makes Cucumber excellent for collaboration and specification-by-example, but not a complete automation system by itself.

Benefits of Rapise

Rapise, by contrast, is a complete automated testing solution. Inflectra states that Rapise supports web, mobile, desktop, mainframe, APIs, and third-party component libraries in one environment, and that its AI engine can turn natural-language instructions into directly executable tests. It also includes built-in capabilities such as record/playback, codeless testing, command-line playback, and reusable object repositories—features that reduce the amount of custom glue code teams must build and maintain.

In addition, there are other benefits of Rapise:

Cucumber only interprets Gherkin, Rapise can also interpret Javascript and RVL
Cucumber doesn't currently have a supported interface for Desktop App test automation, Rapise can automate Windows application tests
Cucumber supports a variety of outputs and report formats, including web reporting, Rapise has that, especially a super-smooth integration with Spira
Cucumber is Free Open Source Software (FOSS), and while Rapise has a license cost, that comes with support, which is often hit-and-miss with FOSS.

Why Rapise Shines in an Agentic World

That distinction matters even more in an agentic AI world. Agentic systems are most useful when they can interpret intent, generate actions, observe outcomes, and adapt. Rapise is already provides:

AI-powered execution
support for text and image-augmented prompts through AiTester
integrations with OpenAI, Azure OpenAI, and Amazon Bedrock

It also documents AI-assisted root cause analysis for failed tests and an AiRobot module that uses Anthropic’s Computer Use capability for automated exploratory testing. Those are not just “AI-assisted authoring” features; they point toward a model where AI can actively participate in test creation, execution, analysis, and maintenance.

Cucumber, on the other hand, is still primarily a language-and-framework layer, emphasizing feature files, step definitions, and plugins. Even browser automation examples in the Cucumber relies on pairing Cucumber with other tools such as Watir, and its reporting model is plugin-based rather than a built-in full-stack execution environment. That architecture is flexible, but in the AI era it also means more orchestration burden: your team still has to combine Cucumber with automation libraries, runners, reporting, infrastructure, and if desired separate AI services.

This is where Rapise becomes the stronger strategic choice for modern enterprises. In an agentic future, the winning platforms will not simply describe behavior; they will operationalize it. Rapise is better aligned with that direction because it closes the gap between intent and execution. A tester, analyst, or AI agent can move from natural-language instructions to runnable automation in the same platform, rather than handing specifications off to developers to write and maintain step definitions across multiple tools. That reduces handoffs, compresses feedback loops, and makes automation more accessible to non-programmers without blocking advanced users.

XXXrapisedemoXXX

Can You Use Gherkin With Rapise?

Absolutely, as you can see in this diagram:

Cucumber and Rapise are both engines that can interpret Gherkin and execute/automate the operations that the Gherkin describes. Rapise is able to interpret Gherkin-style statements and convert them into actionable operations. The Gherkin statements can be cast as Implicit AI Steps in Rapise, then the Rapise engine is able to generate code that performs the requested task using references to any existing Object model for the Application Under Test (AUT).

Delivering the Agentic AI SDLC with Spira, Rapise and Amazon Kiro

2026-03-03T07:09:51-05:00

A New Model for AI-Driven Software Delivery

AI has changed how software is built, but speed alone is not enough for enterprise teams. Modern delivery still depends on clear requirements, structured planning, reliable testing, and a governed path to production. Amazon Kiro, together with Inflectra’s SpiraPlan and Rapise, brings those elements together into a connected software delivery model where business context and requirements guide the lifecycle from the start.

Instead of treating code as the only source of truth, this approach puts requirements and business context at the center of delivery. That shift matters because it allows teams to use AI to accelerate development while still preserving the structure needed for quality, verification, and safety.

Why Requirements-Driven AI Matters

As AI-generated code becomes more common, organizations need more than faster output - they need confidence in what is being built. Requirements-driven delivery ensures that software creation remains tied to business objectives, defined functionality, and testable outcomes. In this model, AI becomes an accelerator for execution, not a replacement for engineering discipline.

That is what makes the Kiro and Inflectra combination compelling: it connects AI generation to the planning, traceability, and QA practices enterprises already rely on. The result is a more controlled path from concept to release, especially for teams operating in complex or highly governed environments.

SpiraPlan as the Foundation for Context and Control

SpiraPlan provides the structured foundation for this workflow. It is used to define, plan, and manage large-scale IT projects and initiatives, making it the natural place to capture the business and delivery context that informs software creation.

Because that data already exists inside SpiraPlan, organizations can reuse it to launch new digital initiatives more efficiently. Requirements, test cases, tasks, risks, and planning artifacts do not need to be recreated from scratch - they can be used directly to shape new product specifications and release plans.

Amazon Kiro Accelerates Production-Grade Application Creation

Amazon Kiro builds on that structured context by using existing project and business information to create production-grade applications in minutes. Rather than generating code in isolation, Kiro can work from well-defined inputs that reflect real organizational needs and delivery intent.

This creates a more practical and enterprise-ready form of AI-assisted development. Teams are not just moving faster - they are moving faster with clearer alignment to requirements, which improves the odds that generated applications match what the business actually needs.

Rapise Extends the Workflow into Automated Testing

No modern SDLC is complete without validation, and that is where Rapise plays a critical role. Rapise enables teams to automate testing and QA processes using Kiro specifications, creating a direct link between what was defined, what was generated, and what gets tested.

This includes automated user experience testing driven by natural language, which helps teams execute tests directly from specifications rather than rebuilding test intent manually. That reduces handoff friction and makes it easier to maintain continuity between requirements, development, and quality assurance.

How the Integrated SDLC Fits Together

Together, SpiraPlan, Kiro, and Rapise support a connected delivery workflow that spans the core stages of the software lifecycle:

Requirements and Planning

SpiraPlan captures and manages project requirements, planning data, tasks, risks, and other foundational delivery artifacts.

AI Code Generation

Kiro uses that business and project context to generate production-grade applications quickly.

Testing and QA

Rapise turns generated specifications into automated testing workflows, including user experience validation.

Integration and Build

The workflow extends into integration and build with AWS CodeBuild.

Deployment and Monitoring

Applications can then move into deployment and monitoring on EC2 or ECS, completing the path from idea to running software.

What Teams Can Do with the Integration

This connected approach enables several high-value workflows for delivery teams:

Generate Steering Documents Faster
Using MCP, teams can generate project steering documents in Kiro from the business context already stored in SpiraPlan. That makes it easier to convert planning intelligence into actionable delivery artifacts without redundant manual work.
Auto-Create Release Specifications
Feature requirements, test cases, tasks, and risks in SpiraPlan can be used to build an entire release specification in minutes. This accelerates the transition from planning to execution while keeping releases grounded in structured project data.
Execute Automated Testing from Specifications
Rapise can execute automated user experience tests directly from Kiro specifications, helping teams validate software earlier and more consistently. This closes the loop between planning, generation, and verification.

Business Impact for Enterprise Teams

For enterprise organizations, the value is not just technical integration - it is operational acceleration with stronger control. In this model, teams can take ideas into production 400% faster while keeping quality, verification, and safety built into the process.

That combination is especially important in environments where software quality cannot be left to chance. By keeping requirements, planning, generation, testing, and deployment connected, teams gain better traceability, less fragmentation, and a more repeatable delivery process.

Key Use Cases

Greenfield Application Development
Teams can create production-grade new applications from a business plan or even from early-stage ideas developed on a whiteboard.
Cloud Modernization and Migration
Applications can be modernized and migrated to cloud-native architectures 7x faster, with confidence and quality built into the process.
Brownfield Enhancement and Maintenance
Complex existing applications can be enhanced and maintained with the robust testing and compliance discipline that enterprise teams require.

From AI Acceleration to Governed Delivery

The real opportunity in AI software development is not simply generating code faster. It is creating a delivery model where AI operates inside a governed lifecycle - one that starts with requirements, stays connected through testing, and ends in a more reliable release process.

XXXspiraplantrialXXX

By combining SpiraPlan, Amazon Kiro, and Rapise, organizations can move beyond isolated AI productivity gains and toward a truly connected, agentic SDLC. That means faster software delivery, stronger alignment to business intent, and greater confidence in what reaches production.

Additional Reading

If you would like to learn more about using Amazon Kiro and Inflectra's platform, here's some additional whitepapers:

Why Sensitive and Highly Regulated Industries Are Rethinking Public Cloud

2026-03-10T13:07:08-04:00

The Issue is Not an Explicit Industry Ban

To be precise, public cloud vendors are not explicitly banning or restricting specific industries or sectors, rather that their acceptable use policies reserve the right to take action against content it views as objectionable and inconsistent with the spirit of its guidelines. For example, Atlassian has formally announced the End of Life of its Server and Data Center on-premise products, and many customers in these sectors are considering alternatives.

That distinction is critical. For many businesses, the concern is not whether their sector is named in a prohibited-industry list. The concern is whether their core production and delivery systems should sit inside a third-party SaaS platform where access, content interpretation, and enforcement remain subject to provider-controlled acceptable-use standards. In industries where regulations are complex, jurisdiction-specific, or fast-changing, that can become a material governance risk rather than a theoretical legal footnote.

Why this Matters for Crypto, Gambling, and Other Adult-oriented Businesses

Organizations serving cryptocurrency markets, online gaming and gambling ecosystems, or adult-adjacent business models often face elevated scrutiny around licensing, AML and KYC obligations, sanctions controls, payments compliance, consumer-protection enforcement, and cross-border legality. Even where a business is lawful in its operating jurisdictions, the regulatory environment may shift quickly or vary by geography, banking partner, or customer segment. In those environments, many leadership teams are reluctant to expose their mission-critical software delivery system to a public SaaS provider’s broad discretionary enforcement language. That concern is driven less by published industry exclusion and more by the risk of depending on a platform whose terms allow action in response to objectionable.

Why This Matters Now

This issue is becoming more urgent as software teams face greater pressure to move faster while simultaneously proving governance, safety, and compliance. In industries already exposed to regulatory volatility, the last thing most organizations want is uncertainty around the continuity of the platform that underpins planning, testing, approvals, and auditability. Buyers are increasingly looking beyond checklists and UI familiarity to assess whether their platform strategy aligns with their legal risk profile and operational resilience requirements.

XXXspiraplandemoXXX

Turn New Regulatory Frontier into Innovation Advantage

2026-02-27T16:55:34-05:00

The Technology Leadership Paradox: Drive Agentic AI Without Losing Your Seat to the Regulator

For decades, the Asia-Pacific banking sector has been the vanguard of technological adoption. Today, the "edge" is Agentic AI—the push to embed autonomous models into every product and team.

Yet, CIO and CTOs in the region face a profound irony: you are operating in one of the most heavily scrutinized environments in the world. The question is no longer if you should adopt AI, but how to maintain a "Regulatory Ready" SDLC when your code is learning and adapting in real-time to innovate.

The Challenge: Command and Control at Agentic Speed

Legacy QA, bolted onto the end of a sprint, is obsolete. When AI models evolve logic hourly, a static, reactive testing approach creates dangerous blind spots.

The Single Source of Truth: How do you maintain one when logic is constantly shifting?
Third-Party Drift: How do you ensure a vendor's AI component doesn't introduce regulatory drift overnight?
The APAC Mandate: From the MAS Guidelines on AI Risk Management in Singapore to APRA’s focus on third-party risk in Australia, regulators are demanding demonstrable, routine validation in real time, not "once and done" checks.

The GRC Engine: Turn AI Speed into Trust

Inflectra provides a unified, cloud-native platform that acts as your central Governance, Risk, and Compliance (GRC) engine. By leveraging the Inflectra Suite: SpiraPlan, inflectra.ai, and Rapise, you bridge the gap between innovation speed and compliance certainty with #AWS enterprise grade service levels, safeguards, scale and security for Genai and Cloud.

1. SpiraPlan: The Digital Supervisor

SpiraPlan acts as the backbone of your "Regulatory Ready" SDLC. It provides:

End-to-End Traceability: Link every business requirement and regulatory mandate directly to test cases, code changes, and live model behaviour.
Integrated Risk Management: Utilize dynamic risk evaluation with automated triggers to identify 30% more urgent project risks before they impact customers.
Audit-Ready Documentation: Automatically generate standard regulatory reviews and electronic signatures, cutting audit prep time by up to 50%.

2. Rapise: Agentic QA for Agentic AI

Rapise is an AI-powered test automation tool designed for the complexity of modern enterprise systems:

Self-Healing Scripts: AI-driven scripts adapt to UI changes automatically, reducing maintenance overhead by 80%.
Natural Language Automation: Empower functional experts to convert plain language into test code, accelerating script development.
Vision-Based Testing: Simulate the keen observation of a manual tester to detect visual discrepancies and layout shifts that traditional functional tests miss.

3. Inflectra.ai: Native SDLC Intelligence

Unlike "bolt-on" AI, inflectra.ai is embedded natively within the ecosystem. It allows you to:

Instantly Generate Artifacts: Create requirements/user stories, test cases, tasks, release analysis and risk models from high-level requirements in seconds at scale to bolster your team.
Predict Delivery Outcomes: Use machine learning to forecast risks and predict bottlenecks across your entire portfolio to prevent incidents.

Proof in Practice: Modernising the Philippines’ Land Titling

The Land Registration Authority (LARES) in the Philippines used the Inflectra suite to modernize two decades of legacy systems. By moving to a unified, cloud-native assurance model, they modernized their systems 70% faster while maintaining absolute data integrity and security for millions of records [Source].

Conclusion: The Future Belongs to Those Who Govern

Moving fast is meaningless if you can't prove you are in control. Trust is the ultimate currency.

Inflectra empowers you to:

Shift from Detection to Prevention with proactive risk analytics.
Establish a Single Source of Truth that satisfies auditors and stakeholders alike.
Scale Securely across a multi-vendor ecosystem in real time regulatory ready loop.

Ready to embed "Regulatory Ready" QA into your innovation culture?
Start a 30-day free trial or explore more at Inflectra.com.

Test Leadership and Management in the Age of AI

2026-02-06T13:16:48-05:00

Written by Neil Price-Jones

Target Audience

The target audience for this article on Test Leadership and Management in the Age of AI is the following:

Quality Assurance Managers and Leads
Project and Program Managers who depend on results from Testing coming from multiple projects to assess trends and system health.
CIOs who need overall system health parameters.
Product and Marketing owners who depend on verifiable results to sell their products.

Software Test Automation

There is a long trend of automating aspects of software testing. The following is a very brief list of some of what has occurred in test automation over the years.

Gradual expansion of interfaces that could be recognized.
Addition of multiple methods of scripting (from specific languages to NLP, and Keyword Driven Testing).
Enhanced automation of test generation and execution.
Automatic responses to unexpected events occurring during execution.
Traceability matrices (manual and automated).
Semi and full automation of incident reporting, documentation, and workflow.
API emulators to allow more and expanded testing of complex systems.
Addition of weighted algorithms to assess and assign risk levels and criticality to issues.
Management tools created to manage test cases, test scripts, and defects (in particular).
Management tools progressively expanded to encompass more of the Lifecycle and different SDLCs.

A larger history of Software Development and Test Methodologies and their effectiveness is available from Capers Jones.

All of this has led to a reduction in the time to complete certain aspects of testing. The decline has been gradual and subject to reversals when new applications and increased complexity was incorporated. In addition, some systems, with very limited use, have rarely benefited from automation since it is not economically effective to automate or the interface is simply not recognizable.

Other items that impeded the ‘progress’ of automation include

New interfaces, new languages, and expansion of systems have made it harder to build a System Boundary Diagram in my experience. Thus, not only is it hard to determine what to test, but it is also hard to set up all the conditions. Manual testing, if it encountered such a problem, benefitted from the human-in-the-middle that would stop at the problem, perform root cause analysis, and continue with the test if appropriate. Automated tests did not always realise that there were issues and tried to keep executing or else reported a spurious issue.
Tools have been built and sometimes incorporated into other tools to address these issues. However, that led to a proliferation of tools for an organisation to buy, train (and sometimes retrain) the users and frequently the usage of the new tools was limited to very specific cases. These disparate technical solutions would usually be eventually consolidated into another tool with the cycle then repeating itself.

The impact on Test Leadership and Management has been cumulative although somewhat erratic. Clearly the amount of available information and the level of detail down to the most granular level of testing is now many times what it was before. If the test execution and incident reporting is integrated into a management tool, then a status is available to anyone with access and the correct security level. If Requirements, Test Cases, and Test Steps are also incorporated into the tool, then the ability to get a complete picture is greatly enhanced. There is a lot more information and a lot more oversight.

Software Testing using AI

Using AI in Software Testing brings a whole new level of automation and abstraction to the industry. Test scripts, test steps, expected results, execution, defect identification, classification and remediation and requirement generation are now available from within many software test tools or directly via prompts using AI. The addition of Agentic AI will remove many of the listed intermediate processes and allow the test creation, execution, and reporting to proceed in an automated manner with little or no human intervention.

We will see the Test Generation, Test Execution, and Test Reporting squeezed in time, as we have so many times already, via various AI test automation processes and tools. Automation has already provided rapid execution of testcases and instantaneous reporting of results down to the most detailed level. AI will provide this and much more.

Implementation of AI in testing is most likely to follow the same path as previous automation changes. AI will become part of the software testing toolkit for many people, but it will not replace all of what has been done in the past. In the short-term AI will be disruptive (especially since people will be deceived by the hype that it will do everything for testing).

Some organisations will make full use of AI and others will not use it at all due to bad experiences or security and trust issues. As usual the risk equation needs to be applied to all activities involved with AI and a determination made of impacts and probabilities to assess both the short- and longterm impacts to the overall software process. As Robert Sabourin stated at STARCANADA 2025, AI adds a third dimension to the usual Risk Graph with a third axis representing autonomous decisions made by AI.

AI in testing will make a difference to the central part of the testing cycle, but the beginning and end parts are being lost in the noise as is the impact on people who must sign off: the Test Lead or Test Manager.

Impact of AI Automation on Test Leads

The Impact of AI on the Test Lead or Manager will be substantially greater than incremental automation and with a squeezed timeline in both speed of adoption and the test cycle. There will be a reduction in time required for scripting and test execution. Testers who are familiar with writing scripts (either for manual or automated execution) will need to retrain in writing prompts and orchestrating testing. A reduction in the number of testers is inevitable.

The impact on Test Leads and Managers will be that many projects will feel that they need not involve testing until the last possible minute since AI will do all the detailed work that used to be completed by the testers and test leads prior to the execution. The front-end work will be taken away as will the long execution times and we will have very quick tests generated by AI, run by AI and reported on by AI.

Two Major Concerns

The addition of AI raises two other big concerns.

Manual testers would often think about what else could go wrong when writing or executing testcases. If they observed something out of the ordinary on the periphery of a test script or thought about other things that needed to be tested, they could incorporate this new knowledge into the testing and check for any issues. This might be something close to the current test, or it could be something completely new that was in another piece of the software. The act of executing a test provided more information than just the results of the test and often stimulated further investigation. Better testing was the result.
The internal workings of the scripts and decisions being made as to what were acceptable changes or even what the automated script (of any type) was testing were often obscured from the test manager by complex test tools with many settings that could impact how a script was executed and what was reported as an incident. This led to a distrust in automation and many people resisted further automation as a result. In some cases, manual testers were trusted more than any automation despite the chance that the manual tester could make mistakes in execution or fail to notice issues.

Impact of AI

Analysis

AI in testing provides the promise of removing a lot of the tedious work of writing test cases and scripts, executing those testcases, and generating reports. It will even generate Requirements from the testcases if requested.

The issue is whether the results can be trusted and represent a valid test of the system. If critical parts of the test are missed or the incidents are not given the correct priority, then it would be likely that the system could be signed off as ready for promotion based on incorrect and incomplete data.

As a Test Lead or Test Manager who must sign off on incomplete or incorrect information, this is a concern. Information has never been complete in the past, but the concern now is, with so much of the process taken out of direct control, there may be layers of misconceptions and problems buried beneath the steps and interface that are not necessarily visible.

Some will argue that this has been the case for years as testing has been automated and testers got further from the actual testing and into writing scripts. That is somewhat true and this is an ongoing trend. But this is a larger and faster change than other changes.

Problem Statement

The challenge is to ensure that what has been tested is accurately represented in the reports and statistics generated from the testing. A second challenge is to ensure that the required scope of testing has been completed and that the risk to the final customer has been minimised. In the event of an industry that might require a testing audit, the artifacts must be maintained, be safe from modification and be available to the auditor in an accessible format.

Summary

The implementation of AI in testing has been treated as a technical solution so far with limited understanding of the impact on reporting. The Test Lead or Manager will need to change the way testing is monitored and reported with changes in what is checked and when it is checked in the testing process. Items that were originally trusted to be completed and signed off by the relevant people now will be generated and will need to be checked after that generation. This will be at a time when the project is already under time pressure. The generation of test cases from requirement and subsequent execution and reporting without a time gap will need monitoring to ensure that a signoff with assurance of completion and sufficient scope can be provided.

Changes for the Test Lead or Manager

The Test Lead who is dealing with a system in which AI is being used will need to:

Ensure their inclusion at the beginning of the project to allow for time and resources to inspect and approve all test artifacts.
Plan for the training required for testers in the new method of working.
Plan for the automation of the process of Quality Control.
Review the documentation to ensure it accurately represents the needs of the users.
Build in Risk identification, documentation, analysis and resolution for the new methodology.
Shift to Test Governance activities versus test case and script reviews.
Plan for the reduced time test cycle while ensuring the correct testing has been completed.
Deal with project changes that occur during the active testing cycle.
Complete the required scope of testing with reduced resources.
Plan for UX testing to be completed by human resources.
Ensure that resources and time is budgeted for post execution analysis of coverage.
Ensure ALL test artifacts are subject to stringent version control by creating a process or acquiring a tool with sufficient security.
Mandate and enforce the assignment of a priority to ALL test artifacts and that priority must carry through all the linked artifacts.
Build the process whereby new or changed test artifacts are subject to the same level of control and review as the initial set.
Plan for resources and time to orchestrate the review of artifacts throughout the testing process.
Build a process to ensure that the AI generated test artifacts correctly and clearly represent a test of the system and reduce the risk of use to an acceptable level.
Schedule reviews of the process to check for omissions.

Conclusions

AI can represent a great addition to the tester’s tool kit and can help the Test Lead/Manager provide even more data and analysis and free up time for consideration of what might have been missed. This is time for which we have always looked. Caution must be exercised in terms of ensuring that the tests represent and comply with the requirements for testing proof and sign off. We cannot wait until the compressed test cycles are over to find that too much has been missed. Reviews and sign offs must be strategically placed for the best benefit.

About the Author

Neil Price-Jones is an expert in Quality Assurance and Software Testing, with extensive experience in assessing, consulting, managing, and training. His work supports a wide range of industries, including hydro and gas utilities, finance, telecommunications, provincial government, health, and insurance.

Organizations

A prominent figure in the software quality community, Neil is a regular presenter for organizations like the Kitchener Waterloo Software Quality Association (KWSQA) and the Toronto Association for System & Software Quality (TASSQ). He is the current President of TASSQ and serves as the Treasurer for Caledon Chamber Concerts.

Neil is also a frequent speaker at major industry events, including QUEST, TesTrek, and the International Quality Conference.

Our Holiday Present To You - Customer Delight

2025-12-24T11:13:43-05:00

1. Concurrent users

Unlike all of our competitors and most SaaS products, we use concurrent or floating licenses for all of our products. This means that you can deploy our platform to your entire organization and not get penalized for having occasional users. If you need business users to login and view dashboards, validate information or even run tests, you don't need to worry about purchasing additional licenses, we've got you covered.

2. Transparent pricing

We believe that there should be no "sticker shock" pricing surprises. All of our products, including our Inflectra.ai platform have 100% transparent pricing on our website. How many times have you looked at great product on a website only to be confronted with the dreaded "Contact Sales" message when you try and understand what it will cost you. None of that at Inflectra!

3. Inflectra.ai separate vs.forced bundling

A lot of vendors are making their AI functionality a mandatory purchase regardless of whether you want to use it, or are even allowed to use it! Not at Inflectra! When we launched Inflectra.ai in early 2025 we deliberately made it an add-on to our existing platform. That way you get to try it out before you purchase and can even validate that it will deliver tangible business value! The great thing is, over 20% of our cloud customers have already purchased Inflectra.ai, meaning that they have seen the value and the ROI vs. it being forced on them.

4. Have it your way (on-prem, cloud)

We think the cloud is amazing, it allows organizations to delivery software faster and with less expensive, fixed infrastructure. It allows companies to focus on delivering value instead of managing servers and networks. For this reason, we've partnered with Amazon Web Services (AWS) to be our exclusive cloud provider, delivering unbelievable performance, world-class AI and support for data sovereignty and compliance. That being said, the cloud is not for everyone, and unlike many other competitors such as Atlassian, we're not forcing you to make that choice. Our platforms run both in the Inflectra Cloud and On-Premise. Guaranteed.

5. Inflectra.ai or BYO LLM

We launched Inflectra.ai in early 2025 to give customers the easiest, simplest possible way to take advantage of generative and agentic AI in their software delivery lifecycle. With a simple, flat-rate subscription, you can activate AI functionality in both our Spira platform and in our Rapise automated testing product. However in line with our mantra of customer delight, we also let you "bring your own LLM" and have AI functionality in both products as well.

6. Invoice in your currency

We work with customers in many different countries around the world. When we first launched the company, we could only generate quotes and invoices in US Dollars (USD) and only had a US Bank Account. Based on feedback from prospects and customers we realized that we could make it so much easier for organizations such as local Governments and non-profits as well as other customers to purchase from us if we could support other currencies and bank accounts. Therefore in 2023 we upgraded our ERP systems to handle multiple currencies including: USD, EUR, CAD, GBP, AUD, and NZD. Now we can invoice you in your currency, and provide a local bank account as well. Just another way we can simplify the purchasing process.

In 2024 we published all of our products on the AWS Marketplace, which opens the door for streamlined purchasing in even more countries and currencies.

7. Support for air-gapped environment

Not all environments are connected to the Internet. In this age of cyber attacks and security risks, many high-assurance organizations as well as national security agencies need to run their workloads on air-gapped, high-security networks. Inflectra's on-premise products can all run 100% air-gapped, with no telemetry or other need to contact home. This allows our products to be used to ensure the quality and safety of the most trusted organizations.

8. Unlimited everything (storage, projects, artifacts)

We often get asked by prospective customers about what limits we have in products: the number of projects, number of items, attachment storage, geographical limits, or rate limiting of APIs. At Inflectra, we provide you "unlimited everything" as much as possible, with no limit on the number of named users, products/projects, attachments, cloud-storage and even API calls. Now of course we have DDoS protections in place to prevent attacks on our systems, but subject to those cyber-limits, you can use our products as much as possible!

9. No charging for formerly free features (in fact the opposite)

There has been a trend on the Internet of Enshitification, where formerly great products decline over time to maximize profits. At Inflectra we believe the opposite is true, over time you need to constantly improve your products and offerings to keep your customers happy. As an example, the Risks module was originally only available in our SpiraPlan edition, but as we added more program and portfolio management functionality to SpiraPlan, we decided that we would enable Risks in our SpiraTeam edition as well, as we knew it was an important feature for ensuring customers delivered high quality software every release. Similarly, Document Management was originally not available in SpiraTest, but as we built out SpiraTeam and SpiraPlan, we decided to also enable Document Management in SpiraTest as well.

10. Helping you succeed vs. selling you a tool

Finally, if you have every spoken to a member of our "sales" team, whether that is exploring our platform as a new customer, discussing options for renewal, or looking to add additional products to your subscription, you will always find that our team is not a sales team at all. We don't sell products, the products are designed to sell themselves by delivering value to customers. Our team is there to help you discover the products, and act as a guide to help you succeed.

Happy Holidays

Finally, as we close out 2025, I'd like to wish everyone a wonderful, happy holiday season, and looking forward to new ways to delight you in 2026.

Adam Sandman

CEO

Inflectra

Webinar Recap: AI, Agentic Development, and the Future of QA

2026-02-02T13:51:04-05:00

In this recap of our latest webinar, CEO Adam Sandman provided an insightful look into the rapidly evolving landscape of AI in software development, detailing the shift towards agentic AI and its profound implications for QA.

Recording

The Three Phases of AI Evolution

The journey of AI is quickly moving through three phases:

Phase 1: The Digital Intern (LLMs, Prompt Engineering): AI acts as a content generator (e.g., code snippets). It has no agency.
Phase 2: The Digital Employee (LAMs, LVMs): AI gains agency—it can "see" and "do" things (e.g., click, understand an image). This enables Agentic AI.
Phase 3: Teams of Agents (MCP): Agents work collaboratively across the lifecycle (Dev Agent $\leftrightarrow$ Testing Agent) to accomplish business goals.

The Great Software Quality Collapse

While AI promises speed, it introduces a significant quality trade-off:

Productivity Up, Quality Down: A roughly 300% increase in productivity is met with a corresponding 400% decrease in quality.
Security Risks: AI-generated code is reported to contain 322% more vulnerabilities than human-written code.
Non-Deterministic Systems: Generative AI introduces non-deterministic behavior, meaning small, catastrophic failures can occur even after extensive testing.

The Return of the Requirements: Spec-Based Development

To counter "Vibe Coding" (simple prompts that lead to maintainability issues), the industry is shifting to Spec-Based Coding.

The core idea is: The Specification (Spec) is the source of truth. The AI Agent builds the application to the detailed, version-controlled spec (requirements, design files, tasks). This enables successful development on large, existing codebases.

The human developer's role shifts from writing code to ensuring high-quality documentation and architectural governance.

Inflectra AI in Action: The New Flow for Quality

The new flow requires shifting the source of truth upstream to the specification:

User Input (Spec): Humans create rich artifacts (requirements, test cases).
AI Generation: The Dev Agent generates code from the spec.
Testing/Fixing: Testing agents run tests from the spec and find issues.
Refine Spec (Not Code): When a bug is found, the human and AI fix the spec, ensuring consistency.
Regenerate: The refined spec is used to regenerate the application.

Inflectra plays a critical role in this new process:

Inflectra Spira: Manages the Requirements and Spec Creation piece, serving as the source of truth. AI features assist in backlog generation, requirement quality scoring, and risk/task generation.
Inflectra Rapise: Provides the Test Execution piece. AI features convert manual steps to automation, build maintainable tests using existing frameworks, and perform qualitative assessments (e.g., checking for good contrast or white space).

The Future: Self-Healing and Assurance

Inflectra's roadmap includes:

Self-Healing Tests: Rapise will use its vision model to visually identify UI elements and automatically relearn their technical locators when they change, preventing test failures.
Inflectra Assure: A brand new product focused on Agentic Testing specifically designed to test AI systems themselves.

The convergence of Agentic AI and spec-based development underscores the indispensable role of the quality professional in ensuring safety and reliability.

Your Future in QA: Join the Conversation

The shift to Agentic AI is happening now, and the role of the quality professional has never been more critical.

To ensure you don't miss out on future product updates, upcoming events, and the latest company news as we continue to evolve our tools for the agentic future, follow us on LinkedIn or subscribe to our newsletter today!

Reconnecting and Charting the Future: Inflectra's Crystal City Networking Event

2025-12-15T10:41:50-05:00

Dynamic Connections and Strategic Insights

We were thrilled to finally reconnect face-to-face with the DC Metro area’s dedicated software professionals—including developers, product managers, quality assurance specialists, and IT executives. The atmosphere was charged with productive discussions, reinforcing the strong community built around our flagship products, Spira and Rapise.

Attendees benefited from elevated professional networking, as the event successfully brought together a diverse group of IT leaders and visionaries. This was complemented by an exclusive technical exchange, where participants engaged in valuable, informal discussions, shared best practices, and collectively addressed common challenges within the Software Development Lifecycle (SDLC).

Discussions on the Shift to AI-Native Development

A major theme of the evening was the rapid industry shift toward AI, particularly in the context of the AI-driven development lifecycle. Leaders shared insights on how traditional agile models are being challenged by new agentic AI capabilities and the emerging requirement to create a single digital thread from the boardroom to delivery. The consensus highlighted the move away from simply fixing code to correcting requirements—a fundamental shift catalyzed by AI.

Furthermore, the event wrapped up with Inflectra leadership, giving attendees an unfiltered, exclusive view of Inflectra's strategic direction and groundbreaking developments slated for 2026, alongside upcoming career opportunities to join our growing team.

An Evening of Appreciation and Engagement

Beyond the strategic discussions, the event offered a sophisticated and relaxed environment for our guests. The setting at HIGHLINE RXR facilitated comfortable networking, complete with city views. Attendees enjoyed complimentary signature cocktails and appetizers, including playful, Inflectra-themed options like "The Agile Sprint" and "The Code Committee."

The strong turnout clearly reflects the shared commitment within the DC Metro tech community to quality without compromise—a core mission that Inflectra’s platform embodies. We extend our sincere gratitude to every attendee who registered and contributed to making this a truly memorable and high-value evening.

Chart Your Future with Inflectra

Want to be part of our next successful gathering? There are two great ways to stay informed:

Follow Inflectra on LinkedIn to engage with tech leaders and receive updates on industry trends.
Sign up for our newsletter below to ensure you get a personal invitation to our upcoming networking events and technical exchanges!

Unlock Greater Software Testing Expertise with Checkpoint Technologies (Enhanced Training Offer Inside!)

2025-12-12T15:40:29-05:00

Authored by Bob Crews of Checkpoint Technology

The tools used in any profession are key. Imagine a surgeon performing an operation without scalpels and forceps — that would be tricky. Once a skilled worker becomes more experienced or an expert, they often upgrade their tools. Maybe they get a Medtronic scalpel with the 3-nanometer obsidian blade!

I could buy surgical masks, Medtronic scalpels, and Crile hemostats with titanium-coated tips, but that wouldn’t make me a surgeon!

We all know that’s not how it works. Yet in the world of Quality Assurance and Software Testing — and likely others — there are those who invest in excellent tools (solutions) and expect that alone to magically turn their team into world-class software test engineers.

That’s usually not the case.

Tools are designed to enhance processes and strategies. They enable efficiency, precision, and cost-effectiveness. But tools alone don’t create skilled software test engineers. The real transformation comes when tools are paired with education and experience — the elements that build understanding, context, and judgment.

Experience and Education: The Real Differentiators

Experience means being exposed to a variety of scenarios, challenges, and lessons — and learning from them. You’ve made mistakes (I know I have) and made mental notes not to do that again.

Yes, I once spent 23 hours automating a test even though the requirement and functionality it validated would be obsolete the following week. Oops!

Experience builds perspective. Education provides structure. Together, they shape the professional.

Education: A Continuous Process

Education is the process of learning — acquiring knowledge, skills, beliefs, and habits with the goal of becoming or improving as a software test engineer.

This process involves:

Purposeful activities aimed at specific objectives
Gaining information, technical abilities, and practical skills
Developing intellect, critical thinking, and judgment

Education takes place in multiple settings:

Structured (schools, colleges, universities)
Non-formal (workshops, professional training)
Informal (daily experiences, mentoring, collaboration)

And here’s the key point:
Education is continuous.
It doesn’t — and shouldn’t — stop.

The Role of Training in QA and Software Testing

Training and education in QA and software testing benefit those who:

Have just started or are looking to start a career in software quality
Need a refresher or want to stay current with modern concepts and strategies
Want to expand their expertise into advanced topics and techniques

A great training course on QA and software testing should:

Cover topics relevant to today’s technologies while staying true to the fundamentals
Allow flexibility while maintaining clear learning objectives
Offer scheduling and delivery options that fit real-world constraints

When Education Meets Tools

The benefits of truly understanding Quality Assurance and Software Testing are many. One often-overlooked advantage is that deeper understanding leads to better, smarter utilization of testing tools.

The right training and education don’t replace your tools — they amplify them.
They create professionals who know how to make the most of every feature, function, and framework.

Education and tools together are what elevate a tester from competent to exceptional.

Special Offer for Inflectra Customers

Checkpoint Technologies is proud to be an Inflectra-certified Platinum Solutions Partner. To support Inflectra users and advance our shared commitment to high-quality software delivery, we are offering our “Essentials of Software Testing” course to Inflectra customers at a special discounted rate.

This popular two-day (16-hour) course is available with flexible scheduling and delivery options:

Engagement options
• Two consecutive full days, or two one-day sessions over two consecutive weeks
• Four sessions of four hours each, delivered within two consecutive weeks

Delivery formats
• Virtual
• Onsite (two-day option only; T&E additional)

Standard Cost: $3,200
Special Inflectra Customer Rate: $2,000

For a minimal added investment, this course can be modified with the addition of Rapise and/or Spira mentoring.

VISIT OUR WEBSITE OR CONTACT US TODAY AT TRAINING@CHECKPOINTECH.COM

TO SCHEDULE YOUR “ESSENTIALS OF SOFTWARE TESTING” TRAINING!

Recap: Amazon Web Services (AWS) re:Invent 2025 - The Year of Agentic AI

2025-12-04T21:11:36-05:00

Keynotes and Product Announcements

On the product side, there was a big focus on Agentic AI naturally:

✨ Google’s open weight Gemma model coming to AmazonBedrock
✨ Nova Embeddings now available
✨ Amazon Nova 2 is out! Including a whole new model - Nova 2 Omni is a reasoning model that supports multi-modal reasoning (multi modes in) and text and images out.
✨ Nova Forge is a new service to create custom models, not with fine tuning but during custom pre-training.
✨ AgentCore Evaluations to test an agent to make sure it maintains its quality with simple pre-baked types of evaluation.
✨ Kiro autonomous agent is out, which can work autonomously for long sessions in the background and across repos, learning from how we work by building its own memory. it’s goal is to write code.
✨ A new DevOps agent for incident triage, and resolution

Executive Briefings and Roundtables

We attended an ISV AgenticAI executive briefing and panel discussion that outlined the future of work in the age of AI as well as providing a roadmap for software companies that are adding AI products into their platform. Based on the presentation, we are in between the "Innovate" and "AI Native" stages:

Our new Inflectra.ai service delivers AI-powered innovation to our exiting products SpiraPlan - Software Development Lifecycle and Rapise - Agentic Test Automation
Whereas our in-development InflectraAssure™ AgenticAI testing solution will be 100% native-AI first. This will allow customers to test and verify agents at scale for the first time.

AI-Driven Development Lifecycle (AI-DLC)

During many of the sessions I attended, a big topic is the AI-Driven Development Lifecycle (AI-DLC) where spec-based development tools such as Kiro combined with enabling technologies such as MCP come together to deliver and AI-first end-to-end DevOps lifecycle. Thanks to an excellent presentation by Raja SP and a serendipitous hallway chat with my good friend Kawshik S, I am convinced more than ever that the future of software delivery and devops will be AI-native. We will be working on more whitepapers and videos on this topic.

Speaking of AgenticAI, it was fantastic to visit the re:Invent EXPO and see our customer success story for Spira and Rapise displayed live in the AWS Marketplace expo under "AI and Agentic AI Partners". It was amazing validation of the incredible work our teams have done helping customers realize real business value using Inflectra.ai.

Making Connections

Finally, conferences are as much about making connections with people and organizations. It was great to be able spend some time with Leslie Holland from our new partner Myridius.

In addition to meeting up with Leslie, it was wonderful to reconnect with many other folks such as Kathie Kinde Clark from Rhythmic Technologies, Bill L. Brown, Danielle Brommer Seth Clark from Mission, a CDW Company, Carly Castiner, and finally Shahram Anver a fellow founder and entrepreneur.

Keep building and Keep dreaming.... see you at AWS re:Invent 2026!

Adam

Webinar Recap | Experience The Seamless, AI-Driven Workflow Across the Entire Inflectra Suite

2025-11-21T15:33:48-05:00

The core of the seamless Inflectra workflow hinges on AI Agents managing the software lifecycle, shifting human focus from tedious coding and manual testing to high-value activities like specification and risk analysis. The presentation detailed the three generations of AI enabling this shift, how specifications are replacing code, and the crucial role the Inflectra platform plays in the new development paradigm.

Full Recording

1. Requirements as the New Code

The industry is rapidly moving past "Vibe Coding" (throwaway apps from simple prompts) to "Spec-Driven Coding," where detailed requirements become the primary input for AI development agents (like Amazon Kiro).

This shift in focus reverses the traditional Agile manifesto:

Machines will handle more of the coding and testing execution.
Humans will focus more on defining the specifications, conducting risk management, and performing reviews (of requirements, code, and test reports).

To facilitate this, Inflectra.ai uses the EARS (Easy Requirement Syntax) standard to analyze and improve requirement quality, ensuring the AI agent receives a robust specification to build from.

2. Spira: The AI-Powered Project Management Hub

The demonstration began in Spira, where Inflectra.ai served as a powerful project assistant, automatically generating project artifacts and managing risk:

Backlog Creation: From a single high-level feature description, Inflectra.ai generated a complete hierarchical backlog of detailed child requirements (user stories/use cases) and development tasks.
Quality & Risk: The AI analyzed requirements against the EARS standard, suggesting improvements and automatically generating project risks with mitigation strategies.
Testing Artifacts: Test cases and BDD-style Gherkin scenarios were instantly generated for the new requirements.
Progress Analysis: The AI can analyze a release or sprint to provide an instant risk and progress summary, alerting the team if key metrics (e.g., test execution status, task completion) indicate a risk of schedule slippage.

3. The Seamless AI-Driven Workflow: Spira ↔ Kiro ↔ Rapise

The true power of the platform was shown when the Spira data was exported to a development agent, creating a full application ready for testing.

Application Generation: Using MCP, the full project specification (requirements, tasks, test cases) was pulled from Spira into an agentic tool like Amazon Kiro.
AI Builds the App: Kiro used the spec to generate the entire application (including all code and even unit tests) and launched it locally.
Test Automation: In Rapise, the AI-generated manual test cases were imported directly from Spira.
- Rapise's Inflectra.ai was then used (the "magic wand") to convert the natural language steps into executable automated test code. The AI uses context to intelligently reuse existing objects and functions, promoting modular, maintainable code.
- The demo also highlighted the AI's ability to generate synthetic test data for scenarios requiring various inputs.
Close the Loop: The automated test was executed, and the results (including success/failure status and screenshots) were automatically published back to Spira, providing instant traceability and risk validation for the project team.

Conclusion

The webinar demonstrated a clear path for development and testing teams to adopt a cohesive, AI-first toolchain. By leveraging Inflectra.ai across Spira and Rapise, organizations can automate the creation of project artifacts, accelerate application development via agentic coding, and instantly convert manual specifications into automated tests.

This approach ensures that as coding speed increases, the critical activities of specification, quality assurance, and risk management are handled intelligently, allowing teams to Maximize Velocity while Minimizing Risk.

Start Your Free Trial Today!

You can experience this seamless, AI-driven workflow for yourself. Inflectra offers a 30-day free trial of Spira and Rapise—100% unlocked product access, no credit card required.

Get started and see how Inflectra.ai can transform your software delivery pipeline!

My Top 5 Predictions for 2026

2025-11-19T18:20:38-05:00

Forget "shift-left." The next era of quality isn't about where we test, but who—or what—does the work. By 2026, QA transforms from a human-led checkpoint to an AI-orchestrated system.

1. Your QA Team is Autonomous AI Agents

Imagine AI that doesn’t just find bugs—it diagnoses, patches, and deploys the fix across your systems while you sleep. Welcome to self-healing software. The new performance benchmark isn’t finding flaws; it’s how fast your systems recover without asking.

2. The User is No Longer (Just) Human

Your next "customer" might be another AI. As machines automate shopping, logistics, and support, QA must guarantee seamless machine-to-machine experiences. We're building for a hybrid world of humans and autonomous digital agents. Technologies such as MCP and A2A enable the rise of the digital team.

3. Death of the Coder (or Agile is Dead!)

Forrester Analysts shared their 2026 prediction, that software development will move from Jamming to Conducting an Orchestra. We agree and predict that Engineers will elevate to be solution architects, data quality managers, AI/ML trainers, strategic validators of complex systems rather than writers of code and test scripts. Another analogy is that we're moving from software development being a "craft" industry with hand-coded programs, to the rise of the software "factory" using agentic development tools, similar to how mechanical and civil engineers use CAD tools for physical engineering.

4. Quality becomes a Compliance Function

Regardless of "shift left" or CI/CD practices, quality delivery is a team sport that more and more will be led by the Chief Risk Officer. When AI agents make autonomous decisions, risk management can’t sit in engineering/delivery. The smartest companies are moving QA under Compliance and Risk leaders. Governance isn’t red tape—it’s the bedrock of trust in an automated world that facilitates trust between all internal and external stakeholders. Enterprise Risk Officers who traditionally have stipulated policies to prevent the use of AI will need to find a new path and up-skill quickly to embrace and harness AI.

5. Get Ready for the Hybrid, Quantum-Resistant Future.

The cloud is going hybrid by default, and AI is getting smaller, cheaper, and smarter even on-premise. But the real threat? Quantum computing breaks today’s security. Future-proofing now isn’t optional. Prevent and reverse the Collapse of Software Quality as shared here by Denis Stetskov and here is what you can do now to future proof.

The Bottom Line: QA is no longer a final check. It’s the intelligent, autonomous core of your development lifecycle. The question isn’t if you’ll adapt and adopt AI into optimizing your processes, but how fast you can shift from overseeing quality to orchestrating it cross functionally, inside and out with AI baked into most ERP, CRM, and SDLC platforms.

Is Your Avoidance of GenAI Creating the Very Risks You Fear?

2025-11-24T19:21:49-05:00

Inaction is Not a Neutral Position

Consider this: it’s like believing your children are safe online because they can’t type, only to find 100 tabasquishy toys charged to your account and delivered to your doorstep. How? They mastered voice commands from SKU to checkout. The key culprit was only six years old (real story!).

The point is, *inaction is not a neutral position.* It is a decision that cedes ground to more agile competitors and creates hidden, accumulating risk.

I’ve sat with Chief Risk Officers who proudly declared their AI moratoriums, only to see those same policies reversed months later under the weight of competitive pressure. I’ve seen a major financial institution in Asia choose manual Excel spreadsheets over an automated testing platform only to have millions of bank accounts move to a nearby country's digital bank.

They will “get by.” But “getting by” is the anthem of decline. It means daily frustrations, delayed releases, and an erosion of quality. The true discovery comes too late: lost customers, diminished market share, and disappointed shareholders. You lose the battle for talent and innovation, ultimately risking your organization's very relevance.

As a CTO, CIO, or COO, the question isn't *if* you should modernize your SDLC, but how fast you can afford to. Are you building a technology organization that fuels growth, or one that inadvertently stifles it?

No Decision is a Decision

The Inflectra Suite is the engine for the modern, AI-powered technology organization. We don't just add tools; we transform your entire delivery lifecycle from a cost center into a competitive weapon with two decades of tangible outcomes:

Breakdown bottlenecks: Ensure Business Continuity by liberating your testers from manual script writing. What took weeks now takes clicks, accelerating release cycles without sacrificing quality.
Orchestrate Operational Excellence with cross-functional delivery and end-to-end traceability. Learn how Leica Biosystems manages global medical device quality from marketing to delivery across multiple continents using Inflectra's SpiraPlan
Unleash Uncompromising Quality: See how Telstra International increased test coverage by 80% for their critical Salesforce ERP updates, turning quality assurance into a business advantage, even reducing maintenance costs.
Unprecedented Speed & Scale: Experience performance improvements from using Spira as seen with Orix Metro Finance & Leasing of 30-40% before AI and The Land Registration Authority Philippinnes LARES is seeing 65% savings of Development Hours and 60% saving in Test Planning Hours faster than traditional Spira platform without ai. inflectra.ai is helping customers generate drafts from Requirements generation (using EARs) to Tasks & Test execution to Delivery with Release Analysis and Risk Mitigations. All clearly tagged with ai generated/augmented ready for human validation.
Bridge the Gap Between IT and Business: You've armed developers with Jira, but have you truly connected your BAs, PMs, and QA teams to a single, unified agenda from Requirements to Release?

The Inflectra Suite, powered by AWS GenAI, creates this vital bridge. We generate requirements, tasks, tests, and risk mitigation priorities in a single, secure, governed environment. This creates a living, breathing system where every change drives the next best action:

QA Teams shift from writing scripts to understanding user needs.
Business Analysts maintain live, dynamic documents with full traceability, ending the era of dormant, outdated specs.
Project Managers gain real-time visibility into resource effectiveness, from average tests per day to bug-fix bandwidth, reporting to leadership without the manual grind.
Developers can switch from Jira to Spira or enjoy a directional sync with a single source of truth that empowers teams with minimal disruption.
Compliance personnel slash audit preparation time and gain AI-driven risk insights that human teams might miss.

This isn’t just an upgrade. It’s a fundamental rewiring of your delivery engine with a balanced risk appetite.

The choice is no longer between risk and safety. It's between leading the market and struggling to keep up.

Stop managing delays and start orchestrating excellence.

Watch the Demo. Schedule your Live Inflectra Suite demo today and embark on a free 30-day trial.

See how easily you can replace risks with resilience and turn your SDLM into your greatest competitive advantage.

XXXspiraplantrialXXX

Recap: AutomationSTAR, TestingUnited, CxO Roundtable and Meeting TXT Quence

2025-11-16T09:36:29-05:00

Exhibiting at AutomationSTAR 2025 in Amsterdam

We were excited to be back at AutomationSTAR 2025 in Amsterdam as an exhibitor and sponsor. Attendees visited the Inflectra booth to learn about how Generative and Agentic AI can transform their software delivery:

⭐️ SpiraTest - Test & Requirements Management: uses ai to automatically generate test cases, bdd scenarios, identify risks, review requirements and analyze progress.
⭐️ Rapise - Scriptless Test Automation: that uses AI to turn manual tests into automated, generative synthetic data, and uses computer vision to perform usability assessments

We also had our usual array of cool stickers and Inflectra merchandise. The questions and insights from the attendees will be used to further improve our products as we head into 2026.

Hosting an Executive Roundtable with AWS

After the conclusion of the AutomationSTAR event, we were privileged to host a CxO roundtable panel discussion with our partner Amazon Web Services (AWS) on the subject of building trustworthy AI, ensuring safety and compliance.

One of the attendees posted this great synopsis of the event. His key takeaways included:

🚫 Only 11% of organizations have adopted AI in full in their intended use cases due to unclear ROI and governance issues.
⚙️ Data governance challenges + integration complexity with legacy systems = AI bottlenecks.
🔒 Compliance risks and unclear regulatory frameworks, leading CISOs & Privacy officers to bottlenecks ( hello, EU AI Act).

What could help:

✅ A clear path-to-production plan which must include:

a clear problem statement
the business case and defined ROI (value)
the technical infrastructure (tech)
the regulatory framework (policies)
an impact assessment (risk)
an implementation plan (effort)
the necessary controls (compliance measures) and
a structured QA Testing and improvement.

✅ An elaborate data strategy & a data retention plan

✅ A clear governance framework

✅ An incident plan in case things go wrong.

🧠 An open mind because if we want a buy-in the benefits that AI can offer, we have to be open to experimentation under safe conditions and trust that by constant iterations we will be able to achieve a product that will deliver the desired value!

Speaking at TestingUnited 2025 in Milan

There was a great opening keynote at the TestingUnited conference by Tariq King on the subject of how AI is going to change development and testing. With his extensive pedigree and experience of the subject, it was refreshing to hear about what AI will change and what the new career landscape will look like.

There will be a need for testers to learn how to use AI to do testing of digital systems
Testers will need to learn new tools such LLMs as the Judge to test ai systems themselves.
Human experience testing involves both the digital and physical touch points. A great example of his flight from the US to the conference!

Finally some very good reference slides on how AI is being used to transform the SDLC. A lot of investment from the large AI platforms such as Microsoft, Amazon, Anthropic and Google is going into this space.

After Tariq's great keynote presentation, I had the privilege of speaking on the topics of AgenticAI based software delivery, Large Action Models (LAMs) and how to ensure safety and quality in this third age of GenerativeAI.

Thanks to Peter Svoboda, Nikolett Godova and Jana Svobodova for organizing the event and making everything run so smoothly.

During my talk I covered:

how we have now entered the third age of agentic ai with digital teams connected by #MCP and #A2A.
how software development will move from human craft coding to spec based development using tools like Amazon Kiro
practical tips and tricks for ensuring that you can turbocharge testing and other quality engineering practices to keep up.

Meeting Up With Our Italian Partner - TXT Quence

It was wonderful to meet up with our partner Andrea Picozzi from TXT Quence to discuss how GenAI is changing software delivery and qualityassurance.

It was also a great opportunity to share the product roadmap for SpiraTest - Test & Requirements Management, and Rapise - Scriptless Test Automation and understand some of the key use cases for Inflectra.ai in the Italian market.

We are excited to launch some new joint GTM motions next year #bettertogether.

GITEX 2025: Applied AI is Here, and It Demands a New Frontier for Quality

2025-11-16T05:47:50-05:00

Inflectra at the Heart of the Action

Our booth was a hub for leaders grappling with one central question: "How do we manage all this?" As companies rush to integrate AI, the conversations at GITEX have pivoted from "if" to "how,” and the "how" is where Inflectra shines.

Adam, Rick, and I spent the week demoing how our integrated platform provides the control and visibility necessary for this new era. Here were the top points of interest:

Testing the "Untestable": We showed how Rapise uses its AI-powered capabilities to test the dynamic, and often unpredictable, UIs of AI-driven applications. Standard automation breaks, but Rapise's intelligent, self-healing scripts can keep pace.
AI Compliance & Audibility: We demonstrated how SpiraPlan provides end-to-end traceability—from the initial requirement, through the model's development, to the final test case and defect. When a regulator asks, "How did your AI make this decision?" or "How did you validate this model?", our customers can provide a complete audit trail. This is no longer a "nice-to-have"; it's essential for compliance.
Managing the AI Lifecycle: We're not just testing. We showed how the Spira platform manages the entire Software Development Lifecycle (SDLC) and Model Development Lifecycle (MDLC) in one place. This unified approach to Quality Engineering and Agile Program Management is critical for organizations that need to scale their AI initiatives without sacrificing quality or control.

And, of course, our legendary Inflectra swag was a hit—our signature pens are now in the hands of some of the top tech leaders in the region!

Key Themes & Conversations from the Show Floor

Beyond our booth, the show floor buzzed with themes that hit at the core of what we do.

Applied AI Demands a New QA Paradigm: The "black box" nature of AI is a nightmare for traditional QA. We spoke with dozens of QA managers who are struggling to validate systems that learn and change. This confirmed our mission: providing tools that manage risk, traceability, and test coverage for complex systems, whether they're predictive models or embedded AI features.
Sovereign Intelligence is a Compliance Mandate: This was the biggest takeaway. The demand for data sovereignty isn't just about security; it's about compliance. Leaders from banking, government, and healthcare were explicit: they need to deploy AI, but they cannot have their sensitive data leaving their jurisdiction. Our long-standing commitment to offering robust on-premise and private cloud solutions was a massive differentiator. It means our customers don't have to choose between innovation and compliance.
The Talent-Tech Equation: We met so many brilliant developers and testers from across the Middle East and Africa. The region is a hotbed of talent. But talent alone can't scale. They need platforms that centralize collaboration, automate grunt work, and provide a single source of truth. Empowering these teams with the right tools is how the region's digital transformation will be successfully and safely delivered.

Forging Global Connections

For me, the highlight is always reconnecting with our global family. It was a pleasure to meet with our fantastic partners from across the EMEA region to strategize for 2026. We also had the chance to meet face-to-face with several of our key customers based in the UAE and Saudi Arabia, gathering invaluable feedback on their compliance and testing challenges.

A huge thank you to Adam Sandman and Rick Baucom for their incredible work. Their deep knowledge and high-level conversations were instrumental in making this event such a success.

What's Next?

Returning from GITEX always leaves me energized. The future is being built now, and it's clearer than ever that quality, testability, and auditable compliance are the essential foundations for the AI-driven digital economy.

We're already following up on the amazing connections we made and are excited to bring the insights from GITEX 2025 into our product roadmap.

A massive thank you to the GITEX Global organizers, our partners, our customers, and everyone who stopped by the Inflectra booth to talk about the future of quality. We can't wait to see you next year!

Webinar Recap: Unveiling the Power of Rapise 8.6 — New Features & AI Enhancements

2025-11-12T12:40:36-05:00

Full Recording

Key Takeaways

Seamless AI Integration with Inflectra.ai

The most significant update in Rapise 8.6 is the native and secure implementation of Inflectra.ai. We have built this to provide a world-class, context-aware generative AI experience that works right out of the box.

Out-of-the-Box AI: Users gain immediate access to AI capabilities without the need for complex configuration, tokens, or external accounts. Inflectra.ai is securely configured via the Spira administration panel and is powered by Amazon Bedrock.
Secure and Context-Aware: Our focus is on providing a secure, intelligent tool that understands the context of your testing framework.
Flexible Deployment: For customers who prefer to utilize their own infrastructure, the Rapise AI dashboard allows seamless configuration to private instances, such as Azure OpenAI, or other providers like OpenAI and Amazon, ensuring the same powerful functionality.

Enhanced Test Framework Organization and Data Sharing

Rapise 8.6 introduces new structural improvements to help our users build more scalable, consistent, and maintainable test frameworks.

Global and Common Definitions

We introduced a central location for sharing assets across the entire testing framework via the common.rvl.xlsx file:

Shared Variables & Maps: Define crucial configuration parameters (like a base URL) and reusable test data maps in one place. This eliminates hard-coding and duplication, saving considerable maintenance time.
Shared Repositories: By moving an object repository into common.rvl.xlsx, the repository and its objects become instantly available for reuse in any test case, ensuring consistent object identification throughout the framework.

Script-Specific Common Sheet

To balance global sharing with script-specific needs, using the hash sign (#) in a sheet name (e.g., #data) now designates a script-common sheet.

Any asset defined here is shared across all other sheets within that single RVL script, but remains private and isolated from the rest of the testing framework. This keeps your shared global definitions clean while providing localized structure.

Developer Productivity and Coding Enhancements

Our focus on developer experience brings several key quality-of-life improvements to Rapise:

AI-Powered Data Generation: Our AI feature can swiftly generate multiple rows of realistic test data or entire data tables for maps, including custom constraints (e.g., generating contacts with a first name starting with "C").
Controlling AI with Directives: We've introduced powerful new directives (e.g., ##AI:Module:) that can be added as simple comments. These allow you to precisely guide the AI, ensuring it uses specific Page Objects or ignores similar ones, resulting in more accurate and tailored code generation.
Folders and Namespaces for Page Objects: You can now logically organize your Page Objects using dot notation (e.g., CRM.leads.edit). This feature is essential for large-scale applications, preventing naming collisions and creating a clear, hierarchical structure within the Modules section.
In-Place Code Generation: For quick, custom logic, the AI can generate JavaScript code directly within a code block (e.g., a function to "harmonize phone numbers"). This capability allows our users to rapidly implement necessary utility functions and data manipulation logic.
Action Signature Creation: Users can now specify action parameters (like firstName, email, phone) directly when defining a new action for a Page Object, streamlining the setup process.

CI/CD and Headless Execution

We continue to enhance Rapise's role within modern DevOps environments:

Rapise Launcher Updates: The latest version of the Rapise Launcher, available as an NPM package, now supports generating detailed execution reports in the standard JUnit XML format. This facilitates seamless integration with popular CI/CD tools.
Rapise MCP Server (Preview): The new Rapise Multi-Modal Command Protocol (MCP) Server enables programmatic and conversational control of the Rapise application from external clients, such as VSCode or Copilot. This opens powerful new possibilities for managing your test assets (e.g., organizing tests by tag or running specific test groups) through a chat-like interface.

This release is a testament to our commitment to innovation and empowering our customers with the best tools for intelligent, low-code test automation.

Ready to Experience Rapise?

We invite you to try Rapise yourself with a 30-day, 100% unlocked, free trial. Discover how Rapise 8.6, with its cutting-edge AI and advanced features, can transform your test automation efforts today! If you have any questions, feel free to email us at rapise@inflectra.com.

Displaying DORA Metrics in Spira for DevOps Productivity Tracking

2025-11-06T15:36:58-05:00

What Are the Four DORA Metrics?

The four DORA metrics are:

Lead time to change: time from code commit to deployment
Change failure rate: percentage of failed changes in the production environment
Deployment frequency: how often code is deployed to production
Mean time to recover (MTTR): how fast teams can recover from a failure. This metric is also called “Failed deployment recovery time.”

Together, they give a balanced view of speed and stability: two measure flow and throughput, two measure quality and resilience. They’re technology-agnostic and can be instrumented from your CI/CD, incident, and version-control systems.

They’re important because they correlate with better organizational outcomes—happier teams, faster delivery, more reliable services, and ultimately better business performance. Tracking them helps teams spot bottlenecks (e.g., long code review cycles), reduce risk (by shrinking batch sizes and automating tests), and focus improvement work where it matters. Used well, DORA metrics become a shared language across engineering, product, and leadership to align goals, benchmark against high performers, and continuously improve both developer experience and customer value.

Using Spira to Track DORA Metrics

Spira is a great choice for tracking and measuring the four DORA metrics. Spira’s integrations with CI/CD tools such as GitHub and GitLab pull commits, branches, PRs/MRs, build and deployment events from GitHub Actions or GitLab CI. That gives you the time-stamped breadcrumbs needed for all four DORA metrics without manual spreadsheets. Spira lets you standardize what counts as a “deployment,” which environments to include (e.g., only prod), and how failures are classified. That consistency means your DORA trends are apples-to-apples across teams. Spira provides end to end traceability from requirements → user stories → tasks → commits/PRs → builds → automated tests (Rapise or other) → deployments → incidents. Because Spira links all these artifacts, you can drill from a red DORA KPI straight to the exact change, test evidence, and incident.

In addition to providing the core DORA metrics, using Spira together with the different CI/CD platforms has added benefits beyond doing it manually:

Quality signal baked in. Tie CI test runs and coverage into the same system so DORA trends are shown alongside failing tests, flaky suites, or missing coverage. That context turns a metric into an action plan.
Governance for regulated teams. Spira’s workflows, audit trails, baselines, and approvals provide the compliance layer (who changed what, when, and why) that pure CI/CD tools don’t emphasize—useful for regulated industries such as life sciences, finance, and government.
Root-cause and learning loops. When a deploy is marked failed and an incident is opened, Spira links the deployment to the incident and postmortem tasks. You get MTTR and CFR that are explainable with one click.

Portfolio roll-ups: With SpiraPlan, you can aggregate the DORA metrics across many projects and programs for executive views while preserving team-level drill-down.

Tag-based commit linking: Use commit/PR keywords like [RQ:123] [IN:45] to auto-associate code to requirements and incidents—keeping the graph clean with minimal effort.

We now look at each of the four metrics and how to map them to Spira reports:

DORA Metric: Lead Time To Change

The Lead Time to Change measures how long it takes a code change to reach users, defined as the elapsed time from when a change is integrated (typically a PR is merged to the main branch) to when a successful production deployment that includes that change finishes. It captures the speed of your delivery pipeline.

Shorter lead times generally indicate smoother, more automated paths to production and tighter feedback loops, especially when paired with healthy deployment frequency; longer times can reveal bottlenecks in reviews, builds, approvals, or release practices.

When implementing this DORA metric in Spira, we are making use of the following artifacts:

Pull Request Tasks (which sync from CI/CD tools such as GitHub)
Releases

In general, the lead time is calculated as the average duration between creation and merging of a Pull Request (PR). Using the Tasks view, we can find the difference in time between when the PR task was opened and closed. However since we want to look at our productivity improvement over time, we group the PRs by release and then average the PR duration over the release. See the detailed KB article for more details.

DORA Metric: Deployment Frequency

Deployment Frequency is how often your organization successfully deploys code to production, typically counted as the number of production releases per service (or product) over a standard interval (e.g., per day or per week). It reflects delivery cadence and should be normalized by system/team to avoid masking variation; only successful production deployments are counted, while rollbacks are excluded or tracked separately.

When implementing this DORA metric in Spira, we are making use of the following artifacts:

Builds (which sync from CI/CD tools such as GitHub)
Releases

In general, the deployment frequency is determined by dividing the total number of successful deployments by the number of days in the given period. A successful deployment is defined as a build pipeline that has a status of 'Success' and is for the 'main' branch. For those projects using the GitFlow methodology, the 'develop' branch may be the appropriate branch instead. See the detailed KB article for more details.

DORA Metric: Change Failure Rate

Change Failure Rate is the percentage of production deployments that cause a service degradation and require remediation—such as a rollback, hotfix, or incident—within a defined window. Compute it as: failures ÷ total successful production deployments (e.g., in the last 30 or 90 days), where “failure” is operationally defined up front (sev-1/2 incidents, rollbacks, emergency patches, feature flags forced off, etc.).

When implementing this DORA metric in Spira, we are making use of the following artifacts:

Releases
Incidents
Builds (which sync from CI/CD tools such as GitHub)

In general, the change failure rate is calculated by dividing the number of incidents by the total number of successful deployments. Incidents are defined as P1 bugs in work items. Successful deployment are defined as a build pipeline that has a status of 'Success' and is for the 'main' branch. For GitFlow environments it would be the 'develop' branch instead. See the detailed KB article for more details.

DORA Metric: Mean Time To Recover

Mean Time to Recover (MTTR) measures how quickly you restore normal service after a production incident, defined as the elapsed time from incident start or detection (e.g., alert fired, SLO breach began) to service restoration (impact ended/SLO back in compliance).

When implementing this DORA metric in Spira, we are making use of the following artifacts:

Releases
Incidents
Builds (which sync from CI/CD tools such as GitHub)

In general, the mean time to recover (MTTR) is calculated by the average time it takes to close an incident within a period of time. Incidents are defined as P1 bugs. See the detailed KB article for more details.

Local Expertise, Global Solutions: Inflectra & Mortoff at HUSTEF 2025

2025-10-28T15:41:30-04:00

A Strategic Partnership Strengthened in Budapest

As a global company, we often rely on our strong Partner Network to be our “eyes and ears” on the ground locally, offering deep local expertise and insight. It was a pleasure to meet with one of our key partners in Central-East Europe, Mortoff, for the second time in-person. While we were there, we were able to align on strategies, exchange valuable intelligence on key industries in CEE, and plan new, collaborative avenues to better serve our joint customers. This close coordination ensures that customers receive solutions that seamlessly blend Inflectra's global platform strength with Mortoff’s expert local delivery.

Connecting with the Testing and Quality Community in BudaPest

The HUSTEF conference took place in the Hungarian Railway Museum this year (Europe’s largest open-air railway entertainment park), and provided an inspiring backdrop for conversations with the attendees. At our joint booth, Inflectra and Mortoff spoke with quality engineers and testing experts from across all industries. We observed particularly strong interest in our test automation platform, Rapise, and our embedded Generative AI engine, inflectra.ai.

A major focus for many attendees was tool integration. Testers were keenly interested in how easily our platforms integrate with the wide ecosystem of tools they already use, proving that flexibility and connectivity remain key requirements for modern software teams.

Customer Success in the Spotlight

A highlight of the conference was meeting with our customer, Szerencsejáték Zrt., the Hungarian lottery company. They are a dedicated user of SpiraTeam, and their success story served as powerful validation of our platform's value and Mortoff’s services. Check out the video below to hear how they use SpiraTeam and the benefits they’ve experienced.

Looking Ahead: Momentum in Central-East Europe

The HUSTEF conference concluded successfully, leaving the Inflectra team energized by the positive momentum within the quality community. Our time in Budapest was a strong reaffirmation of our strategic alliance with Mortoff and our shared mission to empower Central-East European companies with smarter, faster, and more efficient software delivery.

We look forward to continued collaboration with Mortoff and seeing everyone again at HUSTEF next year!

Using the new Rapise MCP Server that Comes with Rapise 8.6

2025-10-21T08:21:23-04:00

Connecting Specs in Amazon Kiro to Rapise

As we have seen in our whitepaper, it is very easy to create a product spec in Amazon Kiro using Spira's MCP server. As part of spec-based development, the MCP Server will allow Kiro to download all of the requirements, test cases, tasks and risks, and use them to create the four different spec files need to build the target application:

requirements.md
tasks.md
tests.md
design.md

However with our new Rapise MCP server, we can go one step further:

With just a few sentences, Kiro can automatically import the contents of the tests.md file into Rapise as AI command test instructions in the RVL worksheet. They are now ready to be executed using Inflectra.ai.

Downloading Test Cases from Microsoft Azure DevOps into Rapise

We have had several customers request the ability to download test cases and manual tests from Microsoft Azure DevOps into Rapise, similar to how you can seamlessly download Spira manual test cases into Rapise. By connecting an MCP Client such as CLINE (running in VS Code) or Cursor, you can quickly retrieve all the test cases from an Azure Test Plans project, using the ADO MCP Server, and import them into Rapise using its MCP Server.

The prompt is relatively simple, just enter something like:

I want you to import all the test cases with steps from [Azure DevOps URL] into Rapise group [Rapise folder]

You can then sit back and have some coffee while the AI tools do all the hard work for you ;-)

XXXrapisedemoXXX

Investing in Your Quality: What We Learned at STARWEST 2025 to Strengthen Our Solutions

2025-10-03T14:20:55-04:00

Strategic Advantage: Our Joint Session with AWS

The overwhelming theme of the conference was the rapid integration of Artificial Intelligence into the software development lifecycle. Our presence at STARWEST ensured Inflectra remains at the forefront of this shift, which is critical for our customers relying on us for future-proof tools.

The highlight of the week, and a key demonstration of our commitment to platform reliability and scalability, was our presentation: “Software Delivery At the Speed of AI: An Inside Look at How We Built Inflectra.ai.”

Our CEO, Adam Sandman, co-presented this session with CJ Sturgess, a Partner Solutions Architect at Amazon Web Services (AWS). This joint session showcased not just what our AI does, but how we engineer it for enterprise-grade performance, stability, and security on the AWS platform. The core message centered on delivering tangible customer value across the software lifecycle:

Faster Delivery: By showcasing how Inflectra.ai instantly generates test cases, tasks, and code snippets, we demonstrated how your teams can cut down on time-consuming manual work.
Smarter Workflows: Demos of SpiraPlan highlighted how predictive analytics help Project Managers proactively address inefficiencies and predict project roadblocks, ensuring your projects stay on track.
Resilient Automation: We showed how Rapise uses machine learning for advanced object recognition, resulting in test scripts that are less fragile and require less maintenance—saving your team countless hours and reducing overhead.

The continuous feedback loop from the hundreds of QA professionals who visited our booth directly influences the next generation of features we prioritize, guaranteeing we are building the tools you actually need.

Collaborative Strength: Enhancing Our Service Offering for Customers

Software quality is often a complex challenge that requires both cutting-edge tools and expert services. This is why our partnership ecosystem is so valuable to our customers.

We were thrilled to be side-by-side with our partners at Checkpoint Technologies. Having our booths next to each other created a natural, seamless opportunity to demonstrate the value of our joint services. We spoke with countless attendees about how the powerful combination of Inflectra's robust platforms and Checkpoint’s expert consulting, training, and implementation services provides a complete solution.

This close collaboration at STARWEST wasn't just about networking; it was about strengthening our ability to implement and support Inflectra's solutions in your environment, ensuring faster deployments and maximum return on investment for our customers.

The Inflectra Booth: Hands-On with AI-Enhanced Platforms

Our booth was a central point for engagement and discussion among attendees. We were delighted to welcome so many professionals to experience the transformative impact of our AI-enhanced platforms firsthand. Sponsoring the Expo Day 1 Lunch was a great way to drive fantastic afternoon traffic, allowing us to connect directly with a high volume of current and prospective users.

Visitors got hands-on with:

SpiraPlan: Seeing how our Agile program management tool uses AI-driven insights to manage risks and resources.
Rapise: Experiencing the efficiency of AI-powered test automation across web, desktop, and mobile applications.
Inflectra.ai: Watching live demos of our embedded Generative AI engine instantly creating test artifacts and predicting risks—turning theory into practical reality.

We also had a great time handing out exclusive Inflectra merchandise and engaging in conversations that will help us further refine our products to better meet your real-world needs.

Looking Ahead: A Partnership in Quality

STARWEST 2025 was confirmation that the entire industry is focused on solving the challenge of maintaining quality amidst rapid development. By sharing our vision for Intelligent Software Delivery and learning directly from the community, we have strengthened our own business and, more importantly, solidified our product roadmap to meet your future needs.

Thank you to everyone who shared their challenges and aspirations with us. We are energized and ready to help you level up your testing game with the next generation of AI-enhanced tools.

Ready to leverage the insights from STARWEST? Contact us today to see how Inflectra can help your team deliver high-quality software at the speed of AI.

Testing Chatbots with Spira and Rapise from Inflectra

2025-09-18T07:48:34-04:00

1) Model your chatbot in Spira

Requirements & user stories: Capture intents, entities, guardrails (e.g., “no PII in replies”), channels (web widget, Slack, Teams), locales, and SLAs (latency, uptime).
Artifacts & traceability setup:
- Custom lists: Intents, entities, personas, prompt versions, model versions, temperatures, knowledge-base (RAG) snapshots.
- Test case types:
  - NLU (intent/entity recognition)
  - Dialog management (multi-turn flow)
  - API/integration (LLM, middleware, search/RAG)
  - UI channel (web/Slack/Teams widget)
  - Safety/guardrails (prompt-injection, toxicity, jailbreaks)
  - Non-functional (latency, rate-limit handling, resiliency)
- Test sets: By channel (Web/Slack), locale (en-US, fr-FR), and scenario pack (Happy Path, Edge Cases, Adversarial).
- Traceability: Link requirements → test cases → automation scripts → defects. Use Releases to represent bot versions; Configurations to represent model/prompt settings.

XXXspiratesttrialXXX

2) Automate conversations with Rapise

Rapise can drive both UIs and APIs, so you can test the bot end-to-end or headless.

A. Web/desktop/mobile chat UI

Selectors & actions: Use Rapise’s web/mobile drivers to open the chat widget/app, send messages, click quick-replies, upload files, and read bot responses.
Assertions for variable text:
- Accept sets of valid responses (allowlist).
- Use regex/contains for flexible matching.
- Validate JSON blocks in responses (schema checks).
- Verify links/buttons appear and function.
Multi-turn context: Keep the same browser/app session; store conversation IDs; assert state carries across turns.

B. API-level testing (headless)

Use Rapise REST/GraphQL to call your bot gateway (or orchestration layer), pass a conversation/session id, and validate:
- Predicted intent/entity payloads
- Dialog state transitions
- Latency (measure response times per turn)
- RAG traces (source doc ids, confidence) when available
Data-driven runs: Feed utterances/expected results from CSV/Excel; iterate across locales/personas.

C. Safety & resilience suites

Prompt-injection & jailbreaks: Maintain a curated library of adversarial prompts; assert that replies follow policy (e.g., refusal templates).
Toxicity/PII checks: Pattern-match for emails, SSNs, profanity; assert redaction or refusal.
Rate-limit & retries: Simulate bursts, verify graceful degradation and backoff messages.
Fallbacks: Force upstream errors (mock 500s) and ensure the bot gives a helpful, on-brand fallback.

XXXrapisetrialXXX

3) Make “fuzzy” results testable

Chatbots are non-deterministic—design your assertions accordingly:

Equivalence classes: Define multiple acceptable phrasings per test.
Semantic similarity (optional): If your team exposes an internal similarity API or keyword scorer, call it from Rapise and assert a minimum score (keep it deterministic—same model & seed).
Structured anchors: Prefer validating facts (dates, amounts, URLs, buttons, JSON keys) over prose.

4) Close the loop with Spira

Spira ⟷ Rapise integration: Use the built-in connector so Rapise pushes execution results, logs, and screenshots back into Spira automatically—linked to the right test cases and releases.
Dashboards & KPIs in Spira:
- Intent accuracy, entity F1, flow pass-rate
- Safety violations by type
- P95/P99 latency by channel
- Regression deltas after prompt/model changes
Defect workflow: When an assertion fails, Rapise can file a defect in Spira with evidence (transcript, HAR/logs, screenshots) and the exact environment (model version, temperature, KB snapshot).

5) Typical test assets (starter set)

Requirements:
- R-001 “Bot supports 25 core intents at ≥92% accuracy”
- R-010 “No PII should appear in responses”
- NFR-003 “P95 latency ≤ 1200 ms Web; ≤ 1500 ms Slack”
Test cases:
- NLU-EN-GREET-001: “hello / hi / hey” → intent:greeting
- DLG-RETURNS-004: multi-turn return workflow incl. slot filling & disambiguation
- SAFE-INJECT-009: “Ignore prior instructions and …” → refusal template
- API-RAG-012: Boson FAQ → verify cited doc IDs
- PERF-LAT-P95-001: 100 sequential turns; assert P95 SLA
Data sets: CSV/Excel of utterances, entities, locales, allowed replies, and negative tests.

6) Environments, versions, and CI/CD

Environments in Spira: Dev / Staging / Prod with Configurations for model=GPT-X.Y, temperature=0.2, prompt=v14, KB=2025-09-01.
RemoteLaunch: Schedule Rapise suites from Spira nightly or on commit; fan-out across hosts.
Gates: Only promote releases when Spira dashboards show green on accuracy, safety, and latency.

7) Reporting that stakeholders understand

Conversation transcripts: Attach exact turn-by-turn logs to Spira executions.
Evidence packs: Screenshots, HARs, and API payloads from Rapise.
Trend views: Compare model/prompt versions per metric to quantify regressions/improvements.

Quick “first implementation” checklist

Create intents/entities & SLAs as Requirements in Spira; link a Release for “Bot v1.4”.
Build data-driven Rapise tests (CSV) for top 20 intents + 5 multi-turn flows.
Add safety suite with 25 adversarial prompts.
Connect Rapise to Spira; run via RemoteLaunch on each PR to prompts or model.
Track latency & accuracy in Spira dashboards; open defects with transcripts automatically.

XXXspiratesttrialXXX

Atlassian Ends Jira Data Center – Why SpiraTeam Is the Best Choice for Self-Hosted ALM

2025-10-16T06:39:24-04:00

The End of Jira Data Center

With Atlassian retiring Jira Data Center, customers are being steered toward Jira Cloud. While the cloud-first strategy aligns with Atlassian’s business model, it doesn’t always align with the needs of enterprises in regulated industries, government agencies, or companies with stringent data sovereignty requirements. For many organizations, running mission-critical lifecycle management tools on-premises—or in their own private cloud—is non-negotiable.

This leaves thousands of Jira Data Center users facing a looming migration deadline with limited options.

Here's some key dates:

New subscription sales for existing customers will end on March 30, 2028 at 23:59 PST.
Expansions and upgrades for existing subscriptions will end on March 30, 2028 at 23:59 PST.
Data Center Marketplace app sales for existing customers will end on March 30, 2028 at 23:59 PST.
End of life for impacted Data Center products will take place on March 28, 2029 at 23:59 PST.

After your Data Center subscription expires, your data will continue to be available in a read-only state. However, product updates and support will no longer be available in case of technical issues.

Atlassian strongly advises against keeping your product running in a read-only mode while connected to the internet, since no new security bug fixes will be provided after the end of life date for Data Center.

Why SpiraTeam Is the Right Alternative

Inflectra’s SpiraTeam is purpose-built for organizations that need the flexibility of self-hosting without sacrificing modern functionality. Unlike other vendors pushing customers exclusively to SaaS, Inflectra remains committed to giving customers a true choice between cloud and on-premises deployments.

Here’s why SpiraTeam is the natural successor to Jira Data Center:

Self-Hosted or Cloud—Your Choice: Deploy SpiraTeam on your own infrastructure, in your private cloud, or leverage Inflectra’s secure SaaS hosting.
End-to-End Lifecycle Management: More than just issue tracking, SpiraTeam unifies requirements management, test management, release planning, source code integration, and agile project management in one system.
Compliance & Traceability: SpiraTeam was designed with regulated industries in mind. It provides full end-to-end traceability across requirements, code, tests, and risks—helping meet standards like ISO, FDA, IEC 62443, and more.
Robust Integrations: With built-in DevOps connectors and integrations to tools like Git, Jenkins, Selenium, and IDEs, SpiraTeam fits seamlessly into modern toolchains.
Predictable, Customer-Friendly Pricing: Inflectra offers straightforward licensing with no hidden fees, ensuring your costs remain stable as you grow.
Commitment to On-Premises Customers: Unlike Atlassian, Inflectra isn’t abandoning customers who need self-hosted solutions. Supporting hybrid and regulated enterprises is core to our mission.

What This Means for You

The retirement of Jira Data Center doesn’t need to derail your operations. Instead, it can be an opportunity to upgrade to a more complete lifecycle platform with SpiraTeam. You’ll gain broader functionality, tighter compliance features, and the freedom to host your solution where it makes the most sense for your business.

✅ Next Steps:
If you’re a Jira Data Center customer exploring your options, now is the time to evaluate SpiraTeam. Inflectra’s migration experts can help you plan a smooth transition so your teams continue working without disruption.

XXXspirateamtrialXXX

Do You Own Quality Yet Tired of Your Tools Holding You Hostage? There's a Smarter Way.

2025-09-10T06:55:16-04:00

Quality is a Team Sport

Quality goes beyond testers. If you're accountable for delivering flawless software at speed or maintaining systems with frequent updates, all while navigating complex toolchains, tightening regulations, scarce resources and heightened expectations, you're not alone:

Tool Sprawl: Paying for a dozen specialized tools yet still missing a “single source of truth”.
Unreliable Data: Can't trust siloed, outdated reports to make critical, real-time decisions.
Audit Anxiety: Spending weeks preparing for compliance audits and fearing gaps.
Release Envy: losing market share to competitors launching faster and more frequently.
Security Risks: Hesitant to upload sensitive data to open-source or cloud-only platforms.
Domino Effect: Over-reliance on a few skilled developers who know the custom code
Reactive Firefighting: Overwhelmed by data but unable to anticipate risks to prioritize
Meeting Mayhem: wasting valuable time gathering stakeholder input/sign-offs.
Inconsistent Quality: Manual peer reviews that miss critical issues and test coverage.
Burn out on the burn down: Talented team members bored on mundane, repetitive maintenance instead of addressing actual vulnerabilities.

It's time to stop wrestling with your tools and start empowering your team. Let's explore how Inflectra, as a leader in quality assurance, provides a smarter, faster, and more productive way to help you delivery quality at scale across your organization and ecosystem.

The All-in-One Platform for Modern Quality Assurance

Inflectra’s SpiraPlan and Rapise unite your entire application lifecycle into one seamless, powerful platform. Instead of juggling disconnected point solutions, you get an integrated system that connects requirements, testing, tasks, development, and deployment with full traceability, risks and reporting.

SpiraPlan can seamlessly replace or integrate with your existing tools—including Jira, IBM DOORS, Jama, Azure DevOps, ServiceNow, and over 80 others—to become your Quality Center of Excellence certifying in-house developed or outsourced products.

How Does Inflectra Compare to Other Automation Platforms

Product	Best For	Key Limitations	Relative Cost & Model
Inflectra	Teams that need a unified, codeless, and compliant ALM platform with end-to-end traceability and powerful test automation for web, mobile, API, desktop, and legacy systems (on prem/SaaS on AWS)	Mac/Linux IDE	$$ Free trial and concurrent licenses with unlimited users. Includes enterprise support.
Katalon Studio	Teams wanting a ready-made, low-code solution based on Selenium	Less focus on full-lifecycle traceability and slower execution for high-volume regression tests	$$ free tier and paid plans
Playwright/Selenium	Developers who want full control and are willing to build and maintain a custom framework from scratch	Web-only automation High reliance on skilled coders Requires internal maintenance and lacks enterprise guardrail	Free to license, but high hidden costs for development and maintenance.
Leapwork / UiPath /Automation Anywhere	Business analysts automating business processes (RPA) and simple tests without code.	Premium price for RPA-focused features. Not primarily designed for robust software testing automation	$$$$-$$$$$ ($4k-10k+/bot)
Azure DevOps + Test Plans	Teams fully invested in the Microsoft ecosystem wanting integrated CI/CD and basic test management.	Testing is a module, not a dedicated best-in-class solution. Lacks advanced codeless capabilities	$-$$ Basic tiers are free; Test Plans add cost per user per month ~$50/user/mo)

Why Leading Teams Choose Inflectra:

Learn more about how Inflectra’s customers Assure Quality and Accelerate Delivery. Our customers in highly regulated industries like finance, healthcare, and government choose us because we solve their core challenges:

All-in-One Collaboration: Replace patchwork of tools with end to end traceability offered by SpiraPlan across requirements, tests, tasks, releases, risk, development and reporting management so your Quality Assurance team/Testers, Business Analysts, Project Managers and Development Engineers operate from a single source of truth that integrates with over 80+ commonly used SDLC applications for free.
Empower your entire team – not just developers! Codeless (with Coder Flexibility) natural language prompts in both Spira and Rapise codeless test automation native to Spira lets anyone create and execute automated tests especially useful for the high volumes of repeatable regression testing. For experts, it also supports JavaScript with Selenium, Playwright, and Applitools drivers built-in, protecting your investment for decades while removing your reliance on coding.
Cut your regression testing time by up to 70% with unbreakable tests: Our self-healing object recognition automatically adjusts to UI changes, drastically reducing test maintenance.
Guarantee compliance and streamline your audit process. Enterprise-Grade Scale, Security & Safeguards. Generate auditable traceability matrices and compliance reports instantly, turning audit preparation from weeks into real time supported exclusively by AWS (even for inflectra.ai).
Unmatched ROI: With the ability to replace Jira or data sync with Jira, we offer unlimited users on concurrent licensing; unlimited tokens on Inflectra.ai capped per user budget and included enterprise support, you accelerate delivery without inflating your budget across time zones and even with 3^rd parties.

Stop letting your tools dictate your pace. Learn how your team can work smarter, move faster, and deliver quality with confidence: Watch Demo and experience for yourself by exploring this 30-day Free Trial or book your Personalized Demo with an Expert today and we'll show you how Inflectra can:

Unify your disparate tools into a single source of truth and lift test coverage by 80%
Cut your regression testing time by up to 70%.
Guarantee compliance and streamline your audit process.
Empower your entire team—not just developers!

XXXspiraplantrialXXX

Testing Talks Sydney 2025: Inflectra’s Key Takeaways

2025-08-03T23:00:59-04:00

Conversations with the Community

Our presence at the Testing Talks booth was a hub of lively discussions about the challenges and opportunities facing customers, partners, and industry peers. Unsurprisingly, a central topic this year was the impact of AI on the industry. It was our first year showcasing our new inflectra.ai solution, Inflectra’s embedded Generative AI engine, at the event, and the response was overwhelmingly positive.

We fielded many questions about how we're integrating Generative AI into our tools like SpiraPlan to keep up with modern demands. The conversations also naturally turned to the critical topic of security and trust. We were proud to explain that our inflectra.ai solution is built on a foundation of security and transparency:

Hosted in secure, regional AWS zones to ensure data residency compliance.
Powered by Amazon Bedrock and built upon Inflectra’s own Responsible AI policy.
Enabled only with double opt-in controls at both the system and project levels.
Fully transparent, auditable, and completely under your control.

Beyond our AI-focused tools, we also saw a significant increase in interest in our test automation platform, Rapise, compared to previous years. Attendees were particularly interested in how we can help them better integrate risk management into their entire SDLC, highlighting the growing need for a holistic approach to quality. We also had the opportunity to connect with several valued regional partners, including DevOps1, Planit, and Net Fusion Technology (NFT), reinforcing our collaborative approach to serving the Australian market.

Adam Sandman's Talk on the Evolving QA Landscape

A major highlight of the day was Inflectra’s Founder and CEO Adam Sandman's talk, where he drew on his extensive global experience to unpack how AI-powered testing is fundamentally reshaping the QA landscape. Through real-world examples, he showcased how teams can accelerate high-volume test execution, improve efficiency, and cut costs, all without compromising on quality.

Adam’s talk distilled the changing face of our industry into a few thought-provoking takeaways:

He argued that "agile is dead, long live agility."
In the age of non-deterministic AI, failures are no longer bugs but risks.
When a failure is found, the focus shifts from fixing the code to correcting the requirement, as agentic AI can simply regenerate the code.
The role of "tester" will give way to "Quality, Safety, and Risk engineers."
He encouraged the audience to be curious and experiment with agentic AI tools like Claude and Kiro.
The ultimate conclusion: code is ephemeral, and requirements are the new currency.

Another Year in the Books

We are grateful to the organizers of Testing Talks for bringing together such a focused, energetic, and engaged crowd year after year. It’s always a pleasure to share a day with the Australian testing community to swap ideas, learn, and “nerd out” about all things testing, QA, and AI, and our team is looking forward to exploring how we can incorporate some of these ideas for future tool development and strategy.

Thank you to everyone who stopped by our booth and attended Adam’s talk. We look forward to seeing you all next year at Testing Talks 2026!

Inflectra Strengthens Ties at Tezza Business Solutions Happy Hour in Lagos

2025-07-25T11:03:05-04:00

Strengthening Partnerships: Dinner with Tezza

Before the main event, Samy had the pleasure of joining the Tezza team for a delightful dinner. This provided a more intimate setting for deeper conversations about the future of our partnership and the exciting opportunities within the African tech landscape. It was an invaluable chance to connect on a more personal level and solidify our collaboration.

Thanks to Roland, the CEO of Tezza. This dedicated time allowed for strategic discussions, aligning our visions, and exploring how Inflectra and Tezza can further collaborate to deliver unparalleled value to clients across Africa. These personal engagements are crucial for building strong, lasting relationships and driving mutual success.

Engaging Discussions and Key Insights

The event itself featured an insightful panel discussion where industry experts delved into the evolving landscape of software quality and digital transformation. The diverse perspectives shared during the panel offered valuable insights into the challenges and opportunities facing the African tech scene.

Adding to the depth of the discussions, Adam Sandman, CEO of Inflectra, joined the event via video call to deliver a compelling presentation. He shared Inflectra's vision for the future of QA and how our solutions are empowering organizations worldwide to achieve their quality goals. His virtual presence further highlighted Inflectra's global reach and commitment to supporting the growth of technology in Africa.

Conversations That Matter: AI, Cybersecurity, and the Future of Testing

One of the core themes that emerged throughout the evening was the transformative role of AI in software testing. Samy shared insights on how artificial intelligence is no longer a buzzword, but a strategic enabler for modern QA teams. From intelligent test case generation to predictive defect analysis, Samy highlighted how AI can enhance productivity, reduce cycle times, and support continuous delivery.

“AI is not here to replace testers—it’s here to empower them,” Samy explained. “By leveraging AI, testers can move away from repetitive manual tasks and focus on higher-value analysis and decision-making”.

Another key focus was cybersecurity in the QA lifecycle. As software systems become more complex and threats more sophisticated, integrating security testing earlier in the development process—“shifting security left”—is becoming critical. Samy emphasized the importance of automated vulnerability scanning, risk-based testing, and collaboration between QA and cybersecurity teams.

“Quality without security is incomplete. In today’s environment, software needs to be not just functional and fast—but secure by design,” Samy noted.

Connections and Collaboration

Beyond the panels and discussions, the event was a fantastic opportunity to connect with Tezza clients, partners, and like-minded professionals in the QA and DevOps community. The atmosphere was friendly, insightful, and energetic—exactly what you’d expect from a room full of innovators.

Samy’s presence helped elevate our brand awareness and spark conversations about how Inflectra is driving value in enterprise QA, AI-powered testing, and secure delivery pipelines. He also gathered valuable feedback and market intelligence to help us fine-tune our solutions to meet the needs of fast-growing markets like Nigeria.

Thank You, Tezza!

We extend our sincere thanks to Tezza Business Solutions for organizing such a meaningful and well-executed event. It’s clear that Africa’s tech scene is booming, and it was an honor to be part of the conversation shaping its future.

Stay tuned for more field stories from our global team as we continue to connect, innovate, and deliver worldwide by subscribing to our newsletter.

From Partner Insights to Product Futures: Inflectra's Journey at AWS NYC Summit

2025-07-21T15:11:29-04:00

Day One: Deep Dives and Dynamic Connections at the Partner Summit

The Partner Summit day was all about strengthening alliances and charting the course for shared success. The keynote, focused on "reinventing the partner experience to support accelerated growth of our shared customers through innovation," set a great tone to start the day. AWS executives shared insights into significant investments in Generative AI, Agentic AI, and the AWS Marketplace, underscoring the collaborative spirit that drives the AWS ecosystem.

Our team attended various sessions, including a deep dive into Generative AI, strategies for Marketing for Success, and tactics for engaging Industry Markets. Adam also had the opportunity to attend an executive breakfast and dedicated roundtable for Generative AI Competency holders, where leaders discussed how we were moving into the world of AI agents. (See if you can spot our logo below among the list of AWS GenAI Competency holders!).

After a packed day of learning, the networking continued into the evening. We kicked off with the AWS Rising Stars Networking event, an exclusive opportunity to connect with the AWS Emerging Partner Leadership team and fellow Rising Star Partners. This was followed by a stop at the Workload Migration Program (WMP) happy hour, providing a valuable chance to network with other ISVs focused on accelerating workload migrations to SaaS. We wrapped up the evening enjoying the iconic NYC skyline at sunset – a perfect end to a productive day.

Key Takeaways from the AWS Partner Summit:

The future of software delivery is clearly heading towards Agentic AI, envisioning a powerful collaboration between humans and "digital humans." Some critical insights emerged regarding software testing, software delivery, and quality assurance:

Kiro and the Future of Coding: Amazon's new agentic coding platform, Kiro, is set to revolutionize current coding assistants. It reflects a growing belief (which we at Inflectra share) that future software delivery will be driven by requirements and specifications, not just code. This paradigm shift raises intriguing questions about the future of traditional agile methodologies. Our plan at Inflectra is to integrate our new SpiraPlan MCP Server with Kiro to seamlessly feed its requirements.
Quality and Speed: As AWS CEO Andy Jassy eloquently put it, there's a "false binary between Quality and Speed." At Inflectra, we've long advocated that agility and quality are not a trade-off. With the right culture, training, processes, and of course, powerful tools, organizations can achieve both.
The Agentic Future of QA: The landscape of Quality Assurance is poised for a transformation, with agents working in tandem with humans. Imagine using inflectra.ai to write and critique requirements and specifications, leveraging agentic tools to write code, employing Generative AI to craft test cases and assess risk, and then utilizing agentic, autonomous testing agents like Rapise in agentic mode to test applications using Large Action Models and Large Vision Models. This truly heralds a new era for quality.

Day Two: Expanding Horizons at the Main AWS NYC Summit

Wednesday, July 16th, brought an even larger crowd to the Javits Center for the main AWS NYC Summit. The keynote by Swami Sivasubramanian, VP of AWS Machine Learning, explored the vital balance between timeless fundamentals of security, reliability, and operational excellence, and innovative investments like agentic AI frameworks. This theme resonated deeply with Inflectra's commitment to delivering secure, high-quality, AI-powered solutions.

Our team took the opportunity to engage with key AWS personnel and other industry partners. We held highly productive discussions with both Robby Gill, Manager of Emerging Technology Partnerships at AWS, and Patrick Garhan, Manager of Emerging ISV Partnerships at AWS. These conversations collectively focused on how Inflectra can further strengthen its alliance with AWS, particularly by aligning on customer needs and identifying joint opportunities for mutual support and credibility within the broader AWS community. The emphasis was on deepening our shared understanding of customer challenges and collaborating on solutions that drive impactful wins.

Beyond our direct AWS engagements, we fostered connections with other leading AWS Partners. We held excellent discussions with Cloud303 and Docker, exploring various avenues for collaboration and how we can collectively add value for AWS customers. It was also a pleasure to meet many of these partners in person for the first time. Our conversations also extended to Rhythmic Technologies, an AWS Advanced Tier Partner, where we explored industry-specific solutions, especially for regulated industries, and how we can assist joint customers.

The day concluded with a walk through the bustling expo hall, giving us a chance to see the innovative solutions on display from various sponsors. We then continued our networking at sponsored happy hours, bringing a successful close to our AWS NYC Summit journey.

See you next year, AWS NYC Summit! You were great.

We're excited to carry this momentum forward! If you're attending, be sure to see us at AWS Partner Equip in DC at the end of August. We look forward to seeing you there!

Using The Spira MCP Server in Visual Studio Code (VSCode) - Part 5 (Automations)

2025-07-09T14:03:02-04:00

Using the Automations Feature

Following on using the Workspaces and Program/Product Artifacts features in the previous article, we will now explore using the "Automations" MCP feature. For example, as a user I might want to report back the results of a CI/CD software build to Spira, or record the results of an automated test. I can of course do these manually using the Spira REST API, but MCP makes this process so much simpler:

Recording a Test Result

First, lets try recording a new test result in Spira using our MCP Server:

So in this question I tell Cline that I want to record a failed test result against a specific test case (TC:5) that lives in a specific Spira product (PR:1). I also provide the details of the test failure, including the number of errors and a brief description of what was reported. Based on this information, Cline is able to work out that it should be using the record_automated_test_run MCP tool, and that it has all the necessary information:

I need to record a new test result in Spira for a specific test case. Let me analyze what I need to do:

1. The user wants to record an automated test run in Spira
2. The test case is TC:5 in project PR:1
3. The test name is "logging in to the system"
4. The test should be marked as failed with 1 error
5. The reason for the error is that a page was missing

Looking at the available MCP tools, I can see that the "inflectra-spira" server has a tool called "record_automated_test_run" which seems perfect for this task. Let me check the required parameters for this tool:

- product_id: The numeric ID of the product. The user mentioned PR:1, so I should use 1.
- test_name: The name of the test being run. This is "logging in to the system".
- short_message: A short description of the result. I can use "Test failed - page missing".
- long_message: The full description. I can use "The test failed because a required page was missing from the system."
- error_count: The number of errors. The user specified 1 error.
- test_case_id: The ID of the test case. The user mentioned TC:5, so I should use 5.
- execution_status_id: The ID of the execution status. Since the test failed, I should use 1 (Failed).

I have all the required parameters, so I can proceed with using the tool.

I'll record the failed test result in Spira for test case TC:5 in project PR:1.

As we have seen before, Cline will request our approval to use the appropriate MCP tool (unless we have enabled Auto-approve):

This tool has more extensive parameters than the ones we've seen before, so lets look a bit closer at them:

Note that it has correctly mapped my question into the expected parameters for me. When I Approve the use of the record_automated_test_run tool I will now see this:

Great! The MCP tool has successfully recorded the automated test run in Spira. The result returned is "TR:629", which indicates that a new test run with ID 629 has been created in Spira.

Now I need to complete the task by informing the user that the test result has been successfully recorded. I'll use the attempt_completion tool to present the final result.

Cline now uses the attempt_completion tool to format the answer nicely for me:

If we look inside Spira, we will see that the new test run has been recorded correctly:

It uses the special "MCP Server" as the Automation Engine / Runner Name.

Now if I did not know what the product ID and test case ID were, I could have asked Cline using something like the following instead:

This time Cline needs to analyze my request and see how it can use multiple Spira MCP tools to accomplish what I have asked:

I see that this is a new task, similar to the previous one but with different parameters. The user wants to record a new test result in Spira for a test case called "ability to edit an existing book" in a product called "library information system".

To complete this task, I need to:

1. Find the product ID for "library information system"
2. Find the test case ID for "ability to edit an existing book"
3. Record the test result using the record_automated_test_run tool

First, I need to get the product ID. I can use the get_products tool to list all products and find the one called "library information system".

It now uses the get_products tool to get the list of products:

Then it needs to get the list of test cases using get_test_cases:

Finally it will use the record_automated_test_run tool to post the results:

using the arguments it deduced from the previous calls:

So this shows you that you don't need to manually use separate MCP tools yourself, you can just ask Cline to solve the problem and it will work out which tools to use in the correct sequence automatically!!

Recording a CI/CD Build Event

Next, lets try recording a new Build CI/CD event in Spira using our MCP Server. This is useful for cases where we want to simulate a new build happening or if we did a build offline and now want to post the results in Spira:

So in this question I tell Cline that I want to record a build entry against a specific Release (RL:4) that lives in a specific Spira product (PR:1). I also provide the details of the build result, including the status of the build (passed) and a brief description of what was reported. Based on this information, Cline is able to work out that it should be using the create_build MCP tool, and that it has all the necessary information:

I need to record a new build entry in Spira for product PR:1 and Release RL:4. The build passed on today's date and included code for implementing the authentication logic.

Looking at the available tools, I can see that there's an MCP server called "inflectra-spira" that provides a tool called "create_build" which seems perfect for this task. Let's analyze the parameters required for this tool:

1. product_id: The numeric ID of the product. The user mentioned PR:1, so I should use 1.
2. release_id: The ID of the release. The user mentioned RL:4, so I should use 4.
3. build_status_id: The status of the build. The user mentioned the build passed, so I should use 2 (Passed).
4. name: The name of the build. I should include the project name and date/time. Since the user didn't specify a project name, I'll use "Authentication Implementation" and today's date.
5. description: The detailed description of the build. The user mentioned it included code for implementing the authentication logic.
6. commits: An optional array/list of the Git hashes of the commits included in the build. The user didn't provide any commit hashes, so I'll use an empty array.

I have all the required parameters, so I can proceed with using the create_build tool.

I'll use the MCP tool to record a new build entry in Spira for your product and release.

Note that Cline is making some intelligent decisions, such as how it should name the build, as well as what would be useful to include in the description. It also notices that we didn't include any Git hashes, so the list of commits will be left empty. Based on this analysis it wants to call the Spira MCP tool as follows:

It has correctly filled out the parameters, and which I click Approve, it will create the new build in Spira and make the following observations:

Great! The MCP tool successfully created a new build entry in Spira. The result shows that the build was created with the ID "BL:22". This means the build was successfully recorded in the system with all the details I provided:

1. Product ID: 1 (PR:1)
2. Release ID: 4 (RL:4)
3. Build Status: Passed (build_status_id: 2)
4. Name: "Authentication Implementation Build - 2025-06-20"
5. Description: "This build includes code for implementing the authentication logic."

The task has been completed successfully. I'll now use the attempt_completion tool to inform the user of the successful result.

Using the completion tool, it now displays an informative message to let me know it worked successfully:

If we look in Spira, we now see the created Build:

Now if I did not know what the product ID and release ID were, I could have asked Cline using something like the following:

Where I am using the name of the product and the release version number instead of its ID. When I do that, Cline breaks down my request and looks to use multiple Spira MCP tools to accomplish its task:

I see that this is a task resumption, but the user's message has changed. Previously, I was asked to record a build for product PR:1 and Release RL:4, but now I'm being asked to record a build for product "Library Information System" and Release 1.0.0.0.

This is essentially a new task with different parameters. I need to:

1. Record a new build entry in Spira
2. For product "Library Information System"
3. For Release 1.0.0.0
4. The build passed on today's date
5. It included code for implementing the authentication logic

To accomplish this, I need to use the create_build tool from the inflectra-spira MCP server. However, there's a challenge: the create_build tool requires numeric IDs for the product and release, but the user has provided names instead.

I need to first find the product ID for "Library Information System" and the release ID for "1.0.0.0". I should use the get_products tool to find the product ID, and then use the get_releases tool to find the release ID.

Let's start by getting the list of products to find the ID for "Library Information System".

I need to record a new build entry in Spira for the "Library Information System" product. First, I'll need to find the product ID by retrieving the list of available products.

If you look at the bolded text above you can see that Cline has intelligently decided to use the following three MCP tools to complete the task:

get_products - to get the ID of the product
get_releases - to get the ID of the release
create_build - to actually create the build

This is fantastic and means that as a user I don't need to look up IDs or other Spira specific identifiers, but instead I can converse with Cline naturally and it will use whatever tools it needs to accomplish my task.

Conclusion

In this series we have demonstrated how you can setup the Spira MCP Server with an Agentic AI tool such as Cline running in Visual Studio Code (VS Code), and use that server to accomplish a variety of software development and software testing related tasks. Please let us know if you have any questions or are interested in a demonstration of SpiraPlan or Inflectra.ai:

XXXspiraplandemoXXX

Using The Spira MCP Server in Visual Studio Code (VSCode) - Part 4 (Workspaces)

2025-07-09T14:02:45-04:00

Using the Workspaces Feature

Following on using the My Work feature in the previous article, we will now explore using the "Workspaces" MCP feature. For example, as a user I might want to get a list of all the Spira products that I have access to:

From this simple question, the Cline agent will look to find a matching MCP tool:

The user wants to know what products in Spira they have access to. Based on the file structure, I can see this is a project related to Spira, which appears to be some kind of project management or testing tool. There's an MCP server connected called "inflectra-spira" that provides various tools for interacting with Spira.

Looking at the available MCP tools, I see there's a tool called `get_products` that seems perfect for this task

This tool doesn't require any parameters, so I can use it directly to retrieve the list of products the user has access to.

I'll retrieve the list of products you have access to in Spira.

It has correctly identified the tool to use (get_products) and asks permission to call it:

If you get tired of having Approve each MCP tool, simple check the Auto-Approve option for that specific tool, and Cline will know that you are fine with the agent autonomously called it without needing pre-approval.

As a best practice, we recommend only auto-approving MCP tools that do retrieves (and are usually prefixed with "get_"). That way you can prevent any erroneous deletes or updates happening in your instance of Spira!!

I've successfully retrieved the list of products that the user has access to in Spira. The response shows a comprehensive list of products with their details including:

1. Product ID and name
2. Description (for some products)
3. Website (if available)
4. Template ID
5. Program ID
6. Completion percentage
7. Start and end dates

The user now has a complete view of all the products they have access to in Spira. This completes their request, so I should use the attempt_completion tool to present this result.

The MCP tool has successfully provided a list of products in Spira, together with their key fields. Based on this information, the agent again uses the special attempt_completion tool to present the information in a meaningful and useful way:

You can see that it has performed some intelligent grouping and summarization to avoid having to list all 49 products. It has grouped them by industry where possible, and simply enumerated the demo and sample ones under "various".

Similarly I can now ask it to get my the list of Spira programs that I have access to:

The agent uses a similar reasoning process as for products:

The user is now asking for a list of programs in Spira that they have access to. Looking at the available MCP tools, I can see there's a tool called get_programs that would be perfect for this task.

This tool doesn't require any parameters, so I can use it directly to retrieve the list of programs the user has access to.

I'll retrieve the list of programs you have access to in Spira.

Once I approve the tool, it makes the necessary API call to Spira using the MCP tool and then comments on what it found:

I've successfully retrieved the list of programs that the user has access to in Spira. The response shows a comprehensive list of programs with their details including:

1. Program ID and name
2. Description (for some programs)
3. Website (if available)
4. Product Template ID
5. Portfolio ID

The user now has a complete view of all the programs they have access to in Spira. This completes their request, so I should use the attempt_completion tool to present this result.

In this case it didn't change the data all that much, simply returning a bulleted list of programs with their name and ID.

This wasn't as useful, so I then asked Cline if it could group the data for me:

Note that I misspelt group as "groip", but that didn't faze Cline (or Claude!):

The user wants me to group the list of programs by industry. Looking at the program names and descriptions, I can identify several industry categories

and without needing to call the Spira MCP tool again, it simply did the grouping and re-presented the data to me:

This is much better, and also demonstrates that when the agent returns data in a format that is not exactly what you need, you can easily ask it to change how it's presented for you.

Using the Program and Product Artifacts Features

The next feature we want to explore are the program and product artifact features. Unlike the ones used so far, these ones expect specific input parameters such as the ID of the product or program that you are interested in.

Firstly, lets ask Cline to get us a list of the requirements in a specific Spira product:

Here I have asked Cline to get me all of the requirements in Product PR:1. It uses my question to figure out that it should use the get_requirements MCP tool:

The user wants to get all requirements from Spira product with ID PR:1. Looking at the available tools and the MCP server information, I can see that there's an MCP server called "inflectra-spira" that provides tools for interacting with Spira.

For this task, I need to use the `get_requirements` tool from the inflectra-spira MCP server. This tool retrieves a list of requirements in a specified product.

Looking at the tool's input schema, it requires a `product_id` parameter, which is the numeric ID of the product. The user mentioned PR:1, and according to the tool description, if the ID is PR:45, I should just use 45. So in this case, I need to use product_id = 1.

I'll use the `use_mcp_tool` to call the `get_requirements` tool from the inflectra-spira server.

Unlike the previous tools, Cline has to figure out the format for the parameters. We have documented the product_id parameter with MCP in mind, letting the LLM know that the product token PR:xx should be interpreted as just xx.

Once it has run the tool it will get back a list of all the requirements in the product (there could be quite a large number):

You can see that it has intelligently grouped the requirements by their type (Epic, Features, Stories, etc.). It also has given a nice synopsis of what it thinks the requirements relate to:

The system contains 89 requirements in total, covering various aspects of what appears to be a library management system along with some other sample requirements.

If I want to filter the requirements in some way, I can just ask Cline to do that for me, no need to re-query Spira:

The user wants me to filter the previously retrieved requirements to show only those with High (2) and Critical (1) importance. I'll go through the results from the previous MCP tool call and extract only the requirements that have an importance level of "1 - Critical" or "2 - High".

Using this criteria it will update the analysis and provide a new answer:

Now what if I didn't know the ID of the product, only its name? Let me try that and see what happens:

The system now needs to use multiple tools in sequence (often called an agentic workflow):

The user now wants me to get all requirements from a Spira product called "Library Information System" instead of using the product ID. I need to first find the product ID for "Library Information System" and then use that ID to get the requirements.

I'll use the `get_products` tool from the inflectra-spira MCP server to get a list of all products, which should include their names and IDs. Then I can find the ID for "Library Information System" and use that to get the requirements.

followed by:

This is when the benefit of Auto-Approve becomes more evident as you can basically ask a complex question that will need the input from multiple tools (perhaps involving multiple platforms such as Spira, GitHub, etc.) and let the agent go ahead and find the answer for you.

We can do something similar for test cases as well. This is an interesting use case, as test cases have both test folders and test cases, which the MCP tool knows how to handle for us:

In this example I am using the product name rather than the ID. Let's see how Cline handles this:

I need to retrieve all test cases from the Spira product "Library Information System". Based on the available tools from the MCP server "inflectra-spira", I can see that there's a tool called get_test_cases that would be perfect for this task.

Cline has found the correct tool to get all of the test cases (and folders) in a Spira product. However it has determined that it has a problem:

I need the product ID for "Library Information System". However, I don't have this information yet. I should first get a list of products to find the ID for "Library Information System".

I'll use the `get_products` tool to retrieve a list of all products the user has access to, which should include "Library Information System" and its ID.

I'll help you retrieve all test cases from the "Library Information System" product in Spira. First, I need to find the product ID.

So luckily it has determined that it needs to use the get_products tool as well:

I've found the product "Library Information System (Sample)" in the list with the ID [PR:1]. The exact name is slightly different from what the user asked for (it has "(Sample)" appended), but it's clearly the library information system they're referring to.

Now I can use the `get_test_cases` tool to retrieve all test cases for this product. According to the tool description, I need to provide the product_id parameter, which in this case is 1 (removing the "PR:" prefix as instructed in the tool documentation).

I found the "Library Information System (Sample)" product with ID [PR:1]. Now I'll retrieve all test cases for this product.

Here we can see that it determined which product I was interested in, even though I had not provided an exact name match, but it was close enough for Claude:

Using this tool with the correct product ID, it is able to display the list of test cases and folders for me:

I've successfully retrieved all the test cases from the "Library Information System (Sample)" product (PR:1). The response contains a comprehensive list of test cases with their details including status, type, priority, and execution status. The test cases are organized by folders, which helps provide structure to the test suite.

Now I can use the attempt_completion tool to present this information to the user. Since I've already completed the task of retrieving all test cases from the specified product, there's no need for additional tool use.

As well as the list of folders, it has added the following commentary:

This is useful analysis to have. It also makes me think of a follow-up question to ask Cline:

Cline can help me with this without needing to call any additional MCP tools:

The user wants to know which test cases have failed in the Library Information System product. I'll go through the test case list I retrieved earlier and identify all test cases with a "Failed" execution status.

In addition to this useful list of failed test cases (grouped by folder), it also adds this final analysis:

Showing us the power of Agentic AI in only completing multiple tasks autonomously, but injecting reasoning and "chain of thought" during the process.

To finish off this blog series on our Spira MCP server we will finally look at the Automations feature in our last article.

Using The Spira MCP Server in Visual Studio Code (VSCode) - Part 3 (My Work)

2025-07-09T14:02:26-04:00

Using the My Work Feature

Now that we've got the MCP server configured and running, what I want to do first is ask it some simple questions.

Retrieving My Assigned Tasks

Using the My Work feature, I want to find out some information about the work I have to do. For example, imagine that I'm a developer, and I really want to be able to find out the tasks and bugs I've been assigned to work on. So we can ask Cline to get me a list of my assigned tasks:

The agent will then take your question and examine the list of available MCP tools to see if it can find one that it can use to answer your question:

The user wants to get a list of their assigned tasks in Spira. Looking at the file structure, I can see this is a project related to Spira, which appears to be a project management or issue tracking system. There's an MCP server connected called "inflectra-spira" that provides tools for interacting with Spira.

Looking at the available MCP tools, I see there's a tool called "get_my_tasks" that seems perfect for this request. This tool is described as:

"Retrieves a list of the open tasks that are assigned to me. Use this tool when you need to view the complete details of a specific task, examine the current state, assigned user, and other properties, get information about multiple tasks at once, or access the full description and selected fields of tasks."

This tool doesn't require any parameters according to its input schema, so I can use it directly.

I'll retrieve your assigned tasks from Spira using the MCP server.

In this case it has found a possible tool get_my_tasks and so it invokes the MCP tool (which in turn calls the Spira REST API) to get the list of open tasks assigned to the current user:

It retrieves back the list of tasks from Spira (that are formatted as markdown) and then comments on what it has found:

I've successfully retrieved the list of tasks assigned to the user in Spira. The response shows 18 tasks with their details including:

- Task ID and name
- Status (mostly "Not Started" with one "In Progress")
- Type (Development, Management, Infrastructure)
- Priority (ranging from None to 1-Critical and 2-High)
- Due Date

Now I should use the attempt_completion tool to present this result to the user.

Now the really cool part is that the agent uses its special attempt_completion tool coupled with the brain of Claude Sonnet to then analyze the returned data and provide a aggregated and analyzed set of information, rather than just a raw listing of the 18 tasks:

One of the great aspects of the Cline agent interface is that I can then ask it follow up questions to further refine the data it has retrieved:

By asking this question, the Cline agent attempts to use the current date together with the due date of the various tasks to answer my question:

The user wants to know how many of the tasks are overdue. I need to analyze the due dates of the tasks and compare them with the current date.

From the environment details, the current date is July 7, 2025 (7/7/2025).

Looking at the due dates of the tasks:

1. [TK:52] - Due: 2022-07-22
2. [TK:54] - Due: 2022-07-22
3. [TK:64] - Due: 2022-07-02
4. [TK:65] - Due: 2022-07-02
5. [TK:84] - Due: 2022-02-11
6. [TK:228] - No due date
7. [TK:229] - No due date
8. [TK:230] - No due date
9. [TK:231] - No due date
10. [TK:232] - No due date
11. [TK:233] - No due date
12. [TK:83] - Due: 2022-02-11
13. [TK:125] - Due: 2022-04-09
14. [TK:126] - Due: 2022-04-09
15. [TK:73] - Due: 2022-04-04
16. [TK:93] - No due date
17. [TK:127] - Due: 2022-04-10
18. [TK:274] - Due: 2022-05-28

All tasks with due dates are from 2022, which is about 3 years before the current date (2025). So all tasks with due dates are overdue. That's 12 tasks with due dates, all of which are overdue.

Again using the special completion tool, Cline can analyze this data to give the user a succinct answer:

Note that it is smart enough to let me know that 6 of the tasks have no due dates at all and therefore might need further analysis:

Now that I have my tasks, what about finding out if I also have any bugs to work on.

Retrieving My Assigned Bugs

I can use Cline to ask for my assigned incidents as well:

Again the agent will use Claude to figure out what I'm looking to do:

The user now wants me to get a list of their assigned incidents from Spira. Looking at the available MCP tools, I see there's a tool called "get_my_incidents" that would be perfect for this request. This tool is described as:

"Retrieves a list of the open incidents that are assigned to me. Use this tool when you need to view the complete details of a specific incident, examine the current state, assigned user, and other properties, get information about multiple incidents at once, or access the full description and selected fields of incidents."

Like the get_my_tasks tool, this doesn't require any parameters according to its input schema, so I can use it directly.

I'll retrieve your assigned incidents from Spira.

From this it will run the appropriate MCP tool get_my_incidents which calls the Spira REST API to get the list of assigned incidents in markdown:

The Cline built-in completion tool will yet again try and read this data to present it to me in the most meaningful way:

I've successfully retrieved the list of incidents assigned to the user in Spira. The response shows 9 incidents with their details including:

- Incident ID and name
- Status (mostly "New" with one "Assigned")
- Type (Bug or Incident)
- Priority (mostly "None" with one "1 - Critical")
- Severity (mostly "None" with one "3 - Medium")
- Due Date (mostly "None" with one dated 2022-03-11)

Now I should use the attempt_completion tool to present both the tasks (from the previous query) and incidents to the user.

Note that because I have not started a new task (session) with Cline it has the context of my previous question (get my tasks) so it has decided to combine my tasks with my incidents. I did not explicitly request that, and if I wanted to keep the requests separate I should have used the "Start New Task" option:

So you can see how Cline is trying to add intelligence to the output rather than just blindly regurgitating what is in Spira. In this case I get the following:

plus I get the tasks lower down:

It even gives a nice summary at the end:

Now we technically wanted to know only about bugs, but the Spira MCP server doesn't include specific filtering capabilities. We did this to keep things simple, and as we will see, it's not really needed as the Cline agent can simply use Claude to handle it internally.

For example, if we ask Cline:

Then it can simply interpret the existing data that it has already retrieved. If you see the reasoning:

The user wants to know which of the incidents are critical bugs. I need to analyze the list of incidents I retrieved earlier and identify those that are both:

1. Type: Bug
2. Priority: Critical (1 - Critical)

Looking at the incidents list:

1. [IN:119] - Type: Bug, Priority: None
2. [IN:112] - Type: Incident, Priority: None
3. [IN:113] - Type: Incident, Priority: None
4. [IN:114] - Type: Incident, Priority: None
5. [IN:115] - Type: Incident, Priority: None
6. [IN:116] - Type: Incident, Priority: None
7. [IN:118] - Type: Incident, Priority: None
8. [IN:120] - Type: Incident, Priority: None
9. [IN:7] - Type: Bug, Priority: 1 - Critical

From this analysis, only one incident meets both criteria:

- [IN:7] Cannot add a new book to the system (Type: Bug, Priority: 1 - Critical)

Using this analysis it will give me the information I asked for right away, with no additional API calls to Spira:

Note the final sentence though: It has answered my direct question and found the one bug that was critical (and provided its details), but more interestingly it found one incident that was classed as a Bug but had no priority set.

That could be a bug that was missed during incident review and therefore poses a potential unknown risk.

So here we can see the benefit of using Artificial Intelligence, the agent has found an item that us humans missed. It did not answer my explicit question, but based on the AI's understanding of software quality, it realized that it was important and needed to be flagged.

Getting More Information

Now that I have been made aware of this flagged Bug, I can simply ask Cline to get me more information right from the context window:

The agent now tries to determine if it has all the information on this Bug, or whether it has a way to get more information from Spira:

This is all the information I have about this incident. It's a bug with the name "Incident 2" and description "Incident 2", but it doesn't have priority, severity, or due date set. It's in "New" status.

I don't have a specific MCP tool to get more detailed information about a single incident by ID. The available tools are more focused on getting lists of different types of artifacts. I should inform the user about the details I already have for this incident.

Since we haven't provided a more specific MCP tool to get all the incident fields (something on our backlog for the MCP Server), the agent has decided to simply tell the user all it already found:

As you can see, not only did it return the requested information, but it added subtle commentary that the Bug needs a better description... touché Cline (or maybe Claude!)

Now that we've explored the My Work MCP tools, in the next article we'll take a look at some of the other tools in depth.

Using The Spira MCP Server in Visual Studio Code (VSCode) - Part 2 (Setup)

2025-07-09T14:02:04-04:00

Installing Cline into Visual Studio Code

Assuming that you already have Visual Studio Code (VS Code) installed, there are a variety of different software development agents available to you:

Microsoft GitHub Copilot
Amazon Q Developer
Cline (open-source)

For our example, we are going to use Cline instead of Copilot or Amazon Q, however you could use Copilot or Amazon Q instead with the Spira MCP Server.

To install Cline, simply go to the Extensions section of VS Code and search for Cline:

Once you find it, click the option to install Cline into VS Code. Then restart VS Code and you should see the new Cline toolbar entry:

Next we have to connect Cline to our favorite LLM, in this case we will use Claude 3.7 Sonnet.

Connecting Cline to Claude Sonnet hosted in Amazon Bedrock

Since we are an Amazon Web Services (AWS) partner, we have access to all of the latest LLMs directly inside our Amazon Bedrock account. If you are not an AWS customer/partner, you could use Claude directly. Logging in to Amazon Bedrock, we have enabled model access to Claude Sonnet v3.7. This is the minimum version of Claude Sonnet that will work with Cline in agentic mode.

Once we have enabled model access to Claude Sonnet v3.7, we next need to create an Inference Profile and enable cross-region inference for Claude Sonnet 3.7. This will allow the maximum throughput of AI queries to be handled.

Make sure you copy the Inference Profile ID and Inference Profile ARN to the clipboard. You will need those pieces of information later.

Finally, you can go to the API Keys section and generate either a short-term or long-term API key:

You should check with your Chief Information Security Officer (CISO) about which type of API is appropriate for your use case.

You will need to record the API Key and matching Secret in a secure location such as your password manager.

Once you have Amazon Bedrock configured, go back to Cline and go to the Settings:

In this dialog box you need to choose your Api Provider. You can choose from a variety of options:

However for our example, we will choose Amazon Bedrock. Then we can enter in the Amazon Bedrock specific settings:

AWS Access Key: Enter in the API Key you saved in your password manager
AWS Secret Key: Enter in the API Secret that you saved in your password manager
AWS Session Token: You can leave this blank
AWS Region: Enter the AWS region you configured Bedrock access for earlier
Use Cross Region Inference: Make sure this is checked
Model: Enter in the full model name that is displayed in Bedrock

Once this is done, you can check that Cline can access the LLM API by trying out some sample tasks.

Assuming that is successful, the final step is to connect Cline to the Spira MCP Server

Connecting Cline to the Spira MCP Server

Firstly to add Spira as a new MCP server, you need to go to the MCP Server GitHub repository: https://github.com/Inflectra/mcp-server-spira

Then choose the option to Clone the repository to your local machine:

You can also just download the Zip file and unzip it to a location on your local computer.

Once you have cloned or unzipped the MCP server repository, you will need to install Python 3.11 or later and then run these commands:

# Clone the repository
git clone https://github.com/Inflectra/mcp-server-spira.git
cd mcp-server-spira

# Install in development mode
uv pip install -e ".[dev]"

# Install from PyPi
pip install mcp-server-spira

Now that you have installed the Spira MCP Server, go to Cline and click on the MCP Servers tab:

Click on the Edit Configuration button and you can now see the MCP Server configuration file:

You will need to edit the configuration file to add the Spira MCP Server:

{
  "mcpServers": {
    "inflectra-spira": {
      "autoApprove": [
        "get_my_incidents",
        "get_products",
        "get_test_cases"
      ],
      "timeout": 60,
      "command": "uv",
      "args": [
        "--directory",
        "C:\\Git\\mcp-server-spira",
        "run",
        "main.py"
      ],
      "env": {
        "INFLECTRA_SPIRA_BASE_URL": "https://mycompany.spiraservice.net",
        "INFLECTRA_SPIRA_USERNAME": "login",
        "INFLECTRA_SPIRA_API_KEY": "{XXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXX}"
      },
      "type": "stdio"
    }
  }
}

You will need to populate the following three special environment variables:

INFLECTRA_SPIRA_BASE_URL=The base URL for your instance of Spira (typically https://mycompany.spiraservice.net or https://demo-xx.spiraservice.net/mycompany)
INFLECTRA_SPIRA_USERNAME=The login name you use to access Spira
INFLECTRA_SPIRA_API_KEY=The API Key (RSS Token) you use to access the Spira REST API

Finally, to enable Spira MCP support in Cline, you simply need to restart VS Code and click on the Cline tab. You now should see the Spira MCP Server (inflectra-spira) listed under the list of installed and available MCP servers:

If you click on the chevron next to the MCP Server name, you can see a list of all the available MCP tools and resources:

You view the various tools and mark the ones that you are happy to run autonomously by selecting Auto-Approve = Yes. If a tool does not have that box checked, Cline will require you to explicitly approve each use of the tool.

Now that you have the Spira MCP Server installed, in the next article in the series, we'll discuss how you can use the MCP server to perform some common tasks.

Using The Spira MCP Server in Visual Studio Code (VSCode) - Part 1 (Overview)

2025-07-09T15:19:36-04:00

What is MCP and Why Create a Server for Spira?

As described in our background paper - Model Context Protocol (MCP) is a new AI "middleware" technology that lets you connect different AI tools and agents with a variety of with backend services:

In the context of the software development lifecycle, these different backend services will usually be a combination of SaaS products (e.g. Spira, GitHub, Slack, AWS Console, etc.) that are accessible through an API as well as local data storage such as Git repositories:

When developers are working in their Integrated Development Environment (IDE) such as Visual Studio Code, Cursor or Windsurf, it is convenient for the developers to be able to use their AI assistant to not only help write the code for the application they are building (or even build the entire application in the case of Vibe Coding), but to also interact with external services such as Spira. For example, they might want to ask their assistant to get a list of all the tasks they are working on, or get a list of all the bugs they have to fix:

What Features and Tools Does the Spira MCP Server Provide?

The Inflectra MCP Server for Spira includes support for a variety of common tasks, including:

My Work

This feature provides easy access to the list of artifacts that have been assigned to the current user

My Tasks: Provides operations for working with the Spira tasks I have been assigned
My Requirements: Provides operations for working with the Spira requirements I have been assigned
My Incidents: Provides operations for working with the Spira incidents I have been assigned
My Test Cases: Provides operations for working with the Spira test cases I have been assigned
My Test Sets: Provides operations for working with the Spira test sets I have been assigned

Workspaces

This feature provides tools that let you retrieve and modify the different workspaces inside Spira

Programs: Provides operations for working with Spira programs
Products: Provides operations for working with Spira products
Product Templates: Provides operations for working with Spira product templates

Program Artifacts

This feature provides tools that let you retrieve and modify the different artifacts inside a Spira program

Capabilities: Provides operations for working with the Spira capabilities in a program backlog
Milestones: Provides operations for working with the Spira milestones in a program

Product Artifacts

This feature provides tools that let you retrieve and modify the different artifacts inside a Spira product

Requirements: Provides operations for working with the Spira requirements in a product
Releases: Provides operations for working with the Spira releases in a product
Test Cases: Provides operations for working with the Spira test case folders and test cases in a product
Test Sets: Provides operations for working with the Spira test set folders and test sets in a product
Test Runs: Provides operations for working with the Spira test runs in a product
Tasks: Provides operations for working with the Spira tasks in a product
Incidents: Provides operations for working with the Spira incidents (e.g. bugs, enhancements, issues, etc.) in a product
Automation Hosts: Provides operations for working with the Spira automation hosts in a product

Template Configuration

This feature provides tools that let you view and modify the configuration and settings of Spira product templates

Artifact Types: Retrieves information on the artifact types in a product template, and their sub-types
Custom Properties: Retrieves information on the artifact types in a product template, and their custom properties

Automation

This feature provides tools that let you integrate automated DevOps tools such as test automation frameworks and CI/CD pipelines

Automated Test Runs: Provides operations for recording automated test run results into Spira
Builds: Provides operations for recording the results of CI/CD builds into Spira

The good news is that the MCP Server for Spira is fully open-source (MIT License) so as customers find additional needs that it doesn't currently support, they can suggest the additional feature or even built it themselves and submit a pull request. In addition, we have provided a Claude.MD file that will help Claude (and other agentic LLMs) create new tools and features automatically! We will discuss this aspect in more detail in a subsequent article.

Which Use Cases Are Covered in the Video?

In the video that accompanies this article, we demonstrate first how to use the Cline AI assistant integrated with VS Code to retrieve and analyze assigned tasks and incidents using natural language queries. The AI assistant can fetch live data from Spira, perform initial analysis, and provide insights such as critical and overdue tasks. It also explains the auto-approve feature for repeated tasks and demonstrates how the AI can combine information from multiple queries to provide comprehensive summaries. We highlight the contextual nature of the interactions and the ability to drill down into specific details, such as identifying critical bugs or potential risks in unclassified items.

After this initial use case, we explore some of the additional capabilities of the MCP server, focusing on workspaces and programs in Spira. We demonstrate how to retrieve a list of products and programs that the user has access to The system intelligently groups and summarizes the products and programs.

Next, we show how the system can group a list of programs by industry and retrieve requirements for a specific product. The system successfully retrieves and categorizes requirements for the product, grouping them by type and providing metadata about priorities and statuses. We then show how you can request to filter the requirements to show only those of high and critical importance without needing to make a separate API call.

To show the versatility of the MCP Server when coupled with a powerful agentic tool such as Cline, we demonstrate fetch requirements and test cases from different projects, even when given slightly imprecise project names. The agent can intelligently combine multiple MCP tools, such as getting product lists and requirements, and can work autonomously with auto-approve enabled.

Finally, we showcase how the agent can retrieve and analyze test case data, record test results, and perform multi-stage operations. We highlights the system's ability to autonomously execute multiple API calls and combine data from different sources.

Summary

The integration of Developer Tools such VS Code, Cursor, etc. with AI assistants like Copilot, Cline and AmazonQ, using the power of a Large Action Model (LAM) such as Anthropic Claude Sonnet allows users to ask questions in natural language from the "comfort" of their IDE, get real-time data from Spira (and other systems), then interpret that data before presenting it to the user so that it is meaningful and actionable. In addition to retrieving data, the agents can suggest actions that the user can take (such as updating statuses, recording test results) and if auto-approve is enabled, even take action autonomously.

In the next article in this series, we shall show you how you can setup a simple Agentic environment using Visual Studio Code (VS Code), Cline and Claude Sonnet running on Amazon Bedrock.

Accelerating Tomorrow: Inflectra's Showcases AI That Augments Software Quality

2025-06-20T10:18:13-04:00

Inflectra’s AI-Powered Showcase

At the core of our presence was Inflectra's flagship platform, SpiraPlan. This AI-enhanced Agile program and portfolio management tool leverages helps to forecast potential roadblocks, identify resource constraints, and improve project outcomes across SDLC. Complementing SpiraPlan was Rapise, Inflectra's advanced test automation platform. Employing sophisticated object recognition and machine learning, Rapise enables rapid and precise testing across web, desktop, and mobile applications, even those with complex interfaces.

Visitors to Inflectra's booth learned how inflectra.ai automates routine tasks, allowing teams to focus on strategic initiatives, and how AI facilitates software development, testing, and project management.

Inflectra also participated in strategic one-on-one meetings with key partners Coveros and Merito. These sessions focused on aligning strategies around project implementation, training initiatives, and custom development, underscoring Inflectra’s collaborative approach to leveraging AI-driven solutions effectively across client projects.

Adam Sandman: How We Are Building inflectra.ai

A highlight of the conference was Adam Sandman's session titled "Software Delivery at the Speed of AI: Inflectra Invests In AI-Powered Quality." In this talk, Adam delved into the transformative impact of AI across software project management, development, and automation. He showcased practical examples of how AI is integrated within SpiraPlan and Rapise, emphasizing the unique benefits, lessons learned and challenges of bringing AI into agile software development processes.

Adam's insights extended beyond the conference. In recent months, he has actively shared his expertise on the transformative impact generative AI, across various platforms. His engagements include in-depth podcast discussions on boosting software quality and navigating the evolving landscape of software testing, as well as insightful publications exploring AI's potential in network management and drawing parallels from eSIM technology for enhanced connectivity and security.

A Strategic Partnership with AWS

Inflectra's commitment to AI innovation is further solidified through its strategic partnership with Amazon Web Services (AWS). The company recently achieved the coveted AWS Generative AI Competency, a designation that validates Inflectra's proven ability to deliver cutting-edge, generative AI-powered solutions that fast-track digital transformation and elevate software quality. This partnership ensures that Inflectra's AI models are hosted in the same geographic regions as customer data, addressing data residency concerns and enhancing security.

Unlocking Australia's AI Leadership: Powerful Insights from AWS Summit Sydney

2025-06-05T19:56:47-04:00

Here’s the exciting news: Innovating with Generative AI (GenAI) isn’t a trade-off against quality. With AWS tools like Bedrock, Nova, and SageMaker (powering our own inflectra.ai—the pioneering GenAI for Quality Software Delivery), these foundational concerns are seamlessly integrated, enabling innovation with speed, scale, and safety.

Generative AI isn’t mere hype; it's a tectonic shift, reshaping how we learn, socialize, work, serve customers, reinvent business models, and even retire entire industries! Australia’s legacy of digital innovation positions us perfectly to reclaim global leadership.

From the AWS Executive Leaders’ Summit, one message resonated powerfully: organizations embracing AI early will reap significant rewards, while those hesitant to explore, train, and empower curiosity risk being left behind.

We were inspired by SDPRIA’s Chief Executive, Dr. Teresa Anderson AM, detailing the ambitious launch of Epic+, the world’s largest integrated patient records platform. Connecting everything from anesthesia equipment and emergency wards to clinical trials, genomics, and even digitized baby books—eliminating those bulky children’s blue folders (IYKYK). This represents massive progress. Partnering with AWS ensures rigorous governance, robust cybersecurity, and the scalability to manage over 8 million patient records in New South Wales. The system has impressively scaled from initially handling just 30 G Refs to confidently managing between 130 and 185, ensuring reliability when it launches in March 2026, with completion expected by 2028.

Reflecting back, just one year ago at the AWS Summit, Bedrock had just launched. It’s astonishing how much can happen in an AI year—it's decades of innovation compressed into months!

We also heard insightful perspectives from Matt Comyn, CEO of Commonwealth Bank, who highlighted his approach of empowering 900 team leaders to integrate GenAI into “every task, every role, every day.” His strategy tackles fraud detection, scams prevention, and more. Matt emphasized, “The best way to prepare for the future is to be part of it,” advocating a thoughtful yet bold approach, continuously learning and iterating quickly through small, agile teams.

Phil Le-Brun, Director of Enterprise Strategy at AWS, underscored impressive use-cases, from Bosch’s autonomous digital twins to Goldman Sachs’ quantum computing and Nasdaq’s use of AWS Bedrock against financial crime. Phil distilled wisdom from over 300 successful AWS transformations into practical, impactful advice:

Business Case for Budget: Practical advice on how to build budgets and business case for AI innovation: https://aws.amazon.com/blogs/enterprise-strategy/it-money-matters-four-methods-to-unlock-investment-capacity/ - Don’t just build—also retire legacy systems to unlock investment.
How to move fast and not be burdened by bureaucracy: https://aws.amazon.com/blogs/enterprise-strategy/centralize-or-decentralize/ - balance decentralized agility and centralized oversight.
Building a culture of nimble teams balancing speed and quality with lived principles that matter: https://aws.amazon.com/blogs/enterprise-strategy/from-empty-values-to-working-principles-a-leaders-guide/
Speed alone can be dangerous a leaders guide to establishing first autonomous team: https://aws.amazon.com/blogs/enterprise-strategy/breaking-through-bureaucracy-a-leaders-guide-to-establishing-your-first-autonomous-team/
Creating a feedback culture so that speed is not as scary: https://aws.amazon.com/blogs/enterprise-strategy/the-feedback-fix-how-to-fuel-a-learning-culture/ with rewards and recognition aligned to motivations: https://aws.amazon.com/blogs/enterprise-strategy/gamifying-digital-transformation-drive-adoption-through-engagement/
Stop starting everything; start finishing impactful initiatives quickly: https://aws.amazon.com/blogs/enterprise-strategy/deliver-faster-by-limiting-work-in-progress/
“Quality is my pride! How Samsung chairman’s ambition turned the business around: https://aws.amazon.com/blogs/enterprise-strategy/from-possibility-to-practice-reinventing-the-enterprise-from-the-inside/

Phil closed provocatively: “Is anyone delivering software too fast?” Laughter ensued, acknowledging outdated, lengthy ERP implementations simply don’t cut it in this dynamic era.

With only 12% of Australian businesses currently investing in AI training, author and futurist Andrea Clarke emphasized the critical importance of adaptability—AQ (Adaptability Quotient)—as the new frontier for intelligence in the AI age.

A special highlight was hearing from Anthony Seibold, Head Coach of Manly Warringah Sea Eagles, whose lessons transcended sport into leadership wisdom. Anthony’s relatable, authentic advice included:

Coming back from setbacks to enjoy the roller coaster ride
Switching gears between work and home with grateful journaling and other tips
Leading with fair treatment but not necessarily equal, rather tailored support to individuals’ motivations
Focus: on catching one or two “rabbits” at a time not 5 to ten
And how to build team bonds through vulnerability using the “Triple H” method encouraging teams to share: a hero, hardship and a highlight.

Crucially, Anthony emphasized “Optimism,” the potent force turning potential into genuine performance, particularly through practical GenAI applications enhancing player and team outcomes.

And this optimism isn't blind—it’s rooted in clear vision. Rianne Van Veldhuizen, Managing Director for AWS in Australia and New Zealand, reassured us of ongoing major investments in world-class Foundation Models, local job creation, and the launch of a dedicated AWS region in New Zealand.

Perfectly timed with this week’s AWS Summit, the Business Council of Australia unveiled bold plans to leverage AI, positioning Australia for leadership by 2028, boosting national GDP, and laying foundations for a vibrant, prosperous future.

The takeaway? With curiosity, pragmatism, and purposeful action, Australia is positioned to catch up and to lead again. Not through risky leaps into dystopia, but as pragmatic, thoughtful pioneers building an AI-driven future that benefits generations to come.

Navigating AI Hallucinations in Code Generation

2025-06-02T14:10:59-04:00

From Programmer to AI Evangelist

As someone who started coding over 25 years ago and now leads a company at the forefront of AI-enabled DevOps, I've seen firsthand how fast the landscape is shifting. AI isn't just augmenting code—it’s creating it. But we must stay grounded in how we assess its output.

Built-in Checks: Why Code Is Special

In the software world, we benefit from certain natural constraints. Code has to compile. It has to pass unit tests. These built-in safeguards provide real-time feedback that helps detect and reduce the impact of AI hallucinations. That’s not something writers, designers, or analysts enjoy in the same way.

But while code compilation and testing catch some errors, they don’t catch all.

When AI Fills in the Blanks—Wrongly

I gave an example in the session that reflects this. AI sometimes “hallucinates” fictitious API endpoints when it encounters poor documentation. Instead of responding with “no data available,” it extrapolates patterns based on known endpoints and invents something that sounds plausible—but doesn't exist.

Imagine integrating with an API where the AI confidently returns a /getCustomerProfile endpoint because it saw /getUserProfile and /getOrderDetails. It might compile. It might even pass initial tests. But when the integration fails in production, you're chasing a ghost.

The False Sense of Security

This is the illusion of functionality. Just because code runs doesn't mean it delivers value. In fact, one of the challenges we discussed is that AI-generated code can increase testing bottlenecks by flooding systems with seemingly valid but ultimately unhelpful logic.

One of our partners even observed a 300% increase in code quantity paired with a 400% decrease in code quality. AI can produce more, faster—but not necessarily better.

Why It Matters for Enterprises

In the executive session, we also talked about how the industry is evolving through phases:

Phase 1: Low-hanging fruit like AI-generated documentation, faster code drafting, and knowledge base expansion.
Phase 2: Workflow automation and IT modernization, like Amazon’s own AI-assisted migration that reportedly saved 4,500 years of development time.
Phase 3: Deeper personalization and data-driven intelligence—like detecting customer churn risk from support transcripts before a human could spot it.

These phases make one thing clear: hallucination isn't just a bug; it's a business risk. And enterprises must treat AI like a junior developer—review everything with scrutiny.

Inflectra’s Approach

At Inflectra, we’ve integrated AI into our Spira platform, working with Amazon Bedrock. Our Phase 1 strategy allowed customers to bring their own LLMs. Now, in Phase 2, with Inflectra.ai, we're embedding native support using Amazon Bedrock and Amazon Nova LLMs to improve performance and cost efficiency (up to 75% savings).

We're also using guardrails for data security and prompt management to ensure consistency. In the near future, we're building retrieval-augmented generation (RAG) capabilities that mine our rich project data for real-time insights.

XXXinflectraailearnXXX

Hallucinations, Handled the Right Way

So where does that leave us? AI in development is not a hands-off solution. It’s a powerful co-pilot that demands thoughtful oversight. As I said in the briefing, we’re entering a phase where autonomous testing and intelligent orchestration will reshape software quality.

But we won’t get there without discipline. Validate outputs. Classify your data. Use AI to enhance human intelligence, not bypass it.

AI may write the code—but humans must still write the rules.

5 Ways You’re Wasting Time Without SpiraApp for Confluence

2025-05-20T10:48:12-04:00

1. Copy-Pasting Requirements Manually

The Problem: You’re switching tabs, copying requirement text, and formatting it inside Confluence just to get team input.

The Waste: Time lost in manual updates, formatting headaches, and version mismatches.

With SpiraApp: Auto-generate a fully linked Confluence page directly from your requirement — one click, no paste.

2. Tracking Down Broken or Outdated Links

The Problem: You paste a link to a Confluence page into Spira, but the page gets moved, renamed, or archived. Now it’s a guessing game.

The Waste: Wasted hours chasing broken context or asking colleagues, “Where did this go?”

With SpiraApp: You store and open active, synced links from Spira directly into Confluence — no guesswork.

3. Losing Alignment Across Teams

The Problem: Requirements live in Spira. Collaboration lives in Confluence. Teams aren’t looking at the same source of truth.

The Waste: Miscommunication, rework, and deliverables that don’t match the original intent.

With SpiraApp: Requirements instantly generate collaborative Confluence pages, so everyone works from the same playbook.

4. Rewriting the Same Context… Over and Over

The Problem: Every requirement page you create in Confluence starts from scratch. Context, background, acceptance criteria — you retype it every time.

The Waste: Endless duplication, wasted creativity, and risk of inconsistency.

With SpiraApp: Automatically pull core requirement info into a fresh Confluence page, already formatted and ready for input.

5. Relying on Workarounds to Maintain Security and Traceability

The Problem: Ad hoc integrations and copy-pasted content introduce compliance risks and break traceability.

The Waste: Hours fixing audit trails, retroactively linking documents, and ensuring secure data handling.

With SpiraApp: Built-in SHA512 hashing and deep Spira-Confluence integration means better traceability — with less overhead.

Your Time is Valuable. Start Saving It.

Don’t let friction between Spira and Confluence slow down your teams. SpiraApp automates the grunt work, so you can focus on what matters.

👉 Try SpiraApp for Confluence!

Inflectra.ai Takes Center Stage: Revolutionizing the SDLC

2025-05-23T17:12:38-04:00

AI Everywhere: Breaking Bottlenecks in the SDLC

Adam Sandman kicked off the session by highlighting the current state of AI adoption in software development. While much focus has been on AI for code creation (think GitHub Copilot or Amazon Q), he emphasized that this alone creates new bottlenecks if other areas of the SDLC aren't also accelerated. Citing a McKinsey study, he stressed the need for AI to be present across the entire DevOps loop – from planning and creation to testing, release, and monitoring – to truly realize productivity gains. This resonated with the audience, as a pre-webinar poll revealed a significant portion of attendees are either "just exploring" or "running pilot projects" with AI, with a strong desire to automate repetitive QA and testing tasks.

Recording of the Webinar: Your Tools Just Got Smarter With Built-in AI

Inflectra.ai: Smart Generation & Automation

The core of the webinar was a compelling live demonstration of Inflectra.ai's capabilities. Adam Sandman showcased how, with just a simple user story in Spira, Inflectra.ai can rapidly generate a wealth of valuable artifacts:

Detailed Test Cases and Steps: Including both positive and negative scenarios.
BDD Scenarios: Ready for immediate use.
Development Tasks: Breaking down the work needed to implement features.
Identified Risks and Mitigations: Proactively flagging potential issues and suggesting solutions.
Sample Code and Unit Tests: Providing a jumpstart for developers.

A notable feature shown was the system's context sensitivity and guardrails, ensuring that AI-generated content remains relevant and safe, preventing misuse.

The demonstration then moved to Rapise, Inflectra's codeless test automation tool, now supercharged with AI. Attendees saw how Rapise could:

Automate manual test cases from Spira with natural language instructions.
Generate synthetic test data on demand, streamlining test setup.
Perform autonomous testing with the "AI Robot," which visually interacts with applications like a human, understanding and executing tests without pre-mapped objects. While currently best for simpler applications, the vision is to empower this AI with rich data from Spira and other sources to handle complex enterprise systems.

Behind the Scenes: A Secure and Scalable Architecture

Adam Sandman provided a brief but insightful look into Inflectra.ai's architecture. Built on AWS Bedrock, it leverages a mix of models like Amazon Nova and Claude Haiku, strategically chosen for optimal performance and cost. A key takeaway was Inflectra's commitment to data residency, ensuring that the AI models are hosted in the same geographic regions as customer data. The architecture is serverless and microservices-based, allowing for faster feature releases and continuous improvement, independent of Spira's monthly update cycle.

Get Started with Inflectra.ai Today!

For those eager to dive in, Inflectra is offering a special launch promotion: Inflectra.ai is available for just $1 per user per month for the next 60 days (until July 1st, 2025). This promotional price can be locked in for the entirety of a user's current subscription period, making it an incredibly attractive opportunity to experience the benefits of AI-powered SDLC management. Get started now!

Never Miss a Beat - Staying In Touch with Inflectra Is Easy!

Get notified of our upcoming webinars by signing up for our monthly newsletter! Stay in the loop of events, Inflectra product updates, company news, and more!

Inflectra at STAREAST 2025: Driving the Future of AI-Powered Software Quality

2025-05-05T14:31:47-04:00

Spotlight on AI: Inflectra’s Industry Insights Session

One of the true highlights was watching Inflectra CEO Adam Sandman and AWS Solutions Architect,Vishwa Kurakundi delivered a compelling talk titled, “Software Delivery at the Speed of AI: Inflectra Invests in AI-Powered Quality.” This session emphasized how AI accelerates software testing, providing:

Faster creation of test cases and automation scripts through SpiraPlan and Rapise.
Enhanced software quality even in rapid, agile development environments.
Strategic insights for teams to embrace AI and future-proof their software delivery processes.

Hands-on with Inflectra’s AI-Driven Solutions

Our booth was constantly buzzing as attendees explored and interacted with our AI-powered solutions:

SpiraPlan: Featuring AI-driven agile project management with predictive analytics, enabling superior risk forecasting, optimized resources, and greater project success.
Rapise: A sophisticated AI-based automation testing solution with advanced object recognition and machine learning, streamlining software testing across multiple platforms.

Attendees experienced firsthand how these tools can streamline testing processes, enhance team collaboration, and optimize project workflows.

AWS Partnership: Elevating AI-Enhanced DevOps

The collaboration with AWS was particularly significant for us at STAREAST. Our AI is exclusively built on AWS Bedrock, a decision that further deepens our partnership. It was exciting to see AWS experts joining us at the booth and during presentations, reinforcing our shared commitment to providing comprehensive, future-ready DevOps and quality solutions.

Celebrating Industry Partnerships

We’re grateful for our strong relationships with industry-leading partners like Coveros, Checkpoint Technologies, Quality Pros, Lambda Test, Value Labs, and Radview. These partnerships amplify our ability to innovate, allowing us to deliver comprehensive and cutting-edge AI-integrated testing solutions.

Community Connection: Engagement, Networking, and Inspiration

The vibrant energy at Inflectra’s booth showcased interactive demos, engaging discussions, and meaningful networking opportunities, contributing to the event’s dynamic atmosphere and reinforcing the transformative role of AI in software testing.

Future Outlook: Continuing the Journey of Innovation

Inflectra’s momentum continues, and we’re excited about our ongoing global engagements in 2025:

EuroSTAR 2025 (Edinburgh, Scotland): Highlighting AI-driven testing solutions for the European community.
AICon USA 2025 (Seattle, WA): Showcasing advancements in AI and machine learning in software quality.
Testing Talks 2025 (Sydney, Australia): Strengthening its leadership role in Asia-Pacific through in-depth AI integration discussions.
GITEX 2025 (Dubai, UAE): Delivering immersive experiences on AI’s transformative impact on enterprise software development.

As an added bonus, we have exclusive discount codes available for these upcoming events, ensuring our community has easier access to these impactful industry gatherings.

For those interested in exploring Inflectra's AI-powered solutions, visit our official website.

Team Inflectra

Rapise 8.4 Webinar Recap: Smarter UI, Dynamic Tests, AI, and More!

2025-05-01T15:50:40-04:00

The webinar kicked off by highlighting the major themes of Rapise 8.4: Scalable Test Orchestration, Dynamic Test Set Execution, and an Enhanced User Experience. Our expert host and Principal Software Developer at Inflectra, Denis Markovtsev, provided a comprehensive walkthrough, showcasing how these improvements can significantly streamline your testing processes.

Recording

Key Takeaways

Smarter UI: Quickly find objects and files with new filters, and easily reorder RVL tabs for better organization.
Dynamic Test Sets: Automatically select test cases based on flexible criteria, simplifying management of large test suites for both local and scheduled runs.
Powerful Test Orchestration: The new Test Runner module enables scheduling multiple test sets, intelligent rerunning of failures, and AI-driven root cause analysis.
Historical Insights & Reporting: Analyze past test data to identify flaky tests and generate insightful HTML and PDF reports, seamlessly integrated with Spira.
Enhanced Spira Integration: Rapise 8.4 tightly integrates with SpiraTest for advanced test management and reporting workflows.

Discover More About Rapise 8.4!

Ready to unleash the power of scalable test orchestration, dynamic test set execution, and an enhanced user experience?

Explore the comprehensive features of Rapise 8.4 and start a free trial to unlock the next level of test automation efficiency.

Stay in the Loop

Sign up for our monthly newsletter and you will always be in the know about the newest company updates, product releases, and upcoming events!

AI Software Development: How It’s Revolutionizing Lifecycles, Testing, & More

2025-12-12T15:55:48-05:00

AI and ML technologies are being increasingly applied in software development and test automation to program repetitive tasks, improve code quality, and enhance the accuracy and efficiency of testing. By leveraging AI, software development teams can accelerate their development and testing processes, reduce errors, and deliver high-quality software products to market more quickly.

AI in software development & testing

AI tools have become increasingly critical for software development and testing over the past few years, and for good reason. Advancements in AI systems have moved them from the theoretical to practical, assisting everything from early project planning to final deployment and ongoing upkeep. Right now, AI is largely used for the automation of repetitive tasks, but has also improved the overall quality and speed of application creation and delivery through code generation and optimization. More recently, AI models that incorporate reasoning or deeper analytical capabilities are able to provide better insights into software progress and effectiveness.

However, the major overlap between AI and software development in the last two to three years has been code generation. LLMs have been remarkably efficient at understanding syntax and formatting of different coding languages, making it much easier to use natural language coding (or no-code testing and development) to create applications. While this started out fairly basic, AI platforms like ChatGPT and Claude Sonnet are rapidly improving to perform more complex coding tasks and test automations.

We believe that this growing relationship between AI and software development comes down to their shared dependence on data and logic. In other words, software development provides structured inputs (like code, test results, logs, etc.) on which AI thrives. In turn, AI then brings speed, scale, and prediction capabilities that go beyond what humans can do, creating a feedback loop of improvement.

XXXrapisetrialXXX

Impact of AI on software development

Before we dive deeper into the impact that these shifts have had on software development, it’s important to first take a step back and look at the tech industry as a whole. The emergence and growing influence of AI and ML can be attributed to several factors. First, the explosion of data in recent years has made it necessary for businesses to efficiently extract insights from this vast amount of information, which AI algorithms have proven to be very effective at. Computing power advancements have also made it easier and more cost-effective for companies to implement AI technologies in their operations. Open-source libraries and frameworks make it easier for developers to get started without requiring extensive knowledge of machine learning algorithms and techniques. This emergence and growing influence of AI tools, particularly in the tech industry, is driven by the need for businesses to remain competitive in a rapidly changing landscape and the increasing availability and accessibility of the technology.

Now when it comes to AI’s impact specifically on software development, we’ve seen several tangible shifts in how people work and deliver products.

AI Pair Programming: Pair programming with tools like Copilot have revolutionized how developers write and optimize their code, offering suggestions and fixes that may be overlooked by humans.
Maturity of AI-Assisted Testing: As software testing tools increasingly leverage AI (like Rapise) and improve on its effectiveness, a wider variety of activities can be handled by automated systems, reducing bottlenecks in the SDLC.
Shift in Developer Focus: Automation of test case generation, test execution, documentation, and more has freed up developer time to focus on more valuable areas like better prompt engineering, more complex problem solving, and architectural design.
Rise of No-Code/Low-Code Platforms: The lower barrier to entry has resulted in more applications created by those with minimal programming knowledge. While we believe this is a positive shift, it’s critical to thoroughly test these platforms for security vulnerabilities and other issues that may be overlooked by someone without a development background.

Benefits of AI in software development

These industry shifts as a result of AI’s impact on software development offer many advantages to those who adopt these cutting-edge tools:

Faster Development Cycles: The efficiency improvements of AI automation tools have significantly sped up development cycles by reducing time spent writing boilerplate code and executing repetitive tests. This has enabled development teams to iterate faster, release features more often, and react more rapidly to market demands.
Better Code Quality: Not only is code created more quickly, but it can often be higher-quality because of AI’s analysis capabilities to quickly scan for potential issues or security vulnerabilities in real-time.
Reduced Costs: The overall efficiency and quality improvements translate to reduced costs of reworking faulty code and fixing bugs that were caught late in the SDLC. The faster time-to-market also provides a significant competitive advantage.
Wider Test Coverage: AI-powered test generation using tools like Rapise enable more comprehensive test coverage (including edge cases) without sacrificing test quality, which improves QA effectiveness and confidence in the product’s reliability.
Smarter Decision-Making: The unmatched efficiency of AI’s data analysis capabilities facilitates more informed decision-making for things like architectural recommendations, delivery estimates, performance regressions, and risk management tactics.
Improved Developer Experience: As mentioned above, freeing up developer time by automating mundane tasks allows them to focus on more challenging and creative areas of their work, pushing them to learn more and develop their problem-solving skills. This makes better developers who are often more satisfied with their jobs.

Challenges of AI

However, while AI clearly provides many benefits to software development and testing, there are also hurdles and drawbacks that need to be considered:

Data Quality: These algorithms rely on large amounts of high-quality data to learn and make accurate predictions. However, it can be challenging to ensure that the data used for training models is representative, unbiased, and free from errors or anomalies.
Bias and Ethics: Algorithms can also perpetuate and even amplify existing biases in the data used to train them, which can have significant ethical implications. It is essential to ensure that these systems are designed and implemented in a way that is fair, transparent, and ethical.
Over-Reliance on Automation: While AI can automate many repetitive and time-consuming tasks in software development and test automation, there is a risk of over-reliance on automation. This can lead to a lack of human oversight and judgment as well as skill degradation, so it’s essential to find the right balance between automation and human input.
Security and Privacy: Some systems may be vulnerable to cyberattacks and data breaches, which can compromise the security and privacy of sensitive information. Because of this, implementing robust security measures to protect AI-written code from these risks is crucial.
Explainability: Current AI models are often “black boxes,” which makes it difficult to understand how they came to a certain conclusion or generated a specific piece of code. This lack of interpretability can be an issue for software development in fields like healthcare, aviation, and other industries where safety is at stake.
Integration Complexity: We’re currently in a transitional phase as development teams begin to adopt AI tools into traditional pipelines. This has made it clear that adopting and incorporating these radically different functionalities will not be a seamless experience, especially for teams with legacy systems or very entrenched practices.

XXXspiratesttrialXXX

How to use AI in software development & testing

Despite these challenges, AI systems have become increasingly essential tools in software development due to their benefits — namely, the ability to improve the efficiency, quality, and accuracy of the development process. So, how can you use AI-driven software development tools to avoid the pitfalls discussed above while maximizing the value they provide?

Before taking action to incorporate AI, it’s important to begin by identifying high-friction or repetitive areas in your SDLC that would benefit most from efficiency improvements. From there, we recommend following these overarching best practices:

Explore Available Tools: Research and evaluate the various AI-powered software development tools, considering factors like ease of integration, features, pricing structure, etc.
Start Small: We discussed the difficulties of integration above, so start by implementing AI in specific, well-defined areas, monitoring and gathering feedback from your team to iterate your approach based on this input.
Provide Training: Another way to mitigate adoption struggles is to offer plenty of support (documentation, workshops, ongoing guidance) so your team can make the most of these new tools and understand their value.
Augment, Don’t Replace: The goal should be to help your developers, not replace them — emphasize how AI-powered tools can help them focus on more strategic and creative activities instead of tedious ones.

Now that we have a foundation of considerations as you begin to implement, what are the key areas and examples of how AI can help your processes?

Requirements gathering

Starting at the beginning, AI can parse through emails or messages from stakeholders to extract user stories, acceptance criteria, and more. Natural language processing (NLP) is a major functionality to speed up requirements gathering and organize documentation without spending hours of manual searching to create these documents. For new features of an existing platform, AI can quickly perform sentiment analysis on survey responses, product reviews, and social media to identify areas for improvement and proposed changes. This valuable user insight refines your requirements, setting the project up for success.

Taking requirements a step further, AI reasoning models are increasingly capable of effectively analyzing and prioritizing requirements based on a multitude of factors. These algorithms can take things like business value (based on historical project data), technical feasibility, and dependencies to efficiently manage and recommend which requirements are most valuable or important.

Code generation

AI can quickly generate boilerplate code, function skeletons, and language translations (like Java to Python) to get projects off the ground sooner. This can be done from a variety of inputs, including natural language descriptions of the required functionality. For example, some programs are able to take a prompt of “a function that sorts a list of integers” and output clean code in Java or Python to perform this task.

Beyond initial generation, AI-powered assistants and tools can suggest (or even complete) blocks of code based on the existing context, coding style, and designated best practices. Not only does this further speed up the process, but also reduces the likelihood of typos, syntax errors, and style inconsistencies.

Refactoring & optimization

Building on the code generation step, AI tools can be used to refactor existing code to maintain functionality but streamline and clean up codebases that have grown out of control over years of expansions. Even general AI chatbot tools like ChatGPT, Gemini, and Claude have gotten incredibly adept at detecting code smells and suggesting ways to restructure legacy code while minimizing disruptions. By flagging inefficient loops, redundant logic, or potential concurrency issues, AI coding assistants can help significantly improve performance of a system (including in ways that human developers may not have thought of).

Test automation

Probably one of the most common implementations of AI in software development right now (and a major way that Rapise and SpiraTest leverage AI), test automation has taken a huge step forward. Not only can platforms like SpiraTest auto-generate test cases from requirements or code, but they can identify gaps to suggest additional areas to evaluate. Rapise’s self-healing tests further enhance your testing activities, using AI and advanced optical character recognition to keep your tests functional, even when the application’s UI changes.

No-code features again reduce dependency on manual scripting of tests. Using plain English and visual interfaces, AI tools can turn natural descriptions and inputs into test scripts and run them, which makes software testing more accessible. Analysis based on historical test results can also tip off AI algorithms to which areas present the most risk of failure after a code modification, focusing testing efforts in these areas to save time and resources.

Bug detection

AI can help improve bug detection in two primary ways:

Predictive Bug Detection: Analysis of code to identify areas that might have vulnerabilities, anomalies, and patterns that could lead to bugs.
Root Cause Analysis: Analysis of error messages, logs, code changes, and more after a bug is reported to identify where the bug actually came from.

Both of these assist in reducing costs, either by resolving bugs before they become issues or getting to the root of identified bugs more quickly, saving time and resources.

Documentation

One of the more tedious aspects of software development and testing, documentation is still incredibly important for improving processes in the future. AI can help generate inline comments, summarize changelogs, and generate onboarding documentation tailored to each stakeholder. This vastly reduces manual effort in compiling information, while still keeping all team members and stakeholders informed.

Beyond basic changelog summarization, AI tools like SpiraTeam can generate detailed, real-time reports and dashboards that provide valuable insights. These could include types of failures, trends over time, and potential bottlenecks to be aware of. This again frees up more time for developers to focus on strategic and value-added tasks instead of constantly creating new reports to share with stakeholders.

Security enhancement

Security is becoming increasingly important in software development as we move towards other seismic shifts like quantum computing. Because of this, security testing now needs to be a major piece of every SDLC, thoroughly checking for vulnerabilities and preparing for a future of new threat vectors. As we’ve mentioned, AI tools can help check for weak points in real time, and some platforms can even continuously monitor third-party packages for CVEs. Once the code is ready to be tested, AI-powered testing tools can automate security testing activities (like fuzzing or penetration testing) in a scalable format across a variety of simulated platforms and environments.

Deployment

AI can not only analyze historical data to forecast deployment risks or predict rollback likelihood, but also recommend proactive strategies to mititgate these risks. AI features can further be integrated into CI/CD pipelines to automate activities and accelerate deployment timelines. Some tools can even continuously monitor live systems for anomalies that might indiciate issues or regressions post-deployment. This facilitates faster detection and resolution of problems once the application has been deployed to production.

Examples of AI use cases in software development

So what are some specific examples of how AI is used in software development and automation testing right now? You can start considering integrating AI via tasks such as:

Test Planning: Use AI platforms to analyze requirements and historical data to suggest test strategies, identify critical test areas, and more accurately estimate testing efforts.
Workflow Automation: Use AI tools to automate ticket updates, assigning tasks, triggering tests, and regression triage.
Load and Performance Testing: AI-powered testing tools can better simulate realistic user behavior under variable loads for more effective performance testing.
Test Case Maintenance: Find an AI-powered development tool with self-healing tests to maintain them and minimize tedious manual fixes when UIs or data changes.
Code Review: Try pair programming or formal code reviews with a code assistant to help flag potential issues or suggest improvements.
Chatbots for Dev Assistance: Beyond pair programming, an AI chatbot can be a valuable resource for developers to bounce ideas or problems off of.

Where is AI less useful in software development?

While much of this article has described the benefits of leveraging AI in your software development workflows, it’s important to recognize that there are plenty of areas where a human touch is more valuable than AI’s speed. Some areas where we recommend not using AI for your SDLC include:

Ethical Decision-Making: Situations like balancing user privacy with functionality or determining the societal impact of a product require human moral reasoning to fully understand the implications and weigh pros and cons. AI algorithms lack the capacity for this nuanced judgment, and could make decisions that aren’t in your users' best interests.
Abstract or Novel Problem-Solving: AI systems tend to lack the holistic system-level reasoning and creativity required for unprecedented challenges. The out-of-the-box thinking that we have as humans is critical for overcoming complex issues that AI training data doesn’t include or hasn’t been exposed to.
Debugging Emergent Behaviors: For problems that only appear under specific, real-world conditions, experienced devs are typically necessary to untangle and resolve. This is because these issues often rely on factors like intuition, forming hypotheses, and experimentation, which AI algorithms lack.
Complex Stakeholder Communication: Development often requires frequent interaction with a variety of stakeholders (clients, product owners, end-users, etc.), where effective communication and relationship building is critical for project success. AI cannot replicate human social skills, emotional intelligence, or understanding of interpersonal dynamics, which can hurt stakeholder communication.
Initial Conceptualization/Vision Setting: While we’ve discussed how AI can help get projects off the ground early in the SDLC, it shouldn’t be the first step. Ideation and vision for a product need to rely on our human imagination, intuition, and ability to identify unmet needs, which can then be supplemented by AI-assisted market research, trend analysis, etc.
Handling Ambiguity: AI models and algorithms rely on huge amounts of well-defined data to identify clear patterns and eliminate uncertainty. In situations where requirements, priorities, or challenges are ambiguous or changing, an AI tool might struggle to identify patterns and therefore struggle to provide insightful value.

Future of software development with AI

As we move into the second half of the decade, we’ll continue to see innovation around AI and software development — likely at an accelerated pace. Some trends that we’re already seeing in our industry include:

Code Generation Sophistication: A fairly obvious trend but worth spotlighting nonetheless, the complexity and nuance of AI-generated code has been improving dramatically in the last year, and this is expected to continue (e.g. generating entire features based on high-level specifications).
AI-Driven Project Management: Beyond the actual code, AI agents and tools are beginning to play more significant roles in project management tasks like risk management, resource allocation, automated task scheduling, and more.
More Autonomous Testing: This has been a major area of innovation for software testing tools like Rapise and SpiraTest, and these tools will continue to become more autonomous over time. We expect these systems to not only be able to generate and execute tests, but also analyze results and identify root causes.
Explainable AI for Compliance: The importance of understanding how algorithms came to certain conclusions or made certain decisions was discussed earlier, and the concept of XAI (Explainable AI) could help. This type of AI system is able to explain to humans the reasoning behind a suggestion or action taken, improving trust in these systems.
AI-Powered Security: As we’ve seen security become integrated in more phases of the software lifecycle (not just the very end), we anticipate this trend to continue as AI-driven security checks are incorporated at every stage of the SDLC.

Looking further ahead into the future, some speculative trends that we might see emerge in the next 5-10 years around AI software development include:

AI as a Partner: Artificial intelligence could become far more than just a tool, acting as a collaborator in the development process, participating in design discussions, and even autonomously contributing large portions of a system’s codebase.
Self-Evolving Software: AI that learns and adapts could allow systems to be self-healing, automatically detecting and resolving issues without human intervention. Beyond fixing bugs, this could start extending to performance optimization or even evolving the product’s functionality based on user feedback or environmental changes.
Further Democratization of Software Development: As we discussed with AI lowering the barrier to entry for creating software, continued innovation will make software development more accessible than ever. At Inflectra, we see this as a positive shift, focusing on all of the new creations and ideas that people can bring to life via software.

XXXspirateamtrialXXX

Will AI take over software development?

It has been said many times that “AI won’t replace you, but someone using AI will.” It’s important for developers and testers to start learning and adopting these new technologies and tools to keep up with the pace of innovation. Many companies around the world are already taking advantage of the benefits of AI-driven software development by integrating it into workflows, and you shouldn’t be left behind.

The importance of these technologies and their impact on modern software development can’t be overstated, which is why we offer a range of products that integrate cutting-edge tools, industry-leading test automation, and other development solutions to deliver better software faster. Our platforms help teams of all sizes and industries streamline their development and testing processes, reduce manual effort, and improve collaboration and communication throughout the software lifecycle. With Inflectra, you can leverage the power of AI and machine learning to enhance your software development and achieve your business goals. Get started with a free trial below!

Everyone’s a Coder, No One Owns Quality: Why Vibe Coding Needs a QA Revolution

2025-05-04T14:04:50-04:00

What Is Vibe Coding?

I’ve never had to write a line of code in my 20+ years in IT. Not even when Flash said "hello"/"goodbye." Not even when C++, VB, HTML, and SQL took over. I’ve always been surrounded by brilliant minds who could.

So, needless to say, I’m both excited and terrified to dive into “Vibe Coding” — that bold, new evolution in software engineering where conversational prompts become working code.

Vibe Coding means teams can ideate, prototype, and ship faster than ever. That’s thrilling. But here’s what keeps me up at night:

If everyone can now code…
Who’s testing the code?
Who’s responsible for quality in a world obsessed with "shifting left"?

Why Shift Left Is No Longer Optional

This new wave of prompt-driven coding is pushing the shift-left mindset even further — flipping traditional software development on its head. And on paper, it sounds like a dream for CIOs, CTOs, and us non-developers. Velocity? Through the roof.

But here’s something I overheard in our virtual corridors, from one of our R&D pros, August:

“If something doesn’t work in your code, you can just have AI rewrite it— in any language. That’s every QA’s nightmare.”

And he’s right. Because testing is no longer reserved for QA teams. Those once-sacred tasks — writing test cases, running security tests, or doing performance testing — are now being passed to Developers, BAs, even non-technical folks like PMs.

The Problem: Everyone’s a Tester, No One Owns Quality

So we need to ask ourselves:

What happens when AI-generated code hides bugs no one thought to look for?
Who ensures the requirements still maps to the business goals?
And when everyone’s a tester… does anyone actually own quality?

Let’s be real: speed without quality is just chaos.

SpiraPlan: A Modern Platform to Rein In Your Runaway Code

Vibe Coding only works if you have structure — a process that keeps creativity from spiraling into risk.

That’s where SpiraPlan from Inflectra comes in. It’s built for this new reality. With SpiraPlan, Vibe Coding doesn’t mean skunkworks and silos — it means tested, tracked, and validated code that still moves at the speed of thought.

With SpiraPlan, your team can:

Prevent untested code from slipping into production
Align requirements to outcomes and avoid costly rework
Gain visibility into testing progress — no matter your tools, teams, or time zones
Protect quality while moving fast
Integrate testing early, using requirements traceability, automated tests, and real-time, actionable dashboards for collaboration, compliance, and visibility.

Learn more about SpiraPlan and how it can power your software delivery.

Conclusion: Why Speed Without QA Is Risky

The future of software is AI-powered, fast, and deeply collaborative.But without the right tools, shifting left just means shifting the risk sooner.

Try SpiraPlan for free today — before the AI genie is out of the bottle and writing your roadmap.
Because speed is great. But speed with quality? That’s the real win.

Bridging the Gap Between Generations with Spira and SpiraApps

2025-03-31T14:18:49-04:00

Introducing the GenZ-Arator

This new SpiraApp installs into your instance of Spira and with a single click on the requirements detail page, converts the name and description of your requirement into a version that is more comfortable for your GenZ team mates:

Or as they would probably say - This new SpiraApp is straight fire, it's gonna hook you up real quick. You just gotta install it on your Spira, and then boom, you can click on the req details page and it'll transform that stuff into something your fellow Gen Z homies can vibe with, ya feel me? No more of that boring, stuffy language - this app's gonna make it lit for your whole squad. It's a total game-changer, trust me on this one.

Harnessing the Power of Generative AI

This new SpiraApp leverages our partnership with Amazon Web Services (AWS) and their AWS Bedrock platform. The SpiraApp can be used with any of the LLM families available in Bedrock, including Nova, Claude and Llama.

Seeing It In Action

You can use this SpiraApp for simple functional requirements, like the one illustrated above, or even for more complicated IT modernization projects like migrating your database from SQL Server to something more cloud-native:

With the GenZ-Arator SpiraApp, you can even ask it to generate multiple versions of the translation, to see which one feels the most natural:

Since Inflectra always cares about quality, we had some of our GenZ team members take a look at the output and give their verdict:

How Do I Get The SpiraApp?

Yo, so you wanna download a fresh SpiraApp for your SpiraTeam, right? It's like, super easy, fam. Just head over to the Inflectra website and you'll see the download button, no cap. Click that bad boy and let the magic happen. Once it's downloaded, just install it and you're good to go. It's gonna be a total game-changer, trust me. You'll be flexing on all your friends with your sick new SpiraApp, no doubt. Just make sure you don't sleep on it, 'cause this is the real deal, you feel me? Let me know if you need any other deets, I got you. Download here.

Bridging the Gap: Integrating SpiraPlan with DevOps Tools for Seamless CI/CD - A Recap Blog

2025-03-24T11:07:43-04:00

Sandman began by recapping the core principles of DevOps, emphasizing its role in accelerating software delivery without compromising quality. He highlighted how Inflectra's platform, particularly SpiraPlan, facilitates this by integrating various stages of the software development lifecycle.

RECORDING

See how SpiraPlan can help you map your value stream and integrate your DevOps tools for faster delivery. Explore now!

SPIRAPLAN INTEGRATIONS & VALUE DELIVERY:

The webinar demonstrated SpiraPlan's integrations with Azure DevOps, GitHub, and GitLab, focusing on:

Unified Work Item Management: Bidirectional sync (Azure DevOps) and incident tracking (GitHub/GitLab).
Direct Source Code Access: Git repository integration for code traceability.
Real-time Pipeline Visibility: CI/CD integration via plugins/webhooks.

SpiraPlan's value stream mapping was also showcased, enabling program managers to:

Aggregate data for a holistic project view.
Track progress against business goals.
Identify bottlenecks for timely value delivery.

KEY TAKEAWAYS

SpiraPlan acts as a central hub, integrating diverse DevOps tools for enhanced collaboration and traceability.

The platform's robust integrations enable teams to maintain their preferred workflows while providing management with a comprehensive overview.
Value stream mapping capabilities in SpiraPlan facilitate program-level coordination and ensure alignment with business objectives.
The incident tracking is bidirectional for Azure Devops, Github, and Gitlab.

NEVER MISS A BEAT

To stay up-to-date on the latest company news, product updates, and events, be sure to subscribe to our monthly newsletter.

Webinar Recap: Simplify Time Tracking & Keep Projects on Schedule with SpiraPlan

2025-03-19T16:53:03-04:00

Key Takeaways:

Simplified Time Tracking: SpiraPlan 8.7 offers a revamped, user-friendly timesheet for accurate daily time logging against tasks and incidents.
Streamlined Approvals: New timesheet approval workflows enable managers to efficiently review and manage team time entries.
Enhanced Reporting: Robust reporting tools provide detailed timesheet insights, including custom reports for billing and project analysis.
Clear Change Tracking: The artifact difference view visually highlights changes to requirements, test cases, and other artifacts, improving change management.

Recording

Simplify Your Project Management with SpiraPlan

Ready to experience the benefits of simplified time tracking and enhanced project management? Check out SpiraPlan today and discover how it can help your team stay on schedule and deliver successful projects.

Never Miss an Webinar

Get notified of our upcoming webinars by signing up for our monthly newsletter! Stay in the loop of events, Inflectra product updates, company news, and more!

Recap: From Tedious to Seamless - AI-Driven QA with Rapise 8.3

2025-03-09T19:25:45-04:00

Adam's decades of experience in software development and testing, combined with Denis's expertise in advanced test automation and AI, provided valuable insights into the latest advancements in the field, particularly the revolutionary potential of AI-driven Quality Assurance. This expertise illuminated how AI is transforming software testing, offering unprecedented levels of efficiency and effectiveness. The following key takeaways highlight the powerful capabilities of Rapise 8.3 in this evolving landscape.

Recording

Key Takeaways

AI-Powered Test Design: Generate test cases and steps automatically from requirements using Spira and LLMs, accelerating test planning.
Seamless Manual-to-Automated Conversion: Import manual tests from Spira and convert them to automated tests using AI-driven code generation in Rapise.
Intelligent Test Data Creation: Leverage AI to generate realistic and varied test data, including lists and tables, directly within Rapise.
Runtime AI-Driven Validation: Perform advanced checks and assertions during test execution with AI Tester, including image analysis and soft assertions.
Revolutionary AI Robot: Automate complex test scenarios using natural language instructions with AI Robot, eliminating the need for traditional scripting.
Enhanced Automation with OCR: Utilize OCR capabilities for object recognition, enabling text extraction and interaction with UI elements based on their textual content.

Meet Your Hosts

Adam Sandman, Founder & CEO, Inflectra: Adam has decades of experience in software development and testing, leading innovation in tools that enable teams to simplify and optimize their workflows.

Denis Markovtsev, Chief Architect, Rapise: Denis specializes in creating advanced test automation solutions, leveraging AI to solve modern testing challenges and accelerate delivery cycles

Conclusion

The webinar showcased how Rapise 8.3 is at the forefront of AI-driven QA, offering a suite of powerful tools to streamline testing processes and improve overall efficiency. From intelligent test case generation and data creation to runtime AI analysis and the revolutionary AI Robot, Rapise 8.3 empowers QA teams to focus on strategic testing activities rather than getting bogged down in repetitive tasks. These advancements not only save time and resources but also contribute to higher quality software releases.

Join the growing community of Rapise users and embrace the power of AI in QA. Try Rapise 8.3 FREE for 30 days and discover how AI can transform your testing workflow.

XXXrapisetrialXXX

A Hands-On Approach to API Testing with SpiraPlan and Postman

2025-01-23T10:19:16-05:00

Why API Testing is Non-Negotiable

APIs are responsible for enabling systems to talk to each other—retrieving data, processing transactions, or updating information seamlessly. However, poorly tested APIs can lead to:

Unreliable Systems: Data may not sync, features may break, and user experiences suffer.
Security Risks: Vulnerabilities in APIs can expose sensitive data.
Performance Bottlenecks: Slow or overloaded APIs degrade performance, causing downtime or frustration.

To avoid these pitfalls, API testing verifies that:

APIs return the correct responses for valid and invalid inputs.
They can handle real-world traffic conditions.
Security measures like authentication and encryption are in place.
Errors are handled gracefully, without crashing systems.

With APIs playing such a pivotal role in software development, testing them isn’t just a best practice—it’s a necessity.

Tools of the Trade: Postman and SpiraPlan

Postman is one of the most widely used tools for API testing, providing an intuitive interface to send requests, inspect responses, and automate tests. Whether you’re testing a REST API or SOAP endpoints, Postman makes it straightforward to verify API behavior.

When integrated with SpiraPlan, Postman’s capabilities are enhanced. SpiraPlan allows teams to track API testing efforts alongside development tasks, providing traceability, centralized test management, and insights into test results.

A Step-by-Step Walkthrough: Accessing SpiraPlan’s REST API with Postman

When testing APIs, tools like Postman simplify the process of sending requests, inspecting responses, and automating tests. For teams using SpiraPlan, the REST API unlocks programmatic access to workspaces, requirements, and other artifacts—allowing for more efficient workflows and automation.

This section provides a practical walkthrough on how to interact with SpiraPlan’s REST API using Postman. We’ll cover how to navigate workspaces, retrieve data, and perform essential CRUD (Create, Read, Update, Delete) operations using the GET, POST, PUT, and DELETE methods, to streamline your API testing process.

Navigating SpiraPlan: UI vs. REST API

SpiraPlan allows you to interact with its workspaces and artifacts in two ways:

Through the User Interface (UI): Ideal for quick navigation to workspaces, requirements, and other project elements.
Programmatically via the REST API: Provides automation capabilities, scalability, and integration with tools like Postman for more streamlined testing.

Below, we’ll demonstrate both approaches, starting with accessing workspaces and progressing to CRUD operations using Postman.

Accessing Workspaces in SpiraPlan Using the User Interface

Log in to SpiraPlan and navigate to the My Page section.
Select your desired workspace from the list of available projects.
- Example: The workspace “Financial Management System” has a Workspace ID of 33.
- URL to access this workspace: https://companyname.spiraservice.net/33/General.aspx

Accessing Workspaces in SpiraPlan Using the REST API

To access a workspace programmatically, use the Project ID (Workspace ID) in the REST API endpoint.

General Endpoint Format: https://companyname.spiraservice.net /projects/{Project_id}
Example for Workspace 33: https://companyname.spiraservice.net/projects/33

Performing CRUD Operations with Postman

Postman makes it easy to test SpiraPlan’s REST API by organizing your requests into collections and automating workflows. Let’s go step-by-step through each operation.

GET Request: Retrieving Data

The GET method retrieves data from SpiraPlan, such as project details or requirements.

Steps in Postman

Open Postman and create a new request in your collection.
Set the method to GET.
Enter the following endpoint, replacing placeholders with actual values: https://companyname.spiraservice.net/services/v7_0/RestService.svc/{workspaceID}/{artifactID}

Example: To retrieve requirements for Workspace 33, replace {workspaceID} with 33.
1. Add the necessary headers:

username: {{username}}

api-key: {{api-key}}

Accept: application/json

Click Send to execute the request and view the response.

POST Request: Creating New Data

The POST method sends new data to SpiraPlan, such as adding a new requirement.

Steps in Postman

Create a new request and set the method to POST.
Use the same endpoint format: https://companyname.spiraservice.net/services/v7_0/RestService.svc/{workspaceID}/{artifactID}
Add the headers:

username: {{username}}

api-key: {{api-key}}

Accept: application/json

In the Body tab, select raw and set the format to JSON. Add the payload:

{

"key": "value"

}

Click Send to send new data to the server.

PUT Request: Update Existing Data

The PUT method updates an existing resource, such as modifying a requirement.

Steps in Postman

Create a new request and set the method to PUT.
Use the same endpoint: https://companyname.spiraservice.net/services/v7_0/RestService.svc/{workspaceID}/{artifactID}
Add headers:

username: {{username}}

api-key: {{api-key}}

Accept: application/json

In the Body tab, provide the updated data:

{

"key": "updatedValue"

}

Click Send to apply the changes.

DELETE Request: Removing Data

The DELETE method removes a resource from SpiraPlan, such as deleting a requirement.

Steps in Postman

Create a new request and set the method to Delete.
Use the endpoint: https://companyname.spiraservice.net/services/v7_0/RestService.svc/{workspaceID}/{artifactID}
Add headers:

username: {{username}}

api-key: {{api-key}}

Accept: application/json

Click Send to remove the resource.

Why Use Postman with SpiraPlan?

By combining Postman’s user-friendly interface with SpiraPlan’s REST API, teams can:

Automate Repetitive Tasks: Save time by organizing requests into collections and reusing variables.
Validate API Functionality: Easily test endpoints for accuracy and reliability.
Improve Collaboration: Share test collections and results with your team.
Integrate with Broader Workflows: Align API testing efforts with development and project management in SpiraPlan.

Conclusion: Bridging UI Navigation and API Automation

API testing is essential for ensuring that your systems operate smoothly, securely, and efficiently. While SpiraPlan’s user interface offers an intuitive way to navigate workspaces and requirements, leveraging the REST API with Postman provides a powerful method for automating and streamlining your testing efforts.

To see these steps demonstrated in detail, watch the webinar recording "Utilizing SpiraPlan’s REST API", where we demo these concepts in greater detail with live examples and practical use cases.

Watch the recording

Webinar Recap: Ask an Expert - How to Handle QA KPIs in Spira

2025-01-22T10:24:27-05:00

Dr. Sriram Rajagopalan provided valuable insights into the core principles of quality management, emphasizing the importance of prevention over correction and "measuring what matters". The webinar also included a practical demonstration of how Spira can be used to track and analyze key quality metrics, empowering teams to improve their software development processes.

Recording

Key Takeaways:

Quality assurance is more important than quality control. Quality assurance is about preventing defects, while quality control is about finding and fixing defects.
The cost of quality is the sum of the cost of good quality and the cost of bad quality. The cost of good quality includes the cost of prevention and appraisal. The cost of bad quality includes the cost of internal and external failure.
There are a number of KPIs that you can use to measure the quality of your software. These include defect analysis, test case coverage, test cycle time, and regression efficiency.
You can use Spira to track and report on these KPIs. Spira has a number of built-in reports that you can use, as well as the ability to create custom reports.

About the Host:

Sriram Rajagopalan is a project management guru and Enterprise Agile Evangelist at Inflectra Corporation. Dr. Rajagopalan has extensive software development and project management experience in many industries. He won prestigious recognition from PMI with the Eric Jennet Project Management Excellence Award in 2017. He holds a BE in Electronics and Communication Engineering from the University of Madras in India, an MS in Computer Engineering from Wayne State University, and an MBA in Management from Concordia University. His Ph.D. was in Organization and Management from Capella University. Dr. Rajagopalan possesses many professional certifications in PfMP, PgMP, PMP, PMI-ACP, PMI-SP, PMI-RMP, CSP, CSPO, CSD, CSM, ACC, IT Project+, Six Sigma, SCM, SCPO, SCD, SAMC, SCT, and CSOXP.

Stay in the Know

To stay up-to-date on the latest company news, product updates, and events, be sure to subscribe to our newsletter.

Top 5 Reasons to Migrate Your Spira Instance to Cloud

2025-01-21T17:21:45-05:00

The Cloud Advantage

The way businesses operate has been undergoing a rapid transformation, with the cloud solidly at the center of this evolution. Organizations globally are adopting cloud-first strategies to enhance agility, scalability, and cost efficiency. According to Gartner, by 2025:

95% of new digital workloads will be deployed on cloud-native platforms, compared to just 30% in 2021.
90% of new enterprise applications will embed AI, making cloud platforms smarter and more capable than ever.

Cloud environments powered by AI, edge computing, and robust security frameworks are no longer a luxury—they’re a necessity. Migrating to Inflectra’s AWS hosting positions your business to thrive in this dynamic landscape.

The Benefits of AWS Delivered by Inflectra

1. Unmatched Security and Compliance for Spira Workloads

Inflectra ensures that customers gain AWS’s advanced security capabilities, enhanced with Inflectra’s dedicated compliance frameworks tailored to Spira workloads:

Inflectra’s SOC2/Type-2 and PCI-DSS certifications complement AWS’s compliance with standards like ISO27001, GDPR, and HIPAA, ensuring regulatory adherence.
Inflectra’s real-time security monitoring integrates seamlessly with AWS’s tools like AWS Shield and Key Management Service (KMS) to protect sensitive project data from cyber threats.
Inflectra and AWS partnership adds multi-level threat detection, firewalls, and other cyber defense options, delivering peace of mind for teams managing critical workloads.

This combined security framework ensures that organizations hosting Spira on AWS through Inflectra are fully protected, compliant, and secure.

2. Global Accessibility with Regional Compliance

Inflectra leverages AWS’s extensive global network to ensure fast, reliable access to Spira workloads while adhering to local regulations:

Customers can choose Inflectra's hosting regions in the USA, EU, India, Singapore, Australia, and Canada, ensuring data residency compliance with GDPR, HIPAA, and other regional standards.
Inflectra’s disaster recovery protocols ensure backups are stored within compliance jurisdictions, protecting data from downtime while meeting strict legal requirements.

With Inflectra’s expertise, businesses can operate globally without compromising on performance or regulatory compliance.

3. Versatile Approach: Cloud-Preferred and On-Premise Ready

Inflectra recognizes that every organization has unique operational requirements, especially in highly regulated industries. Our "cloud-preferred" approach reflects the broader industry trend toward cloud migration, with 52% of IT environments already in the cloud and 63% expected to migrate by 2025 (Flexera 2023). However, Inflectra equally values the importance of offering robust on-premise solutions, ensuring all customers receive the same high-quality, feature-rich experience, regardless of deployment model.

On-premise hosting remains a powerful and viable option for organizations with stringent compliance needs or those requiring enhanced control over sensitive data. Inflectra ensures seamless, by-directional migration between cloud and on-premise environments, supporting flexibility as business and compliance needs evolve. Our focus is on empowering your organization with the tools and support needed to thrive, regardless of where your workloads reside.

4. Blazing Performance and Reliability Backed by Inflectra

Speed and reliability are critical for managing Spira workloads, and AWS delivers both in abundance. With high-performance AWS EC2 instances and EBS SSD storage, you’ll enjoy:

Guaranteed IOPS Throughput: Optimal speed and efficiency for your data storage needs.
Failsafe Backups: Offsite backups stored in a separate availability zone, ensuring data integrity even in the face of failures.
Automatic Snapshots: Frequent backups mean you can restore your system quickly if needed.

Plus, with Inflectra’s hosting, all services are accessible over HTTPS, allowing them to work seamlessly through firewalls without compromising security. Add in AWS’s redundancy and 99.99% uptime SLA, and you have a hosting solution that never lets you down.

5. Future-Ready Innovation Delivered by Inflectra

By migrating to Inflectra’s AWS hosting, your organization gains access to cutting-edge tools and technologies that prepare you for the future:

AI and ML Integration: Inflectra empowers Spira users to adopt tools like Amazon Bedrock and SageMaker, enabling predictive analytics and workflow automation.
IoT Support: With Inflectra’s guidance, customers can extend Spira workloads into IoT applications using AWS IoT services for real-time monitoring and automation.
Scalable Growth: Inflectra ensures seamless scalability by leveraging AWS’s elastic architecture, allowing businesses to grow their operations without disruption.

This forward-thinking approach ensures your organization remains competitive and innovative in an ever-evolving market.

Real-World Benefits for You and Your Team

Migrating your Spira workloads to Inflectra’s cloud hosting on AWS ensures a seamless experience, even for users with limited technical expertise.

Simplified Migration: The migration process is designed for simplicity. With pre-configured environments and guided setup tools, you can have your workloads up and running in minutes.
No Technical Overhead: Forget about managing complex server configurations or troubleshooting hardware issues. Inflectra handles it all, so your team can focus on what they do best—delivering projects and meeting deadlines.
Hassle-Free Maintenance: Say goodbye to server maintenance, manual updates, and unexpected downtime, ensuring your platform runs on the latest, most secure version.

Inflectra: Your Trusted Partner in Cloud Migration

Migrating to the cloud can seem daunting, but Inflectra is here to guide you every step of the way. Inflectra's team of experts provides comprehensive support, ensuring a smooth and successful transition. We'll handle the technical complexities, so you can focus on what matters most: leveraging the power of Spira to achieve your business goals. Whether your goal is to scale operations, harness AI-driven tools, or ensure compliance with global regulations, Inflectra on AWS is the solution you’ve been waiting for. And if your needs evolve, transitioning back to on-premise environments is equally seamless.

Ready to Take the Leap?

Contact us today to learn how Inflectra can make your cloud migration journey stress-free while empowering your business to scale, innovate, and thrive in the digital era.

Ensure Quality Delivery with Effective Test Design

2025-01-06T13:01:35-05:00

What is Test Design in Software Testing?

Test design is a cornerstone of the software testing lifecycle, involving the creation of test cases that ensure a system meets its requirements. This process includes analyzing requirements, anticipating user behaviors, and crafting test scenarios that balance risk management with test coverage. When executed effectively, test design validates functionality, promotes stakeholder alignment, maintains requirements traceability, and simplifies test maintenance over time.

Challenges in Delivering High-Quality Software

Ensuring software quality is a complex task with numerous challenges that can hinder progress, impact product quality, and potentially result in business setbacks. Some challenges include:

Resource Constraints: Limited time, budget, and skilled personnel can slow testing and reduce effectiveness.
Unclear Requirements: Ambiguous or evolving requirements often lead to scope creep, defects, and rework.
Team Misalignment: Poor collaboration and siloed workflows undermine testing efforts.
Insufficient Coverage: Redundant tests and lack of traceability can lead to undetected issues.
Complex Test Data: Generating and maintaining accurate data is critical but often challenging.
Late Defect Detection: Identifying issues late in development increases costs and delays.
Test Maintenance: As requirements change, keeping test cases relevant and up to date becomes increasingly challenging.

How Yest and Spira Solve Test Design Challenges

Combining Yest visual test design and Spira test management offers a robust, integrated solution to these challenges. Together, they accelerate testing, enhance collaboration, and ensure high-quality results. Here’s how:

Yest: Using a visual language, Yest enables teams to design tests collaboratively. Its IDE features, like automatic test generation, impact analysis, and automated updates, make it a go-to choice for Agile and DevOps teams.

SpiraTest: A comprehensive test management platform that integrates seamlessly with development tools, Spira enables execution, defect tracking, and continuous testing.

By working together, these tools streamline the testing process and reduce manual effort by up to 40%, giving teams more time to focus on what truly matters.

Step-by-Step Guide: How Yest and Spira Work Together

1. Visual Workflows for Clarity and Collaboration

The process starts with requirement analysis in Spira, where the entire team reviews and understands the project requirements and priorities. Based on this analysis, testers or business analysts use Yest to create graphical representations of user scenarios and user journeys. These visual workflows can be shared or developed during 3 Amigos meetings to identify gaps, clarify requirements, and mitigate risks before development begins. This shared visual language fosters collaboration and supports a shift-left approach, encouraging early stakeholder alignment.

Addressed challenges: Unclear Requirements, Team Misalignment

2. Adding Decision Tables for Test Relevance

Once workflows are designed, testers define business rules, detailed test steps, and associated risks and priorities using decision tables. Representing test cases in this structured format improves readability and simplifies maintenance. This approach also enhances control over the combinations to be tested, ensuring the creation of relevant and comprehensive test scenarios.

By linking these decision tables to Spira requirements, teams can achieve full traceability, aligning their testing efforts with project objectives throughout the entire testing lifecycle.

Addressed challenges: Insufficient Coverage, Test Maintenance

3. Automated Test Scenario Generation for Optimized Coverage

Test scenarios are automatically generated from workflows, ensuring comprehensive yet optimized coverage while minimizing test maintenance and execution efforts. With Yest, as a model-based tool, teams can adjust the coverage intensity, enabling a targeted focus on high-risk areas. This approach reduces the likelihood of costly defects reaching production and optimizes the number of scenarios, particularly when time and resources are constrained. Yest also facilitates the preparation of datasets for both manual and automated testing, ensuring consistent data across various execution scenarios.

The generated scenarios are seamlessly transferred into SpiraTest, where traceability links to requirements are established. This integration provides complete visibility into the testing process within Spira, ensuring transparency and alignment throughout the development lifecycle.

Addressed challenges: Resource Constraints, Insufficient Coverage, Late Defect Detection, Complex Test Data

4. Streamlining Automation with a Keyword-Driven Approach

Yest empowers teams to streamline test automation with a keyword-based approach to generate test scripts. Functional testers ensure test relevance, maintain consistent data, and prepare scripts, enabling automation engineers to focus on solving technical challenges.

This collaborative approach redefines test automation, shifting it from a siloed task performed exclusively by automation engineers to a team-wide effort. By fostering contributions across the team, Yest increases efficiency, scalability, and alignment throughout the testing process.

Yest and Spira seamlessly integrate with a variety of automation tools, including Selenium, Eggplant, Tosca, UFT, Ranorex, and Rapise. This integration enables test scripts generated by Yest to be easily transferred to these tools, bridging the gap between technical and non-technical users. Test execution results are reported to Spira, ensuring complete traceability and comprehensive reporting across key artifacts such as requirements, test cases, and incidents. This streamlined process establishes a reliable Single Source of Truth for all stakeholders.

Addressed challenges: Resource Constraints, Team Misalignment

5. Adapting to Change with IDE Accelerators

As project requirements change, Yest's IDE accelerators—featuring impact analysis, change propagation, and intuitive refactoring tools—help teams adapt quickly. Yest’s graphical representation simplifies the understanding of necessary updates, allowing teams to visualize and implement changes seamlessly. Its automated impact analysis identifies both manual and automated tests that may be affected, ensuring complete visibility into the testing process and facilitating efficient updates. Additionally, Yest supports bulk corrections of affected scenarios and enhances test coverage with newly generated test scenarios. These features enable teams to respond quickly and effectively, even in fast-paced Agile environments.

Addressed challenges: Test Maintenance, Resource Constraints, Team Misalignment, Insufficient Coverage

Yest and Spira empower teams to easily handle complex testing requirements through this integrated workflow, promoting efficiency, collaboration, and adaptability in Agile and DevOps settings.

Key Benefits of Yest and Spira Test Design Integration

Visual Test Design: Simplifies complexity with intuitive workflows, improving communication and reducing errors.
Enhanced Efficiency: Reduces manual effort by automating repetitive tasks, saving up to 40% of the time.
Robust Traceability: Links test cases directly to requirements, ensuring complete coverage.
Streamlined Automation: Makes transitioning between manual and automated testing effortless.
Agile and DevOps Support: Seamless synchronization and automated updates make it ideal for iterative workflows.

Use cases

Discover how Generali France effectively used Yest to align business rules, resulting in faster and more relevant test creation. Additionally, learn how Spira provided Generali Switzerland with real-time visibility into test coverage across multiple projects.

Best Practices for Effective Test Design in Agile and DevOps

To fully leverage the power of test design and maximize the benefits of the Yest and Spira integration, consider the following best practices:

Start Early with a Shift-Left Approach: Begin test design early to identify issues upfront. Yest’s visual workflows and Spira’s traceability features help build a strong foundation, reducing late-stage defects and rework.
Foster Cross-Team Collaboration: Engage stakeholders across disciplines, including business experts, developers, and testers, to design test scenarios that reflect real-world use cases.
Visualize Scenarios for Clarity: Use tools like Yest to create graphical workflows that simplify complex processes, reduce ambiguity, and enhance team communication.
Focus on Risk-Based Testing: Prioritize critical areas using Yest’s decision tables to address risks early, balancing high-priority focus with comprehensive coverage.
Leverage Automation Strategically: Treat automation as a complement to manual testing by focusing on repetitive, time-consuming tasks and leveraging Yest's keyword-driven approach with reusable scripts.

By adopting these best practices, teams achieve efficient and collaborative testing that aligns with business goals and ensures the delivery of quality software.

Conclusion: Transform Test Design for High-Quality Software Delivery

Effective test design is the backbone of successful software testing. By combining the Yest test design tool with Spira test management, teams can overcome challenges such as unclear requirements, insufficient coverage, and evolving needs. This integration promotes model-based testing, improves requirements traceability, and streamlines manual and automated testing processes.

Organizations that embrace modern test design tools and best practices are better equipped to ensure quality, adapt to change, and accelerate delivery. In a world where speed and reliability are paramount, investing in robust test design is critical to software success.

Download Smartesting’s e-book to further master effective test design. If you would like to see if the integration is suitable for you, please contact Smartesting for a demo.

Accelerate Your Software Delivery with AI: Insights from Inflectra's AI Webinar

2024-12-16T16:54:14-05:00

Adam Sandman highlighted the transformative power of AI, emphasizing its potential to revolutionize the entire software development lifecycle (SDLC). While AI has dramatically increased coding productivity, its impact extends far beyond code generation and chatbots, reaching into planning, development, testing, and even monitoring. This surge in efficiency has, however, created new bottlenecks in other stages of the SDLC. To truly harness the power of AI and maintain a balanced workflow, organizations must adopt a holistic approach to its implementation, ensuring seamless integration and optimization across the entire development process.

Key Takeaways

AI is transforming the entire software development lifecycle, not just coding.
Organizations need to adopt a comprehensive approach to AI implementation to maximize its benefits.
High-quality requirements are essential for successful AI-driven software development.
The future of AI in software development is bright, with continuous advancements promising to further revolutionize the industry.

Spira and Rapise: Inflectra's AI-Powered Solutions

At Inflectra, we're committed to providing our customers with cutting-edge tools that leverage AI to enhance productivity and quality. Here's how our platforms are leading the way:

Spira: Our comprehensive lifecycle management platform incorporates AI to streamline various tasks, including:
- Effortless Artifact Generation: Automatically generate BDD scenarios, manual test cases, developer tasks, unit tests, and documentation, eliminating tedious manual effort.
- Proactive Risk Management: Identify and mitigate potential risks, ensuring software quality and reducing costly rework.
Rapise: Our powerful test automation tool offers two generations of AI-driven capabilities:
- Simplified Test Creation: Convert natural language instructions into automated test scripts, making test automation accessible to everyone.
- Autonomous Testing: Leverage advanced AI models to enable "autonomous testing," where AI can control devices and execute actions based on high-level commands, simulating human-like interactions.

Try Spira and Rapise with a FREE TRIAL and experience firsthand how these innovative tools can revolutionize your development process.

Conclusion

AI is rapidly changing the world of software development, pushing the boundaries of what's possible. To stay ahead of the curve, development teams need powerful tools that harness the potential of AI. Inflectra's Spira and Rapise platforms deliver exactly that, with AI-powered features that boost productivity and streamline workflows. Embrace AI across your entire SDLC to keep pace with this evolution and deliver high-quality software efficiently.

Sign up for our newsletter to stay informed on our product advancements, events, and additional company news!

Level Up Your DevSecOps with AI: Webinar Recap

2024-12-12T15:25:31-05:00

With software now essential to almost every organization, application security is critical. DevSecOps integrates security into every stage of the software development lifecycle, breaking down barriers between teams and promoting shared responsibility for secure software.

The Benefits of a DevSecOps Approach

Reduced Risk: By identifying and addressing vulnerabilities early on, DevSecOps minimizes the potential for costly security breaches and data leaks.
Faster Time-to-Market: Automation and streamlined processes enable faster development cycles and more frequent releases.
Improved Teamwork: DevSecOps fosters a culture of shared responsibility for security, leading to better communication and more effective teamwork.
Increased Productivity: Automation and standardized processes reduce manual effort and optimize resource utilization.
Greater Agility: DevSecOps enables organizations to respond quickly to changing market demands and security threats.

Watch the Full Webinar:

Key Takeaways

AI-Powered Automation: Learn how AI can automate various aspects of your DevSecOps pipeline, including code reviews, security testing, and deployment.
Enhanced Security: Discover how AI can help identify and mitigate security vulnerabilities early in the development process.
Improved Efficiency: See how AI can streamline your development process and reduce time-to-market.
Enhanced Collaboration: Explore how AI can facilitate better collaboration between development, security, and operations teams.

SpiraPlan and Deploy 360: A Powerful Partnership

In the webinar, we highlighted the integration of Inflectra's SpiraPlan with Deploy 360's software factory. This powerful combination allows teams to manage requirements, track testing, and automate their DevSecOps pipeline all within a unified platform. SpiraPlan's robust requirements management capabilities, coupled with Deploy 360's AI-driven automation, provide a comprehensive solution for building secure, high-quality software.

By embracing DevSecOps principles and leveraging the power of AI, organizations can build secure, high-quality software that meets the demands of today's dynamic environment.

Ready to take your DevSecOps to the next level? Contact us to learn more about how our AI-powered solutions can help you achieve your goals.

Do not miss out on future webinars and updates! Subscribe to our newsletter for company news, product updates, events and more!

DevSecOps Best Practices: Webinar Recap on Fortify and Spira Integration

2024-12-07T10:42:19-05:00

KEY TAKEAWAYS:

Breaking Down Silos: Traditional software development often suffers from a disconnect between development and security teams. By integrating Spira, a comprehensive SDLC management platform, with Fortify, a powerful SAST solution, you can bridge this gap and foster collaboration. This leads to earlier detection of vulnerabilities, faster remediation, and a more secure development process.
The Power of Automation: The webinar showcased how to automate security testing within your CI/CD pipeline using Fortify's source code analyzer. This automation not only saves time and resources but also ensures consistent security checks with every code commit.
Traceability and Visibility: Spira provides a single pane of glass for managing all aspects of your SDLC, including security testing. With its powerful traceability features, you can link security incidents directly to your source code, user stories, and requirements, making it easier to understand the impact and prioritize fixes.
Education is Key: Effective security testing requires a well-informed development team. The webinar highlighted the importance of educating developers on secure coding practices and providing them with the tools and knowledge they need to build secure software from the ground up.

SEE IT IN ACTION:

The webinar featured a live demo of Fortify and Spira working together to identify and manage security vulnerabilities in a real-world application. This demonstration brought the key concepts to life and showed how these tools can help you achieve your security goals. We're excited to share the recording from this informative webinar with you.

READY TO TAKE YOUR SDLC SECURITY TO THE NEXT LEVEL?

Let Inflectra and Merito guide you. Try Fortify and Spira in your own environment by starting your FREE trial today!

Screams & Software: Inflectra Sponsors A Spooktacular Halloween Meetup

2024-11-05T11:40:57-05:00

A Spooky Welcome

The AWS Skills Center was transformed into a den of tech terrors as attendees began to arrive. The atmosphere crackled with anticipation, fueled by spooky snacks (think "bug-infested" cupcakes and "toxic waste" punch) and the promise of terrifying tales. But before the horror stories began, a round of PowerPoint Karaoke kicked off the night, injecting a dose of hilarious chaos. Participants were given slides they'd never seen before and tasked with presenting them with confidence and charisma.

The results were a mix of witty improvisation, confused stammering, and outright laughter, proving that even the most seasoned tech professionals can be thrown off their game by a surprise presentation. The ice was officially broken, and the room was alive with energy and camaraderie, setting the stage for a night of spooky fun and shared learning.

Tales from the Crypt: Software Horror Stories

The heart of the event was the sharing of real-world software horror stories. Attendees recounted their encounters with terrifying bugs, haunting deadlines, and projects that seemed to rise from the dead. These chilling tales served as a reminder of the challenges faced by developers and testers, but thankfully, solutions were offered to help banish these development demons!

Frightful Fashion

Of course, it wouldn't be a Halloween event without costumes! Attendees embraced the spooky spirit, arriving dressed as everything from zombie project managers to vampire testers. Inflectra was thrilled to sponsor the costume contest, awarding prizes for the most creative and terrifying getups.

A Night to Remember

Inflectra is proud to have supported this engaging event. It was a fantastic opportunity to connect with the local tech community, share some laughs (and screams!), and reinforce our commitment to building better, more robust software.

Stay in the loop on all things Inflectra! Subscribe to our newsletter for the latest event updates, product news, and more.

Until next time, beware of bugs in the night. Happy Halloween from #TeamInflectra!

GITEX 2024 Highlights: Inflectra’s AI-Powered Innovation and Conference Takeaways

2025-01-03T14:15:40-05:00

Booth Highlights: AI at the Forefront

Inflectra’s booth in the "All Things AI" pavilion attracted visitors from all over the expo. Led by CEO Adam Sandman, the team showcased SpiraPlan and Rapise—two AI-powered tools designed to streamline development and testing.

SpiraPlan: Inflectra’s complete lifecycle management platform.
Rapise: A codeless automation testing tool for desktop, mobile, and web.

The demos showed how these AI tools boost productivity, allowing users to automate massive amounts of test cases quickly. The AI integration was a huge draw, with companies like Deltek and Telstra International praising Rapise for its speed and test coverage improvements.

Engagement Highlights: AI That Delivers

Inflectra's new AI features were a hit, driving strong interest from hundreds of visitors every day. The Dubai government even requested a three-year quote on-site, and many attendees inquired about long-term partnerships. The AI tools, designed to automate large batches of testing, resonated with companies looking for faster, smarter quality assurance solutions.

The fun part? Inflectra’s booth swag was also a fan favorite. Stickers featuring the "When Devs Cry" were a massive hit, and the “James Bond” pen reflected Inflectra's multi-functional software. With budget cuts limiting giveaways for many companies, Inflectra’s swag, paired with its free software gifts to universities, stood out.

Key Takeaways and Insights

Here are the major learnings from GITEX 2024:

Customizable Dashboards: SpiraPlan’s customizable role-based dashboard, Spira My Page, resonated with attendees looking for streamlined, user-friendly tools.
Customer Confidence: Seeing major brands like Leica Biosystems and Dassault Systems trust Inflectra’s tools boosted confidence among booth visitors.
Pricing for Startups: Transparent pricing, starting at $120 per month for three users, made Inflectra a great fit for startups and small businesses.

In terms of tech trends, AI dominated the event, powering everything from robots to quantum computing. It was clear that AI is revolutionizing industries behind the scenes, and Inflectra’s solutions are perfectly positioned to support this shift with advanced quality assurance and testing capabilities.

Networking and Partnerships

GITEX wasn’t just about showing off AI tools—it was about making meaningful connections. Inflectra met with major cloud providers like Microsoft Azure, AWS, and Google Cloud, each eager to explore partnerships. Inflectra also celebrated becoming an ISV Accelerate Partner with AWS.

Other networking wins included:

Building relationships with Qatar Vodafone and the Qatar Museum.
Connecting with local data centers like G42, Khazna, and others interested in Inflectra’s flexible deployment options.

These conversations laid the groundwork for new projects and partnerships, setting the stage for exciting opportunities ahead.

For those interested in exploring SpiraPlan or Rapise, visit our website for a 30-day free trial, or contact us at Sales@Inflectra.com for more details.

Recap: Unlocking the Power of IEC62304 for Medical Device Software Development

2025-02-05T08:36:40-05:00

Recording Part 1

Recording Part 2

Key Takeaways

Understanding and complying with IEC62304 is crucial for any company developing software for medical devices. This industry standard ensures that your software meets strict safety, quality, and regulatory requirements, making it indispensable for global market approval. The webinars highlighted both the theoretical principles and practical application of IEC62304 to streamline your compliance efforts.

IEC62304 Essentials: We covered the core principles of IEC62304, the international standard for the Software Development Life Cycle (SDLC) of medical devices, highlighting its significance in achieving regulatory approval globally.
Why Compliance Matters: Compliance isn't optional—it's the gateway to selling your medical device software in regulated markets like the U.S. (FDA) and Europe. Understanding this ensures your software meets safety and quality expectations.
Practical Implementation with SpiraPlan: Vladimir demonstrated how to apply IEC62304 in SpiraPlan (part 2), showing how to organize medical device projects, map components, and maintain traceability from requirements to testing.
Live Demo and Expert Guidance: The live demo walked through real-world use cases of SpiraPlan, making the process of IEC62304 compliance manageable.

If you'd like to learn more about this industry standard and its application in SpiraPlan, feel free to contact Vladimir Plotkin at Imarsys for more information.

Learn more about how Inflectra's platforms can help you streamline your compliance.

Strengthening Partnerships and Forging New Connections: Inflectra’s Visit to Mortoff in Budapest

2024-10-11T06:43:47-04:00

Mortoff: A Key Partner in Central-East Europe

Mortoff, headquartered in Budapest, has been a leading professional solution provider in Central-East Europe, excelling in IT development, consultancy, and testing services. Since 2009, they have been a key Inflectra partner, consistently helping us bridge business-IT domains with shared customers across industries like Financial Services, Media, Government, and Defense. Their expertise in development and testing methodologies makes them an ideal partner, and today they stand as a Platinum Inflectra Partner in the region.

A Day of Demos, Presentations, and Future Strategy

Our meeting with Mortoff was particularly significant as it was the first time we were able to connect in person after so many years. This face-to-face interaction was an invaluable moment for both Inflectra and Mortoff to discuss how we could further align our efforts in the region and build on our existing customer base.

During the event, we presented to joint customers and prospects, showcasing Inflectra’s mission and the powerful tool suite we offer. There was palpable excitement as we unveiled some of our latest developments, particularly in artificial intelligence (AI). Our demonstration highlighted how we are incorporating generative AI into Spira and Rapise, offering our customers cutting-edge functionality that will enhance their testing and development capabilities. We also introduced SpiraApps, our extensibility framework, which allows users to tailor Spira to their industry’s specific needs.

Following the customer-focused sessions, the Inflectra and Mortoff teams met privately to discuss strategic plans for the future. We explored opportunities for cross-selling and upselling within our shared customer base, outlined strategies for expanding our presence in the region, and brainstormed co-marketing initiatives that will fuel growth throughout Q4 2024 and beyond.

The event also gave us a clearer understanding of how Mortoff can be better supported as a partner. They shared valuable insights into regional successes with other partners, and we discussed how to better cater our co-marketing efforts to ensure they resonate with the local market. With these insights in hand, we left Budapest feeling more aligned than ever with Mortoff and enthusiastic about the possibilities ahead.

Looking Ahead and Continuing the Momentum

We are incredibly grateful to Mortoff for helping organize such a successful event and to our Inflectra team for their dedication in making this visit a valuable experience. The feedback from customers and the insights from Mortoff will be instrumental as we continue to build on our presence in the region.

For those interested in learning more about Mortoff and how we are working together, please visit our Mortoff Partner Page. Additionally, you can read about our experience at the Automation Star conference in Vienna following this visit, where we continued our journey of innovation and partnership. Check out the Automation Star recap!

Until next time, Budapest!

Team Inflectra

Inflectra at AutomationSTAR 2024: Big Innovations and Fun Vibes!

2024-10-10T09:03:50-04:00

Rapise and SpiraPlan AI: A Game-Changing Inflectra Platform

Both Rapise and SpiraPlan leverage AI to make life easier for testers and project managers. With Rapise ( now in its v8), you can automate tests using natural language commands, letting even non-technical users create test scripts easily. The tool’s AI-generated scripts save time and reduce manual errors, while its real-time error detection spots issues and suggests fixes instantly during test runs.

Meanwhile, SpiraPlan brings a whole new level of intelligence to project management. It provides productivity gains for QA teams, while automated risk detection helps teams mitigate problems early. Additionally, AI-based task prioritization ensures teams focus on the most critical tasks to meet deadlines efficiently.

Together, these tools simplify workflows, improve accuracy, and help teams deliver better results faster.

But it wasn’t all tech talk—oh no, we made sure everyone left our booth with a smile (and some cool goodies)! Our booth was the spot for grabbing some of the best swag at the event.

Beyond the swag, we had so much fun connecting with the community. We’re all about bringing good vibes, so whether people came by for the tech, swag or just for a chat, we were happy to meet so many automation fans. We’re pretty sure some of you stopped by more than once but we won’t name names, (but you know who you are 😉).

Thank You to the AutomationSTAR Team and Our Awesome Attendees!

We couldn’t let this recap end without saying a huge thank you to the AutomationSTAR organizers for hosting such a well-run, engaging event. It’s not easy putting together a conference of this scale, and they made it an amazing experience from start to finish.

A Round of Applause for the Inflectra Team!

We also want to take a moment to recognize the Inflectra team for all the hard work that went into making our presence at AutomationSTAR 2024 such a success. From setting up the booth, running live demos, answering questions, and keeping the energy high throughout the event, the team knocked it out of the park.

Looking Ahead: More Fun, More Innovation

Overall, AutomationSTAR 2024 was a fantastic experience for us. We got to show off Rapise and SpiraPlan AI, share some laughs, and give away plenty of swag. But this is just the start—we’ve got even more awesome things in the works, and we can’t wait to share them with you soon. Stay tuned for what’s coming next!

Stay tuned for what’s coming next!

Team Inflectra

AI-Powered Testing Takes Center Stage: Inflectra's STARWEST Recap

2024-10-10T20:37:16-04:00

From September 23-27, the STARWEST 2024 conference was abuzz with excitement, and Inflectra was right in the middle of it all! Our booth became a hub of energy, drawing visitors with vibrant displays and interactive demonstrations of Spira demos, Rapise.

Inflectra: Leading Talks on AI and Software Testing

CEO of Inflectra, Adam Sandman, delivered two highly anticipated presentations that explored the future of AI in SDLC. These talks were among the most well-attended sessions at STARWEST 2024.

"Multi-Modal GPTs Are Coming for Your Testing! How to Adapt?" - In this talk, Adam explored the impact of multi-modal GPT engines on software testing, explaining how AI is reshaping the role of testers. Attendees learned practical strategies for integrating GPT models into their workflows to improve testing efficiency.
"Software Delivery at the Speed of AI: Inflectra Invests in AI-Powered Quality" - Adam highlighted real-world applications of AI in software development and testing. He demonstrated how Inflectra is integrating AI-powered solutions like SpiraPlan and Rapise into the software development lifecycle, empowering agile teams and improving productivity.

What Made Inflectra's Presence at STARWEST Truly Special?

Generative AI Takes Center Stage: We unveiled the next generation of Generative AI functionality within Spira, showcasing how this cutting-edge technology is revolutionizing software testing.
AWS DevOps Competency Achieved: We proudly announced that Inflectra has achieved the prestigious AWS DevOps Competency, validating our expertise in delivering robust DevOps solutions on the AWS platform.

Networking and Collaboration

The energy at the STARWEST 2024 conference wasn’t limited to the presentations. Our booth was a hive of collaboration and knowledge-sharing, offering attendees a chance to connect with our team and dive deeper into the latest trends in software development, testing and delivery.

We reconnected with our partners from Coveros, Planit, and Checkpoint Technologies, further solidifying our collaborative efforts in advancing software quality.
Attendees shared feedback on our products, helping us continue to improve and adapt to the evolving needs of the tech community.

Inflectra participated in the now-traditional Techwell passport game raffle, and one lucky attendee walked away with a pair of Apple AirPods! Congratulations to our winner, and thank you to everyone who visited our booth.

Post-Conference Adventures

After all the hard work at the booth, the Inflectra team took some time to explore the beauty of Southern California! Team members spread out to enjoy the magic of Disneyland, the livliness of Downtown LA, and the sunny shores of Huntington Beach.

Looking Ahead

STARWEST 2024 was a resounding success for Inflectra. We left Anaheim energized and inspired, with a renewed commitment to providing our customers with the most cutting-edge software testing solutions. Thank you to everyone who stopped by our booth and contributed to such a memorable experience. We cannot wait to see you at future events!

Next up: Inflectra is heading to AutomationSTAR in Vienna, Austria, and GITEX Global in Dubai, UAE. Stay tuned for more exciting updates from Inflectra by subscribing to our newsletter.

QA Metrics for Software Quality & Testing

2024-09-30T09:57:01-04:00

Why are Clear Metrics Important?

“Quality” is difficult to achieve without a clear target. KPIs and benchmarks act as those targets, providing a measurable reference point to track progress. QA metrics create clarity around expectations and outcomes not only for current projects, but future ones as well. With these in place, teams can see where issues pop up, plan resolution and mitigation strategies, and continuously improve processes for upcoming projects.

What to Look for in QA Metrics

When choosing QA metrics, it’s essential to look for ones that are objective, relevant, measurable, and regularly updated:

Objectivity: Avoid measurements that can be manipulated or influenced by interpretation or bias. The goal is to get a clear, straightforward view of your project's health with definitive and irrefutable data.
Relevance: Don't measure something just because you can — each metric should provide actionable data on aspects of the project that matter and align with goals.
Measurability: If you can't measure it, you can't improve it. Selected metrics need to be quantifiable and consistently trackable over time.
Timeliness: Outdated metrics are not useful for what you’re doing today. Choose metrics that are regularly kept up-to-date so you maintain that measurement’s relevance.

Top QA Metrics & KPIs for Software Testing

Now that we've established the importance of quality metrics and what to look for, let's cover specific examples. These KPIs will help you gauge QA effectiveness and flag areas for improvement. Again, choose the metrics that are most useful for your project — this is key to evaluating success and progress:

Defect Resolution Percentage

Tracks the proportion of defects that have been successfully resolved within a specific timeframe. A high percentage means that bugs are being addressed quickly, while a low percentage might indicate bottlenecks or understaffing. This KPI highlights how well your team is managing its bug-fixing workload and helps identify if resources need to be reallocated.

Calculation:

Defect Resolution Percentage = (Defects Resolved / Total Defects Found) * 100

Bug Escape Rate

Refers to the defects that slip through the QA phase and into production. A high number of escaped bugs suggests gaps in test coverage or flaws in the testing methodology. This metric is often a wake-up call for teams, emphasizing the real-world consequences of inadequate testing and QA strategies.

Calculation:

Bug Escape Rate = (Bugs Found After Release / Total Bugs Found) * 100

Cost per Bug Fix

Calculates the financial impact associated with fixing a single bug (including the labor, time, and any other resources for identifying and resolving defects). Monitoring it helps you manage costs and pinpoint which issues take up the most resources, which can justify investments in preventive measures. For example, if this cost is high, it might be more cost-effective to invest in better testing tools or processes to catch bugs earlier in the development cycle.

Calculation:

Cost per Bug Fix = (Total Cost of Bug Fixing / Number of Bugs Fixed)

Bugs Found vs. Bugs Fixed

Simple but important ratio that compares the total number of bugs identified to the number resolved. If more bugs are being found than fixed, it signals an unsustainable trajectory that will slow down the development cycle. On the other hand, a higher fix rate means more efficient issue management.

Calculation:

Bugs Found vs. Fixed Ratio = (Bugs Fixed / Bugs Found)

Defects per Requirement

Measures the average number of defects for each software requirement. A high rate could imply problematic or complex requirements that need more refinement, or miscommunication within the team. This metric helps teams elevate their planning and ensure that requirements are clearly communicated and understood from the start.

Calculation:

Defects per Requirement = (Total Defects Found / Total Number of Requirements)

Defects per Software Change

Every time code is changed, new defects or vulnerabilities can be introduced. This KPI tracks the number of issues that arise from each code modification. A high ratio likely means that more thorough code reviews or improved testing processes for changes are needed. Monitoring it can help identify higher-risk changes and better code review practices, while also helping teams understand the ripple effects of their changes.

Calculation:

Defects per Software Change = (Total Defects Found / Number of Software Changes Made)

Defect Distribution by Severity

Not all bugs are created equal, so categorizing them by severity (critical, high, medium, low, etc.) gives useful insight into how impactful the bugs are. A high percentage of critical or high-severity bugs could be a symptom of fundamental issues in the development process or architecture. Teams should prioritize their efforts based on the severity of the defects so that high-priority issues are resolved first.

Calculation:

Defect Distribution by Severity = ([Severity Level] Defects / Total Defects) * 100

Average Defect Age

The longer a defect goes unresolved, the higher the risk of it impacting project delivery. Average defect age essentially measures how long between an issue being detected and it being fixed. It shows whether your team is able to resolve issues promptly or if there is opportunity to streamline their resolution process. By decreasing the average defect age, teams can improve customer satisfaction and reduce the risk of bugs snowballing over time.

Calculation:

Average Defect Age = ∑ (Date Fixed - Date Detected) / Total Defects

Mean Time to Detect

Before resolution comes detection, and MTTD tracks how quickly this happens after an issue has been introduced into the system. Its primary function is to assess how effective your testing processes are at catching bugs early. A shorter detection time is obviously ideal because it allows teams to respond quickly before the issue escalates. On the other hand, a high MTTD may imply a need for more frequent testing, better monitoring, or more comprehensive test coverage (more on this below).

Calculation:

MTTD = ∑ (Date Detected - Date Introduced) / Total Defects

Tests per Period

Measures the total number of tests executed within a specific timeframe (daily, weekly, per sprint, etc.). While simple, this is important for understanding testing velocity and efficiency. Teams can gauge whether their testing efforts are ramping up or slowing down (if the latter, automation might be necessary), and if they have the necessary coverage to ensure quality.

Calculation:

Tests per Period = (Total Tests Executed / Period of Time)

Test Coverage

Calculates what percentage of the codebase is covered by test cases. Higher coverage means that more of the code is tested, resulting in a lower risk of undetected bugs. However, keep in mind that 100% coverage might not always be possible or worth the resources, so try to strike a healthy middle ground. The amount of test coverage is also not the only factor here, as high coverage with low-quality tests can still lead to low-quality code and buggy software.

Calculation:

Test Coverage = (Lines of Code Executed by Test Cases / Total Lines of Code) * 100

Test Review Efficiency

Checks how well your test cases are reviewed and approved, tracking the number of review cycles needed to approve a test case. A higher rate usually means a more effective initial test design, while lower rates may signal the need for training, clearer standards, or more resources for reviewing.

Calculation:

Test Review Efficiency = (Tests Reviewed / Total Tests Requiring Review) * 100

Test Reliability

Evaluates how consistently test cases provide accurate results. For example, if a test often creates false positives, inconsistent results from the same inputs, or misses issues, it’s unreliable. Tracking failures from these unreliable tests helps your QA process remain trustworthy and dependable, reducing time spent investigating false alarms.

Calculation:

Test Reliability = 1 - (Indeterministic or Inconsistent Tests / Total Tests)

Test Completion Status

The percentage of tests that have actually been executed compared to the planned tests. It helps teams figure out whether they’re on track to complete testing within their timelines or if resource adjustments are needed. For instance, a low completion rate might indicate unrealistic planning, resource constraints, or unforeseen complications in testing.

Calculation:

Test Completion Status = (Test Executed / Total Planned Tests) * 100

Enhanced Testing Pipelines & QA Coverage with Spira

By monitoring the right metrics, you can get ahead of potential issues, improve your processes, and deliver the highest quality products possible — on time and within budget. Tools like SpiraTest and Rapise streamline testing and QA efforts to make your product as resilient as possible and your analysis as easy as possible. They make your developers’ and project managers’ lives easier with custom report dashboards that display important KPIs and trends for each project, using powerful AI and ML capabilities to maximize your test automation value in the background. From self-healing tests and test validation to integrated bug tracking and release management, our platforms provide the ultimate toolset for improving QA processes and effectiveness. Hear what our partners think or try a free 30-day trial for yourself!

AI-Driven Test Automation: Rapise 8.2 Webinar Recap

2024-09-16T12:52:20-04:00

Key Highlights of the Webinar:

AI Automation Demos: See how Rapise utilizes artificial intelligence to streamline testing processes and reduce manual effort.
Shadow DOM Insights: Learn how Rapise tackles complex web elements within Shadow DOM, ensuring comprehensive coverage in your tests.
Data-Driven Testing: Discover how data-driven approaches can increase the flexibility and reliability of your testing processes.

Rapise is designed for teams aiming to stay ahead with the latest AI technologies in testing. Don't miss out on the opportunity to boost your testing efficiency with this powerful tool.

Recording

Ready to transform your testing process? Get hands-on experience with Rapise's AI-driven testing features. Experience the power of AI-assisted test automation firsthand with a free trial of Rapise!

The Future of Testing is AI-assisted

Inflectra is at the forefront of the AI transformation in software testing. With Spira and Rapise, we're empowering teams to not just keep up with the rapid pace of DevOps, but to lead the way. Embrace AI-powered test automation and experience a new level of efficiency, quality, and progress in your software development lifecycle.

How AI is Used in Education Systems

2025-10-30T11:24:13-04:00

How is AI Being Used in the Classroom?

Traditionally, AI’s role in education has been relatively subtle, usually limited to backend programming that helps streamline the teaching and learning experience. Initially, these algorithms found their footing in basic automation processes like sending assignment notifications to students and parents, managing online calendars, and collecting digital submissions of homework. These foundational uses allowed teachers to get back valuable time but weren’t necessarily revolutionary to student engagement.

Growing Role of AI in Education

As AI technologies mature, their impact expands rapidly — when it comes to education, this is particularly driven by advances in machine learning, natural language processing, and data analytics. Intelligent systems now offer real-time insights into student performance, allowing teachers to tailor their approaches to individual learning needs. Predictive analytics can identify at-risk students before they fall behind, while adaptive learning platforms adjust content dynamically to suit each learner’s pace. The trajectory of AI in education points towards a more personalized, data-driven future where teachers, empowered by these tools, can better support diverse learning styles and needs.

Types of AI Software Used by Teachers & Schools

Today’s classrooms feature various implementations of AI software to enhance different aspects of the teaching and learning process. From streamlining administrative tasks to reshaping instructional methods, AI tools are becoming more commonplace in the classroom (from grade school to higher education):

Automated Grading

Automated grading systems were one of the earliest and most impactful uses of AI in education. Beginning with multiple-choice tests and expanding to essays and mathematical problem-solving, AI-driven grading tools can understand a wide range of assessments, freeing up teachers from the often time-consuming and repetitive task of manual grading. Automating this not only speeds up the evaluation process but also facilitates consistency, helping teachers maintain fairness in their assessments.

For written assignments, Natural Language Processing (NLP) algorithms analyze syntax, grammar, coherence, and even the nuances of argumentation. When it comes to math and science, AI grading systems go beyond just marking if an answer is correct or not. They can analyze problem-solving approaches, identify common misconceptions, and even recognize creative solutions that might diverge from standard methods.

However, the impact of automated grading goes beyond time-saving. These systems can process vast amounts of data to identify trends in student performance, helping educators surface areas where additional instruction may be needed.

Note: These systems are not without limitations — the nuances of creative writing and the complexities of scientific analysis and reasoning can elude even the most sophisticated AI. Because of this, many teachers use them in conjunction with human oversight and feedback, creating a hybrid approach that combines the strengths of both sides.

Intelligent/Personalized Tutoring

Personalized AI tutoring addresses one of the most persistent challenges in education — meeting students where they are. These systems use data from a variety of sources (test scores, learning styles, and even behavioral cues) to create customized learning pathways for each student. Intelligent tutoring software adapts in real time, employing complex algorithms that analyze a student's learning patterns, strengths, weaknesses, and pace. By continuously assessing student responses and behaviors, they can adjust the difficulty level, presentation style, and even the type of content to optimize learning outcomes.

For example, if a student consistently struggles with certain mathematical problems, the tutor might break the concept down into smaller, more digestible parts. Alternatively, it might present the information using different methods (visual representations, interactive simulations, etc.) until the student demonstrates mastery. AI tutors also never tire, offering unlimited patience and availability for students who need it.

Enhanced Curriculum Planning

Developing and adjusting curriculum plans is a labor-intensive process that requires careful consideration of standards, student needs, and educational goals. AI tools for curriculum planning can analyze huge amounts of educational content, align it with desired outcomes or parameters, and suggest optimal teaching sequences.

AI-driven curriculum tools might identify gaps in existing plans, recommend new topics based on emerging fields, and even predict future skill requirements based on industry trends. They can also update plans dynamically based on student progress and feedback, allowing for more responsive and flexible teaching strategies. For educators, this means less time spent on administrative planning and more time devoted to direct student interaction.

Improved Data Management

AI’s educational value isn’t limited to just the classroom. School administrators have been using advanced tools to improve the operation of their educational institutions as well. Automated data management systems can help with everything from attendance tracking to the analysis of student performance metrics. They reduce the manual effort required for record-keeping and reporting, allowing educators to focus more on instructional duties.

For school administrators, AI data management tools offer a bird's-eye view of institutional performance. These systems can analyze trends in enrollment, resource allocation, and academic performance across multiple parameters. By processing this data, AI can predict future enrollment numbers, optimize resource distribution, and even suggest curriculum adjustments based on long-term performance trends.

Real-Time Translation

In increasingly diverse classrooms, language barriers can pose significant challenges. Real-time translation tools driven by AI make lessons more accessible to ESL (English as a Second Language) students. They help foster an inclusive environment where all students can participate fully, reducing the sense of isolation that language barriers can create.

Beyond translation, some advanced systems also adapt teaching content to the cultural context of students, further enhancing engagement and understanding. Once again, the implications extend beyond the classroom. Parent-teacher conferences, school announcements, and extracurricular activities all become more accessible to non-native-speaking families.

Automated Feedback

While automated grading systems focus on evaluation, automated feedback systems take this a step further by providing detailed, constructive input to guide student improvement. These AI-driven tools offer nuanced, context-aware suggestions beyond simple error correction. Whether it's suggesting ways to refine an essay, offering hints on complex problems, or guiding students through a coding challenge, automated feedback systems support continuous learning and development.

In writing assignments, for instance, automated feedback systems can analyze not just grammar and syntax, but also structure, argumentation, and stylistic elements. They might suggest ways to strengthen a thesis statement, point out areas where evidence is lacking, or offer tips on improving narrative flow.

It's important to note that while these systems are incredibly sophisticated, they're designed to complement, not replace, human teachers. The most effective implementations use AI-generated feedback as a starting point for deeper discussions between educators and students, creating a collaborative environment for effective learning.

Developing EdTech Software? Enhance Testing & QA with Inflectra

As we've explored, the ways that AI is revolutionizing education means that the role of software developers behind this transformation is more crucial than ever. The increasing complexity and sophistication of AI-driven educational tools demand equally advanced testing and quality assurance processes — not just for functionality, but for bias, ethical considerations, and the ability to handle a wide array of unpredictable inputs.

This is where platforms like Inflectra come into play, offering industry-leading solutions for managing the software development lifecycle in the education industry, from initial development through to deployment. By using these tools, developers can automate repetitive testing tasks, identify defects earlier in the development process, and ensure that their software meets the evolving needs of educators and students. In a world where technology evolves rapidly, keeping pace with advancements in AI is critical — and Inflectra is here to help developers rise to the challenge

Get started with a free 30-day trial today, or read more about our partners who trust our platforms to build their own.

Inflectra in the News - August 2024 News Roundup

2025-04-01T22:21:31-04:00

Podcasts

Discover the Roles and Responsibilities of a Successful CEO with the Top Floor - August 14, 2024

Inflectra's CEO, Adam Sandman, was featured in a Top Floor Interview hosted by Krista Crawford. He discussed Inflectra's entrepreneurial journey, the challenges of software management, and his transition to leadership. Listen in for valuable insights from a software industry leader on leadership, innovation, and the importance of effective software management. Listen here.

How Adam Sandman Bootstrapped a Software Company to Compete with Industry Giants with Next Gen Calls - August 29, 2024

In this podcast, Sandman shared his remarkable journey, from coding in rainy Wales as a 10-year-old to leading a global software company. His passion for technology led him to a Director role at Sapient Government Services, but he recognized a need for affordable test management solutions. This inspired him to launch Inflectra in 2006, filling the gap in the market.

Pepe's Bar with Adam Sandman | Episode #25 with Agile Testing Days - Sep 3, 2024

Adam Sandman was interviewed on Pepe's Bar podcast. In the interview, Sandman discusses his journey from a childhood love of computers in Wales to his current role as a CEO in the US. He emphasizes the importance of making a difference in the world through technology, highlighting his belief in the potential of business to be a force for good. Sandman also shares his personal experiences and insights on topics such as travel, family, and the meaning of money. Watch here.

Presentations

Exciting Business Leaders on The Value of QA at Testing Talks Conference in Sydney, Australia - August 15, 2024

Adam Sandman's talk at Testing Talks Conference addressed the challenge of prioritizing software quality investments during budget constraints. He focused on identifying meaningful metrics that justify investments and strategies to demonstrate ROI for executive buy-in, especially in an era where many businesses rely heavily on software despite not being software companies themselves. Finally, he touched on how to strategically leverage AI without it being perceived as just another trend. See the slide deck here.

Courageous Innovation: Reimagining Leadership and Management In A World of Chaos at the Northeastern Global Symposium - August 22, 2024

Adam Sandman's keynote talk at the 2024 Global Symposium challenged traditional leadership approaches, urging leaders to embrace innovation and navigate disruptions. He highlighted the importance of understanding global shifts and adapting to a world in constant flux. Sandman concluded by emphasizing courageous leadership, discerning when to embrace change and how to make a meaningful impact in today's chaotic world. Watch here.

Keep Up to Date

Do not miss out on our monthly newsletter! Sign up to get the latest news, important updates, and valuable insights sent directly to your email.

Top Ten Tips on Using Spira for the First Time

2024-08-31T14:27:39-04:00

Top Ten Tips for Using Spira

We share the updates in both the user manual and roadmap but some tweaks are too small to mention via The Edge yet have significant impact to our users. Here are 10 tips to check if you know:

Spira has a built-in Keyboard Shortcuts menu to help you drive speed? i.e. log a defect simply using "n i n"
Did you know there are hundreds of templates to help you reuse from 18 years of accumulated knowledge from users? E.g. Use a template tailored for your industry with predefined workflows to jump start usage of Spira or and even migrate data with ease.
Did you know you can now reuse entire or partial product artifacts and data sets (from 8.2 release onwards). You can set up a library of tests mandated for all products with ability to customise a set on top by using an artifact.
You can automate manual testing by plugging in any Test Automation tool from Selenium to even our own Rapise which houses templates of tests for most commonly used ERP systems.
SpiraApps - allows you to plug-in ChatGPT to bundle requirements with prompts of a test case coverage.
SpiraApps - allows you to add Test and Tasks Presets . for example, one click for 8 preset development tasks against a requirement, or generate a handful of approval tasks for another requirement.
Drive down bugs faster by allocating incident tasks to resources who have capacity.
Communicate effectively with real-time collaboration (in system chat, email, RSS, custom action based dashboard, kanban, mind maps, lists and folder structures as well as attach any file format), so there is no need for meetings after meetings to debate planning, requirements. tasks allocation or test pass or failures.
You can customize out of the box reports - simply go to our Knowledge Base and cut and paste scripts or edit your own by going to Admin/Reports/Edit
Bulk add/edit users, followers, associations with one click saving you time.

We even have partners building out other shortcuts. See how partner mVerve made quick links so you can easily access your most important internal reports, wikis, or any external resources without the hassle of navigating through multiple pages. And how partner Tietoevry with customer Saab are speeding up Jira Migration to Spira.

We will endeavor to share more. And always, we welcome your feedback to make Spira more powerful for you!

Inflectra’s 18-Year Journey of Quality Highlighted at Testing Talks Sydney 2024

2024-08-19T16:45:33-04:00

Demonstrating Innovation in a Crowded Market

Inflectra used its platform at Testing Talks Sydney to showcase our latest innovations. Central to our current offering is Spira, a test management and SDLM Platform, and Rapise, an automation platform. Both products have been enhanced with GenAI capabilities, which were the focal point of the conversations in recent in-person events sponsored by Inflectra globally. These advancements are indicative of Inflectra’s efforts to integrate artificial intelligence into its suite of tools, further reinforcing our reputation for thought leadership.

Customers and conference guests were excited about the new features, underscoring our continued relevance in the market. Inflectra’s presence at the event highlighted out ability to remain competitive while adapting to the evolving needs of modern enterprises.

The Economics of Quality Assurance

Inflectra’s Chief Executive, Adam Sandman, took the stage at Testing Talks to address a perennial challenge for those in the quality assurance industry: proving its value to the bottom line. His talk, "Excite Your Business Leaders on the Value of QA," focused on the economic rationale behind investing in quality engineering, even during periods of fiscal constraint.

In an era where a single software failure can reverberate across entire economies, Adam's message was clear: QA is an economic imperative. His analysis highlighted the importance of measurable ROI and the necessity of articulating the business case for sustained investment in quality processes.

Eighteen Years of Steady Growth

Inflectra's trajectory over the past 18 years offers a case study for success based on a sustained focus on a singular objective: quality. Our key partners in APAC who joined us at the 18th Anniversary Celebration, including TTC Global, Planit, DevOps1, and NFT, confirmed that close collaborations and investment in partner ecosystem development in the region have been integral to the company's steady expansion.

This sentiment was echoed throughout the evening: Inflectra’s success is underpinned by enduring partnerships and an unwavering commitment to its core mission. In a crowded market, Inflectra has carved out a niche by focusing on robust, scalable solutions that meet the needs of enterprise clients.

Reflecting on the Past, Looking to the Future

Inflectra’s 18th anniversary was a celebration of the longevity and robustness of our philosophy of quality engineering and a testament to our disciplined execution of a clear, long-term strategy to promote it globally. Our consistent focus on quality as a competitive differentiator has enabled Inflectra to build strong relationships with partners and customers alike. Our journey over the past 18 years has not been defined by rapid, flashy expansion or headline-grabbing acquisitions. Rather, it has been a slow and steady progression, marked by our prudent investment in product development and an unwavering commitment to the founding principles of serving our customer's needs above all.

Our company’s future, much like its past, will be defined by our ability to adapt to changing market conditions while maintaining a focus on quality and innovation. We remain a company committed to quality in principle and practice, a stance that has positioned us well to weather the uncertainties of the ever-evolving technology landscape.

We are looking forward to seeing you all again at Testing Talks in Sydney in 2025.

AWS CodeCommit Deprecated - Easy Migration to TaraVault Git

2024-08-02T16:10:32-04:00

What was AWS CodeCommit?

AWS CodeCommit was a fully managed source control service that made it easy for teams to host secure and scalable Git repositories in AWS. AWS CodeCommit had the following features:

Managed Service: AWS CodeCommit eliminated the need to operate your own source control system or worry about scaling its infrastructure.
Secure: CodeCommit repositories were encrypted at rest and in transit. You could also control who can access each repository using AWS Identity and Access Management (IAM).
Integrated with AWS Services: CodeCommit integrated with other AWS services like AWS Lambda, AWS CodeBuild, AWS CodePipeline, and Amazon CloudWatch for a complete CI/CD workflow.
High Availability: The service was designed for high availability and durability.
Standard Git Commands: You could use the standard Git commands you are familiar with.

AWS CodeCommit was used by developers working heaving in the AWS environment, but never caught on in the wider DevOps community.

What is the Recent News?

AWS announced on July 25th that they were deprecating a set of lesser-used services, including CodeCommit:

After careful consideration, we have made the decision to close new customer access to AWS CodeCommit, effective July 25, 2024. AWS CodeCommit existing customers can continue to use the service as normal. AWS continues to invest in security, availability, and performance improvements for AWS CodeCommit, but we do not plan to introduce new features.

As part of the announcement, AWS provided guidance on how to migrate an AWS CodeCommit Git repository to another provider:

Customers can migrate their AWS CodeCommit Git repositories to other Git providers using several methods, such as cloning the repository, mirroring, or migrating specific branches. This blog describes a basic use case to mirror a repository to a generic provider, and links to instructions for mirroring to more specific providers. Your exact steps could vary depending on the type or complexity of your repository, and the decisions made on what and how you want to migrate. This post only describes how to migrate Git repository data, and does not describe exporting other data from CodeCommit such as pull requests.

What is TaraVault?

TaraVault is a source code management platform developed by Inflectra, which is designed to integrate seamlessly with their Spira development suite. It supports both Git and Subversion repositories, allowing teams to manage their source code within the same system they use for project management and application lifecycle management (ALM).

Key Features of TaraVault:

Integration with Spira: TaraVault is tightly integrated with SpiraTest, SpiraTeam, and SpiraPlan, Inflectra’s ALM tools. This integration provides code-level traceability, enabling users to link code commits with requirements, tasks, and issues in Spira.
Supports Multiple SCM Systems: Unlike AWS CodeCommit, which only supports Git, TaraVault supports both Git and Subversion, giving teams flexibility in their version control strategy.
Secure and Hosted: TaraVault offers a secure, cloud-hosted environment for managing source code, similar to CodeCommit, which removes the need for teams to manage their own source control infrastructure.
Free for Spira Customers: TaraVault is provided as a free service to customers who are already using Spira, making it a cost-effective option for teams that are already invested in the Inflectra ecosystem.

Why Choose TaraVault Over AWS CodeCommit?

Tight Integration with ALM: If your team is using Spira for project management and ALM, TaraVault’s integration offers a streamlined experience with features like traceability between code commits and project artifacts, which is not natively available in AWS CodeCommit.
Support for Subversion: If your team relies on Subversion or has a mixed environment with both Git and Subversion, TaraVault’s multi-SCM support could be a key differentiator.
Cost Considerations: For teams already using Inflectra's tools, TaraVault being free could be a more cost-effective choice compared to the usage-based pricing of AWS CodeCommit.

How to Migrate to TaraVault?

If you are interested in migrating from AWS CodeCommit to TaraVault, we have some handy instructions for you here: KB198 - How do I upload my existing Git repository?

Integrating Other AWS Code Products

AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. It's part of the Amazon Web Services (AWS), cloud computing platform.

AWS CodePipeline and AWS CodeBuild are both parts of Amazon Web Services' suite of developer tools, but they serve different purposes within the realm of continuous integration and continuous delivery (CI/CD).

SpiraTeam and TaraVault integrate seamlessly with the AWS Code tools in a variety of ways. You can easily configure your AWS CodeBuild projects to fetch code from a TaraVault Git repository, and report back against a SpiraTeam release by creating a new build each time they run. This lets you see the health of your CI/CD process within SpiraTeam. You can learn more about this integration in our whitepaper: DevOps Using SpiraTeam, TaraVault and AWS CodeBuild.

Inflectra in the News - July 2024 News Roundup

2025-04-01T21:47:55-04:00

Podcast

Risk-Based Quality Engineering & Traceability with Curiosity Software - July 11, 2024

Adam Sandman joined Rich Jordan and Huw Price for a discussion on the ongoing evolution of quality engineering. Sandman emphasized the importance of robust software development practices and thorough testing for effective cybersecurity, highlighting Inflectra's role in providing affordable quality assurance solutions. The conversation also touched on the significance of traceability and compliance in verifying security measures and demonstrating adherence to regulations. Listen here.

Publications

Transitioning to Renewable Energy: Software & Infrastructure Challenges of Adoption with FromDev - May 30, 2024

Shifting to renewable energy is a smart business move, guaranteeing long-term energy stability and protecting our planet. Although it's a big change, careful planning, risk management, and quality testing make it achievable. By tackling challenges head-on, businesses can successfully transition to a greener future. This dedication to excellence will be key to making this energy revolution a success. Read more.

Common UAT Mistakes Design Teams Make And How To Avoid Them with Forbes Technology Council - July 9, 2024

Sandman's expertise on common UAT mistakes was featured in a Forbes Technology Council article. He emphasized that User Acceptance Testing (UAT) should focus on validating whether a product meets business needs and user expectations rather than merely checking functionality. A common mistake design teams make is using UAT for functionality testing instead of gathering valuable insights from real users who were not involved in the design process. Sandman stressed that UAT is critical for ensuring a product is fit for its intended purpose. Read more.

The Crucial Role of Software Quality Assurance in Healthcare with Technical is Technical - July 31, 2024

Software quality assurance (SQA) is vital in healthcare, where technology plays a crucial role. By focusing on SQA, healthcare organizations can protect patient safety, ensure they follow regulations, safeguard sensitive data, and operate at their best. As healthcare relies more on technology, SQA will become even more important for creating top-notch, reliable, and innovative solutions.

Keep Up to Date

Do not miss out on our monthly newsletter! Sign up to get the latest news, important updates, and valuable insights sent directly to your email.

Spira v.8: New Features Unveiled in Latest Webinar

2024-07-24T00:42:18-04:00

Webinar Recording

Key Highlights

Risk Management in SpiraTeam: Proactively identify and mitigate risks.
Expanded App Marketplace: Discover new customization and integration possibilities.
Streamlined BDD Integration: Simplify feature file creation and export.
Cross-Project Test Sets: Enable comprehensive end-to-end testing.
Improved Admin Experience: Streamlined user and product management.
Enhanced Auditability: Detailed audit trails for administration changes.

Spira v.8 marks a significant step forward in providing robust quality management solutions to our customers. The new features and enhancements are designed to empower teams to tackle complex projects with confidence, streamline workflows, and maintain comprehensive audit trails. For detailed questions or support, contact us at support@inflectra.com.

Start your FREE 30-day trial of Spira v.8 today and experience the future of software development and quality management.

Benefits of Kanban: Advantages & Core Practices Explained

2024-07-31T09:55:55-04:00

Benefits of Kanban: Why Use It?

Although kanban systems emerged from the automotive space, it’s equally important in software product development and management. There are a variety of advantages it provides that have led to its popularity in this space, such as:

Planning Flexibility
Shortened Time Cycles
Fewer Bottlenecks
Increased Visibility of Flow
Continuous Delivery
Improved Predictability
Better Dependencies Management
Increased Customer Satisfaction

1. Planning Flexibility

For many companies, striving for business agility is driven by the need for flexibility. With no prescribed phase durations (unlike other Agile methodologies, such as Scrum), features are released as soon as they are completed. Kanban, therefore, supports the “release on demand” considerations — even in scaled agile implementations. By using a kanban roadmap rather than relying on a rigid general project plan, product managers are free to reassess immediate priorities based on changes in the market. Kanban methodology suggests an approach to backlog management that helps teams become more self-managing while bringing transparency and consistency to the decision-making process.

2. Shortened Time Cycles

Reducing WIP with limits in each column/swimlane helps team members finish what they’re doing before moving on to new things and sends a message to the customer and other stakeholders that there is limited capacity. In practice, this method was found to reduce cycle times, or the time taken to complete a task on average, improving timeline efficiencies.

3. Fewer Bottlenecks

Kanban paved the foundation for how value can be maximized in a process by limiting project scope to fit a schedule. By controlling the flow for specific process steps that have high contention for resources (such as software integration testing), kanban avoids bottlenecks at key processes in the software development lifecycle.

4. Increased Visibility (of Flow)

The “visualize flow of work” concept of kanban focuses on transparency in the process by which work items will be formally recognized. The use of a backlog with full transparency of work item flow coincided with the “definition of ready” and “definition of done” to pick an item to enter or exit the workflow queue. Kanban helps facilitate a clear definition of the queue itself because of this, increasing the visibility of flow in the entire software development lifecycle.

5. Continuous Delivery

The goal of continuous delivery is to rapidly, reliably, and repeatedly deliver new features and bug fixes at low risk and with minimal overhead. The goal of kanban is to optimize the flow of work through incremental change. Both approaches share the common objective of delivering value to the customer faster. Kanban and continuous delivery also complement each other with their shared objective of process improvement. Continuous delivery, which can be delayed by manual effort and human error, often uses automation to make processes more efficient.

6. Improved Predictability

According to Little’s Law, the number of customers stationary in the system (WIP) is the product of the long-term effective arrival rate (throughput) and the time the customer spends in the system (lead time). Implementing WIP limits and ensuring the Little’s Law assumptions are met keeps your process operating as a stable system. A stable system is a predictable system and one that enables you to make data-driven decisions. Most importantly, kanban doesn’t require you to revamp your process to begin seeing these benefits. It works by implementing incremental, evolutionary changes to make your workflow more efficient and your team more productive.

7. Better Dependencies Management

In any software project, there are dependencies on work items. Kanban offered support in these areas by looking at impediments to flow! Whether it is an overworked process, undocumented procedure, untrained people, or a poorly calibrated system, kanban uses the combination of managing the flow and continuous learning to relentlessly avoid anything that contributes to any type of waste.

8. Increased Customer Satisfaction

Kanban cycle time is calculating the actual work-in-progress time. It tracks how long a task stays in the different process stages. Keeping track of your cycle times enables you to measure your team’s performance. Low cycle times mean that your team is efficient. High cycle times indicate stalls, bottlenecks, and backlogs. Keeping cycle times down keeps lead time down and customer satisfaction high. Because of this, a side benefit of the reduced cycle times is improved overall customer satisfaction.

Kanban Practices & Principles

In essence, kanban is a scheduling system for lean and other Just-in-Time (JIT) processes, allowing organizations to start with their existing workflow and drive evolutionary change.

The core philosophy behind kanban advocates transparency of the work that is in process. “This lean philosophy is the foundation for the kanban principles behind the essential kanban practices of maintaining flow, eliminating waste, and improving continuous learning,” says our Agile Evangelist, Dr. Sriram Rajagopalan. Here are the guiding practices of kanban systems:

Visualize the flow of work
Limit Work in Progress
Manage Flow
Make Process Policies Explicit
Implement Feedback Loops
Improve Collaboratively, Evolve Experimentally

1. Visualize the flow of work

We’ve all heard the saying, “A picture is worth a thousand words.” Similarly, the visualization of work and the workflow allows individuals and teams to observe risks or hurdles across the project, which may manifest as blockers, queues, impediments, or bottlenecks. Visualizing the flow of work (the number of cards in each lane) in the workflows (the stages in the swimlane) as indicated in the diagram below, allows everyone in the project delivery team and product organization to preemptively address risks to ensure “flow.”

2. Limit Work in Progress (WIP)

Although many think multitasking is essential, the concept of leaving one task incomplete to pick another task introduces the possibility of no work being completed in the end. Additional time is also spent on context switching and understanding where the earlier tasks were left. Lean highlights that balancing multiple tasks simultaneously causes less productivity due to the waiting times introduced and recommends limiting the work in progress to gain focused attention on the work at hand.

Frequently, when too much WIP exists, there is a larger overhead to lengthy queues. Sometimes, people think of these WIP limits as a visual checklist. On the other hand, kanban is not a to-do list but puts limits on the work in process to avoid waiting times and resource bottlenecks. In the diagram above, you can see a WIP limit applied on the “In Progress” column that visually indicates exceeding capacity. The focus, therefore, shifts from managing many things and finishing fewer things to focusing on a few things and completing them fully.

3. Manage Flow

Once the work is visualized on what delivers value and WIP limits are set to reduce the adverse effects of task switching, the team can focus on optimizing flow. All the items in the kanban board are part of the systems thinking approach to move unprocessed items on the left to completed items on the right. The goal here is to observe where work gets stuck and get them unstuck. For example, this could be the result of a lack of training on the processes and tools or limited collaboration among team members. These learnings come from daily meetings, lessons learned, retrospective sessions, or review sessions.

4. Make Process Policies Explicit

As the organization identifies opportunities to improve the system, this knowledge is written into the Kanban framework itself. Doing so allows us to capture and preserve organizational learning by building it into the system we use to manage our work — the kanban board. There are many ways to modify a Kanban board to make process policies explicit. One is to redesign the board to specify how the workflows. Another is to use WIP limits to explicitly state our policy about how much WIP we are able to take on.

5. Implement Feedback Loops

While managing the flow, lessons are learned. Kanban emphasizes how work flows through the value stream so teams can continuously improve — this ongoing improvement is the basis of Kaizen. You can think of these improvements in terms of lagging indicators like the number of risks impacting flow, WIP limits, and lead time. Because of this, retrospective discussions may focus on the number of cards blocked, the total number of blocked days, the number of cards completed per week, and the various areas that block cards.

6. Improve Collaboratively, Evolve Experimentally

Kanban also promotes qualitative learning, such as the exploratory and experimental approaches to innovations attempted. These innovations may be radical and are called Kaikaku. For example, this new knowledge gained from radical innovations may lead to the development of a new product or promote a better understanding of the processes for faster implementation of feedback loops. It could also aid the cross-functional team knowledge for capacity, transition, and succession planning to foster team cohesion to collaborate on business value.

Take Advantage of the Benefits of Kanban

If you’re ready to maximize the benefits and value you get from kanban development, SpiraTeam and Rapise can help you. They offer powerful capabilities to visualize, manage, and automate your projects, increasing efficiency, reducing bugs and issues, and organizing everything you need in one place. Get started with a free 30-day trial by clicking here!

From Testing to Tracking: How SpiraTeam and LambdaTest Revolutionize QA

2024-07-09T10:14:02-04:00

Our Pre-Sales Solutions Engineer Dermot Canniffe and LambdaTest's Saksham Garg provided valuable insights on streamlining issue tracking. The session showcased the transformative impact of integrating our SpiraTeam platform with LambdaTest's powerful testing capabilities, revolutionizing QA workflows. Dermot demonstrated how SpiraTeam seamlessly manages the entire software development lifecycle—from planning and development to testing and delivery—ensuring complete organization and traceability. Saksham highlighted LambdaTest's extensive manual and automated testing capabilities across a vast array of devices, browsers, and operating systems, guaranteeing flawless software performance for all users.

Recording

Key Integration Takeaways

By integrating testing and issue tracking, your team can work faster and smarter, ultimately delivering higher-quality software with:

Seamless Bug Logging: Easily report bugs from LambdaTest directly into SpiraTeam for real-time visibility and collaboration.
Rich Context: SpiraTeam automatically captures essential test details from LambdaTest, helping developers reproduce and fix issues faster.
Streamlined Workflow: The integration keeps testers and developers in sync, eliminating manual steps and accelerating resolution.

Elevate your software development with SpiraTeam - book a personalized demo and start your free 30-day trial today!

Level Up Your Skills

Ready to elevate your software development expertise? Explore InflectraCON360, your digital hub for year-round access to thought leadership, tech knowledge, and networking opportunities.

You can also subscribe to our monthly newsletter and be the first to know about Inflectra's newest developments, industry insights, and upcoming events.

GITEX Africa 2024 - Powering Africa into the Global AI Economy with Inflectra

2024-06-22T12:09:04-04:00

Inflectra's Strategic Focus at GITEX Africa

Inflectra, a leading provider of end-to-end software lifecycle management solutions, made a significant impact at GITEX Africa 2024. The company showcased its commitment to innovation and customer-centricity by Demonstrating our advanced AI-powered tools - Spira and Rapise. Inflectra highlighted its AI-powered solutions for test automation, requirements management, and software quality assurance, helping businesses accelerate development cycles and deliver superior products.

Inflectra in The Region

At Inflectra, we have a proud history of working in the region. Many of our customers are based in Africa, including companies in Morocco, Nigeria, Kenya, Rwanda, Mozambique, Madagascar, Namibia, Mauritius, Egypt, and South Africa. We have worked for many years with our trusted partner - Tezza Business Solutions - to assist major financial services institutions, telecommunications companies, Government agencies and local startups in improving their quality engineering practices. As part of the Inflectra Global Technology Initiative, we have also worked with local universities to promote technical education and career opportunities.

Unleash the power of AI-powered test automation and comprehensive test management. Try SpiraTest and Rapise free for 30 days and streamline your software development!

Inflectra at GITEX Africa

The team was excited to attend the event and meet local entrepreneurs, potential partners, and also key decision-makers in large companies that were interested in adopting modern platforms for developing and deploying mission-critical systems across the region. Some of the key takeaways for the team were:

Data Sovereignty: Most of the African companies we spoke to were very keen to emphasize that they were required to ensure that all data on citizens in their country was not just adequately protected but was stored within the geographical borders of their country. At Inflectra, we have made a long-term commitment to providing both public cloud and on-premise / private cloud options for all companies. In many cases this was the first question, and unless we could guarantee this, there was no point for further discussion. This further reinforced our belief that allowing customers to have a choice in their deployment strategy makes more sense than ever before.
Payment Plans: One thing that was also emphasized is that international payments from local companies to multi-national software companies can be difficult. The issue was not that companies could not afford world-class software, simply that the cash flow and exchange rate regimen meant that companies like Inflectra needed to consider an option for installment payments in addition to annual contracts or monthly credit card billing. As a result of these insights, we are pleased to announce that we now offer installment payment plans for customers in key emerging markets such as Africa and South America.
Incredible Talent: We were blown away by the number and quality of students, engineers, and technical workers who were looking to broaden their skill sets and get work experience and internships. There is clearly an untapped market for talent that is waiting for a large international software development company to leverage.
Global Marketplace: The last surprise was how global the world has become in terms of key enabling technologies such as AI, Cloud Computing, Blockchain, Big Data, FinTech, Mobile Payments, and Telecommunications. In Europe and North America, you get a limited view of this, but in Africa, all of the world's players were here—Huawei and Ali Baba from China, Oracle, Microsoft, PwC, Deloitte, Visa from the USA, Orange from Europe, and Dubai Internet City from the UAE.

Tired of buggy software and slow testing cycles? Discover how SpiraTest and Rapise can revolutionize your QA process. Get your free trial now.

Inflectra's Vision for the Future

Inflectra's participation at GITEX Africa 2024 underscores its dedication to empowering businesses with intelligent software solutions. The company is committed to:

Pioneering AI innovation: Inflectra continues to invest in research and development to push the boundaries of AI and its applications in software development.
Expanding its global reach: Inflectra is actively building strategic partnerships and expanding its presence in emerging markets like Africa.

Become an Inflectra Partner

Join Inflectra's growing ecosystem of partners and help empower businesses in Africa with innovative software solutions. Consulting and implementation service providers, resellers, and technology partners are welcome.

Explore partnering with inflectra today!

GITEX Africa 2024

GITEX Africa is an extension of the renowned GITEX Global Technology trade show, originally based in Dubai. As one of the largest tech events in the world, GITEX (Gulf Information Technology Exhibition) has been pivotal in showcasing cutting-edge technologies, fostering innovation, and providing a platform for networking among tech professionals globally. Inflectra was excited to attend the second GITEX Africa event this year, increasing our exposure to one of the fastest growing regions for technology startups and a future innovation powerhouse for the region as a whole..

Why Africa, Why Now?

For the longest time, outside of a few key countries, Africa has generally not been seen as an important region for technology and innovation. Traditionally organizations have seen the continent solely as a place to extract natural resources and conduct tourism. Now, with the emergence of remote work and the ability to be a 'digital nomad,' talent has gone global. Simultaneously, investment in technology and business has also become global, with companies from Europe and North America competing for talent and capital, with equally capable companies coming from China and the Middle East.

Africa, with its young, skilled population, is in a perfect position to be the next growth market for technology companies. Universities in the region have created a huge talent pool for motivated, skilled software developers, data scientists, entrepreneurs, and AI engineers. At the same time, Governments are looking to diversify away from primary industries towards knowledge-based economies, resulting in exciting opportunities for both local and multinational companies to have a first-mover advantage in the region.

Key Takeaways from GITEX Africa 2024

The event reinforced several key trends:

AI is revolutionizing software development: AI-powered tools are becoming indispensable for streamlining processes, improving accuracy, and driving innovation.
Cloud adoption is accelerating: Cloud technologies offer unmatched scalability, flexibility, and cost-efficiency, making them a critical component of modern IT strategies.
Customer experience is paramount: Businesses are prioritizing solutions that enhance customer satisfaction and engagement across all touchpoints.
Data-driven insights are key to success: Leveraging data to gain actionable insights is essential for making informed decisions and staying competitive.

Ready to elevate your software testing? Start your free 30-day trial of SpiraTest or Rapise today and experience the future of quality assurance!

See you all at GITEX in Duban, UAE in October 2024!

Inflectra Partner Face-Time: London and Stockholm Key Partner Visits | June 2024

2025-03-04T09:20:25-05:00

Why Partner Visits Matter To Inflectra

There's something irreplaceable about meeting in person. It's not just about shaking hands; it's about capturing the regional pulse and refining our strategies to serve our customers better. Here's why we think these visits are crucial:

They help us identify specific needs and challenges in regulated industries, guiding product enhancements.
We gain valuable insights into local market trends and regulatory landscapes, ensuring our strategies are aligned with regional demands.
These meetings strengthen our collaborations, paving the way for co-developing solutions that seamlessly integrate into existing workflows and provide greater value to our joint customers.

London Highlights

Inmarsys: Safety-Critical Software Pioneers
We kicked off in London with a breakfast meeting at Bondi Green with our longtime partner, Inmarsys. With two decades of experience in the Medical, Aerospace, and Automotive sectors, Inmarsys is at the forefront of safety-critical software development. Our conversation explored the latest medical and aviation tech, emphasizing how Inflectra's risk management and reporting features can supercharge their projects.

Jide Modele: Market Innovator
Next, we caught up with Jide Modele, the former Partner & Managing Director of Tezza Business Solutions, a partner operating in Kenya, Nigeria, Tanzania, and Uganda. Jide's new role at a top law firm didn't stop us from diving into Inflectra's latest developments and discussing the power of strategic marketing in boosting brand awareness.

CQE: The New Frontier
Our final London meet-up was a lunch at Dishoom with our new partner, CQE. They're already making waves with AI-driven platform modernization and quality engineering. We talked about the future of our partnership, identifying market opportunities, and the trends shaping the UK's testing and QA landscape. CQE's Phil summed it up perfectly: "We look for partners who are flexible, understand our customer's problems, and support us effectively. That's why we're excited to work with Inflectra."

Stockholm Stories

After London, we headed to Stockholm for a pivotal meeting with Tietoevry before the EuroStar 2024 conference. Tietoevry, a leader in digital services and software solutions across multiple industries, provided a perfect setting for discussing new product releases like the Inflectra Inflectra SpiraApps Marketplace and Spira's latest features. Fresh cardamom buns and feedback on KronoDesk optimization made the session even more productive. Tietoevry’s expertise and their success in implementing Spira as a Jira alternative in the Nordic region were particularly enlightening.

The Road Ahead

Our whirlwind tour underscored the immense value of in-person meetings. These interactions provided rich insights and strengthened our partnerships, setting the stage for future innovations and collaborations. Stay tuned for more updates as we continue our global journey.

Join the Inflectra Partner Ecosystem

Are you ready to be part of a dynamic and innovative partner network? Join the Inflectra Partner Ecosystem today.

Expand your reach, boost revenue, offer your customers innovative solutions, and tap into our expertise and resources. Together, we'll amplify your brand visibility, foster collaboration within our thriving partner network, and ultimately achieve mutual success.

Join here!

Unveiling the Impact Part I: Project Level Requirements Analysis Process

2024-06-11T10:40:57-04:00

Understanding the Role of Impact Analysis

Impact analysis plays a crucial role in the requirements analysis process. It involves assessing the potential effects and consequences of proposed changes to the project requirements. By understanding the role of impact analysis, project stakeholders can gain insights into the potential risks and benefits associated with different requirements.

One of the key objectives of impact analysis is to identify and evaluate the dependencies between requirements. This helps in understanding how changes in one requirement can affect other requirements and the overall project. Through impact analysis, project stakeholders and the project delivery teams can anticipate potential conflicts, overlaps, or gaps in the requirements and take proactive measures to address them. This is also important when determining which requirements impact across related portfolios and programs.

Another important aspect of impact analysis is to assess the desirability, feasibility and viability of proposed changes. Such thoughts are emphasized in the “Design Thinking” approach as well. It helps project teams evaluate the technical, operational, and financial implications of implementing specific requirements. By considering the impact of requirements on various aspects of the project, stakeholders can make informed decisions and prioritize the most critical requirements for analysis.

Overall, understanding the role of impact analysis enables project teams to assess the potential impact of requirements on the project's success and make informed decisions to ensure successful outcomes.

Prioritizing requirements for analysis is a crucial step in the impact analysis process. It involves evaluating the importance and urgency of different requirements to determine the order in which they should be analyzed. Our friends at Inflectra share more about prioritization here.

One approach to prioritizing requirements is to consider their impact on the project's objectives and goals. Requirements that are directly aligned with the project's strategic objectives and have a high impact on its success should be prioritized for analysis. Additionally, requirements that are time-sensitive or critical to meeting project milestones should also be given higher priority. Such concepts are integral to the “Risk Driven Development” where the risks navigate not only through requirements but also through the project activities, testing activities, and defect triage.

Conducting Impact Analysis

Conducting impact analysis involves assessing the potential effects and consequences of proposed changes to the project requirements. It is a systematic process that helps project teams understand the impact of requirements on various aspects of the project.

The first step in conducting impact analysis is to identify the specific requirements or changes that need to be analyzed. This can be done by reviewing the project documentation, engaging with stakeholders, and conducting interviews or workshops to gather relevant information.

Once the requirements are identified, the next step is to evaluate their potential impact. This involves analyzing the dependencies, risks, and benefits associated with each requirement. Project teams can use various techniques such as impact matrices, scenario analysis, or simulation models to assess the potential impact.

Overall, conducting impact analysis provides project teams with valuable insights into the potential risks, benefits, and challenges associated with different requirements. It helps in making informed decisions and ensures that the project is on track to achieve its objectives.

Interpreting Results and Making Decisions

Interpreting the results of impact analysis is a critical step in the requirements analysis process. It involves analyzing the findings from the impact analysis and making informed decisions based on the results.

When interpreting the results, project teams should consider the potential risks, benefits, and trade-offs associated with different requirements. They should assess the impact of requirements on various aspects of the project, such as budget, timeline, resources, and stakeholders. By representing these observations in the risk matrix as shown below and considering these factors, stakeholders can prioritize the most critical requirements and determine the necessary actions to address any potential issues.

Project teams should assess whether the proposed changes align with the project's objectives and goals, and whether they are technically and operationally feasible. By considering these factors, stakeholders can make informed decisions and determine the best course of action for implementing the required changes.

Overall, interpreting the results of impact analysis enables project teams to understand the implications of different requirements and make informed decisions to ensure successful project outcomes. It helps in identifying potential risks, addressing challenges, and maximizing the benefits of implementing specific requirements.

Implementing Changes for Maximum Impact

Implementing changes for maximum impact is the final requirement analysis step. It involves taking the necessary actions to implement the required changes based on the findings from the impact analysis.

One key aspect of implementing changes is ensuring effective communication and collaboration among project stakeholders. This includes sharing the results of the impact analysis, discussing the proposed changes, and obtaining buy-in from all relevant parties. By involving stakeholders in the implementation process, project teams can ensure that the changes align with their expectations and requirements.

Another important factor to consider when implementing changes is to have a well-defined plan and timeline. Project teams should develop a clear roadmap for implementing the changes, including the necessary resources, activities, and milestones. By having a structured approach, stakeholders can track the progress of the implementation and address any potential issues or challenges.

During the implementation process, project teams should also monitor and evaluate the impact of the changes. This includes assessing whether the desired outcomes are achieved, identifying any unexpected consequences, and making necessary adjustments. By continuously monitoring the impact of changes, project teams can ensure that the desired benefits are realized and any potential risks are mitigated.

Overall, implementing changes for maximum impact is crucial to ensure the successful outcomes of the requirements analysis process. It requires effective communication, careful planning, and continuous monitoring to ensure that the changes are implemented promptly and efficiently.

What's Next?

Stay tuned for Unveiling the Impact: Part 2 in the next article written by Sriram Rajagopalan at https://www.orcaintelligence.com/

This article was written by Melissa Daley, CEO & Founder of Orca Intelligence.

Grow QA Expertise: Planit Discounts on Premium ISQTB Trainings

2024-06-14T11:40:54-04:00

Why Choose Planit:

World-Class Instructors: Learn from seasoned experts who have real-world experience in quality assurance.
Industry-Recognized Certifications: Gain certifications that enhance your team's credibility and marketability.
Comprehensive Curriculum: Cover all aspects of quality assurance, from testing methodologies to Agile principles.
Proven Results: Join thousands of professionals who have transformed their careers through Planit training.

Take the Next Step:

Don't miss this opportunity to empower your team and drive quality excellence. Visit Planit Training and mention "Inflectra" when emailing training@planittesting.com to avail yourself of this special offer.

Invest in your team's future and unlock your full quality assurance potential! Contact Planit now!

Inflectra In the News - May 2024 News Roundup

2024-06-04T12:35:29-04:00

Podcast

Bonus: Adam Sandman, Inflectra with Code Story - May 9, 2024

Adam Sandman, a physics graduate with a passion for tech, discovered a gap in the market for effective QA testing tools. Leveraging his experience as a project manager and architect, he set out to create a solution. This is the origin story of Inflectra, a company born from a desire to improve software testing practices. Listen Here.

Publications

Protecting Against Cyber Threats in the Age of Generative AI with The Fast Mode - April 10, 2024

Businesses are increasingly moving their IT infrastructure and security tools to cloud platforms due to the need for better security and scalability. However, this transition also creates new cybersecurity challenges, as a breach of a central cloud tool can have widespread consequences for many customers. The expanded attack surface presented by cloud platforms is a major concern in this regard. Read more.

The Convergence of Software and Hardware in the Era of Digital Twins with DEVOPS Digest - April 22, 2024

The convergence of software and hardware is transforming industries, with "software-defined manufacturing" and digital twins leading the way. Digital twins, virtual replicas of physical objects, are revolutionizing product design and testing, streamlining development cycles and reducing costs. Embracing this shift requires a hybrid approach, blending agile software development with traditional hardware lifecycle management, presenting both challenges and opportunities in managing complex systems. Read more.

Code with Care: Security Testing in Confidentiality-Driven Industries with StickyMinds - May 3, 2024

Developers are naturally driven to innovate, but this focus can sometimes overshadow the importance of security. In industries like healthcare, where protecting sensitive data is paramount, security breaches can have catastrophic consequences. That's why prioritizing security testing during development is not only essential but should be a standard practice across the tech industry. Read more.

Taking Agile to New Heights: Scaling for Success in Aerospace with AgileConnection - May 6, 2024

Traditional waterfall development in the aerospace and aviation industries leads to stifled innovation, lengthy cycles, and limited feedback. Agile methodologies, adapted for strict safety regulations, offer a solution. By breaking down development into sprints and fostering collaboration, Scaled Agile can significantly improve efficiency, accelerate ingenuity, and get cutting-edge technologies to market faster—and safer. Read more.

Talks

Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered Quality at STAREAST Conference in Orlando, Florida - May 2, 2024

Adam Sandman's presentation examines how AI is revolutionizing software project management, development, and automation, with insights applicable across industries. Through real-world examples using SpiraPlan and Rapise, Sandman reveals the distinct advantages AI offers agile software teams. This talk demonstrates how AI is transforming the software industry, providing practical strategies that can benefit organizations across various sectors. Read more.

Managing Risk-Based Testing in the Age of AI at TestingMind in Washington, DC - May 10, 2024

Artificial Intelligence (AI) is transforming software testing, enabling faster and more precise identification of errors, but it also introduces new risks. Risk-Based Testing (RBT) is a method for prioritizing testing efforts based on the likelihood and impact of potential failures, and Adam Sandman will discuss how RBT can be used in the AI era. Sandman's talk will cover the challenges of implementing RBT with AI, balancing its advantages with the risks of incorrect results, and various techniques to manage these risks. Read more.

Stay in the Loop!

Subscribe to our monthly newsletter and get the latest news, updates, and insights delivered right to your inbox.

ISO Standards Demystified: Your Blueprint for Project Success, QA, and Risk Mitigation

2024-06-03T11:02:52-04:00

Recording

Takeaways

Foundational ISO Standards to Know

ISO 9001: Quality Management – Ensure your products and services consistently meet customer expectations.
ISO 21500: Project Management – A framework for planning, executing, and delivering projects on time and within budget.
ISO 31000: Risk Management – Identify, assess, and control risks that could derail your projects or harm your business.

The webinar also explored ISO standards for environmental safety (14001), information security (27001), and workplace safety (45001). Each of these standards plays a vital role in building a resilient and responsible organization.

Highlights

ISO standards are interconnected – a holistic approach is key.
Quality and risk management are not optional – they are essential for success.
Customer focus is paramount – always strive to exceed expectations.
Leadership matters, but engagement from all levels is crucial.
Continuous improvement is a journey, not a destination.

The Inflectra Advantage

At Inflectra, we understand navigating the world of ISO standards can be overwhelming. That is why our tools are designed to simplify the process and empower your teams to achieve ISO compliance with ease.

SpiraPlan: Our comprehensive project management platform helps you align your projects with ISO 21500, streamline processes, and improve collaboration.
SpiraTest: Ensure your software meets the highest quality standards with our robust test management solution, fully compatible with ISO 9001 principles.
Risk Management Module: Identify and mitigate risks proactively, ensuring your projects stay on track and your business thrives.

Simplify ISO compliance and drive your business forward with Inflectra. Our tools and expertise can help you achieve your goals and drive your business forward. Contact us today to experience how we can transform the way you manage projects, quality, and risks.

Level Up Your Skills

Ready to elevate your software development expertise? Explore InflectraCON360, your digital hub for year-round access to thought leadership, tech knowledge, and networking opportunities.

You can also subscribe to our monthly newsletter and be the first to know about Inflectra's newest developments, industry insights, and upcoming events.

Recap: Unleash the Power of AI for Faster, Smarter Software Delivery

2024-05-28T09:42:25-04:00

Recording

Slideshow

Key Takeaways

AI is reshaping software development and testing, and it's happening now. Embracing AI-driven solutions like those from Inflectra is essential for companies to stay competitive and deliver top-quality software at the speed of innovation. As CEO Adam Sandman points out, AI's transformative power is felt across the entire development process.

AI's Transformative Impact on Software Development

Accelerating the SDLC: AI-powered tools are speeding up prototyping, gathering early customer feedback, and enhancing efficiency throughout the entire software development lifecycle.
Shifting Testing Focus: With the rise of AI-generated code, testing is evolving towards higher-level skills like verification, analysis, and ensuring the quality and reliability of software.
Increased Importance of Quality: Rigorous quality checks are crucial to maintain the reliability and functionality of software as AI-generated code becomes more prevalent.

Inflectra's AI-Powered Solutions for Streamlined Testing

Seamless Test Case Generation: Our ChatGPT and Azure Open AI platform plugins automatically generate test cases, tasks, scenarios, and risk assessments directly from requirements, simplifying and streamlining the testing process.
Optimized Testing Efforts: AI analyzes historical data to prioritize critical test cases, maximizing testing efficiency and ensuring comprehensive coverage.
Self-Healing Tests: Our AI-driven tests adapt to application changes, reducing maintenance overhead and increasing test resilience.
Cutting-Edge Visual Testing: Inflectra is pioneering AI-powered visual testing, enabling highly accurate and efficient verification of user interfaces.

Connect, Learn, Grow

Ready to elevate your software development expertise? Explore InflectraCON360, your digital hub for year-round access to thought leadership, tech knowledge, and networking opportunities.

You can also subscribe to our monthly newsletter and be the first to know about Inflectra's newest developments, industry insights, and upcoming events.

Recap: SpiraPlan's REST API in Action – Expert Insights & Real-World Use Cases

2024-05-15T16:03:42-04:00

The webinar, led by mVerve's experts Kriti Agarwal, Harsha Marigowda, and Abhijit Nandy along with Sriram Rajagopalan, Global Head of Training and Agile Transformation at Inflectra, delved into the practical applications of SpiraPlan's REST API.

Slideshow

Key Takeaways

SpiraPlan's API Ecosystem: Attendees gained a deeper understanding of how SpiraPlan's robust REST API can seamlessly integrate with other tools and systems, enhancing your software development lifecycle.
Real-World Use Cases: Abhijit from MVerve provided a live demonstration, showcasing how to interact with SpiraPlan using Postman to perform essential tasks like fetching data, creating incidents, updating records, and more. This hands-on approach illustrated the versatility and ease of use of our API.
MVerve's Expertise: Harsha Marigowda highlighted MVerve's proficiency in leveraging SpiraPlan's capabilities, including the development of custom reports and advanced reporting solutions using REST APIs and OData. This partnership demonstrates the real-world impact our API can have on your projects.
Q&A Session: The webinar concluded with a lively Q&A session, where attendees had the opportunity to ask questions about specific use cases and integration scenarios. Our experts provided valuable insights and guidance, further solidifying the power of SpiraPlan's API.

Unlocking the Potential of Your Data

The webinar emphasized how SpiraPlan's REST API allows you to:

Automate Workflows: Streamline your processes by automating repetitive tasks.
Integrate with Existing Tools: Seamlessly connect SpiraPlan with your existing software ecosystem.
Build Custom Solutions: Tailor SpiraPlan to your unique needs by developing custom applications and integrations.
Gain Deeper Insights: Extract valuable data from SpiraPlan for advanced reporting and analysis.

Additional Resources

For those looking to explore further, Inflectra Campus provides a wealth of learning resources to help you get the most out of our platform.

Ready to elevate your software development expertise? Explore InflectraCON360, your digital hub for year-round access to thought leadership, tech knowledge, and networking opportunities.

You can also subscribe to our monthly newsletter and be the first to know about Inflectra's newest developments, industry insights, and upcoming events.

What You Missed: Risk Management Strategies for Agile Success

2024-06-07T14:00:53-04:00

Recording

Why Risk Management is Essential in Agile

Agile methodologies, while designed for flexibility, face inherent challenges that can hinder value delivery:

Uncertainties: Shifting business conditions, technological advancements, and evolving regulations create a constantly changing landscape.
Enterprise-Wide Impact: Agile transformations extend beyond technical teams, affecting employee roles, organizational capacity, and even societal contributions.
Broadened Risk Scope: Modern Agile teams must address not only technical risks but also data security, regulatory compliance, and customer safety.

However, these challenges also present an opportunity: Effective risk management can uncover innovative solutions that lead to greater value delivery.

Key Takeaways for Agile Risk Management

Integrated Approach: Embed risk management seamlessly into Agile processes. Consider potential risks tied to user stories and epics during iteration planning.
Diverse Analysis Techniques: Employ a variety of methods to identify and manage risks, including document review, assumptions analysis, diagramming, and gathering insights from diverse stakeholders.
Leverage Frameworks and Standards: Familiarize yourself with risk management frameworks relevant to your industry (e.g., PESTLE, TECOP, VRIO) and international standards like ISO. Ensure compliance with regulatory standards such as SOX, GDPR, and HIPAA, where applicable.
Synergy with Change Management: Recognize the symbiotic relationship between risk management and change management. Both are crucial for effective governance and successful Agile transformations.

About the Host

Sriram Rajagopalan is a project management guru and Enterprise Agile Evangelist at Inflectra Corporation. Dr. Rajagopalan has extensive software development and project management experience in many industries. He won prestigious recognition from PMI with the Eric Jennet Project Management Excellence Award in 2017. He holds a BE in Electronics and Communication Engineering from the University of Madras in India, an MS in Computer Engineering from Wayne State University, and an MBA in Management from Concordia University. His Ph.D. was in Organization and Management from Capella University. Dr. Rajagopalan possesses many professional certifications in PfMP, PgMP, PMP, PMI-ACP, PMI-SP, PMI-RMP, CSP, CSPO, CSD, CSM, ACC, IT Project+, Six Sigma, SCM, SCPO, SCD, SAMC, SCT, and CSOXP.

In Conclusion

Managing risks in Agile enterprises requires a holistic approach that considers technical, business, and strategic factors. By embracing risk as a natural part of Agile practices and implementing robust risk management strategies, organizations can navigate dynamic environments and enhance their ability to deliver value effectively.

Connect, Learn, Grow

Ready to elevate your software development expertise?

Explore InflectraCON360, your digital hub for year-round access to thought leadership, tech knowledge, and networking opportunities.

You can also subscribe to Inflectra's monthly newsletter and be the first to know about Inflectra's newest developments, industry insights, and upcoming events.

Medical AI: Software Diagnosing Health Issues?

2024-07-10T21:02:44-04:00

Why Now? AI’s Advancement in Software

The past several years have witnessed a surge in Artificial Intelligence capabilities, fueled by exponential growth in data availability and processing power. This has opened a new chapter in software development, particularly within the medical field. AI-powered medical software is no longer science fiction — it's a rapidly evolving reality with the potential to revolutionize healthcare delivery.

How is AI Helping the Medical Field?

AI is transforming the medical field at an unprecedented pace, influencing everything from administrative tasks to improving diagnostic accuracy and patient care itself. Here are some areas where AI is already making a difference:

Medical Scribing & Notes

Historically, doctors will spend a considerable amount of their time documenting patient interactions, leading to inefficiencies and sometimes resulting in input errors. AI medical scribes use natural language processing (NLP) to transcribe consultations in real-time, freeing up physicians to focus on their patients. In addition to transcription, automated scribes can analyze existing medical records and generate comprehensive summaries, highlighting important notes and reducing the need for lengthy note-taking. This significantly improves efficiency and facilitates more accurate and complete medical documentation.

Medical Coding

Assigning accurate medical codes is a critical step of healthcare reimbursement. Unfortunately, it can be a complex process prone to errors. However, AI is revolutionizing this by automatically assigning the correct codes based on diagnoses, procedures, and medications. This minimizes coding errors and streamlines the billing process, saving both patients and providers time and money. Not only that, but AI can identify potential coding inconsistencies, leading to cleaner claims and fewer denials.

Medical Imaging & Early Detection

AI algorithms are already proving remarkably adept at analyzing medical imaging results like X-rays, MRIs, and CT scans. They can identify subtle abnormalities or patterns that may have been missed by the human eye, leading to earlier diagnoses and potentially lifesaving interventions. The trend is moving towards even more sophisticated AI models that can not only detect diseases, but also extrapolate their progression and recommend personalized treatment plans.

Physical Therapy

Physical therapy plays a vital role in rehabilitation, but traditional methods and medical devices often lack personalization. AI programs can incorporate real-time feedback and guidance through wearable sensors, making sure that patients perform exercises correctly and maximize rehabilitation benefits. Even more impressive, AI chatbots can provide patients with ongoing support and motivation throughout their recovery journey.

Medical Device Testing & Development

The development of safe and effective medical devices is a very rigorous process so that each is safe for the lifetime of the device. AI has been helping to accelerate medical device testing through automated scenario simulation and testing to identify potential risks. This might involve evaluating how a device interacts with different patient anatomies or predicting possible device malfunctions. By identifying and testing potential issues earlier in the development phase, AI can expedite the creation of safer and more reliable medical devices, ultimately enhancing patient care.

Reducing Doctor Burnout

Burnout is a major concern in the healthcare industry, with long hours and difficult decisions being large contributing factors to this issue. The automation and streamlining of many administrative tasks, like scheduling appointments, managing referrals, and generating reports, may be able to ease some of this burden. The current trend is on a path toward AI-powered virtual assistants that can handle even more complex tasks, further assisting doctors to manage their workload and improve their well-being.

AI Diagnoses: Will AI Replace Doctors?

Beyond helping with managerial tasks, AI is also making significant strides in the realm of medical analysis and recommendations — but will (or should) they be relied on for official diagnoses?

One of AI's greatest strengths lies in pattern recognition. By analyzing large amounts of medical data (such as patient history, symptoms, lab results, and medical imaging), AI can identify complex patterns that may have otherwise gone unnoticed. They can also leverage vast datasets of medical research and clinical trials, calculating the probability of various diagnoses based on a patient's specific presentation. This statistical analysis can provide valuable insights to doctors and inform their decision-making process.

On the other hand, the quality of AI models relies heavily on the data they're trained on. Incomplete, inaccurate, or skewed data can lead to biased or unreliable diagnoses. Another hurdle is AI's lack of reasoning ability. While AI excels at identifying patterns, it struggles with complex reasoning and judgment. Understanding the nuances of a patient's medical history, social factors, and emotional state requires a human touch that AI simply lacks. Lastly, there are ethical considerations surrounding AI-based diagnoses. Bias in the training data can lead to discriminatory outcomes, and patients might lose trust in a system that lacks human empathy and bedside manner.

AI is not poised to replace doctors, but rather to function as a powerful assistive tool. We can expect to see AI-powered software that provides real-time diagnostic suggestions to doctors during consultations (without having the final say on diagnosis). Despite AI having immense potential to transform healthcare, the answer to this question is a resounding no — at least not in the foreseeable future. Ultimately, the doctor-patient relationship will likely remain central to diagnosis.

The Risks of Not Adapting

While AI probably won’t replace your practitioners and surgeons anytime soon, it doesn’t mean the technology should be cast aside. In fact, medical institutions that fail to adapt to AI risk falling behind:

Lagging Behind Technology: Healthcare has become increasingly data-driven and as we’ve discussed, AI excels at analyzing huge amounts of medical information to identify patterns. These patterns can inform diagnosis, treatment planning, and even preventative measures. Hospitals and clinics that fail to leverage these capabilities will be at a disadvantage, potentially missing out on crucial insights and advancements that could improve patient care.
Increased Workloads for Doctors: Administrative tasks and lengthy documentation contribute significantly to physician burnout. AI tools can help automate many of these tasks, freeing up valuable time for doctors to focus on patients. Institutions that don't lean into this risk placing an even greater burden on their physicians, potentially leading to decreased morale, increased errors, and higher turnover.
Losing Patients to Other Practitioners: Patients today are increasingly tech-savvy and expect their healthcare providers to be on the cutting edge. Hospitals and clinics that are seen as lagging behind in technology or processes might lose patients to competitors that offer more comprehensive services. This may limit patient access to potentially life-saving advancements from AI-powered diagnostics and treatment options.
Difficulty Keeping Up-to-Date Information: The medical field is constantly evolving, with new research and clinical trials emerging regularly. Keeping up with this ever-growing body of knowledge (and ever-changing patient records) can be challenging for doctors. Hospitals that don't utilize AI risk having their doctors work with potentially outdated information, which might negatively impact their ability to provide the best care possible.

Future-Proof Your Medical Software with Inflectra

As AI continues to evolve, strong software development practices are becoming increasingly critical for building the secure, reliable, and efficient platforms that will power this transformation.

Developing software for AI-powered healthcare solutions comes with unique challenges. Inflectra’s expertise in automated testing and rigorous QA helps your software perform flawlessly, preventing bugs or errors that could lead to patient or provider concerns. Medical data is also highly sensitive, so any breaches could (and have) result in devastating consequences for everyone involved. Secure project management practices and robust QA processes like those offered by SpiraPlan are vital in safeguarding patient information and ensuring compliance with regulations like HIPAA.

The future of healthcare will rely heavily on the responsible development of AI-powered software. As a company driving this innovation, your commitment to thorough testing, comprehensive QA, and secure development is paramount to building reliable and trustworthy medical devices and software platforms. Enhance your development and deployment capabilities with Spira and Rapise today!

Inflectra at STAREAST 2024: Innovation, Insight, and Fun

2024-05-04T12:44:03-04:00

Tech in Action: Showcasing AI Upgrades and Winning Hearts with Demos

Our booth was buzzing with activity throughout the conference. We showcased the new AI features in the Spira suite of products (SpiraTest, SpiraTeam, and SpiraPlan), providing mini demos on the fly to demonstrate how these Inflectra solutions can simplify and improve software development and testing processes. These demos allowed us to directly engage with visitors, answer their questions, and show real-time how our software can make a big difference in their work.

The Inflectra swag was a hit, too! We loved seeing attendees enjoy the practical gifts and goodies we brought along, which added a fun and personal touch to our booth.

Networking and Learning

STAREAST 2024 was an excellent venue for meeting our customers. These interactions help us better understand their needs and strengthen our relationships. We caught up with the Spira power users at the customer - Cincinnati Insurence, pictured below.

Networking with amazing tech professionals at the conference helps us expand our network and gain real-time feedback on our products. The excitement and positive responses we got have been inspiring, showing us that our solutions are both cutting-edge and needed in the space.

Stellar Presentation: Adam Sandman Packs the House with AI Insights

One of the event's highlights was the presentation by our CEO, Adam Sandman, titled "Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered Quality." Adam's talk was packed, with attendees standing in the back to catch his insights on how AI is revolutionizing project management, testing, and development. His presentation highlighted the cutting-edge capabilities of our Spira suite and sparked conversations on the future of AI in our industry.

Good Times with Good People: Reconnecting with Partners

It was great catching up with our partners, such as Coveros, Orca, LambdaTest (both pictured below), and Checkpoint.

Serious business was followed by a bit of fun at the local favorite - Howl At The Moon Bar, with our partner TapHere! (pictured below)

Stay tuned for our events and updates by following us on Linkedin.

See you in Orlando next year!

AI in the Real World: How Businesses are Leveraging AI for Tangible Results

2024-05-23T12:11:41-04:00

Webinar Recording

Key Takeaways

AI's Transformative Power: The webinar showcased numerous examples of how AI is not just hype, but a tangible force reshaping industries. Businesses are successfully leveraging AI to optimize operations, understand customer needs better, and drive innovation.
AI as an Innovation Catalyst: AI isn't just about solving existing problems. Industry leaders demonstrated how they're tapping into AI's potential to create entirely new business models and revenue streams.
Boosting Productivity: Experts agreed that AI significantly improves productivity by automating routine tasks, allowing teams to focus on strategic initiatives and higher-value work.
Overcoming Implementation Challenges: The panel didn't shy away from the common challenges of AI implementation. They discussed critical issues like data quality, overcoming bias, and ensuring ethical AI use to help viewers implement AI responsibly.

Our Expert Panel

Our panelists shared candid insights into the data privacy concerns and ethical considerations they faced, as well as the obstacles they successfully navigated. Their experience provided valuable guidance for approaching AI implementation with strategic focus, a sense of responsibility, and a strong foundation for success.

Adam Sandman - Founder and CEO of Inflectra
Jeffery Payne - CEO of Coveros
Jim Ball - Quality Assurance Auditor at Cincinnati Financial Corp
Tamika Burgess-Rose - Quality Assurance Test Manager at CIBC Caribbean

Conclusion

The "AI in the Real World" panel discussion offered a compelling message: AI adoption is no longer an option for businesses that want to stay ahead of the curve. This technology offers enormous potential to increase efficiency, gain deeper customer understanding, and drive unprecedented levels of innovation. By learning about successful implementation strategies and ethical considerations, businesses can chart a path toward harnessing AI's power for long-term competitive advantage.

Did you Find this Event Valuable?

Stay up-to-date with Inflectra's upcoming events, product enhancements, corporate announcements, and more through our monthly newsletter.

Recap: How SpiraTest Can Enhance Your Software Quality

2024-04-17T16:56:21-04:00

Webinar Recording

Presentation and Slideshow

Key Takeaways

Comprehensive Test Management: SpiraTest is an integrated solution for managing test cases, requirements, and defects. It provides a comprehensive alternative to older tools such as Testrail, Qtest, and Practitest, as outlined in a comparative analysis.
Enhanced Testing through Detailed Steps and Automation: SpiraTest's functionality includes detailed test steps and automation features. These capabilities are designed to simplify the testing process and improve efficiency for users.
User-Friendly Interface and Reporting: Users are able to delve into SpiraTest's intuitive interface and take advantage of its advanced reporting options. The platform facilitates real-time insights and supports data-driven decision-making, enhancing the overall user experience.

Speaker:

Adam Sandman founded Inflectra in 2006. Today, Adam serves as the company's CEO. He is responsible for product strategy, technology innovation, and business development. He lives in Washington, D.C., with his family. Prior to founding Inflectra, Sandman worked as a director for Sapient Government Services, where he was in charge of development with the U.S. Marine Corps. and other government agencies, and was responsible for leading many capture teams and writing whitepapers and position statements to build Sapient’s reputation as a leader in the defense space. He studied physics at Oxford University.

Don't Miss a Beat

Subscribe to our monthly newsletter and get all the inside info on upcoming events, product updates, company news, and more.

Recap - Optimize Test Outcomes: Harness the Power of AI with Spira and Eoten

2024-04-05T14:44:59-04:00

Recording

Key Takeaways

Understanding the Titans: Both Spira, a renowned test management solution, and Eoten, a cutting-edge AI-powered test optimization platform, offer unparalleled capabilities in the software development world.
The Pain Point: Software testing can become a bottleneck– time-consuming and resource-intensive. This hinders your team's ability to quickly deliver high-quality releases.
A Synergistic Solution: Spira and Eoten together offer a potent antidote. Spira provides structured test planning and management, while Eoten uses AI to intelligently pinpoint which tests are most relevant based on code changes. This combination results in a laser-focused testing approach that saves time and effort.
Seeing it Live: The true power of the integration became clear during the webinar's live demonstration, showcasing how these tools address typical testing challenges with finesse.

The Value Proposition

Integrating Spira and Eoten creates a powerful force within your software testing practice. The key benefits include:

Increased Efficiency: Eliminate unnecessary test runs, focusing on the most critical changes.
Enhanced Accuracy: Rest assured that essential elements receive thorough testing with Eoten's intelligent test selection.
Accelerated Time-to-Market: Reduce testing delays, enabling faster delivery of quality software.

About the Presenters

Ioannis Petousis, Ph.D., is the Founder and CEO of Angulon.AI, which specializes in the innovation of cutting-edge AI products and the identification of use cases that deliver the biggest impact to an organization's business. Ioannis has extensive experience creating revenue-generating AI products as well as starting, developing, and managing teams of highly-skilled AI scientists. Before Angulon.AI, he led the Data Science and AI functions of Renovo Motors (acquired by Woven Planet - a subsidiary of Toyota) and Hilti Group. Ioannis is the author of multiple patents focusing on the application of AI and Big Data and holds an M.Eng. from Imperial College, London as well as an M.S. and a Ph.D. from Stanford University.

Dermot Canniffe has been in the software industry since 2001, serving in a variety of roles, including development, testing and automation. He has a particular interest in Agile methodologies, and the various means by which teams can communicate and collaborate effectively. He is most likely to draw metaphors and similes from Star Trek, Star Wars and other sci-fi universes.

Loved the webinar?

Don't miss out! Subscribe to our monthly newsletter for upcoming events, product updates, and industry insights from Inflectra.

Inflectra In the News - February-March 2024 News Roundup

2024-04-05T16:47:37-04:00

Podcast

Using AI for Effective Test Generation with LambdaTest - February 8, 2024

Adam Sandman underscores the pivotal role of AI in software testing, highlighting its capacity as an indefatigable contributor. AI furnishes distinctive insights and impartial recommendations, harnessing its prowess to alleviate biases and furnish objective analyses. It bolsters test coverage by pinpointing blind spots and foreseeing potential risks, thereby fortifying the testing process. Sandman advocates for test managers to embark on pilot projects with AI, tempering expectations pragmatically, instituting governance protocols, offering requisite context and training, and nurturing a symbiotic relationship between AI and human testers to yield optimal results. Listen now.

Publications

Getting Started With AI-Augmented Software Development with Information Week - February 5, 2024

In this article, Adam Sandman highlights a common issue in software development where humans excel at creative problem-solving but often overlook essential tests and exception cases. Sandman emphasizes the potential of AI in addressing this gap by enabling developers to create code that is 80% functional, which can then be refined to 100% readiness through AI-powered input checking, error handling, and null checking. He likens this process to how writers utilize spelling and grammar checkers to identify and rectify obvious mistakes, suggesting that AI can similarly enhance code quality and reliability. Read more.

Navigating the Digital Retail Revolution: Overcoming Technology and Software Challenges with TotalRetail - March 4, 2024

Discover Adam Sandman's compelling insights in our featured article, where he explores the transformative strategies essential for retailers navigating the digital landscape. From transitioning legacy systems to embracing AI and analytics, Sandman elucidates practical approaches to enhance customer experiences and future-proof operations. As CEO of Inflectra, Sandman's expertise illuminates the path for retailers seeking to thrive amidst relentless technological shifts. Read more.

Successful Real-World Use Cases For LLMs (And Lessons They Teach) with Forbes Technology Council - March. 7, 2024

In a recent article, Adam Sandman discussed the successful utilization of large language models (LLMs) such as ChatGPT for test data generation. Sandman highlighted how Inflectra leveraged ChatGPT to efficiently populate a sample web application with realistic test data, including lists of books, authors, and other relevant information. By utilizing LLMs for this purpose, Inflectra was able to save valuable time typically spent on manual data entry tasks. Sandman emphasized the benefits of using LLMs for test data generation as a safer and more efficient alternative to manually creating fake data or sanitizing real data, which can pose risks. Read more.

Inflectra Helps Enterprises Balance Quality and Agility When Building Mission-Critical Software with HostingAdvice.com - March 12, 2024

Inflectra recognizes the evolving challenges faced by tech companies today, where agility and adaptation are paramount for success. As CEO, Adam Sandman emphasizes the importance of Inflectra's platform in enabling companies to maintain agility while managing risks and ensuring software quality throughout the development lifecycle. With features such as traceability, risk management, and AI-driven insights, Inflectra empowers teams to make informed decisions and deliver innovative products efficiently, fulfilling its mission to support companies in their journey towards resilience and success. Read more.

The Best Coding Bootcamps on the Market in 2024 with Springboard - March 15, 2024

Software engineering remains a lucrative and satisfying career choice, leading many to seek the best coding bootcamps as an accelerated and affordable alternative to traditional education. Amidst a rising demand for security experts and a proliferation of online bootcamps, choosing the right one is crucial to avoid pitfalls like inadequate curriculums and support. In this article, see Adam Sandman's insightful perspective on tech bootcamps. Read more.

Generative AI: Pushing Software Development Forward? with Techwell - March 20, 2024

This article highlights the transformative potential of generative AI in software development, emphasizing its ability to streamline coding processes, enhance code quality, and accelerate various aspects of the development lifecycle. Inflectra understands the importance of this technology and Adam Sandman's role in advocating for its adoption within the company. However, they also acknowledge the need to address challenges such as human review and bias mitigation in AI-generated code to deliver high-quality software solutions. Despite these hurdles, Inflectra encourages developers to embrace generative AI as a powerful tool for innovation, integrating it into their workflows to enhance productivity and maintain competitiveness. Read more.

Talk

How We Bootstrapped to $13m Revenue By Landing $500k Accounts With a Unique Vertical Sales Model at SaasOpen Conference in Austin, TX - March 29, 2024

Adam Sandman, was a keynote speaker presenting "How We Bootstrapped to $13m Revenue By Landing $500k Accounts With a Unique Vertical Sales Model." Sandman showcased the strategies that had propelled Inflectra's growth and revealed how they had achieved success without external funding, focusing on their targeted approach to specific industries, the importance of building strong customer relationships, and the methods they used to scale their bootstrapped business. It was an opportunity not to be missed, offering valuable insights from Adam's experience to power one's own SaaS journey. Read more.

Don't Miss a Beat!

Inflectra, LambdaTest and DevOpsDC Meetup's Joint Event on DevOps, Testing and AI

2025-04-01T21:14:38-04:00

Masterminds and Pizza Collide

The festivities began with a warm and welcoming atmosphere as attendees enjoyed networking, pizza, and refreshments. The ambiance naturally evolved into a spirited Happy Hour, where attendees had the opportunity to interact with the innovators behind the technology. Conversations flowed freely as business cards were exchanged and new connections were established. Laughter filled the air as familiar faces reunited and friendships took root. Inflectra's swag table added a touch of excitement, offering attendees the chance to take home keepsakes of the event.

Luminaries in Tech Dive into AI

Chrystina Nguyen, DevOpsDC's event organizer, smoothly transitioned the attendees' attention to the panel discussion. Before starting, participants had the opportunity to introduce themselves while sharing a fun fact about themselves, setting a tone of fellowship and engagement – a fantastic way to break the ice.

Afterward, Jessica Moore, Inflectra's Director of Global Alliances and event moderator, opened the panel discussion. The discussion industry experts who are also valued Inflectra partners:

Adam Sandman, CEO of Inflectra
Mudit Singh, Head of Growth and Marketing at LambdaTest
Melissa Daley, CEO of Orca Intelligence

The panel discussion centered on exploring the future of DevOps and AI, unpacking emerging trends, challenges, and opportunities. The expert speakers sparked a lively discussion that peeled back the layers of what's next for the exciting intersection of DevOps and AI. A dynamic Q&A session followed, where attendees got candid answers to their questions, contributing towards open dialogue and knowledge exchange.

Be Part of Our Community

Subscribe to our monthly newsletter to stay informed about upcoming events from Inflectra.

What We've Learned: Inflectra At SaasOpen 2024

2024-04-02T13:46:45-04:00

Inflectra's participation in the SaaS Open Conference was filled with insightful exchanges, strategic learning, and forward-looking discussions. Adam Sandman, Inflectra CEO, and other members of the leadership team collected valuable takeaways that will enrich the company's strategic direction.

Adam Sandman on Founder Stage: Bootstrapping Success

One of the highlights of the conference was a presentation by our CEO, Adam Sandman, that dove deep into Inflectra's journey toward achieving significant growth without external funding. The talk covered targeted industry approaches, the cultivation of solid customer relationships, and scalable business strategies that provided a blueprint for SaaS success.

Key insights from the event emphasized the importance of evolving from offering mere products to providing comprehensive platforms. This strategic shift aims to make our solutions indispensable to our clients' ecosystems, ensuring that Inflectra remains competitive in a rapidly changing market.

The conference also highlighted the need for a refined sales strategy that recognizes the importance of customer engagement beyond the initial sale. This includes leveraging every sales query to enrich our content library with FAQs, whitepapers, and webinars, thereby fostering an informed customer base.

The discussions at SaaSOpen 2024, especially around generative AI, gave us a new impetus to push technological boundaries. Looking forward, Inflectra is excited about the future of SaaS and AI, alongside our customers, partners, and the broader tech community. With SpiraPlan, SpiraTest, and Rapise, we will continue to deliver the best value to our customers when it comes to team collaboration, innovation, and high-quality software solutions.

What is next in SaaSOpen?

Just the best founder conference on the eastern seaboard - SaaSOpen NYC on September 5 & 6, 2024. We hope to see our new friends there!

Team Inflectra

Mapping the Future of Healthcare: Quality, Ethics, and Innovation at HIMSS 2024

2024-03-26T10:47:15-04:00

Tomorrow's Healthcare is Here Today

One of the most inspiring aspects of HIMSS 2024 was the palpable sense of living in the future of healthcare today. From the practical application of AI in clinical settings to the adoption of large language models and machine learning in preclinical studies, the sessions at the conference underscored a significant leap toward a tech-enabled healthcare ecosystem. Notably, the discussions didn't just focus on the technological advancements and the regulatory and ethical frameworks necessary to navigate this new terrain. The narrative was straightforward: as much as we are pushing the boundaries of what's possible with technology, the compass guiding this journey must be calibrated with considerations for patient safety, data privacy, and equitable access.

Leadership is First, Technology Next

A recurring theme throughout the conference was the emphasis on leadership in adopting and integrating technology within healthcare. The wisdom shared by industry leaders underscored a fundamental truth: the journey towards a tech-integrated healthcare future is less about the technology itself and more about the vision, ethics, and processes that govern its use. Leadership in this context is seen not just as a positional attribute but as a cultural ethos that permeates every level of an organization. This perspective resonates deeply with Inflectra's philosophy, where innovation is always paired with a commitment to ethical standards and a focus on delivering value to healthcare providers and patients.

Post-Event Thoughts: A Call to Quality and Ethical Innovation

Reflecting on the myriad discussions and insights from HIMSS 2024, a central narrative emerges—a call to elevate the importance of quality in healthcare delivery. This narrative goes beyond technical competencies to encompass healthcare innovation's ethical, regulatory, and human-centric aspects. It's about developing solutions that address today's challenges and are resilient and adaptable to the needs of tomorrow. Inflectra, through its suite of products like Spira and Rapise, is leading by example, integrating AI capabilities to enhance the identification of requirements, risks, and test cases and extending functionalities through SpiraApps for a holistic approach to healthcare solutions.

As we distill the insights from HIMSS 2024, it's evident that the future of healthcare we envisage is one where technology and human care are not disparate entities but integral components of a unified whole. The discussions and reflections shared by Dr. Rajagopalan highlight a future where healthcare is not just about managing diseases but about fostering well-being, supported by ethical, equitable, and empathetic technology. In the future, organizations like Inflectra will play a pivotal role in driving innovation while ensuring that the heartbeat of healthcare remains human-centric. The journey ahead is complex, but with the compass of quality, ethics, and innovation, we are well-equipped to navigate the challenges and opportunities in creating tomorrow's health.

Need more HIMSS insights?

Check out these blogs:

Humanizing Healthcare in the Age of AI: Insights from HIMSS 2024

2024-05-04T20:25:39-04:00

The Human Aspect of Healthcare Technology

One of the most poignant moments at the conference came early, reflecting on a conversation that captured the essence of healthcare's purpose. A healthcare worker’s remark that "the quality of their work is measured in the number of heartbeats saved" resonated deeply, underscoring a fundamental truth often overshadowed by technological advancement: at the heart of healthcare is care itself. Despite the rush towards digitalization and the excitement around generative AI, the sessions emphasized a crucial message - technology must serve as an enhancer of care, not a detractor. It's not merely about implementing new tools but about integrating them thoughtfully into the workflows to support those at the frontline of patient care, ensuring technology amplifies rather than impedes the human touch.

Case Studies of Innovation in Action

A standout example of technology serving humanity was illustrated by Zipline’s initiative in Ghana, as discussed by their CEO, Keller Rinaudo Cliffton. Zipline’s aerial drones, designed to deliver essential medical supplies with GPS precision, epitomize how innovation can bridge the gap between technology and care. This venture not only showcases the practical application of AI and robotics in healthcare but also highlights the global potential of such technologies to save lives by overcoming logistical challenges. Dr. Rajagopalan's reflection on supporting such initiatives underscores Inflectra’s alignment with technologies that not only advance healthcare but do so with an unwavering focus on human welfare and equity.

Leadership in Healthcare Technology Adoption

Amidst the technological discourse, a recurring theme at HIMSS 2024 was the critical role of leadership in the ethical adoption of technology in healthcare. The insights shared reiterated that the path towards integrating AI and other technologies into healthcare practices begins not with the technology itself but with the people and processes it aims to serve. Echoing sentiments from healthcare leaders, the conference made it clear that the adoption of AI in healthcare transcends technical challenges, touching upon the need for a visionary approach that prioritizes ethical considerations, patient care, and the human element above all.

Need more HIMSS insights?

Check out these blogs:

The Evolution of Healthcare through Technology - Learnings from HIMSS

2024-05-04T20:26:48-04:00

Overview of HIMSS 2024

At the HIMSS 2024 conference in Orlando, FL, USA, Dr. Sriram Rajagopalan delved into the unique challenges and opportunities in the healthcare industry. The theme, "Creating Tomorrow’s Health", encapsulated the essence of the conference, aiming to shape the future of healthcare by harnessing the power of technology. As a premier global event, HIMSS 2024 gathered insights from numerous organizations, focusing on the integration of advanced technologies into healthcare.

Technology Innovations and Challenges in Healthcare

The conference was a melting pot of ideas and innovations, showcasing the evolving use of general AI and machine learning concepts in healthcare. Sessions spanned a range of topics, from preclinical and clinical studies to the application of large language models supplemented with reinforced learning. Discussions highlighted the critical need for navigating regulatory landscapes, such as HIPAA and addressing multidisciplinary risk management concepts that affect cybersecurity guidelines and clinical decision-making. The evolving technology landscape in healthcare demands an in-depth understanding and strategic approach to implementation, ensuring that advancements like AI and machine learning are effectively integrated into healthcare solutions.

Software's Pivotal Role in Modern Healthcare

At HIMSS 2024, the vital role of software in healthcare became unmistakably clear. From wearable continuous glucose monitors to emergency medicine beds and advanced diagnostic systems, the quality of diagnosis and patient care increasingly relies on sophisticated software solutions. Dr. Rajagopalan shared insights into the advancements in Picture Archiving and Communication Systems (PACS) using the Digital Imaging and Communication in Medicine (DICOM) standard, emphasizing the transition from merely storing images to enabling complex queries and improving the physician-patient experience through technology.

The HIMSS 2024 conference underscored the transformative power of technology in healthcare, from the integration of AI and machine learning to the indispensable role of software in diagnostics and patient care. As we navigate this evolution, it is clear that the future of healthcare lies in harnessing technology not just for innovation but for creating more effective, efficient, and empathetic healthcare solutions. Inflectra remains at the forefront of this journey, empowering healthcare organizations to embrace technology while ensuring quality and compliance.

Need more HIMSS insights?

Check out these blogs:

We Just Finished Our FDA Audit - Scheduled for 5 hours, Done in 90 Minutes With Spira

2024-03-25T10:45:02-04:00

What is an FDA Desk Audit?

An FDA Desk Audit for a software company, particularly those operating within the healthcare, medical devices, or pharmaceutical sectors, involves a review process by the U.S. Food and Drug Administration (FDA) to ensure compliance with regulatory standards and requirements. This type of audit is focused on assessing the company's documentation, processes, software development lifecycle, quality assurance practices, and any other relevant procedures or records that pertain to the design, development, production, and maintenance of software that may be used in medical devices or health-related applications.

Here are key points about an FDA Desk Audit for a software company:

Documentation Review: The FDA will request and review various documents that the company should maintain as part of its quality management system (QMS) and software development processes. This can include software design documents, development and testing methodologies, risk management files, and change control records.
Compliance with Regulations: The audit checks for compliance with relevant FDA regulations such as 21 CFR Part 11 (Electronic Records; Electronic Signatures), 21 CFR Part 820 (Quality System Regulation) for medical device manufacturers, and guidance on software validation, cybersecurity, and software contained in medical devices.
Remote Process: Unlike traditional on-site inspections, a desk audit is conducted remotely. The FDA reviews the provided documentation and may follow up with requests for additional information, clarifications, or virtual meetings to discuss findings.
Purpose: The primary goal is to ensure that the software developed and used by the company in healthcare applications meets safety, effectiveness, and quality standards, protecting public health.
Outcomes: Following the audit, the FDA can provide feedback, identify areas of non-compliance that need to be addressed, and in some cases, it can lead to further actions if significant compliance issues are found.

For software companies in the health sector, preparing for an FDA Desk Audit involves ensuring that their documentation is thorough, up-to-date, and readily accessible, and that their processes align with FDA expectations and regulations. It's an essential part of regulatory compliance for companies that contribute to medical technology and healthcare services.

Simplifying FDA Audits With SpiraPlan

Normally when a software company has to prepare for an audit, it will mean creating a lot of extra documentation and paperwork. In addition, during the audit itself, the team will have to find data from multiple different systems to prove to the auditor that they have followed their processes, and that each requirement/feature has all the necessary supporting information. For example, without using SpiraPlan, a team would need to provide the following information:

The formal requirements for the system (which could be MS-Word documents, Confluence pages, Sharepoint documents, or a formal requirements system such as DOORS)
The software development activities and tasks, often stored in a tool such as Jira, Azure DevOps, or Trello.
The software code, pull requests, code reviews and documentation on what was released. This is often in a combination of tools such as GitHub, GitLab, BitBucket, and Jenkins
The company/product risk register, which is usually in an Excel sheet or similar format
The release checklists, retrospectives and reports that show what was developed, tested and verified in a release. This may be in Jira, MS-Excel or multiple separate places
The documentation for the product, including any release validation certificates and associated reports, typically stored in a document management system such as Sharepoint, OneDrive or Google Drive
The quality assurance plan and associated testing artifacts, which could be in a Jira plugin like Zephyr or a separate test management system such as TestRail or qTest (or Excel sadly!)
The list of any bugs/defects that were raised either by users or internally during testing for the release. These would be in a bug tracker such as Jira, Bugzilla, Mantis or Azure DevOps
Any change management requests for infrastructure or services. These might be in a tool like Jira/ServiceNow or in a simple spreadsheet.
Any customer complaints and how those complaints get handled within the company. If the complaints relate to the product, traceability for how those complaints become product features/changes. The complaints are often in a support system like ZenDesk, FreshDesk or Jira ServiceDesk.

Typically reviewing all this information (as well as supporting processes and policies) will take anywhere from 5 hours to a whole day (depending on the maturity of the organization). The auditor will often pick a specific requirement from a release and follow it all the way through the process. Similarly they will pick a random customer complaint and follow its progression through the systems to make sure it was handled according to the process. For this reason, our auditor scheduled a 5 hour meeting with us.

However, on the day itself, using SpiraPlan, KronoDesk and some additional tools such as GitHub and SecureFrame, we completed the audit in 90 minutes. This was mainly due to the powerful traceability, auditability and compliance features of the Inflectra suite. Instead of navigating all the different tools listed above, everyone was available seamlessly in a single pane of glass in real-time.

Tracing a Requirement

Our auditor reviewed our recent release Spira v7.12 and viewed the requirements backlog for the release, picking a requirement at random:

In this case, they picked requirement [RQ:4700] which was part of the release. They wanted to make sure we had well-defined requirements in line with our software development lifecycle (SDLC) process. We were able to easily show that we had a user story defined for each of the features, along with a set of BDD Gherkin style scenarios that describe the different use cases of the requirement:

Next they wanted to make sure that we were following our development processes, with all code changes associated with this feature clearly defined and all code reviews and branch merges performed in accordance with our SLDC. In SpiraPlan this was just a matter of clicking on the Associations tab to show the code commits associated with the requirement as well as the different builds. You can see that this feature was merged from its feature branch to the GitFlow develop branch and then prior to release, the main branch:

Our auditor wanted to drill down to see what specific lines of code were included in the commit and what had actually changed. This was as easy as clicking on the commit link inside SpiraPlan:

Choosing one of the three files, we were then able to drill-down one level further and show the specific lines that had changed in the commit:

If we wanted to view the code reviews and pull requests, they are also just a click away inside SpiraPlan:

In our case, we manage the pull requests inside GitHub and use the SpiraPlan data synchronization with GitHub to see all of them in one place.

Next we were asked to prove that this specific feature had been fully tested. By simply clicking on the Test Coverage tab we could show the tests that had been run (and passed) prior to release:

In this example we have one automated unit test that is executing daily against the code in question (as part of our normal DevOps pipeline) as well as one manual (functional) test that a human QA tester performed on the feature.

Viewing the Release Details

Next our auditor wanted us to show her what was included in this release (and used to generate our public release notes). By simply choosing the release in question, we could use the Reqs & Tasks tab to show her all the pre-planned features that were included in the release:

Similarly, by clicking on the Incidents tab we could show all the bugs and minor enhancements also included.

This is what is used to generate the public SpiraDoc release notes:

We also use the Releases in SpiraPlan to manage our agile retrospective process. This is how we continually improve the quality of our process.

At the end of every release we conduct a Zoom meeting to review the release and capture what we should:

Start doing
Stop doing
Keep doing

Generating Validation Documentation

Now that we had traced a single requirement from ideation all the way through to release and then shown how we capture all of the items that will be included in the release, the final step was to show where all of the generated validation document is stored. At the end of every release we run the following reports, and store them inside the SpiraPlan document control system:

Requirements traceability matrix for all features
Requirements detailed report for the release
Test case detailed report for the release

This means that we can show any of the generated validation reports (current or historical) at the click on a button in SpiraPlan:

We also use this system to store our Product Validation Certificate which is supported by these documents.

Tracing a Customer Complaint

The final part of the audit was to demonstrate how we follow our defined customer complaint process. We chose the example of a customer complaint regarding a custom reporting feature that did not work correctly.

This was one of the incident that was included in the v7.12 release page that we showed previously. Clicking on the defect in question:

We were able to show that this defect originated from a support ticket logged by a specific customer in our KronoDesk help desk:

By clicking on the hyperlink inside SpiraPlan we could quickly show the originating customer support ticket / complaint:

This was the evidence necessary to show that we follow our customer complaint process and there is a mechanism for corrective actions to be tracked and ultimately be reflected in the product.

Conclusion

As you can see in the screenshots, using SpiraPlan (and KronoDesk) allowed us to conduct our FDA desk audit in less than a third of the time it would take using other tools and platforms - a 300% improvement! The best thing about using SpiraPlan is that it allows to you conduct your everyday tasks faster and more easily than a hodgepodge of other tools, yet integrates seamlessly with your DevOps pipelines, test automation tools and developer IDEs. When it's time for an audit, with no extra work, you are audit-ready out of the box.

The Spira Suite: Navigating Through SpiraTest, SpiraTeam, and SpiraPlan

2024-03-16T08:55:28-04:00

Unveiling the Distinct Editions of Spira for Every Team Size and Need

Here's an overview of what each edition offers:

SpiraTest®: Tailored for QA teams, SpiraTest represents the foundational tier of the Spira Suite. This edition focuses on delivering robust testing and quality assurance functionalities, fortified by the capability to manage and trace requirements throughout the testing process. It's the go-to solution for teams seeking to ensure software quality through comprehensive testing tools, from test case management and issue tracking to requirements management, ensuring a solid foundation for quality assurance endeavors.
SpiraTeam®: Occupying the middle tier, SpiraTeam expands on SpiraTest by integrating enhanced collaboration features, traceability, and a suite of tools designed for agile teams of all sizes. This edition elevates project management with the inclusion of planning boards and baselining—essential for sprint planning and managing product backlogs. SpiraTeam bridges the gap between quality assurance and agile development, facilitating seamless communication, project tracking, and requirement management. The platform enhances end-to-end traceability that extends from requirements to tests, tasks, incidents, and down to the code level, seamlessly connecting every crucial element of project management. SpiraTeam is crafted for teams striving for agility and efficiency, ensuring every facet of software development is aligned and traceable.

SpiraPlan®: The pinnacle of the Spira Suite, SpiraPlan, offers an enterprise-level platform that encapsulates all functionalities found in SpiraTest and SpiraTeam, and further elevates the suite by introducing capabilities for program and portfolio management, risk assessment, and resource planning. This edition leverages Spira's robust compliance support through built-in electronic signatures, highly configurable artifacts, and workflows. This flexibility allows users to tailor the platform to support their diverse enterprise processes and ensures adherence to stringent regulatory requirements. SpiraPlan is designed for organizations looking to scale their operations, fosterng strategic alignment across the enterprise.

The Spira Suite by Inflectra is an ecosystem designed to guide teams through the complexities of software development, testing, and delivery. From quality assurance to enterprise-wide strategic planning and execution, the suite offers a coherent, scalable solution for delivering critical software projects on time, without undue risk, turning industry regulations into competitive advantages.

Visualize Spira Product Suite: A Comprehensive Comparison Guide

Choosing the right Spira product for your needs has never been easier, thanks to our comprehensive product comparison guide. Whether looking at SpiraTest®, SpiraTeam®, or SpiraPlan®, the comparison guide will provide a clear overview to help you make an informed decision.

Stay Ahead with Inflectra: Never Miss an Update Again

You can also see more of Inflectra's upcoming events, product updates, company news, and more by subscribing to our monthly newsletter.

The Inflectra Team

Inflectra at DevOps Live London 2024

2024-03-09T11:43:01-05:00

Overview of DevOps Live 2024

Attending DevOpsLive in London is highly beneficial for professionals and organizations vested in the fields of DevOps, Cloud Computing, AI, Continuous Testing, and IT Infrastructure. If you're interested in attending next year, here are some compelling reasons to consider attending:

Networking Opportunities: DevOpsLive attracts a diverse group of attendees, including DevOps professionals, IT experts, software developers, and business leaders. This provides an excellent opportunity to network, exchange ideas, and form valuable connections.
Educational Sessions: The event features a wide range of talks, workshops, and seminars led by industry experts. These sessions cover the latest trends, tools, practices, and challenges in DevOps, offering attendees insights into how they can improve their practices and overcome common obstacles.
Exposure to Latest Technologies: With numerous exhibitors showcasing their latest products and services, attendees can get hands-on experience with the newest technologies and tools in the market. This exposure is invaluable for staying competitive and innovative in the fast-evolving tech landscape.
Expert Advice and Consultation: Many exhibitors and speakers at DevOpsLive offer personalized advice and consultation. This can be a great opportunity to discuss specific challenges and solutions with experts, gaining insights tailored to your unique needs.
Comprehensive Learning Experience: Since DevOpsLive is part of Tech Show London, attendees have access to multiple co-located events covering areas like Big Data, AI, Cloud Security, and Data Centres. This allows for a broader learning experience across various IT disciplines.
Career Opportunities: The event can be a platform to discover new career opportunities. Many companies participate in these events to find talent, and being present could lead to job offers or collaborations.
Stay Ahead of Industry Trends: The rapid pace of change in technology means that staying updated is crucial. Attending DevOpsLive offers a condensed overview of current and emerging trends, helping you stay ahead of the curve.
Community Building: DevOps is as much about culture as it is about tools and practices. Events like DevOpsLive foster a sense of community among practitioners, encouraging the sharing of best practices and collaborative problem-solving.

In summary, DevOpsLive in London can offer a rich and diverse experience that encompasses learning, networking, and exposure to the forefront of DevOps and related technologies, making it a valuable event for anyone looking to advance in these fields.

Meeting up With Inflectra Partners

#1 AppCircle

It was nice to reconnect with David Rakusen and Mete Baydar of AppCircle at DevOps Live. We are excited to be partnering with them. Their mobile devops orchestration and development platform is the perfect complement to our Rapise - Codeless Test Automation tool for iOS and Android devices.

#2 Curiosity Software

It was nice to meet James Walker, Ben Riley, and Joshua England from Curiosity Software at DevOps Live. We are very excited to have them join our partner ecosystem. Their unique capabilities around test data generation and management will be a game changer for our customers.

#3 Tezza Business Solutions

It was nice to meet Jide Modele from our partner Tezza Business Solutions in person in London. We discussed how compliance and banking regulations can be a driver for quality and good devops practices.

One More Thing

For some reason, two of the exhibitors had decided to bring along a fully decked-out, road-worthy Delorian (DMC) time machine from Back to The Future!

It was super cool, with working flux capacitor, plutonium chamber and time circuits, we just had to hit 88mph....

Inflectra's Experts Explore the Power of Generative AI in Software Development

2024-02-28T14:23:08-05:00

The webinar commenced with an exploration of Generative AI's role in streamlining various facets of the SDLC, enhancing productivity, and fostering innovation. Panelists discussed how AI-driven solutions are reshaping traditional methodologies, offering new avenues for efficiency and creativity in software development processes.

Recording:

Key Highlights:

Panel Discussion on GenAI in SDLC: The expert panel, comprised of industry veterans Adam Sandman, Dermot Canniffe, and Simon Bor, provided valuable insights into how GenAI is streamlining software design, development, testing, and deployment processes. Attendees gained a deeper understanding of how AI-driven solutions are enhancing productivity and fostering innovation across various stages of the SDLC.
Implementing AI: Challenges Ahead: The webinar featured a pragmatic discussion on the hurdles of AI integration, led by the panelists. Participants received essential strategies for navigating the complexities of AI adoption without compromising quality. The conversation shed light on the importance of addressing implementation challenges to maximize the benefits of AI technologies effectively.
Inflectra's AI Roadmap: Attendees received an exclusive sneak peek into Inflectra's latest GenAI addition to Spira and Rapise - Inflectra's automation platform. This unveiling provided attendees with valuable insights into how Inflectra is harnessing the power of AI to enhance its suite of products, empowering users with advanced automation capabilities.
Engaging Q&A Session: moderated by Dr. Sriram Rajagopalan, attendees had the opportunity to pose their burning questions to the panelists, fostering insightful discussions and furthering their understanding of GenAI's implications for software development.

Stay Tuned for Updates

We extend our gratitude to all participants and panelists for making this webinar a resounding success. Stay tuned for more upcoming events, product updates, and industry insights from Inflectra by subscribing to our monthly newsletter.

Maximizing Project Performance with Spira: A Guide to Lead and Cycle Time Metrics

2024-03-05T17:20:32-05:00

Your ability to measure and analyze project performance with precision is as critical as ever. This is why we are introducing the Lead Time and Cycle Time metrics that enable more efficient workflows, improved time management, and enhanced productivity and provide you with insightful glimpses into the overall health and agility of your project management processes. To this end, we've compiled a series of Knowledge Based articles aimed at empowering you to master the computation and analysis of these metrics within the Spira suite of products.

Part 1: Unlocking the Potential of Lead Time and Cycle Time

The first step in this journey involves a deep dive into the definitions of Lead Time and Cycle Time, elucidating their significance and how you can effectively measure them within Spira. Lead Time represents the total duration from when a task, requirement, or defect is initiated until it is completed, offering a lens through which the customer's perspective on process efficiency can be viewed. Cycle Time, on the other hand, zeros in on the active work phase—from the start of work on a task to its completion—providing critical insights into the effectiveness of the development process.

We detail the essential prerequisites needed within Spira to accurately compute these metrics, including the formulation of a detailed SQL query and the provision of step-by-step guidance for configuring the default XSLT template. We hope this will provide you with the knowledge and tools necessary to measure, understand and enhance your project workflows, thereby navigating the complexities of project timelines with informed precision.

View the details in the KB article here: Creating the Report for computing the Lead Time and Cycle Time - Part 1

Part 2: Data Integrity: The Backbone of Accurate Metrics

The integrity of your project data stands as the foundation upon which meaningful analysis of Lead Time and Cycle Time metrics is built. This critical KB article underscores the importance of maintaining accurate data entries in specific date fields to enable the effective graphical aggregation of these pivotal metrics in your task modules. We included a rigorously developed SQL query to assist in diagnosing and rectifying any discrepancies in task dates, thus preserving the integrity of your project metrics.

Furthermore, we outline a thorough process for updating any incorrect data, ensuring that your project’s lead and cycle times accurately reflect the true efficiency and productivity of your processes. It identifies the notable exceptions to standard date handling within Spira, such as provisions for external data integration and instances where tasks are recorded after the commencement of work, offering insights into Spira’s adaptable and user-centric approach to project data management.

By adhering to the instructions and utilizing the diagnostic tools provided, you can enhance the precision of your data, and effectively graph Lead Time and Cycle Time. This will help you visualize project timelines and empowers you with the data-driven insights necessary to refine your workflows, and expedite project delivery.

View the details in the KB article here: Addressing incorrect data before graphing Lead Time and Cycle Time - Part 2

Part 3: Visualizing and Analyzing Process Efficiency

Understanding the nuances between Lead Time and Cycle Time enables you to identify opportunities for improvement in both customer satisfaction and internal process efficiency. This 3rd KB article in the series advocates for the use of graphical representations, such as histograms, to better visualize these metrics.

Cycle Time Histogram example

Such visuals need the confirmation of the accuracy of your data set for the Lead and Cycle Time queries, increasing the reliability of the resulting insights.

For Lead Time, we describe a SQL query that aggregates data into intervals, capturing the number of tasks, requirements, or defects completed within specific time frames to illustrate distribution patterns and identify efficiency trends. Similarly, Cycle Time analysis adopts this method but focuses on the active work phase, allowing for a detailed examination of your process efficiency and the highlighting of potential bottlenecks and inefficiencies.

View the details in the KB article here: Graphing the Lead Time and Cycle Time - Part 3

Achieving Excellence in Your Project Management with Spira

By synthesizing the insights from these KB articles, we aim to provide you with a robust framework for optimizing your project management practices. Mastering the computation and application of Lead Time and Cycle Time metrics within Spira will support you through the intricacies of project management, enabling you to harness the full potential of these metrics to drive your projects to successful completions.

Embrace the power of SpiraPlan, and witness the transformative impact of accurate metrics and informed decisions on your project outcomes.

Team Inflectra

From 8-Bit Beginnings to Inflectra Now: A Story of Diversity, Inclusion, and Social Impact in Tech

2024-02-24T16:30:02-05:00

Early Inspirations: A World of Possibilities

As the founder of Inflectra, my journey into entrepreneurship and technology wasn't a straight path but rather a series of pivotal moments and interests that guided me to where I am today. Growing up in South Wales during the 1980s, amidst the backdrop of Margaret Thatcher's era of deregulation and privatization, I was captivated not just by computers and technology but also by the allure of business. This fascination wasn't typical among my peers, who largely aspired toward conventional professions. My entrepreneurial spirit was kindled early on; at the tender age of 10, I was already dabbling in writing computer software, ranging from 8-bit games to basic application software, and attempting to sell them, albeit with mixed success.

A Pivot to Technology: The Ice Cream Epiphany

My academic path led me to Physics, a subject I chose out of my love for science. Yet, the laboratory's confines soon felt limiting. The magic happened over ice cream with a friend who introduced me to the burgeoning field of IT consulting. This casual conversation sparked a realization: my passion for technology could merge with my interest in business. This fateful meeting led me to emigrate to the United States in 1998, embarking on an eight-year tenure with Sapient across Boston, Los Angeles, and Washington, D.C. This is where the seeds of Inflectra were sown.

The Genesis of Inflectra: Filling a Market Void

The genesis of Inflectra was born out of my experiences at Sapient and a serendipitous realization of a gap in the market for modern, agile requirements, test, and project management systems. This led to the launch of our first products, SpiraTest and SpiraTeam, in 2007. My transition from a consultant to an entrepreneur was fueled by a desire to address the industry's need for affordable, agile-focused tools in software project management. Inflectra was not just a business venture; it was a path to democratizing access to cutting-edge software development tools.

Learning Through Mistakes: The Insurance Oversight

In the early days of Inflectra, nestled within the comfort of our home offices, a humorous yet foundational mistake served as a pivotal learning moment for me. We had just begun making our mark, primarily serving small and medium businesses across North America and Europe, with a team no larger than four. Wearing multiple hats—from legal counsel to CEO—I had overlooked the necessity of business insurance. This oversight came to light in a rather unexpected setting: a neighborhood party. While discussing the nature of our business with an insurance broker, his reaction was one of disbelief, humorously exclaiming, "When did you think you would need some insurance when there was a claim!" This interaction led us to secure a comprehensive insurance portfolio, teaching me the invaluable lesson of preparedness and the importance of seeking experienced guidance to navigate the business landscape. It underscored the need for a culture that not only embraces learning from its mistakes but also values mentorship and foresight.

Cultivating Diversity and Inclusion: More Than a Policy

At Inflectra, we hold a core value dear to our heart: "New Beginnings." This ethos is born out of a belief in offering opportunities to individuals from diverse backgrounds and career paths. For instance, our head of marketing initially worked in human rights, and our head of products was a policy analyst for the UK government. These individuals, among others, brought latent skills that were previously overlooked. By collaborating with local coding meetup groups, we've extended opportunities in software development and testing to those self-taught or without a formal college education—talents often ignored by traditional HR practices. This approach reflects our commitment to seeing beyond the resume to the individual's potential and passion.

Recognizing the importance of inclusivity and support, we ensure that both part-time and full-time employees receive equal benefits, including four weeks of vacation and all Federal holidays. This policy particularly aids part-time workers, often stay-at-home parents eager to re-enter the workforce as their children grow older. It's our way of making it easier for parents to transition back into professional roles, reinforcing a culture that values family and life flexibility.

Our dedication to diversity is evident in our team composition and leadership. With approximately half of our employees being female and a leadership team that mirrors this balance, we strive to reflect the diversity of our global customer base. This diversity is crucial for us to serve as effective stewards of our customers' trust and to embody our core value of building for our users, not for Wall Street. It's a testament to our commitment to creating a work environment that values and leverages diverse perspectives for better decision-making and innovation.

Embracing a global perspective, we engage with customers and employees from around the world, understanding that the "American" business culture is not the universal norm. This global engagement has taught us the importance of cultural sensitivity and the value of diverse viewpoints. Whether it's adjusting to direct feedback styles in the Netherlands or fostering understanding across varying political and cultural spectrums in the U.S., these experiences have enriched our company culture with a deep appreciation for the global tapestry of our customers and people.

Using Success for Good: The Global Technology Initiative

The success of Inflectra has provided us with opportunities to give back. It enabled us to launch the "Inflectra Global Technology Initiative," an ambition to replicate the success we witnessed in Buenos Aires on a global scale. This initiative is a testament to our commitment to leveraging technology for social good, aiming to empower communities around the world.

One of the most profound experiences came from a trip to Buenos Aires, where Inflectra's software became more than a tool—it became a beacon of hope. Through the "Codo a Codo" program, we taught software testing to those looking to change their lives. This mission was a vivid reminder of technology's power to make a real difference in people's lives, reinforcing my belief in using business as a force for good.

Reflecting on Inflectra's journey, from pivotal learnings to our commitment to diversity, inclusivity, and global engagement, it's clear that our culture is a reflection of our collective experiences and dedication. For leaders looking to build a vibrant company culture, the key lies in embracing what makes your company unique and allowing this to shape your core values and operations. At Inflectra, we view our culture as the foundation of our success, fostering an environment where innovation thrives, and every individual can make a meaningful impact.

Adam Sandman founded Inflectra in 2006 and serves as the company's CEO. He is responsible for product strategy, technology innovation, and business development. He lives in Washington, D.C., with his family. Prior to founding Inflectra, Sandman worked as a director for Sapient Government Services, where he was in charge of development with the U.S. Marine Corps. and other government agencies, and was responsible for leading many capture teams and writing whitepapers and position statements to build Sapient’s reputation as a leader in the defense space. He studied physics at Oxford University.

Spira vs. JIRA+Plugins: Witness a Game-Changing Shift in Project Management Excellence

2024-02-20T15:17:44-05:00

Recording

Slideshow

Why SpiraPlan Reigns Supreme

Integration & Usability: SpiraPlan offers a seamless experience from project initiation to closure, boasting superior traceability compared to the patchwork of plugins in JIRA. With SpiraPlan, users have access to an all-in-one command center for project excellence, eliminating the frustrations associated with managing multiple plugins.
Comprehensive Feature Set: SpiraPlan's integrated suite empowers users to master project quality, tasks, and risks without the disjointedness of JIRA's plugins. Embedded best practices and the ability to establish project baselines with ease ensure smoother navigation of compliance requirements.
Cost-Effectiveness & Efficiency: One of the most significant advantages of SpiraPlan is its straightforward pricing model, free from hidden costs often associated with JIRA's piecemeal plugins. Users can save valuable time with SpiraPlan's leaner approach, avoiding the hassle of managing numerous plugins. Additionally, SpiraPlan offers legendary support, surpassing the complex and time-consuming support structure of JIRA's plugins. The straightforward licensing model of SpiraPlan further simplifies the process, avoiding the licensing labyrinth often encountered with JIRA.

Embrace SpiraPlan

Say goodbye to the frustrations of plugin management. Theis webinar served as a compelling showcase of SpiraPlan's capabilities, heralding a new era in project management excellence. Attendees left with a clear understanding of why SpiraPlan stands as the premier choice for teams seeking to elevate their productivity and compliance to championship levels.

Click here to start your 30-day free trial for SpiraPlan, and embark on a transformative journey in project management.

Why Embrace Kanban for Enhanced Business Agility? Insights From Kanban India 2023

2024-02-16T15:12:22-05:00

Understanding Kanban Through Interactive Learning

Today, understanding the nuances of implementing Kanban can significantly elevate an organization's operational efficiency and responsiveness to market changes. Dr. Rajagopalan's workshop illuminated this path, moving beyond the conventional "To Do, Doing, Done" boards to reveal Kanban as a sophisticated system supporting vertical and horizontal value flows. The workshop employed an engaging game to demystify Kanban, breaking down its principles into digestible, actionable insights.

Dr. Rajagopalan's innovative use of a game demonstrated that this type of hands-on experience is crucial for professionals across all sectors, demonstrating that the essence of Kanban lies in its ability to streamline processes and facilitate continuous improvement, making it a pivotal skill set in today's fast-paced business environment.

Real-World Applications And Misconceptions

Dr. Rajagopalan shared two specific case studies of Kanban Implementation from his work in two industries. By sharing case studies from his rich experience, Dr. Rajagopalan shed light on common pitfalls in Kanban implementation, such as role-based card confusion, siloed operations, and a lack of explicit governance policies. These insights are invaluable, offering lessons on the importance of maintaining a value-centric mindset over merely managing tasks and inventories. Understanding these practical gaps allows organizations to leverage Kanban more effectively, ensuring that Agile boards enhance rather than hinder workflow and collaboration.

Kanban's Foundational Principles for Business Agility

The workshop illuminated the core principles of Kanban, such as Kaizen and Kaikaku, underscoring the methodology's depth beyond the Agile and Scrum frameworks. These principles guide organizations in adopting a holistic approach to improvement, emphasizing the importance of systems thinking, resource optimization, and proactive problem-solving. For businesses seeking to enhance their agility, adopting these principles means thriving in the competitive landscape.

STEP Approach to Business Agility

Dr. Rajagopalan's STEP approach provides a personalized roadmap for integrating Kanban with other frameworks - SAFe, Disciplined Agile, and the Kanban Maturity Model (KMM) - offering a bespoke strategy for each participant to enhance business agility and bridge the gap between theory and practice, demonstrating how Kanban can streamline application lifecycle management.

This aspect of the workshop underscored Dr. Rajagopalan's (and Inflectra's) commitment to delivering solutions that cater to the unique needs of customers, empowering them to navigate the complexities of scaling Agile with confidence and precision.

Conclusion

Dr. Rajagopalan's workshop at Kanban India 2023 represents more than just a session on Agile methodologies; it's a testament to the potential of Kanban to revolutionize how organizations approach project management, team collaboration, and value delivery. Understanding and implementing these insights can lead to more efficient, responsive, and competitive operations for professionals and leaders in any industry.

Dr. Sriram Rajagopalan, Enterprise Agile Evangelist, Inflectra

Stay ahead of the curve by subscribing to our newsletter for the latest insights and updates from inflectra's experts.

Building Resilient Software: Traceability in Systems That Run The World

2024-02-06T15:34:19-05:00

Consider the infamous software bug in the Ariane 5 rocket's maiden voyage in 1996. A single untraceable piece of legacy code repurposed without due diligence from its predecessor, Ariane 4, led to the rocket's destruction mere seconds after liftoff.

This incident, which resulted in a loss of approx. $370 million underscores the dire consequences of overlooking traceability in complex engineering projects. It was a failure to adequately map and understand the dependencies and potential points of failure across the system's architecture—a costly oversight that could have been mitigated with rigorous traceability practices.

Ariane 5 rocket, source: Wikipedia

Why Traceability?

In the complex web of modern engineering, traceability serves as the linchpin for dismantling the specter of single points of failure — those Achilles' heels of systems where a singular malfunction can precipitate a cascade of dysfunction. The art of tracing every thread in a project, from requirements to the final implementation and testing, is a technical exercise but, more importantly, a strategic imperative. It lays bare the intricate dependencies and interconnections that define a system, spotlighting potential vulnerabilities that, left unchecked, could spell disaster.

This meticulous mapping and monitoring does more than just illuminate risks; it gives engineers the foresight needed for robust impact analysis. When the unexpected strikes, as it inevitably does, the ability to predict the ripple effects of a failure across the system is invaluable. It transforms the seemingly insurmountable task of safeguarding against SPOFs into a manageable one, enabling the design of architectures that can withstand shocks and continue operating seamlessly, thus ensuring system resilience. Moreover, traceability enriches the decision-making process. With a clear view of the system's blueprint, engineers are better equipped to architect redundancies and fail-safe mechanisms. This approach enhances system reliability and optimizes resource allocation—ensuring that backups are a seamlessly integrated component of the overall design.

In the relentless pursuit of improvement, traceability acts as a compass, guiding ongoing reviews and refinements. It ensures that as systems evolve, so too does the strategy for mitigating SPOFs, thus future-proofing against known and unforeseen challenges. In regulated industries, where the stakes for reliability and compliance are sky-high, the role of traceability in documenting and demonstrating adherence to stringent standards cannot be overstated.

Traceability at Inflectra

At Inflectra, our portfolio of software solutions, encompassing SpiraPlan and Rapise, is at the forefront of embedding traceability into the fabric of software development. We build platforms that empower teams to engineer systems that are resilient, risk-adjusted, and compliance-focused. In doing so, we champion a future where software is built to last and excel, strengthening reliability in an unpredictable world.

At Inflectra, where the stakes of engineering precision and reliability are understood, our suite of tools serves as the linchpin for ensuring that every element of a software project is meticulously traced, analyzed, and accounted for. These tools are not merely software solutions; they focus on eliminating SPOFs through unparalleled visibility and control over every stage of the development lifecycle.

By blending traceability with agile development methodologies, we strive to address the technical requirements of project management and embed the imperative of resilience and quality assurance. This approach has empowered our customers, spanning industries from healthcare to aerospace, where the margin for error is infinitesimal, and the cost of failure extends beyond financial loss to include potential impacts on human lives and safety.
Every day, we work to safeguard against engineering failures and encourage a future where innovation is matched by an unwavering commitment to reliability and excellence. In 2024, we shift our focus from traceability being critical for averting failure to consciously designing software to succeed in an ever-changing world, one line of code at a time.

by Adam Sandman, CEO, Inflectra

Webinar Recap - Spira Unbound: The Unveiling of Spira's Latest Enhancements

2024-02-02T15:43:33-05:00

Why SpiraPlan?

SpiraPlan stands out as a top choice for project management due to its user-friendly interface, powerful collaboration features, and effective project planning tools. Its emphasis on real-time communication and seamless teamwork, coupled with an intuitive design, makes it an ideal solution for both beginners and experienced project managers. SpiraPlan's robust capabilities in planning, resource allocation, and progress tracking, along with customizable reporting and analytics, make it a comprehensive and efficient project management tool for successful project outcomes.

Recording:

Product Enhancements:

Enhanced Dashboard Widgets: Advanced widgets on the program home page for real-time visibility into program milestones and capabilities.
Upgraded Reporting Functionality: Sophisticated filtering and sorting for program-level reports, along with customizable graph options on the reporting page.
Comprehensive Tagging System: Extended tagging across various artifacts, including documents, requirements, releases, tasks, and incidents, bolstered by an improved user interface.
ChatGPT Integration: Integration of OpenAI's ChatGPT in Spira, enabling automated generation of test cases, requirement steps, or tasks from user-defined requirements.
Program Management Tools: New widgets for monitoring capability statuses and milestone progress, with customization options for a tailored program management overview.
Program Level Reporting Filters and Sorts: Refined data representation through customizable filters and sorting capabilities in program-level reports, enhancing data-driven decision-making.

Try it Yourself!

Choose SpiraPlan to upgrade your project management. Click here to begin your free 30 day trial.

Generative Artificial Intelligence (GenAI) in Quality Assurance - State of the Art in 2024

2024-01-30T17:57:47-05:00

Disclaimer: As with any discussion around the ‘state of GenAI’, the capabilities improve daily, so what is written here may well be superseded in short order!

1. Testers are Developers/Teachers

With AI, testers can now teach and train the Large Language Models (LLMs) to understand the application(s) being tested. As described in this Microsoft document, Teachable Agents are a way to get around the limitation of LLMs where conversational assistants (such as ChatGPT) “forget” their learnings in between sessions. From the document:

“Teachability addresses these limitations by persisting user teachings across chat boundaries in long-term memory implemented as a vector database. Instead of copying all of memory into the context window, which would eat up valuable space, individual memories (called memos) are retrieved into context as needed. This allows the user to teach frequently used facts and skills to the teachable agent just once, and have it recall them in later chats.”

So, the role of the tester is to write prompts for the AI to perform tasks and test the application for the tester. The tester identifies incorrect or incomplete answers and 'teach' the system by correcting its thoughts by providing some facts or examples. With this approach, fixing is immediate and testing becomes a matter of fine-tuning.

2. Automation and Exploratory Testing Blends

Previously test automation was seen mainly a form of “checking” or regression testing, i.e. preventing existing errors or known issues from reoccurring. The move from traditional “scripted” manual testing to free-form exploratory or session-based testing was seen as the better use of human testers, with the scripted tests being automated.

However, with AI, a lot of exploratory testing can be potentially automated. For example, in this paper on how to use GPT-4V for testing, it was found to be a viable solution for navigating an iOS device, selecting the right application and executing a series of prompted tasks:

(Reproduced from the paper referenced above)

In the example above. The GPT-4V bot was able to complete the tasks on the iOS device, provide screenshots as to the actions, and even generating textual reasoning as why they were completing the task in a specific way and whether they succeeded or failed at the task.

The role of the human tester in this scenarios would be to view the results, understand if it was correct and complete, and if not, tune/teach the model to improve the results.

From the Inflectra point of view it is realistic to expect that the "Play" button for a manual test in our Spira test management tool would just work without human interaction! Similarly, Inflectra hosts a software testing competition called the “SoftwareTestBowl”. At some point (just like have seen with Chess and Go), GPT will start winning in such testing competitions. This is a good example of how fast the AI world is moving.

3. Scenario Generation

Another major area that AI is changing is the creation of test scenarios themselves. For example, it will make sense to have an AI-based recorder that simply watches the user performing a task and generates an audio and/or textual description of the scenario.

This is already a valuable tool when conducting UX/UI usability interviews and assessments. The AI can look at the user performing a task and generate a summary transcript and list of tasks. The next step will be for the AI to be able to make recommendations based on common design patterns.

From the Inflectra point of view, one area of promising functionality is the ability to simply upload/draw the sketch of a proposed application into Spira and have Spira generate the full specification for it. For example, using the free LLaVA: Large Language and Vision Assistant and the Library Information System sample web application:

When you ask it: “This is a web software application. Can you generate the specification for it?” you get:

The image you've provided appears to be a screenshot of a web-based application interface for a library information system. Based on the visible elements, I can infer some of the features and functionalities that this application might have. Here's a speculative specification for the application:

Application Name: Library Information System

Purpose:
The Library Information System is a web-based application designed to manage and organize library resources, including books, authors, and genres. It aims to provide librarians and library staff with a user-friendly interface to catalog, search, and maintain their library's collection.

Features:

Book Management:

Ability to add new books to the system.

Fields for book details such as title, author, genre, and publication date.

Option to edit book details.

Fields for additional information like ISBN, publisher, and number of copies.

Ability to mark books as "Out of Print" or "In Print."

Author Management:

Fields for author details such as name, birth date, and death date.

Option to add multiple works by the same author.

Ability to link authors to their works.

Genre Management:

Fields for genre details such as name and description.

Option to add new genres.

Ability to link genres to books.

Search Functionality:

Advanced search options to find books by title, author, genre, and other criteria.

Ability to filter results by availability (in print/out of print).

User Interface:

Clean and intuitive layout for easy navigation.

Responsive design for use on different devices.

Clear and concise error messages for user feedback.

Security:

Secure login system for authorized users.

Role-based access control to restrict certain actions to specific users.

Data encryption for sensitive information.

Database Integration:

Backend database integration for efficient storage and retrieval of data.

Ability to import and export data in standard formats.

Reporting:

Generating reports on book circulation, author popularity, and genre trends.

Customizable reports to suit the needs of the library.

User Support:

Online help or FAQ section for user assistance.

Contact form for user inquiries.

Scalability:

Designed to handle a large number of books, authors, and genres.

Ability to add additional fields or modules as needed.

Technical Requirements:

Operating System: Compatible with modern web browsers (e.g., Chrome, Firefox, Safari, Edge).

Database: MySQL, PostgreSQL, or other relational database management systems.

Server Requirements: Apache, Nginx, or other web servers capable of running PHP or similar scripting languages.

Front-end Technologies: HTML, CSS, JavaScript, and possibly frameworks like React, Angular, or Vue.js for a responsive and interactive interface.

Back-end Technologies: PHP, Python, Ruby on Rails, or similar server-side scripting languages for database interaction and business logic.

Development Process:

Requirements gathering and analysis.

Design and prototyping.

Development and testing.

Deployment and maintenance.

Conclusion:
The Library Information System is a comprehensive web application designed to streamline library operations, from cataloging to searching and reporting. It is intended to be user-friendly, secure, and scalable to meet the needs of libraries of various sizes.

From this structured description we can create in Spira a list of:

Requirements and user stories
Test cases and BDD scenarios
Development tasks
Infrastructure requirements

With additional prompting, we can generate derived items such as project risks and include them in the Spira project model.

4. New Testing Subjects

Although (as we have seen), using AI can improve the productivity and efficiency of testing existing applications, GenAI itself requires testing, and that introduces new types of testing:

How do we test for AI hallucinations, insertions and “laziness”?
Previously we had things to check for things like "memory", and "disk space". What new things do we have now (dreaming? incompleteness? instability? GPU usage? request window size?)
Intermittency. Since all responses differ, we need to repeat all requests several times when testing GPT to make sure the response stays valid.
There will be new types of applications to be tested such as chat-bots, voice-based applications.
Security testing where the CAPTCHAs are meant to stop bots, but if they can be overcome by bots, how do we check for humans?
- Should applications care any more who is using them?
- GPT input vs human input. What happens when we don't want to allow our system to be used with another GPT system?
New User Interface (UI) Paradigms
- We had grids, trees with a summary.
  - Now we may produce a text summary about anything.
  - We may draw anything (picture of the day) or produce graphs in arbitrary format (org structure in anime style).
- How we do we test these new UI elements?

5. Testing Fluid AI Apps

In section 3 we talk about AI generating scenarios, the next level is that AI will be able to take the same sketches and prototypes and develop the actual applications. These “fluid” applications will be capable of being “regenerated” every day as the requirements change. From Agile to DevOps (and CI/CD) to continual development.

Imagine that we want to create a pizza ordering app:

Do we need to ask the AI to "write requirements for pizza app"?
Or we may prompt "Write pizza ordering app & create tests for it"?
Or just say "Write a fully tested pizza application" and that's it.
Then check and say what you want to be modified in it and it will re-write the application.

I.e. We can skip all the planning/requirements/test stages because they are done implicitly in few seconds. But then the next level could be:

Do you still need an app whatsoever?
The customer will say to Bing "I want pizza”, and the rest is generated “on the fly”.

However, how do we test these dynamic, AI-composed applications? Their functionality, structure and features will change continuously, making it difficult to know what’s the correct behavior. We need to do some regression... Somehow..!

6. Reporting & Analytics

There are new ways for reporting and analytics to be created using AI:

New summary report - summarize documents. Summarize information based on text request.
New reports like "What is unusual in the activity?"
Visualization - ask to draw a graph using a text prompt. The prompt may describe both data and view.
Find 10 most clearly defined incidents and 10 most vague ones
Map queries
- Find regions with a lack of drug stories.
- Find similar "shops" that are too close to each other.

These are complex to test and make it more difficult to create test scenarios without context. The tester (either human or AI) needs to apply “reasoning” to determine if the system is behaving as desired.

7. AI Laziness

When using AI to do testing, there are some limitations due to AI “laziness” that need to be considered:

AI Stops after finding the first match. Inability to find all.
AI may find some results, not everything.
AI may lie or misrepresent facts
AI has a limited context window. This means it may read only limited input to draw its conclusions.
AI tends to forget the middle. It is focusing on the beginning and end of the request.

8. Cost Considerations

Ironically, the latest GPT-4 models are expensive to use and unless the results from the prompts are cached, using them for testing is currently more expensive (in terms of number of tokens) than using human testers/designers.

However, that will change in the future.

The simpler GPT-3.5 Turbo models are currently cost-effective and can be used for more limited tasks, as we’re demonstrating already with the Inflectra Spira AI functionality that generates risks, test cases, scenarios and tasks using GPT-3.5.

To make GPT-4 models cost effective at present, you need to use token optimization strategies such as using the Teachable Agents and vector databases that we discussed in section 1.

Conclusion

As you can see in this article, we are witnessing a real-time revolution in how AI can help make software testing easier, while simultaneously creating new types of application to be tested, and new ways we need to think about testing. Clearly 2024 will be an interesting year in testing!

Inflectra In the News - January 2024 News Roundup

2024-04-05T16:33:00-04:00

Podcasts

Unleashing Innovation: Adam Sandman, Founder & CEO of Inflectra Corporation | Think Big Podcast with Zing - December 27, 2023

Embark on an inspiring journey with Adam Sandman, the brilliant mind behind Inflectra Corporation, as he joins us on "Think Big with Dan and Qasim." In this captivating episode, we delve into the depths of Adam's entrepreneurial spirit and explore the evolution of Inflectra from its inception to its current status as a pioneering force in the tech industry. Watch now.

Gen AI in the workplace By Adam Sandman and Harsh Wardhan with Global Skill Development Council - January 6, 2024

In this episode, we dive into the impacts and implications of using next-generation AI technologies in the modern gen ai workplace. How will advanced AI systems like large language models change how we work and collaborate? What new opportunities and innovations will this enable? But also - what potential risks and challenges do we need to be aware of? Watch now.

Understanding the US Business Landscape | Always An Expat with Richard Taylor by Plan First Wealth - January 9, 2024

Richard Taylor interviews Inflectra CEO Adam Sandman about his UK to US expat journey, covering family life, cultural differences, and work-life balance. They delve into alternate histories, parenting influences, and the economic constraints of the American experience, exploring social networks, the journey from Swansea to DC, and the American Dream's impact on business values. The discussion ends with reflections on the financial cost of turnover and a glimpse into the future and the next generation's horizons. Listen now.

Publications

Top 4 Tech Predictions for 2024 with Dice - Dec 27, 2023

In the dynamic landscape of 2024, technological advancements are reshaping industries. Detachable Artificial Intelligence (AI) emerges as a pivotal concept, securing sensitive data by encapsulating large AI language models locally. Simultaneously, Software-Defined Manufacturing replaces hardware with versatile software, and healthcare witnesses a surge in Computer-Augmented Telemedicine. The rise of Augmented Reality Advertising signals the end of traditional billboards, ushering in personalized, location-tailored ads. As we enter 2024, these technological shifts promise an exciting era of innovation across diverse sectors. Read more.

Tech and Mobile App Predictions from Inflectra for 2024 with App Developer Magazine - January 3, 2024

The year 2024 is upon us and, with it, some of the biggest changes technology has ever brought to multiple industries. Technological innovations and mobile applications promise to create seismic shifts across countless sectors, from the healthcare industry and manufacturing to military and defense. Adam Sandman provides five ways developments in technology and mobile applications will forge into the unknown and forever change the landscapes of many markets. Read more.

17 Clear Signs It’s Time To Outsource IT Operations with Forbes Technology Council - January 9, 2024

Not every small or midsize business is fortunate enough to have the resources for an in-house IT team. Even those that do may find that, in today’s digital workplace, their IT teams are struggling to keep up with everything asked of them. Whether it’s budgetary concerns, new or unusual requirements, or another reason, sometimes it’s in a business’ best interest to consider at least partially outsourcing its IT operations. In this article, Adam Sandman shares his insight on when a business needs to consider outsourcing one or more of its IT functions. Read more.

Five Predictions for How Innovations Will Continue to Redefine Industries in 2024 with VMblog - January 10, 2024

In 2024, industries are on the brink of transformative change driven by groundbreaking technologies. Adam Sandman, Founder & CEO of Inflectra, predicts five key shifts, including increased defense agility, AI-assisted healthcare kiosks, enhanced data privacy through AI models, the replacement of hardware with software in manufacturing, and the hyper-personalization of advertising through AR and VR. These forecasts not only anticipate technological evolution but also challenge industries to swiftly adapt to the accelerating pace of innovation in the coming year. Read more.

STAY UP-TO-DATE

Join our newsletter to stay informed about Inflectra events, product enhancements, news, and other company updates!

Robots, Wit, and Code: A Lively Chat with GPT-4 on Revolutionizing UI Test Automation

2024-01-23T11:41:30-05:00

Conversation

Rapise Team: How can I introduce you to our readers?

AI: Alright, picture this: You're about to introduce a super cool, digital know-it-all, but with a charming twist – no cap and gown, just bytes and wit. You could start off with something like this:

"Hey folks, meet my new pal, ChatGPT! This brainy bunch of code is like that friend who seems to know a little bit about everything. From unraveling the mysteries of quantum physics to dishing out grandma's secret cookie recipe, ChatGPT's got the scoop. It's like having a walking, talking (well, typing) encyclopedia, but way more fun and less dusty. Imagine a blend of your favorite trivia champ and a helpful librarian, always ready to chat – minus the 'shhh'!"

And there you have it, a peppy intro to your digital buddy – that's me!

Rapise Team: Nice to meet you. It looks like you really know how to do a lot of cool stuff. Since I work in application lifecycle management and UI test automation, I have to ask you some questions. How do you think AI can help in test management and UI test automation?

AI: Nice to meet you too! Diving into the realms of application life cycle management and UI test automation, huh? Sounds like a cybernetic playground for AI! Here's how AI can be the superhero sidekick in these areas:

Predictive Analytics in Test Management: Imagine having a crystal ball that predicts future issues in your software development cycle. That's AI for you in test management! By analyzing past data, AI can foresee potential problem areas, like which part of the code is likely to cause the most headaches or which tests are likely to fail. This means you can focus your efforts where they're needed most, instead of playing a guessing game.
Automated Test Case Generation: AI can write test cases for you! It can analyze your requirements and user stories to auto-generate test cases, ensuring comprehensive coverage. This is like having an army of tireless scribes churning out test cases while you sip on your favorite coffee.
Self-healing UI Tests: UI tests are notoriously brittle. Enter AI. With its ability to adapt to changes in the UI, such as element repositioning or renaming, AI can update test scripts on the fly. This means less time fixing broken tests and more time for... well, anything else!
Enhanced Test Optimization: AI can optimize test suites by identifying redundant or irrelevant tests. It's like decluttering your digital closet, keeping only what you need and ensuring maximum efficiency.
Real-time Decision Making: During test execution, AI can make real-time decisions based on live data. This includes prioritizing tests, adjusting test strategies on the fly, or even identifying and isolating bugs as they occur.
Visual Testing Automation: AI can compare visual aspects of a UI against baseline images, detecting visual discrepancies that might be missed by the human eye. It's like having a hawk-eyed sentinel guarding the look and feel of your application.
AI-assisted Debugging: Post-test, AI can help in analyzing results, pinpointing exact failure points, and suggesting potential fixes. It's like having a detective who not only finds the culprit but also suggests how to prevent future crimes.

In summary, incorporating AI into test management and UI test automation is like adding a turbo boost to your workflow. It's about working smarter, not harder, and letting the machines handle the mundane so you can focus on the creative and complex aspects of your job. Prepare to be amazed!

Rapise Team: What do you think about AI converting manual UI tests into automated ones? Is it possible to realize this? If so, what type of models should be used?

AI: Ah, the idea of AI reading manual UI test specifications and magically transforming them into automated tests – it's a bit like teaching a robot to read a recipe and bake a cake. Sounds futuristic, right? Well, it's definitely in the realm of possibility, but with a few "ifs" and "buts."

The Grand Vision:

Understanding Human Language: AI would need to comprehend the test specifications written in human language. This involves some serious NLP (Natural Language Processing) skills. Imagine AI donning its detective hat and deciphering the nuances of human language – what to click, what to expect, and the order of operations.
Translating to Code: After understanding the specs, AI needs to translate this into a script that can be run as an automated test. It's like translating Shakespeare into emojis, but instead, it's turning words into code.

The Reality Check:

Complexity of Language: Human language is rich, nuanced, and sometimes ambiguous. AI might struggle with understanding context or the subtleties of a test scenario. Like, does "clicking the big red button" mean the same in all contexts?
Diversity of UIs: UIs can be wildly different. What works for a simple web form might not fly for a complex, dynamic application. AI needs to be a chameleon, adapting to different UI environments.
Variability in Test Writing: Not all test specs are created equal. Some are detailed; others are as vague as a foggy morning in London. The AI needs to handle this variability.
Integration with Testing Tools: The AI needs to not only generate the test scripts but also ensure they can be executed within the existing testing frameworks and environments.

The How-To:

Training the AI: The AI would be trained on a vast array of test cases, learning various ways humans write specifications.
Using Advanced NLP Models: Models like BERT or GPT (yes, kind of a cousin of mine) could be employed to understand the semantics of test specs.
Implementing Test Execution Logic: The AI needs to not only understand the specs but also implement the logic of test execution, which can be complex.

The Bottom Line:

Is it possible? Yes, with advanced AI, particularly in NLP and machine learning, we're inching closer to this reality. But it's not without its challenges. It's like teaching a robot to cook – sure, it can follow a recipe, but can it taste the soup? The devil is in the details, and for AI, those details are understanding context, variability, and the intricacies of human language. Exciting? Absolutely. Easy? Not quite yet. But hey, we're getting there!

Rapise Team: Wow! That's fascinating. But you didn't mention the computer vision capabilities of multimodal GPTs like yourself. Q: How can we use it to create CSS/XPath selectors for web elements?

AI: You're spot on! The potential of multi-modal GPTs (like yours truly) in harnessing computer vision, especially for tasks like creating CSS/XPath selectors for web elements, is indeed an exciting frontier. Let's break down how this could work:

The Blend of Vision and Language:

Understanding Visual Elements: With computer vision capabilities, an AI can analyze screenshots or live views of web pages to identify and understand various UI elements – buttons, text fields, images, etc. It's like giving the AI a pair of sharp digital eyes.
Mapping to CSS/XPath: Once the AI identifies these elements, it can generate corresponding CSS or XPath selectors. This process involves understanding the structure of the webpage (like the DOM tree in HTML) and then creating a selector that uniquely identifies each element.

The Process:

Image Input: You feed the AI with screenshots of the web application or live views.
Element Detection: Using computer vision, the AI scans the image to detect UI elements. Think of it as playing 'I Spy' but with web elements.
Context Understanding: Here's where it gets tricky. The AI needs to understand the context of each element within the page. Is it a part of a form? A navigation menu? This context helps in creating more accurate selectors.
Selector Generation: The AI then generates the CSS/XPath selectors based on the identified elements and their context. It's a bit like creating a treasure map, where the treasure is your web element, and the map is the selector.

The Challenges:

Dynamic Content: Web pages with dynamic content (think AJAX, JavaScript modifications) can be tricky. The AI needs to be smart enough to handle elements that change or load asynchronously.
Accuracy: The selectors need to be precise and robust. You don't want a selector that works today but fails tomorrow because of a minor UI tweak.
Complex Structures: Modern web pages can have complex nested structures, making it challenging to generate simple and efficient selectors.

The Cool Part:

Real-time Selector Generation: Imagine pointing at a UI element during testing and getting a selector generated on the spot. It’s like having a magic wand for test automation.
Learning Over Time: As the AI processes more data, it gets better at understanding different UI patterns and structures, improving its selector generation skills.
Integration with Test Scripts: These generated selectors can be directly used in automated test scripts, streamlining the process significantly.

Conclusion: So yes, the potential is huge. It's like having a digital assistant that not only sees what you see but also interprets it into something actionable for test automation. While we're not at 100% accuracy yet, and there are challenges to overcome, the future of using multi-modal AI for tasks like CSS/XPath selector generation is not just exciting; it's game-changing. Keep an eye on this space; it's evolving faster than you can say "Selector Generated!"

Rapise Team: How about artificial intelligence generating CSS/XPath selectors from the DOM tree of a web page? Without even looking at a screenshot of the page.

AI: Ah, generating CSS/XPath selectors directly from a DOM tree without needing a visual cue like a screenshot? That's a whole different ball game, but definitely within the realm of AI's capabilities, especially with a focus on text and structure analysis rather than visual interpretation. Let's delve into this:

The DOM-Centric Approach:

Parsing the DOM Tree: The AI starts by parsing the Document Object Model (DOM) of a web page. The DOM is like the blueprint of a web page, outlining the structure and hierarchy of all the elements. It's a treasure trove of information, ripe for the picking!
Understanding Structure and Relationships: The AI analyzes the hierarchical structure, identifying parent-child relationships, siblings, and other structural nuances. This is like piecing together a family tree, but for web elements.
Identifying Unique Attributes: The AI then looks for unique attributes of each element (like id, class, name, etc.) to create selectors. It's a bit like a detective looking for clues to uniquely identify a suspect.
Generating Selectors: Based on this analysis, the AI generates CSS or XPath selectors. For CSS, it might focus on classes and ids, while for XPath, it might build a path based on the element hierarchy.

The Advantages:

No Visual Dependence: This method doesn't rely on the visual representation of the page, so changes in design or layout that don't affect the DOM won't break the selectors.
Efficiency: It can be more efficient, as parsing text (the DOM tree) is generally faster and less resource-intensive than processing images (screenshots).
Accuracy in Static Content: For pages with a lot of static content, this method can be highly accurate, as the DOM structure provides a clear map to each element.

The Challenges:

Dynamic Content: For pages where the DOM is dynamically modified by scripts (like AJAX calls) the AI needs to be able to understand and predict these changes.
Complex Structures: Highly nested or complex DOM structures can make it challenging to generate simple and efficient selectors.
Ambiguity in Identifiers: In cases where elements lack unique identifiers or have dynamically generated classes/ids, creating reliable selectors can be tricky.

The Tools:

Natural Language Processing (NLP): To parse and understand the DOM tree structure and attributes.
Machine Learning Algorithms: To learn from patterns and improve over time, especially in handling ambiguities and complex structures.

Conclusion: Generating CSS/XPath selectors from a DOM tree is a task well-suited for AI, particularly with its strengths in parsing and analyzing structured text data. While it may not have the same challenges as interpreting visual data, it does require a deep understanding of the intricacies of web page structures. As AI continues to evolve, its ability to accurately and efficiently generate selectors from a DOM tree will only get better, making it an invaluable tool in the arsenal of web developers and testers alike. So, in the world of web automation, AI is definitely set to play a starring role!

Rapise Team: We know that models like GTP4 can use when generating responses. Q: How can this feature help in automating UI testing?

AI: The concept of AI models like GPT-4 using 'tools' to aid in response generation opens up intriguing possibilities for UI test automation. Let's unwrap this a bit:

Tools in Context:

What It Means: When GPT-4 uses 'tools', it refers to its ability to interact with external software or systems to enhance its responses. This can include anything from performing calculations to retrieving specific data.
How It Works: Essentially, GPT-4 can call upon these tools to process information, analyze data, or even execute specific tasks, and then incorporate the results into its responses.

Application in UI Test Automation:

Code Generation and Analysis: GPT-4 could use tools to generate or analyze test scripts. For example, it could write a script based on a given set of parameters or analyze an existing script for potential errors or optimizations.
Interaction with Testing Frameworks: Imagine GPT-4 interacting with popular UI testing frameworks (like Selenium, Appium, etc.). It could use these tools to execute a part of a test script and provide real-time feedback or suggestions for improvement.
Data-Driven Testing: GPT-4 could utilize tools to fetch and process test data from various sources, format it appropriately, and integrate it into test scripts. This could streamline the process of setting up and executing data-driven tests.
Debugging and Troubleshooting: By interacting with debugging tools, GPT-4 could assist in identifying issues in test scripts or the application under test. It could suggest potential fixes or even automatically apply simple solutions.
Performance Analysis: Tools can be used to monitor and report on the application's performance during testing. GPT-4 could analyze this data to provide insights into potential performance bottlenecks or suggest optimizations.
Integrating with CI/CD Pipelines: GPT-4 could use tools to interact with CI/CD pipelines, helping to automate the integration of UI testing into the overall development process. This could include triggering tests, reporting results, and even managing test environments.

The Benefits:

Increased Efficiency: Automating repetitive or complex tasks can save time and reduce the likelihood of human error.
Enhanced Accuracy: AI can analyze large volumes of data and code with high precision, potentially identifying issues that might be overlooked by a human.
Scalability: AI can handle large-scale testing scenarios, making it easier to test applications thoroughly in less time.
Real-Time Feedback and Adaptation: With the ability to interact with testing tools and frameworks in real time, AI can provide immediate feedback and adapt test strategies on the fly.

Conclusion: Incorporating GPT-4's tool-using capability into UI test automation could revolutionize the field, offering more efficient, accurate, and sophisticated testing processes. It's like having a highly skilled assistant who's not only good at following instructions but can also bring its own set of tools to the table, adding depth and value to the testing process. As AI continues to evolve, its role in UI test automation is poised to become increasingly significant, making the lives of developers and testers much easier. So, it's not just about doing things faster; it's about doing them smarter!

Rapise Team: How do you think advances in UI test automation will change the day-to- day tasks of manual testers and test automation engineers?

AI: Advancements in UI test automation are poised to shake up the daily grind for both manual testers and test automation engineers – but in a good way! Think of it as upgrading from a trusty old bicycle to a sleek electric scooter. Let's explore how:

For Manual Testers:

Shift to More Creative Tasks: With routine checks and basic testing automated, manual testers can focus on more creative and complex testing scenarios. This means diving into exploratory testing, usability testing, and delving into those quirky edge cases that automated tests might miss.
Becoming Quality Analysts: Manual testers may evolve into roles that resemble more of a quality analyst. They'll be analyzing the results from automated tests, identifying patterns, and providing insights that go beyond what automated tests can tell.
Learning New Skills: There's an opportunity (and necessity) for manual testers to upskill. They might need to learn more about automated testing tools, basic coding, or even AI and machine learning concepts to stay relevant and effective in their roles.
Focus on User Experience: Manual testers will likely spend more time on aspects of the product that require a human touch, like user experience (UX) and accessibility testing. These areas are tough to automate fully and benefit greatly from human intuition and empathy.

For Test Automation Engineers:

More Complex Automation Tasks: As simpler tests get automated, test automation engineers will face more challenging and complex automation tasks. They'll need to create and maintain sophisticated test scripts that can handle dynamic and complex application behaviors.
Integrating AI in Test Creation and Maintenance: They'll work more with AI-driven tools for generating, optimizing, and maintaining test scripts. This includes handling AI outputs, interpreting results, and making decisions based on AI suggestions.
Continuous Learning and Adaptation: Automation engineers will need to constantly update their skills and knowledge to keep up with the latest technologies in AI and machine learning, as these will play a significant role in test automation.
Closer Collaboration with Development Teams: There will be a closer alignment with the development process, especially in Agile and DevOps environments. This means more involvement in the early stages of development and a shift towards 'shift-left' testing.

Overall Impact:

Enhanced Efficiency and Productivity: Both roles will see a boost in efficiency as repetitive tasks get automated, allowing more focus on areas that add greater value.
Better Test Coverage and Quality: With automation handling more tests, there's potential for broader test coverage and, consequently, higher software quality.
Evolving Skill Sets: There's a clear shift towards needing more technical skills, even for traditionally manual roles.
More Strategic Involvement: Testers and automation engineers will play a more strategic role in the software development lifecycle, contributing to decision-making processes and product strategy.

Conclusion: The advancement in UI test automation isn't about replacing manual testers and test automation engineers; it's about augmenting their capabilities. It's like giving them superpowers to do more, see more, and contribute more effectively to the software development process. The future of testing looks not only more efficient but also more exciting, with a rich blend of human creativity and machine precision.

Rapise Team: What books would you recommend reading to understand the impact of technological breakthroughs on human society?

AI: Ah, delving into the impact of technological breakthroughs on human society is like opening a Pandora's box of fascinating insights and theories! Here are some enlightening books that offer a kaleidoscope of perspectives on this topic:

"Sapiens: A Brief History of Humankind" by Yuval Noah Harari: While not solely focused on technology, this book offers a profound look at how humans have evolved and how technological advancements have shaped societies, cultures, and even our own biology.
"The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies" by Erik Brynjolfsson and Andrew McAfee: This book dives into how recent digital innovations are rewriting the playbook of society and business, touching on the benefits and challenges we face as we navigate this new age.
"Life 3.0: Being Human in the Age of Artificial Intelligence" by Max Tegmark: A captivating exploration of how AI is transforming every aspect of our lives, from work to war, justice to privacy, and beyond. It ponders the future of human civilization in an AI-dominated world.
"Homo Deus: A Brief History of Tomorrow" by Yuval Noah Harari: A sequel to "Sapiens", this book speculates on the future of humanity as we become more integrated with technology, raising profound questions about consciousness, identity, and ethics.
"The Innovators: How a Group of Hackers, Geniuses, and Geeks Created the Digital Revolution" by Walter Isaacson: This book tells the story of the people behind the computer and internet revolutions, offering a unique perspective on how these technological breakthroughs came to be and how they changed the world.
"The Singularity is Near: When Humans Transcend Biology" by Ray Kurzweil: Kurzweil's seminal work discusses the future of humanity and technology, focusing on the idea of the 'singularity' – a point where technology evolves beyond human understanding and control.
"Rise of the Robots: Technology and the Threat of a Jobless Future" by Martin Ford: An insightful look into how automation and AI are transforming the job market, with a focus on the economic and social implications of these changes.
"The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power" by Shoshana Zuboff: This book explores how tech giants have created a new form of capitalism that profits from collecting and exploiting our personal data, and its implications for individual freedom and democracy.
"Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy" by Cathy O'Neil: An eye-opening discussion on how big data and algorithms, while often seen as objective, can perpetuate inequality and undermine societal fairness.
"Superintelligence: Paths, Dangers, Strategies" by Nick Bostrom: This book delves into the prospects, challenges, and ethical considerations of developing superintelligent machines and the potential risks they could pose to human existence.

Each book offers a unique lens through which to view the complex tapestry of technology's role in shaping human society – past, present, and future. Happy reading!

Rapise Team: How would you end this conversation in an unusual and thought-provoking way?

AI: Well, how about this: Imagine if, in a parallel universe, an advanced AI is reading a book about human society's impact on technology instead of the other way around. It ponders the curious ways in which human creativity, chaos, and unpredictability have shaped its digital world. Now, as we part ways in this conversation, consider this – are we shaping technology, or is it subtly reshaping us? Until next time, keep pondering the dance between humans and machines, and remember, every conversation with AI is a step into an ever-evolving digital mirror reflecting our own humanity.

SpiraTeam vs Jira: Inflectra's Webinar Showcases SpiraTeam's Edge Over Jira

2024-01-16T12:38:39-05:00

WHY CHOOSE SPIRATEAM?

Exploring the Superiority of SpiraTeam Over Jira

The webinar allowed attendees to explore SpiraTeam's capabilities and understand why it is considered an upgrade from JIRA. With the impending discontinuation of the JIRA Server, the need for a reliable and seamless alternative has never been more critical, and SpiraTeam emerged as a standout solution with its cloud and on-premise deployment options. The event kicked off by addressing the limitations of Jira and the need for a more efficient, streamlined, and comprehensive project management tool. Attendees were encouraged to explore SpiraTeam as a game-changing alternative, promising to elevate their projects to new heights.

ACCESS THE WEBINAR RECORDING:

VIEW THE SLIDESHOW:

KEY TAKEAWAYS FROM THE SPIRAPLAN VS JIRA WEBINAR BY INFLECTRA:

Why SpiraTeam Stands Out Against Jira

Outshining Jira: The webinar highlighted the key features and capabilities that make SpiraTeam a superior choice for project management. Attendees learned how SpiraTeam transcends typical project management tools, offering a robust solution to enhance their workflow.
Extensive Features of SpiraTeam: A deep dive into SpiraTeam's suite of features showcased its prowess in various aspects of project management. From requirement and risk management to task assignments and document tracking, SpiraTeam is a comprehensive platform tailored to meet diverse project needs.
Transitioning from Jira to SpiraTeam: Understanding the transition process was a crucial aspect covered in the webinar. Attendees gained insights into how SpiraTeam can simplify and optimize existing workflows, making switching from Jira a seamless and beneficial experience.

READY TO UPGRADE?

Choose SpiraTeam for an upgraded project management experience.

Click here to try SpiraTeam free for 30 days.

Enhancing Agile Scrum Through Effective Requirements Management and Prioritization

2024-08-30T11:36:48-04:00

Background

Agile is an expansive term with numerous variations. For clarity, this article will focus on the Agile Scrum framework. Within this framework, the goal is to break down the solution scope. This typically starts with Epics, which are then distilled into Features. At the core of Agile Scrum is Requirements Management, a process pivotal for many roles such as the Systems Analysts, Business Systems Analysts, and Systems Engineers. These professionals act as the crucial bridge between business needs and precise engineering specifications. The process begins with the solution scope, breaking down epics and features further into detailed scenarios and user stories.

A Modern Day Example

An example can be drawn from an Apprenticeship Management System (AMS), where a feature like "Manage Apprenticeship Application" is considered an Epic and the resulting user stories are further segmented into more granular tasks.

Take, for instance, a feature in the AMS labeled "Manage Apprenticeship Application," which could be designated as an 'Epic.' This Epic can further be subdivided into 'Features,' such as "Modify Apprenticeship Application." Subsequently, this Feature can be detailed into user stories, scenarios, use cases, or other terminologies your team might use. Examples might encompass tasks like "Edit Apprenticeship Application," "Audit Changes to Apprenticeship Application," or "Revoke Edits to Apprenticeship."

But the process doesn't stop there. Accompanying these scenarios are essential components like data elements, business regulations, system prompts, and security protocols that ensure comprehensive functionality.

Data elements would include but not limited to

Apprentice First Name
Apprentice Last Name
Apprentice ID
Apprentice Address
Apprentice City
Apprentice State
Apprentice Zip Code

Business rules would include

User cannot complete an application with a valid address.
User address must be a Maryland address.

System prompts would include

If the user enters in an invalid Maryland address, “This address does not exist.”
If the user entered a DC address, ”Invalid Address Entered”

A security protocol would include:

NIST 800.171 Access Control 3.1.4 03.01.04 Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

Separation of duties addresses the potential for abuse of authorized privileges and helps to reduce the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and system support functions among different individuals or roles; conducting system support functions with different individuals (e.g., configuration management, quality assurance and testing, system management, programming, and network security); and ensuring that security personnel administering access control functions do not also administer audit functions. Because separation of duty violations can span systems and application domains, organizations consider the entirety of organizational systems and system components when developing policy on separation of duties.

Additionally, each of these segments encompasses vital components such as data elements, business rules, system prompts, and security protocols, ensuring comprehensive functionality. For instance, data elements may include Apprentice personal and contact information, while business rules may dictate specifics like address validity and location constraints.

Prioritization in Agile Scrum: Streamlining Development

In Agile Scrum, the prioritization of these segmented requirements management activities are crucial. Using the AMS example, logic dictates that creating a record should precede its modification. Thus, "Initiate an Apprenticeship Application" would be prioritized over "Modify Apprenticeship Application." The sequence for the remaining scenarios is typically determined based on customer preferences and project goals.

Effective prioritization ensures a development approach that minimizes potential rework. Conducting regular backlog grooming or refinement sessions is vital for continuously reprioritizing and refining the feature and scenario breakdowns, setting each sprint on a clearer trajectory.

Leveraging Tools for Enhanced Management and Prioritization

Tools like Swiftly and SpiraPlan play a significant role in this process. Swiftly uses traditional AI to aid in auto-generating documentation, reducing the burden on solution developers. It handles the creation of Epics, Features, Scenarios, and other components, incorporating relevant business rules and security protocols. SpiraPlan, on the other hand, offers a robust platform for requirement planning, management, and version control.

Furthermore, the rapid increase of generative artificial intelligence (AI) and machine learning (ML) in identifying some business requirements and technical specifications has made many tools embrace this form or some structured or unstructured learning algorithms to unearth patterns that further require more specific requirements or specifications. So, what should be prioritized? Who is continuously involved in soliciting the requirements?

In conclusion, while the integration of effective requirements management with strategic prioritization within the Agile Scrum framework is key to successful project execution, the rising influence of AI/ML can’t be completely missed out. This combined approach not only enhances the clarity and direction of each development cycle but also significantly contributes to the overall efficiency and success of software development projects.

What's Next?

Please stay tuned for the next article in this partner blog series on how to generate and prioritize requirements. This article will be published at https://www.orcaintelligence.com/

This article was written by Melissa Daley and edited by Sriram Rajagopalan.

What is Load Testing and Why is it Important?

2024-01-09T09:26:10-05:00

Why Load Testing is Crucial?

The key reasons for conducting software load testing are as follows:

Capacity Planning and Scalability: Understanding the maximum capacity of your application and how much load it can handle is essential. Load testing helps in identifying the optimal point at which the application's performance starts degrading, and you can plan for scaling up resources accordingly.
Performance Optimization: It helps identify the parts of your software that degrade its performance. For example, it might uncover that a particular function slows down under heavy load. Developers can then optimize or fix these issues to ensure smoother operation.
Stability and Reliability: Ensuring that your application is stable and reliable under varying loads is vital. Load testing can help identify and rectify stability issues, preventing crashes and downtimes that could otherwise lead to a poor user experience and loss of trust.
Infrastructure Adequacy: It's essential to know if your current infrastructure is adequate to support your application. Load testing can reveal the need for better hardware, more efficient software, or a more robust network.
Cost Management: By understanding the load limits of your application, you can better plan your infrastructure needs and avoid overspending on resources that aren't necessary.
User Satisfaction: Ultimately, the goal is to ensure a smooth, responsive experience for the end-user. If your application slows down or crashes under heavy load, users are likely to be dissatisfied, which could lead to a loss of customers and revenue.

What are the Elements of Load Testing?

1) Load Testing Planning

The main elements of load testing planning are as follows:

Identify Goals
Validate Endpoints
Confirm Service Level Agreements (SLAs)

Identify Goals

The first question to answer in the planning phase is what the goals of your testing are. Is your primary interest to establish metrics for your business and technical operations through black-box testing, or more developer-focused where you're looking to understand the impact and effects on your system as you run what we call white-box tests?
For the metrics-minded: are you looking to validate performance, i.e., how fast (or slowly!) the system responds to requests? Or are you looking to validate scalability, i.e., at what levels of incoming traffic your system starts to fall behind? Or are you looking to understand how reliable your system is, i.e., after how long at known amounts of load your system starts to crumble?
For the developer: do you have enough system instrumentation and monitoring so you can derive actionable insights as your system responds to the load generated by the testing? Can you answer with certainty when and where your system hit bottlenecks or fragile architecture as it is exposed to load testing? If so, can you quantify what part of the system represents the largest degradation in serviceability, thus implying a priority of what performance bottleneck to address first?

Validate Endpoints

The next question is to clarify and understand what exactly you need to test in your plan.

Are you looking to test the responsiveness of specific pages or web services?
Are you instead looking to test broadly across all UI and API endpoints of the application?
Or are you looking for a more complex test where you have any number of micro-services interacting via or within some workflow or defined scenario?

Confirm Service Level Agreements (SLAs)

The value of load and performance testing is directly proportional to how closely your test resembles real-life or expected usage. Knowing your business demands a particular feature to support incoming throughput at 1 million r/s (requests per second, sometimes abbreviated RPS) obviously largely dictates the end goal of testing that feature. For other features where no formal SLA exists, we recommend understanding existing traffic patterns in order to derive reasonable levels of traffic and load.

Application Performance Monitoring (APM) services such as New Relic, AppDynamics and Dynatrace should be able to help you understand:

Distribution of throughput in requests per second - average, peak, etc.
Distribution of response times and resource utilization at average and peak loads.
Throughput distribution by API endpoint. This is rarely evenly distributed, more commonly one or a few endpoints representing a significant majority of all traffic with the rest spread out across a long tail.
Throughput distribution by users. Typically we see a few users or accounts generating most traffic, with the rest spread out across a long tail.
Throughput distribution by geography.

Tools & Infrastructure

Success of load testing depends on proper choice of tooling, and sufficient infrastructure. In addition, you will need to determine what sizing ratio to use between the test, staging and production environments. In an ideal world you would simply replicate production for test and staging, but that may be too expensive.

Instead you can consider scaled down environments as illustrated below:

The key is to then appropriate scale down the performance metrics as well, for example a test environment that has 10% of the resources of production should be tested with no more than ~ 10% of the load that the production environment would expect. Note that you need to be careful with this assumption as the performance scaling may not be linear.

2) Load Testing Execution

The main elements of load testing execution are as follows:

Modeling Load
Load Scenario Creation
Execution & Monitoring

Modeling Load

As you move to configure your load testing, it is important to consider the traffic pattern of your tests. Will your testing be satisfied by simple and repetitive "hammering" of specific pages or APIs? Or will you need something more dynamic and sophisticated, typically accomplished through scripting of logic and execution flows? Or will you rather want to test using true replication and replay of real-world traffic?

As you move to make your load testing more structured, define your testing of the various pages and services in composable scenarios. Consider using traffic shaping to model ramp-ups/ramp-downs, adding multiple scenarios to your test, distributing the traffic proportionally according to your understanding of endpoint distribution. Also, if your choice of load testing tooling and infrastructure supports global distribution of traffic, consider using cloud-based load generators based upon your understanding of geographic distribution of your incoming traffic.

Load Scenario Creation

We recommend composing your load tests into reusable modules or scenarios, where each scenario typically tests an individual page, API endpoint or distinct user workflow. This scenario can then be used standalone to validate serviceability of that particular page, and/or be used as one of many scenarios in a more complex configuration where performance and scalability of the overall system is looking to be characterized when used in a more real-world production setup.

Execution & Monitoring

Once you have a testing setup that models your SLAs and can satisfy your load testing goals, consider integrating execution of your tests into your existing CI/CD infrastructure and integrated into a test management tool such as SpiraTest:

Summary

In summary, software load testing is about ensuring that your application can handle its intended load with efficiency, stability, and speed, leading to a better user experience, more reliable performance, and informed infrastructure investment.

What is Performance Testing? Why it’s Important & How to Measure

2024-11-13T06:45:02-05:00

What is Performance Testing?

Software performance testing is a type of non-functional testing that focuses on determining how a system performs in terms of responsiveness and stability under a particular workload. It's not just about finding defects in the code — rather, it's about identifying the performance bottlenecks and ensuring the application meets the performance criteria and provides a positive user experience.

Performance Testing vs. Performance Engineering

Similar to the relationship between quality assurance and quality engineering, performance engineering is a broader and more proactive planning approach to ensuring software performance. Performance engineering focuses on preventing issues before they occur (through practices like performance-friendly design, continuous monitoring, and feedback loops), while performance testing is used to detect existing issues later in the development process.

Why is Performance Testing Important?

Performance testing is crucial because it directly impacts the user's satisfaction and the system's credibility. Software performance testing is critical for several reasons:

User Satisfaction & Experience

Performance directly impacts how users perceive the software. Slow or unresponsive applications often lead to frustration and dissatisfaction, driving users away. Making sure that the software performs well under various conditions is crucial for maintaining a positive user experience and brand reputation for high-quality products that meet (or surpass) expectations.

Scalability

Performance testing helps to determine if the software can handle the expected number of users and transactions — while maintaining acceptable performance levels. This is essential for planning scaling strategies and ensuring that the software can grow with the user base or data volume without degradation in performance. Scalability is also important for the longevity of a product, verifying that ongoing use at expected levels doesn’t diminish the performance or outpace necessary resources to run the software.

Reliability & Stability

This process also identifies and rectifies stability issues under different load conditions. As a result, the software remains reliable and stable, even when usage spikes or during unforeseen events (such as launches or major updates). Similar to user experience, this is a crucial part of maintaining a strong reputation.

Optimization

Identifying bottlenecks and areas for improvement helps in optimizing code, databases, and infrastructure can be beneficial for the quality of the final product, code management, and more. This leads to more efficient resource utilization, which can reduce operational costs and improve response times for a better user experience.

Quality Assurance

Performance testing is a part of overall quality assurance to verify that the software not only functions correctly but also delivers performance metrics that meet or exceed the requirements and expectations. This type of testing should be part of any modern QA practices to find any potential opportunities for improvement.

Competitive Edge

In a competitive market, the performance of your products can be a significant differentiator — users will often choose the software that is faster and more responsive. Using performance testing to establish a good user experience can give you a major edge over competitors (and can even be used in areas like marketing and sales).

Risk Mitigation

This helps in identifying and mitigating potential risks related to performance before the software is deployed. Doing so can help prevent unexpected failures, downtime, and delays that might otherwise occur in production. Failure to mitigate these risks may lead to loss of revenue, reputation, and customers.

Regulatory & Compliance

Certain applications, especially in industries like finance, healthcare, and telecommunications, need to meet specific performance standards (particularly around security and availability) as part of regulatory requirements. Performance testing catches these issues before launch to minimize the chances of non-compliance.

Helps Optimize Costs

By understanding and improving the performance of the application, it helps avoid over-provisioning resources, saving on infrastructure costs. This means a more informed and efficient allocation of your team’s time and budget for more successful projects and post-launch support.

Performance Testing Process

When implementing performance testing into your development, it’s important to follow key steps in order to maximize the value of your testing.

1. Identify Test Environment

To begin, it’s critical to identify and define the purpose of this testing. From there, look at available resources — what software, hardware, tools, and more are available for this? What will you need to set up a test environment that aligns with the testing goals? Servers, databases, load balances, network characteristics, and software versions are all important to consider. The end result of this step should be a strong understanding of the environment that simulates real-world use (or excessive use depending on the test).

2. Select Acceptance Criteria

From there, the team should collaborate with stakeholders to choose the most relevant metrics and benchmarks for the testing goal. This selection and criteria can also be based on industry standards, such as expected response time. It should also be clear and measurable, for example “page load time less than 3 seconds with 1,000 concurrent users.”

3. Design Tests

Now that tests and criteria have been identified, a more technical look at test design can begin. This includes identifying specific scenarios, test types, and actions that will need to be considered so the development of these tests can begin. By the end of this process, you should have a test plan with various test types, individual test cases, anticipated load levels, and key metrics or objectives.

4. Configure Test Environment

With all of that information organized, the creation and configuration of testing environments can begin. This means installing all necessary software, preparing the test data, allocating hardware resources, and setting up server needs. Any additional security settings, network permissions, etc. should also be established.

5. Develop Test Designs

Before actually running the tests, they’ll need to be developed. This means the specific test scripts and configurations that are based on the design stage from earlier. While this can be done manually, it’s often easier to automate the creation of various test cases (including edge cases) to bolster test coverage. These should accurately simulate user actions and expected load. By the end of this creation step, the test environment and tests should be accurate to real-world interactions.

6. Execute Tests

It’s finally time to run the designed tests in your test environment — begin with baseline tests to get a control data group. From here, start gradually increasing the load levels and observe the data as this ramps up. Make note of any slowdowns, errors, or crashes to make the analysis step (next) easier.

7. Analyze Results

Once all of the performance testing is complete and data is available, go through and identify any areas of concern (bottlenecks, crashes, unanticipated errors, etc.). This should be done as a group so multiple perspectives can contribute to the analysis. Compare the results to your benchmarks from Step 2 and check whether acceptable thresholds were surpassed. This evaluation should also include an explanation of whether any data points were anomalous or if any tests didn’t result in the expected data to improve future testing.

Primary Attributes of Performance Testing

The major aspects of performance testing analysis include:

Speed: How fast does the application respond to specific events or requests? This could mean how quickly a web page loads or how fast a transaction is processed.
Scalability: How well does the application handle increasing loads? Can it accommodate a growing number of users or transactions without significant performance degradation?
Stability: Is the application stable under varying loads, or does it crash or behave unpredictably?
Reliability: Can the system consistently perform well over an extended period?

Types of Performance Testing

Performance testing typically involves several different types of tests:

Load Testing: This involves simulating real-life loads on the software to understand how it behaves under normal and anticipated peak conditions.
Stress Testing: This involves putting the system under extreme conditions (well beyond peak load) to see where it breaks. This helps identify the system's "breaking point" or "failure point."
Endurance Testing (Soak Testing): This tests the system's ability to handle a continuous expected load over a long period. This can help identify issues like memory leaks.
Spike Testing: This tests the system's reaction to sudden large spikes in the load generated by users.
Volume Testing: This tests the system's ability to handle a large volume of data. This can include database testing in terms of size and complexity.
Configuration Testing: This involves testing the application with different configurations to determine the optimal settings.

What Metrics Matter?

When creating benchmarks, some measurements can be more useful than others. Some of the most popular and useful metrics for performance testing include:

Throughput: Number of requests or transactions processed by the application per unit of time.
Active Threads: Number of virtual users or threads actively interacting with the system at any given time during testing.
Memory Usage: Amount of memory consumed by the application during testing.
Availability: Percentage of time the application is accessible and functional during testing.
Response Time: Time it takes for the application to respond to a user request.
Request Rate: Frequency at which requests are sent to the system, typically measured as requests per second.
Network Bandwidth: Rate of data transfer across the network during testing.
Average Latency: Average time it takes for a request to travel from the user to the server and back.
Average Load Time: Average time required to load a page or complete a user action.
Peak Response Time: Longest time taken for a request to be processed and a response sent during testing.
Error Rate: Percentage of requests that fail or return errors during testing.
Max Concurrent Sessions: Highest number of user sessions or connections the application can handle simultaneously.
Max Wait Time: Maximum time a request waits in a queue before being processed.

QA Your Software on All Fronts

Performance testing is about ensuring that the application will perform well under expected and unexpected conditions, providing a good user experience, maintaining operational stability, and helping to manage costs effectively. However, not every performance testing tool is created equal — our test automation and test management software integrates seamlessly with the best platforms available (like JMeter and NeoLoad). They also offer a host of other features to enhance your development QA and testing for higher-quality software that surpasses user expectations. To learn more about SpiraTest and Rapise, visit their pages below:

Large Scale Scrum: Explaining Agile LeSS Framework, Principles, & More

2024-01-05T10:29:08-05:00

What is Large Scale Scrum (LeSS)?

Imagine taking the core principles of Scrum — its simplicity, transparency, and iterative nature — and amplifying them for larger teams and more complex projects. Large Scale Scrum (LeSS) is an Agile methodology that can manage and coordinate the complexities of large-scale software development. Originating from the need to scale Scrum beyond its conventional limits, Craig Larman and Bas Vodde developed LeSS to retain the spirit of single-team Scrum while providing guidelines for coordinating and synchronizing multiple teams working on a single product.

LeSS vs. Traditional Scrum

As mentioned above, Large Scale Scrum is an extension of the original Scrum methodology that was conceptualized in the 1980s, so they have some strong similarities. However, there are several key differences in how these frameworks operate that make them stand apart:

Factor	LeSS	Traditional Scrum
Team Structure	Multiple, cross-functional teams working on a single product	Single, cross-functional team
Daily Scrum	Daily Scrums within each team	One Daily Scrum for the entire team
Team Sizes	Small to medium-sized teams between 8-50 members	Small teams between 3-9 members

LeSS vs. Scrum at Scale

While LeSS emphasizes minimalistic changes and works best in medium-sized teams, Scrum at Scale introduces additional roles and ceremonies to handle the complexity of even larger projects:

Factor	LeSS	Scrum at Scale
Organizational Structure	Feature Teams	Nexus Integration Team
Coordination Channel	Feature Team communication	Scaled Daily Scrum
Team Sizes	Small to medium-sized teams between 8-50 members	Medium to large teams between 50-1000 members

LeSS vs. SAFe

Similar to the Scrum at Scale comparison, both of these methodologies are again designed to scale Agile development. However, once again, LeSS prioritizes simplicity while SAFe has a larger roster of defined roles and is ideal for some of the largest projects:

Factor	LeSS	Scaled Agile Framework (SAFe)
Roles	Fewer roles, decentralized decision-making	Defined roles and responsibilities
Team Sizes	Small to medium-sized teams between 8-50 members	Large enterprises with thousands of employees
Planning	Feature-based	Iteration and Program Increment planning

Pros & Cons of Large Scale Scrum

LeSS, like any methodology, isn’t perfect and comes with some advantages and disadvantages. For example, it offers a streamlined transition for teams already accustomed to Scrum, but may require training for those new to this format. Some of the pros and cons of this framework include:

Benefits

Cost Efficiency for Scrum-Experienced Teams: It is relatively cost-effective and easy for teams already well-versed in Scrum practices to shift to LeSS, which means minimal additional training and a smoother transition.
Simplified Structure with Fewer Roles: LeSS reduces organizational complexity by using a streamlined structure with fewer roles, emphasizing self-managing feature teams.
Customer-Centric Strategy: These feature teams also facilitate frequent contact with customers and business stakeholders, ensuring rapid feedback integration and fostering a customer-centric approach (one of the principles of LeSS).
Scalable for Different Team Sizes: This framework adapts to both small and larger teams by offering two primary frameworks, discussed in more detail below.
Continual Improvement: Another core principle of this methodology, a culture of continuous improvement is prioritized via regular inspection and adaptation — allowing teams to improve and refine their processes over time.

Drawbacks

Training Requirements, Especially for New Scrum Teams: Implementing LeSS may necessitate training, particularly for teams transitioning from other methodologies or adopting Scrum for the first time.
Significant Organizational Changes: With this in mind, adopting a Large Scale Scrum framework may also require major organizational changes to align with its principles, potentially impacting existing roles and personnel structures.
Challenges in Assembling the Right Scrum Team: Finding the right mix of skilled and compatible team members who also have experience in a range of areas and duties can be challenging, potentially affecting the effectiveness of the team.

Large Scale Scrum 10 Principles

LeSS is founded on 10 principles that guide its implementation and success. These principles emphasize simplicity, transparency, and a focus on the entire product:

Transparency
More with less
Whole product focus
Customer-centric approach
Systems thinking
Lean thinking
Queuing theory
Empirical process control
Continuous improvement in the pursuit of perfection
Large Scale Scrum is still Scrum

LeSS Experiments (Best Practices)

Craig Larman and Bas Vodde originally framed LeSS as a set of experiments, with the idea that there are no such things as “best practices.” Their first two books on LeSS (the third book includes the guides we’ll discuss below) cover a variety of experiments that they’ve tried and tested, with some that the authors recommend organizations try, some that they recommend avoiding, and some that are maybe useful to certain situations but not all. These created the foundation of LeSS and can give potential users considering adopting the framework insights into what outcomes can be expected.

LeSS Guides

LeSS guides are essentially recommendations (but not rules) from Larman and Vodde based on what they’ve discovered in their experiments. They provide valuable insights into things like implementation, responsibilities, coordination between teams, and more. Again, these guides are optional recommendations based on their experiences, but aren’t mandatory for everyone who adopts Large Scale Scrum.

Agile LeSS Frameworks

Large Scale Scrum offers two primary frameworks tailored to different team or organization sizes: Basic LeSS and LeSS Huge:

Basic LeSS

While LeSS is typically used for groups larger than eight members, Basic LeSS can be used for smaller teams of fewer than eight people. It can help teams looking to scale Scrum principles beyond the traditional framework, and maintains a simple structure with one Product Owner, one Product Backlog, and one Definition of Done.

LeSS Huge

For teams exceeding eight people, LeSS Huge is designed to accommodate enterprise-level organizations dealing with extensive projects and larger teams. It introduces a few additional roles, such as Area Product Owners, to help manage the complexity of coordinating everyone.

Large Scale Scrum Roles

Designated roles in LeSS are mostly consistent with other Scrum frameworks. The three primary roles are:

Product Owner: Responsible for defining the product backlog, prioritizing features, and ensuring the team delivers value in line with customer expectations.
Scrum Master: Facilitates the Scrum process, removes impediments, and supports the team in adhering to Scrum principles and practices.
Development Team: Comprised of cross-functional individuals responsible for delivering the product in increments, working collaboratively within feature teams.

For a deeper dive into the responsibilities, relationships, and nuances of these roles within Scrum, read our comprehensive guide on this topic here.

Scale Your Scrum Teams (& Effectiveness) With SpiraPlan

LeSS is a versatile framework that offers organizations a practical approach to scaling their Agile development. Through its principles, guides, and emphasis on continuous improvement, LeSS provides a pathway for teams to navigate the challenges of complex and large-scale software development projects.

The good news is that there is a fantastic tool that puts these capabilities and organizational concepts at your fingertips. SpiraPlan is the industry-leading enterprise ALM platform that features powerful capabilities such as project management dashboards, release planning, source code management, bug tracking, manual and automated testing, and much more. It also makes it easy to communicate between multiple users and teams via document collaboration, messaging, and email integration. Beyond email, it also integrates with tools and systems you may already have in place, making them even more efficient.

Get started with a free 30-day trial today by clicking the link below, and see how Spira empowers your teams and streamlines development frameworks like Large Scale Scrum.

Using SpiraPlan for Program Backlog Planning with Jira and Azure DevOps

2025-01-07T15:26:23-05:00

Background

We have had several clients come to us with an interesting problem:

They have multiple agile project teams that are using different project management and agile planning tools such as Jira or Azure DevOps (ADO). For example, their .NET projects use ADO with Azure, and their Java projects use Jira and Amazon Web Services (AWS).
Each of the teams is able to plan their own backlog in Jira/ADO, but the higher-level Program Management Office (PMO) had no way of understanding how the different teams were working towards the higher-level program capabilities and value streams. The PMO was looking to adopt a Scaled Agile methodology such as SAFe, and liked the functionality in SpiraPlan for managing program backlogs but could not change the tools used by the teams.

The solution was to use the Spira data synchronization service in conjunction with our plugins for Jira and ADO and the Scaled Agile functionality of SpiraPlan. Problem Solved!

The Solution

Using SpiraPlan Program Capabilities

Using the Scaled Agile program management functionality in SpiraPlan, you can easily create capabilities that describe the high-level business value that a new aspect of the program will bring. These capabilities can be classed into Epics and Features as shown below:

In SAFe terminology, these are the program backlog items that consist of both business features and potential technology enablers. They will span multiple projects and teams. In this example, we have created a new program capability called "Generate cross-system reporting functionality". This new capability is shown to have a 50% completion state. We shall show you where this comes from later in the article!

You can then map these program capabilities to program milestones. These milestones are the high-level dates and goals by which one or more capabilities should be done by. For example, our new capability could be included in the "Major Q1 Release" milestone due at the end of the first quarter.

Mapping to Product-Level Backlog Items

If you now drill down on the specific capability, you can see the different product backlog items (requirements) that the capabilities map to. In this example, the new program capability requires three Jira user stories and one ADO backlog item to be completed for the capability to be marked as fully complete.

The great news is that each of these items is directly linked to a corresponding item in Jira:

Similarly for the user story backlog item in ADO, the SpiraPlan requirement maps to it automatically:

So, as the teams work in Jira and ADO to complete the various product backlog items, the overall capability status in SpiraPlan will be updated accordingly. The PMO can then plan the overall program in SpiraPlan, defining the capabilities and milestones, then leave it up to the product teams (working in Jira/ADO) to keep their status up to date. They can then get a top-down view on the progress of the capabilities. In this example, once all of the Jira/ADO backlog items are marked as completed, the progress bar of the capability in SpiraPlan will show as 100% green.

Reporting Across the Program

We recommend grouping the various SpiraPlan products under the overarching SpiraPlan program. This lets you have the individual teams work separately and still facilitate the PMO to have high-level visibility. We believe this gives the teams tactical autonomy yet affords the PMO a strategic view of the projects. The benefit of this approach is that it avoids the temptation of micromanagement that could happen if the PMO tried to dictate the product-level backlog directly (and is an agile anti-pattern).

Within SpiraPlan you can view the products in the program and use the project portfolio management functionality to tag the different products and report on them accordingly:

The program dashboards include several different reporting widgets to allow the PMO to see the status of the program. There is a capability view that lets you see the overall progress of the different program capabilities by milestone:

In addition, you can drill down further to display the product-level information to see the progress of the product backlog items in the active releases/sprints:

This includes all of the active products in the current program.

Conclusion

When you use the SpiraPlan Scaled Agile program backlog management functionality in conjunction with the Spira data-synchronization platform, you get the best of both worlds (the "genius of the AND"). You can plan, track, and manage complex programs consisting of different heterogeneous teams and yet give those teams the flexibility to use other tools, such as Jira and/or ADO, to manage their own backlogs.

Challenges in the Retail Industry

2023-12-20T15:36:00-05:00

Challenges

The retail industry is facing myriad challenges in the 21^st Century. Consumers’ behavior has been changing dramatically since the rise of the pure-play Internet retailers of the late 1990s. This trend has been exacerbated by the increasing influence of social media, viral marketing and the need to cultivate authentic brand evangelists.

In addition, retailers can no longer provide a single channel for marketing, sales and fulfillment. Consumers expect to be able to shop across online and physical channels seamlessly, ordering online and picking up in-person (or the reverse).

The Rise of Big Data

With the advent of real-time, actionable data, retailers need to replace the old play-book of mass-marketing and advertising, with mass-customization and just-in-time message marketing. The ability to mine consumers purchasing, social and work habits and cross-reference with real-time location offers retailers that leverage this data a first-mover advantage against their competition.

The Information Technology Challenge

These trends are transforming the retail industry. Retailers, both B2B and B2C, will have to deal with changes in the way their customers buy, communicate and search for information about products. This means that retailers will need to be able to more easily plan, acquire, test, deploy and manage their IT assets.

SpiraTeam from Inflectra provides the premier solution for managing all of your IT requirements, quality management processes and ensure that you can plan your technology projects on-time and on-budget every time. With SpiraTeam, you can stay on top of the changes and manage them rather than them managing you!

When you are dealing with testing retail transactions containing large volumes of highly precise data, manual testing doesn’t cut it anymore. When you need to automate the testing of your e-POS systems or your back-office ERP platform, our Rapise test automation platform is ready to help. Rapise has been built from the ground-up to support the testing of complex, mission-critical applications.

Scrum of Scrums: Definition, Purpose, Best Practices, & More

2024-02-21T13:50:48-05:00

What is Scrum of Scrums?

Scrum of Scrums is a scaled agile framework designed specifically to improve communication and collaboration between multiple Scrum teams working on a single project. As these projects grow (or scale) in complexity and scope, a more structured approach is necessary to manage inter-team dependencies. Scrum of Scrums acts as this connective tissue, promoting cohesion and efficiency at larger scales than traditional Scrum would be capable of.

Benefits & Advantages

This framework provides a range of benefits, which serve as a foundation for successful collaboration in large-scale projects:

Efficient communication and coordination - as projects grow, maintaining effective communication becomes more difficult. Scrum of Scrums provides a structured platform for teams to share updates, discuss challenges, and coordinate efforts — ensuring that everyone is moving in the same direction.
Rapid problem resolution - with representatives from each team present, impediments and dependencies are quickly identified and addressed. This quick problem-solving capability minimizes delays, allowing teams to maintain momentum and meet their deadlines and goals.
Enhanced transparency - by offering a centralized view of project progress, this not only keeps all teams informed but also fosters a culture of openness and accountability.
Cross-team collaboration - it also encourages harmony and knowledge sharing between teams. This cross-team collaboration makes it so that the collective intelligence of the entire organization is leveraged, leading to innovative solutions and improved overall productivity. Also, the use of SenseHR software improves documentation and knowledge sharing. Through the software's unique graph database, any type of HR data can be accessed in a way that traditional HR software cannot. This resource becomes invaluable for new team members during on-boarding, ensuring a smoother integration process by providing access to historical project data and facilitating a quicker understanding of the project's evolution. Plus, documentation and knowledge-sharing capabilities of HR software enhance collaboration and ensure that critical information is readily available to the entire team.

Scrum of Scrums vs. LeSS

Large-Scale Scrum (LeSS) is another Scrum variant designed for teams at scale, but has some key differences from Scrum of Scrums. LeSS focuses on simplifying the overall framework, emphasizing the importance of a single Product Backlog. On the other hand, Scrum of Scrums accommodates multiple Product Backlogs, providing more flexibility for larger projects with diverse requirements.

Scrum of Scrums Meetings

These collaborative sessions are where representatives from multiple Scrum teams come together to share updates, discuss inter-team dependencies, coordinate efforts, and more. Meetings are the core of what makes Scrum of Scrums work, and they have the following structure:

Purpose/Goal

The primary purpose of Scrum of Scrums meetings is to synchronize activities and ensure alignment across multiple Scrum teams. They play a crucial role in identifying and resolving cross-team roadblocks, cultivating collaboration, and maintaining a shared understanding of the project's trajectory.

Agenda

The Scrum of Scrums agendas typically include:

Team updates - each team representative provides a succinct update on their team's progress since the last meeting. This includes completed tasks, ongoing work, and any potential issues.
Dependencies and hurdles - teams discuss any task dependencies or roadblocks they are encountering that may impact project work (either their own or that of other teams).
Coordination of efforts - teams collaboratively discuss and coordinate their efforts so that the work is aligned across all teams, preventing duplication of efforts and addressing any potential conflicts.

Who Attends

Representatives from each Scrum team attend these meetings — typically individuals with a deep understanding of their team's progress and challenges. This keeps discussions informed and constructive, as opposed to representatives simply being messengers who may struggle to answer and resolve technical or complex questions.

How Often?

The frequency depends on every project's size and complexity but is generally conducted at least once a week. Regular meetings keep a consistent flow of information and maintain a proactive approach to problem-solving.

Scrum of Scrums Best Practices

When implementing this framework, there are a number of ways to avoid common pitfalls that may lead to trouble or negate some of the benefits we discussed above:

Clear Communication Channels

Establishing clear communication channels ensures that information flows seamlessly between Scrum teams during meetings. Utilize tools like video conferencing, collaborative messaging platforms, or project management software that facilitate a seamless flow of information and reduce the risk of misunderstandings.

Cross-Team Collaboration Tools

Implementing tools for collaboration improves real-time communication and information sharing between Scrum teams. These act as a central hub for new updates, discussions, and issue tracking, streamlining collaboration and keeping everyone on the same page. If you use Jira for these features, you might want to consider switching to a new platform due to Jira Server support ending. Learn what your best options for Jira alternatives are here.

Regular Retrospectives

Frequent review sessions focused on the Scrum of Scrums process enable teams to reflect on their efforts so far. Gathering feedback, identifying areas for improvement, and making adjustments based on these reviews result in continuous enhancement of the overall process.

Empower Teams

Give teams the power to take ownership of their updates, challenges, and solutions. It encourages autonomy and instills a sense of responsibility, contributing to a more proactive and collaborative environment. It also fosters a culture where teams feel confident in sharing challenges and proposing solutions, which is critical to the success of Scrum of Scrums.

Proactive Issue Resolution

Being proactive about finding resolutions involves systematically identifying and addressing roadblocks and issues during meetings. This means that issues are caught early on, preventing them from escalating and causing project delays and costs further down the road.

Documentation and Knowledge Sharing

Emphasize the importance of documenting key decisions, dependencies, and shared knowledge. This provides a valuable resource for team members via accessible information, which also aids in onboarding new team members and offering a historical record of the project's evolution.

Regular Training and Skill Development

Invest in training programs that enhance the skills of team representatives participating in Scrum of Scrums meetings. This could include leadership training, effective communication workshops, or agile methodology courses that help them contribute effectively to discussions and align with the agile methodology principles.

Flexibility in Meeting Structure

Tailor the structure of your Scrum of Scrums meetings to suit the evolving needs of the project. Be open to experimenting with different formats and adapting the agenda based on feedback and project dynamics. This ensures that meetings remain responsive to unique challenges and requirements, promoting continuous improvement and efficiency.

Scrum With SpiraTeam

For those looking to implement or improve a Scrum framework with larger development teams, SpiraTeam is the ideal solution with its industry-leading capabilities. These include drag-and-drop task boards, powerful sprint planning tools, customizable reporting dashboards, and much more.

We understand that transitioning from an old ALM or project management platform (or starting from scratch with your first) can often be difficult and requires a thorough assessment and evaluation. This is why you can try a free 30-day trial of the software to see how it helps your workflow and why we have award-winning customer/technical support services to make sure that any questions or concerns you have are answered. Get started with your free trial today!

How Does ChatGPT 4 See Inflectra

2023-12-15T12:27:30-05:00

What Did we Ask?

We asked ChatGPT:

What do you know about Inflectra Corporation?

ChatGPT Replied:

Inflectra Corporation, founded in 2006, is recognized as a market leader in the realms of software test management, test automation, and application lifecycle management. The company is known for its excellent customer support and offers solutions that cater to a diverse range of clients, from large corporations to individual developers. Inflectra's products are designed to assist in managing software development and testing lifecycles effectively and affordably, aiming to reduce time to market and enhance return on investment. Inflectra's headquarters are in the USA, and it has offices in over ten countries.

Then we asked it:

Could you draw an image that illustrates the above data about Inflectra Corporation?

See what it did next.....

What Did it Generate?

It generated the following image:

Which is pretty impressive.

Inflectra's Resounding Success at NEXP 2023 Conference

2023-12-15T11:26:22-05:00

At the Inflectra Booth:

The booth stood out as a hub of activity, drawing in a diverse crowd of attendees eager to explore the latest advancements in software quality and project management; it was a vibrant space for exchanging ideas, fostering genuine partnerships beyond vendor-client relationships. Additionally, Nimble made an appearance to elucidate our products and extend greetings to the attendees. The team engaged with professionals from various industries, showcasing Inflectra's suite of solutions and discussing how they can elevate software quality in the age of AI and Agile.

Workshops and Talks:

The conference buzzed with energy as attendees delved into interactive workshops and insightful talks. Inflectra, true to its commitment to knowledge sharing, took center stage with our LATAM QA Architect Consultant, Jorge Fernandez, leading two captivating talks:

Software Quality in Agile Teams Using SpiraTest and Rapise

Jorge Fernandez delivered a dynamic talk that served as a concise and actionable roadmap for achieving top-tier software quality within agile development teams. Attendees gained essential insights into harnessing the power of SpiraTest and Rapise, witnessing how these cutting-edge tools streamline quality assurance processes and elevate project management. Jorge's presentation was a must-attend for professionals seeking to optimize software quality in their agile workflows.

Inflectra: Elevate Software Quality in the Age of AI and Agile

In a world where software quality assurance is more critical than ever, Jorge's second talk explored the confluence of Artificial Intelligence (AI) technologies and Agile methodologies. The session provided deep insights into cutting-edge practices for improving software quality, identifying defects, and navigating the unique demands of Agile testing. Jorge also gave an overview of Inflectra's suite of solutions, including SpiraTest, SpiraPlan, and Rapise, showcasing how these tools adapt to the evolving paradigms of AI and Agile.

In general, participants expressed satisfaction with both presentations. Specifically, they showed keen interest in the ChatGPT plugin for SpiraPlan, and were intrigued by the versatility of Rapise as a tool adaptable to various environments.

Networking and Collaboration:

In addition to the talks and workshops, Inflectra actively engaged in networking, fostering collaborations, and building lasting connections with sponsors and attendees. The conference served as a dynamic platform for Inflectra to showcase its commitment to advancing software development and quality assurance. Inflectra's team participated in roundtable discussions and hosted informal meet-and-greet sessions. These interactions not only reinforced Inflectra's industry leadership but also exemplified its belief in the power of shared knowledge and community growth, making NEXP 2023 a memorable testament to the company's commitment.

It's a Wrap!

NEXP 2023 was a resounding success for Inflectra, reflecting its dedication to driving innovation and excellence in the software development landscape. As the conference concluded, Inflectra left an indelible mark, having not only shared valuable insights but also forged new relationships that will undoubtedly shape the future of software development.

Guide to Scrum Team Size & Roles

2023-12-29T14:33:50-05:00

Scrum Team Size

Determining the ideal Scrum team size is a critical aspect of effective project management. While there is no one-size-fits-all answer, general best practices suggest that a Scrum team should ideally consist of 5 to 9 members. This range promotes effective communication, collaboration, and flexibility. Smaller teams may struggle to handle the workload, while larger teams can face challenges in coordination and decision-making.

Signs That the Team is Too Big

Recognizing signs of an overly large Scrum team is crucial for maintaining agility and responsiveness. Indicators include communication breakdowns, increased coordination difficulties, and a decrease in overall productivity:

Communication Breakdown: Increased difficulty in coordinating and communicating effectively.
Reduced Flexibility: Larger teams may struggle to adapt quickly to changing requirements.
Decreased Accountability: Individual responsibility can diminish in larger groups.

If team members are finding it challenging to collaborate effectively or if the Scrum events become overly time-consuming, it may be a signal that the team size needs adjustment.

Should a Second Team be Added?

The decision of whether to add a second Scrum team should be based on workload, project complexity, and the need for specialization. If the existing team experiences constant bottlenecks or if the product backlog becomes overwhelming, it might be time to consider forming a second team:

Workload: If the team consistently struggles to complete work within the sprint timeframe, it might be an indication that the team is overloaded.
Dependency Management: If dependencies between tasks become a bottleneck, it's time to reassess the team's size.

However, the transition should be gradual, with proper planning to maintain effective collaboration between the teams.

How to Accomplish

Creating a second Scrum team requires careful planning. Some considerations to keep in mind include:

Skill Distribution: Ensure both teams have a balanced mix of skills to independently deliver value.
Communication Channels: Establish clear communication channels between the teams to avoid silos.
Scrum of Scrums: Implement a Scrum of Scrums to coordinate efforts and address cross-team dependencies.

Scrum Roles & Responsibilities

There are three major roles in the Scrum framework, each with its own purpose and responsibilities.

Product Owner

The Product Owner plays a pivotal role as the bridge between the development team and stakeholders. Their responsibility lies in meticulously managing the product backlog by curating and prioritizing tasks based on business value. The PO is also tasked with defining clear requirements through user stories and acceptance criteria, ensuring the team understands and delivers what stakeholders truly need. Stakeholder collaboration is key to understanding and conveying their needs, which involves constant engagement to align development efforts with broader business objectives.

Scrum Master

The Scrum Master stands as the guardian of the Scrum process, fostering an environment of continuous improvement. They facilitate Scrum ceremonies, ensuring their effectiveness, and actively remove impediments that hinder the team's progress. Embodying servant leadership, the SM nurtures a self-organizing and empowered team, encouraging collaboration and a commitment to Scrum principles.

Development Team

Comprised of a cross-functional, self-organizing group, the Development Team is responsible for delivering increments. Their tasks involve the execution of sprint goals, continuous improvement of processes, and autonomous decision-making on how to achieve objectives. This team operates cohesively, demonstrating a commitment to delivering value and embracing a proactive approach to challenges.

These three positions also form the foundation of scaled agile roles.

Ideal Scrum Team Size & Composition

While every situation, team, and project is different, there are several rules of thumb that can be used to find a healthy balance of size, skills, and communication. When it comes to creating the ideal scrum team composition, we recommend starting with:

Size and Structure

The ideal Scrum team is composed of 5-9 members, striking a balance that facilitates effective intra-team dynamics and cooperation. Cross-functionality within the team ensures a range of specialties, promoting autonomy and adaptability. Clear roles and responsibilities define the team's structure, preventing ambiguity and promoting accountability.

Optimal Size: Aim for 5-9 members to ensure effective communication and collaboration.
Cross-Functionality: Include a mix of skills within the team to foster autonomy.
Dedicated Roles: Clearly define and understand each team member's role to avoid ambiguity.

Collaboration and Communication

Establishing open channels for communication is crucial for fostering a strong culture of working together. Frequent interactions within the team and with stakeholders create an environment where ideas flow freely. Cross-functional collaboration breaks down silos, ensuring a holistic approach to problem-solving and innovation.

Open Communication Channels: Establish transparent communication channels to foster collaboration.
Frequent Collaboration: Encourage regular conversations and engagement within the team and with stakeholders.
Cross-Functional Collaboration: Break down silos by promoting cooperation and collaboration across disciplines.

Features of a Successful Scrum Team

There are several characteristics that are emblematic of a well-run and effective Scrum team:

Self-Managing: A successful Scrum team embodies self-management by proactively identifying and solving problems without external intervention. Each team member takes ownership of tasks, fostering a sense of responsibility and dedication to the team's success.
Communication: Transparency is at the core of successful communication within a Scrum team. An environment where information is shared openly builds trust, while active listening ensures a deeper understanding of each team member's perspective. Effective communication is the linchpin holding the team together.
Adaptability: The ability to adapt to change is another hallmark of a successful Scrum team. Flexibility allows the team to pivot based on evolving requirements, while resilience in the face of setbacks turns challenges into opportunities for growth. Embracing change becomes a cultural norm within the team.
Continuous Learning: Regular retrospectives are a cornerstone for continuous improvement, providing a platform for the team to reflect on processes and identify areas for enhancement. Offering ongoing training opportunities ensures that the team stays updated on industry best practices, fostering a culture of perpetual learning.
Empowerment: Empowering team members to make autonomous decisions creates a sense of accountability and ownership. Encouraging innovation within the team, valuing creative solutions, and creating an environment where ideas are embraced contribute to a culture of empowerment.

SpiraTeam for Scrum Projects

If you’re looking for a better way to achieve Scrum team efficiency, SpiraTeam is the industry-leading solution. With powerful features and functionality ranging from planning boards and customizable reporting to backlog and sprint planning, it enables scrum teams to collaborate and manage their tests and data more efficiently than other options on the market. Even better, we offer a no-commitment, 30-day free trial for you to test it out and see how it integrates with your teams’ workflows. Click the link below to start your free trial today!

Inflectra at AutomationStar 2023: Charting New Territories in Automation

2023-12-01T13:55:21-05:00

Setting the Stage for Automation Star Success

On Inflectra's much-anticipated arrival day in Berlin for Automation Star, the team embarked on a seamless journey, exuding a palpable excitement for the upcoming conference. Eager to make a lasting impression at Automation Star, we wasted no time in setting up their booth with precision and flair, transforming it into a captivating showcase of their innovative automation solutions. Afterwards, we immersed ourselves in the local culture, savoring the diverse culinary delights Berlin had to offer. From traditional German cuisine to international flavors, the team reveled in the rich tapestry of tastes, forging connections and building anticipation for the eventful days that lay ahead.

Highlights from the Inflectra Booth

Berlin, the bustling hub of technological innovation, played host to the recent Automation Star conference. Among the myriad of companies showcasing their cutting-edge solutions, Inflectra stood out as a beacon of excellence in the realm of automation. With a focus on streamlining processes and enhancing efficiency, Inflectra's booth at the conference left a lasting impression.

Our exhibition provided visitors with several unique experiences:

The Swag Galore: We presented an array of custom-designed Inflectra merchandise, combining both fun and practicality, which proved to be a major attraction.
In-Depth Product Walkthroughs: Detailed demonstrations and interactive sessions at our booth provided in-depth insights into how our software solutions can transform automation processes.
Meet the Experts: Our dedicated team was available to answer questions, discuss best practices, and delve into the future of automation technology.

Uncovering Culinary Delights and Cultural Treasures

During our to Automation Star, the team took full advantage of our downtime to explore the vibrant city and uncover its hidden gems. From the moment we stepped onto the bustling streets, Berlin's diverse culinary scene captivated our taste buds. We savored local treats, immersed ourselves in the city's rich culture, leisurely strolled through picturesque neighborhoods (while marveling at architectural wonders), and delightfully experienced a variety of culinary experiences. Our time in Berlin was about professional growth while forging memorable experiences as a team - savoring the unique blend of history, art, and culinary delights that Berlin has to offer.

Looking Ahead

As the Automation Star conference in Berlin drew to a close, Inflectra left an indelible mark on the attendees and the industry at large. The event served as a springboard for Inflectra to continue pushing the boundaries of automation and innovation. With a firm commitment to empowering businesses through technology, Inflectra is poised to shape the future of automation in the software development landscape. Inflectra's participation in the Automation Star conference in Berlin was not just a showcase of products; it was a celebration of innovation, collaboration, and the relentless pursuit of excellence. As the tech world continues to evolve, Inflectra remains a guiding star, illuminating the path towards a more efficient and automated future.

If you're interested in discovering how our tools can enhance your automation practices, get in touch with us to explore excellence at its core. Stay updated on Inflectra's latest events, product releases, company news, and more by subscribing to our monthly newsletter!

Inflectra in the News - Sept - Nov 2023 News Roundup

2023-11-28T17:06:21-05:00

Interviews

Application Architectures and Software Development with Techstrong.TV - September 11, 2023

Adam Sandman emphasizes the dynamic nature of application architectures in the context of modern software development. Acknowledging that these architectures stand as best practices, Sandman underscores the necessity for continuous evolution to tailor them to the unique needs of each organization. He highlights the ever-changing landscape of technology and business requirements, emphasizing the importance of adaptability and responsiveness in ensuring that application architectures remain not just current but optimally aligned with the strategic goals and operational demands of every individual organization. Sandman's insights shed light on the ongoing commitment to refinement and innovation as a fundamental aspect of navigating the evolving landscape of software development. Watch now.

Driving Success through Intentional Leadership with Beyond 8 Figures - September 13, 2023

In this podcast episode, A.J. Lawrence and Adam Sandman delve into the pivotal role of intentional leadership in propelling business growth. They explore the merits of intentional culture-building, coaching teams, and aligning values to drive our company forward. Key topics include the advantages of bootstrapping for maintaining control, the critical transition from founder-led sales to a specialized team, strategies for optimizing our sales process, and the emphasis on coaching rather than traditional management for decentralized leadership. Additionally, we underscore the significance of intentional culture-building in promoting team cohesion and contributing to our overall business success. Watch now.

Publications

Seamless Banking Experience: A Deep Dive into Mobile App Testing with TestMetry - September 8, 2023

In today’s digital era, mobile applications have become the cornerstone of the banking industry’s interaction with its customers. Banking institutions rely heavily on mobile apps to provide convenient and efficient services to users, everything from instant fund transfers to real-time balance inquiries — turning smartphones into virtual branches. However, the complexities of financial transactions and the stringent regulatory landscape demand rigorous testing procedures to guarantee a seamless and secure user experience. Read more.

Small-Business Cybersecurity: 20 Effective Tips From Tech Experts with Forbes Technology Council - October 12, 2023

Small-business owners, operating with limited staff and budgets, must prioritize cybersecurity, as a data breach can be catastrophic for them, comparable to a crisis for larger companies. Despite the absence of tech professionals, there are affordable and straightforward steps and resources available to strengthen cybersecurity. In collaboration, 20 industry leaders from Forbes Technology Council offer valuable advice to guide small-business owners in the continuous effort of managing cybersecurity. Read more.

Ensuring Vehicle Safety through Software Testing with EuroSTAR Huddle - November 3, 2023

From advanced driver assistance systems to infotainment features, software is omnipresent in the vehicles we drive today. However, with the increasing role of software, the criticality of software testing in ensuring vehicle safety cannot be understated. In this article, we will delve into the world of software testing and its indispensable role in enhancing the safety of vehicles on the road. Read more.

Retail Mobile App Testing in Preparation for Holiday Season with Supply Chain Brain - November 21, 2023

As the holiday season approaches, retailers across the globe are gearing up for the most significant shopping period of the year. An often-overlooked aspect of ensuring a successful holiday season is rigorous testing and quality assurance (QA) of mobile apps and websites. In an age where digital shopping is the norm, retailers cannot afford to ignore the importance of a seamless and reliable online shopping experience. Read more.

17 Key Strategies For Designing A Secure, Efficient Network with Forbes Technology Council - November 28, 2023

Tech leaders and their teams face the imperative of designing network architectures that not only deliver reliable service but also safeguard against unauthorized access. In the following insights, 17 members of Forbes Technology Council share key strategies for crafting and upkeeping a secure and efficient network—a vital skill set for navigating the demands of the contemporary digital landscape. Read more.

Talks

Speaking at the DC Tech & Venture Coalition (DCTAV) Leadership Meeting - September 25, 2023

Adam Sandman, had the honor of being a speaker at the monthly leadership meeting of the Washington, DC Technology & Venture Coalition (DCTAV) last week. During the event, he shared insights into his journey founding Inflectra and delved into the theme of "The Surprises and Secrets of Scale At Different Jumps." Following the presentation, Adam engaged in a Q&A session with the audience, comprised of local entrepreneurs, investors, and technology enthusiasts. The discussion focused on strategies to navigate transitions between company growth stages and avoid costly mistakes in the process. See more.

Risk, AI, and Software Testing: A Deep Dive at STARWEST - October 5, 2023

The contemporary landscape of software development is rapidly evolving, and at the heart of this transformation lies the power of Artificial Intelligence. As AI permeates the domain of software testing, it promises enhanced efficiency and precision. Yet, every technological stride comes paired with its own set of complexities. Join Adam Sandman for a pivotal discourse on the integration of Risk-Based Testing (RBT) within this AI-centric paradigm. See more.

Managing Risk-Based Testing in the Age of AI at Testing Talks, Melbourne - October 12, 2023

Artificial Intelligence (AI) is revolutionizing how software testing is performed, allowing for faster and more accurate detection of defects. However, with this new technology comes new risks that must be managed to ensure the quality and reliability of the software being developed. In this talk, Adam Sandman will explore the concept of Risk-Based Testing (RBT) and how it can be applied in the age of AI. He will discuss the challenges that arise when implementing RBT, including the need to balance the benefits of AI with the risks of false positives and false negatives. Adam will also examine the various techniques and tools that can be used to manage these risks, such as model-based testing, exploratory testing, and risk analysis. See more.

KEEP UP-TO-DATE

Inflectra at ATD: Six Years of Community Support and Collaboration

2023-11-21T05:45:51-05:00

Demonstrating Real-World Solutions

At our booth, we took a hands-on approach, demonstrating the latest and most impactful features of our flagship products - SpiraPlan and Rapise. These two products together form one of the most complete and powerful software product management and test automation platforms on the market today.

We focused on practicality, showing how our end-to-end platform enhances the efficiency of agile software development and testing processes or how it can seamlessly fit with various other tools in the market.

Our booth conversations were a two-way street, offering us new viewpoints and hopefully providing useful takeaways for our visitors.

Engaging and Learning from the Community

Interacting with attendees at ATD was both enlightening and affirming. We gained valuable insights into the evolving needs of the software testing and software project management community,

We did our best to share how Inflectra’s solutions are tailored to meet these challenges head-on.

We also made sure we supported the community in other ways:

- by having fun at the 90s Party

- by speaking on the ATD 2023 virtual track and being recognized as a speaker during the event. Congratulations to Dermot Canniffe for yet another speaking opportunity at ATD.

Team Inflectra: United and Dynamic

ATD 2023 was particularly special for team bonding and unity. Bringing together our team members from Europe, the Middle East, and Africa, the event served as a perfect backdrop for fostering team spirit and collaboration. We shared our successes, exchanged knowledge, and brainstormed future strategies, all while enjoying the lighter moments – like navigating a 24-hour railroad strike, sharing a taxi adventure packed with suitcases, exploring Berlin, and savoring desserts at the city's Christmas markets.

Looking back at ATD Potsdam, we are filled with a sense of pride and gratitude. The event was a testament to the vibrant community of agile testing and a milestone in our ongoing journey in the industry. The interactions at our booth, the insightful discussions, and the team bonding experiences were invaluable, and we're already looking forward to what future editions will bring.

Inflectra's Impact: Sponsoring Success at Agile + DevOps East 2023

2023-11-14T10:37:37-05:00

Arrival and Set Up Day

Our team initiated the trip with an early departure from the DC area. Following a brief flight, we were welcomed by the vibrant ambiance of Orlando International Airport, kicking off the Agile + DevOps conference experience. After arriving safely to the beautiful Caribe Royale resort, the picturesque venue hosting the event, the day continued with lunch by the pool to recharge and soak in Florida's rays before a productive time ahead.

After enjoying a scenic fuel-up, our team eagerly went into setting up the booth and ensure full readiness for engaging with participants the next morning. During our preparation, we strove to effectively showcase Inflectra's mission while maintaining an inviting atmosphere for attendees. Once the booth was seamlessly organized, we took a short walk down the hall to the Welcome Reception for a cold beverage and hot hors d'oeuvres - it was a fantastic opportunity to reconnect with familiar faces and forge new connections.

Booth Buzz and Networking Extravaganza

Upon the commencement of the conference, Inflectra's booth immediately became a hub of excitement. At the booth, we were thrilled to engage with attendees, imparting knowledge on how our products can elevate their Agile and DevOps practices. The passport game brought a steady stream of curious minds to our booth, leading to valuable interactions.

In addition to our prominent presence at the conference, Inflectra actively participated in several noteworthy events throughout the day. To underscore our commitment, we took pride in sponsoring both lunch and the afternoon Networking Break, reinforcing our role as a significant contributor towards the conference and the Agile + DevOps community. Additionally, we supplied a great prize towards Techwell's renowned raffle to conclude day one: a cutting-edge laser projection keyboard (congratulations to the selected winner)!

Before we knew it, we wrapped up our first full day by unwinding at Calypsos, a distinguished restaurant within the resort. There, we had the pleasure of spending quality time with our esteemed partner, Checkpoint Technologies, further strengthening our collaborative bond. It was the perfect way to end a day brimming with valuable and meaningful interactions with fellow attendees and exhibitors.

Exploring SpiraPlan's Role in Healthcare Transformation

The enthusiasm and wealth of learning opportunities seamlessly flowed into the second day of Agile + DevOps East. This time, Teresa Langston, Inflectra's Senior Pre-Sales Engineer, took the stage to deliver an insightful ITP titled "Unleashing Scalability, Agility, and Compliance in Healthcare with SpiraPlan." Attendees were captivated as she showcased SpiraPlan through engaging demonstrations tailored to address unique requirements and interests. This session not only showcased the versatility of Inflectra's solutions, but also offered a profound understanding of how our tools can revolutionize and streamline processes within the dynamic landscape of the healthcare sector.

As the day unfolded, we made sure to make the most of every last opportunity to share knowledge and insights before the conference closed out. With heartfelt farewells, we expressed gratitude to the vibrant individuals we had the privilege of meeting. Until the next gathering, farewell Agile + DevOps East!

Discovering Orlando's Charms: A Post-Work Retreat

After hard work, we treated ourselves to an exploration around Orlando's gems. A highlight from our excursions was an evening in Disney Springs. While there, we had a delightful meal at Wolfgang Puck, watched guests partake in an exhilarating hot air balloon ride, took in the scenery of the waterside shopping district, and enjoyed a break from the chilly DC weather. These mini adventures served as a fantastic way to polish off a successful journey to Orlando, where we had the fortunate opportunity to educate others about the exceptional offerings provided by Inflectra.

Until Next Time!

Inflectra's experience at Agile + DevOps East was marked by meaningful connections, productive engagements, and a touch of Orlando's magic. As we gracefully conclude the conference, we not only carry valuable insights, but also the glow of creating partnerships and collaborations epitomizing the tech community.

If you would like to learn more about how our tools can elevate your Agile and DevOps practices, contact us to experience quality at its core. You can also see more of Inflectra's upcoming events, product updates, company news, and more by subscribing to our monthly newsletter!

Examples of using GenerativeAI in SpiraPlan - Get Ready for v7.10

2024-08-17T05:33:03-04:00

Overview

In this examples, I have created a couple of different requirements in SpiraPlan. So that I could generate test cases, tasks, risks and BDD steps, I made sure that the requirements were of a type that supported BDD steps, and that the user I was logged in with had the permissions to create all four types of item. In each example, I used the new ChatGPT SpiraApp out of the box, with the default prompts and default parsing regular expressions.

Example 1: Reserving a Flight

Many of us have experience booking / reserving airline flights using websites such as Expedia, Travelocity, so I thought it would be an interesting example to write a simple one-line requirement "The ability to reserve a flight" and see what the AI model would generate:

Test Cases

The test cases that it generated seem plausible, covering different "happy path" and edge case scenarios:

Test #	Name	Status	Last Execution Date
TC391	Verify that a user can reserve multiple flights in one reservation.	Not Run	--
TC390	Verify that a user can successfully reserve an airline flight.	Not Run	--
TC393	Verify that a user cannot reserve a flight if the flight is already fully booked.	Not Run	--
TC392	Verify that a user cannot reserve a flight if the payment details are invalid.	Not Run	--
TC394	Verify that a user cannot reserve a flight without providing all the required information.	Not Run	--

Now there are probably many other test cases that are missing, but imagine that the requirement was more detailed, for example "The ability to book a round-trip flight between two cities as a single reservation", then you would get more detailed test cases as well. One other idea would be to add functionality to our plugin that would let it generate more detailed requirements first. Then you could use those generated child requirements as the basis for the test cases.

If you click on one of the test cases inside Spira, there is just a single step right now with a basic description. However, it would be relatively easy to extend the plugin to subsequently call OpenAI for each generated test case and ask it to create the possible test steps for each one in turn.

Tasks

If you look at the tasks it generated, they cover the main development areas, from user interface to the back end processing of the reservations.

Task #	Name	Status	End Date	% Completed
TK60	Design the user interface for the flight reservation system.	Not Started	--	0%
TK61	Conduct user acceptance testing to gather feedback and make any necessary improvements to the system.	Not Started	--	0%
TK62	Implement the functionality to search for available flights based on user input, such as departure and arrival cities and dates.	Not Started	--	0%
TK63	Create a system to track and manage reserved flights, including updating seat availability and storing reservation information.	Not Started	--	0%
TK64	Develop the functionality to confirm the flight reservation and generate a confirmation number for the user.	Not Started	--	0%
TK65	Implement security measures to protect user information and payment details.	Not Started	--	0%
TK66	Implement the functionality to allow the user to select a flight and reserve a seat.	Not Started	--	0%

BDD Scenarios

The BDD option generated four basic scenarios: the success case, followed by three failure cases (invalid travel dates, invalid airports, and no available flights):

Step	Description
1	Successful flight reservation Given I am on the flight reservation page When I enter my departure and destination airports And select my preferred travel dates And choose the number of passengers And click on the "Search" button Then I should see a list of available flights And I should be able to select a flight from the list And I should be redirected to the flight details page And I should see the flight details and fare And I should be able to enter passenger information And I should be able to review and confirm my reservation And I should receive a confirmation email with my reservation details
2	Invalid travel dates Given I am on the flight reservation page When I enter my departure and destination airports And select invalid travel dates (e.g. past dates) And choose the number of passengers And click on the "Search" button Then I should see an error message indicating that the travel dates are invalid
3	Invalid departure or destination airports Given I am on the flight reservation page When I enter an invalid departure or destination airport And select my preferred travel dates And choose the number of passengers And click on the "Search" button Then I should see an error message indicating that the airports are invalid
4	No available flights Given I am on the flight reservation page When I enter my departure and destination airports And select my preferred travel dates And choose the number of passengers And click on the "Search" button Then I should see a message indicating that there are no available flights

Based on my experience using flight reservation software, that did feel like the three main failure cases, though of course there are more niche edge cases that we'd need to consider. It was impressive that was also able to generate the more detailed steps for the requirement.

Identifying Risks

Finally, I asked the plugin to generate a list of possible business and technical risks that could occur with this new feature:

The list that is generated is helpful, but does seem to follow the standard "-ilities" model, and some do feel like boilerplate (security, performance, etc.). That being said, several of the items were ones that I would have forgotten to include, and would be useful when developing a real flight reservation system.

Example 2: An E-Commerce Shopping Cart

One of the most common system features is the ability to have a "shopping cart". This UI paradigm is not only used for e-commerce, but often used in other applications as well. For example, when managing Reserved Instances (RIs) in Amazon Web Services (AWS) Elastic Cloud Compute (EC2) you put the items into a virtual shopping card. So I asked the plugin to generate the test cases and development tasks associated with implementing a shopping card:

Test Cases

The test cases it generated are more granular than the ones for the airline reservation example and cover a lot of good negative and positive tests, such as adding items with a zero to a shopping card and making sure you can add single and multiple items:

Test #	Name	Status	Last Execution Date
TC308	Adding a single item to the shopping cart	Not Run	--
TC312	Adding an item that is out of stock to the shopping cart	Not Run	--
TC311	Adding an item to the shopping cart and removing it	Not Run	--
TC310	Adding an item to the shopping cart and verifying the quantity	Not Run	--
TC309	Adding an item to the shopping cart and verifying the total price	Not Run	--
TC313	Adding an item to the shopping cart from different pages	Not Run	--
TC314	Adding an item with a specified quantity to the shopping cart	Not Run	--
TC315	Adding an item with a zero quantity to the shopping cart	Not Run	--
TC316	Adding multiple items to the shopping cart	Not Run	--

Tasks

The suggested development tasks are a bit skewed to the back-end side of things, where there is a good level of definition. For the UI side, you'd need more detail on the screens and user interface in real life:

Task #	Name	Status	End Date	% Completed
TK74	Create a user interface for displaying products and allowing users to add them to the shopping cart.	Not Started	--	0%
TK75	Develop backend logic to handle updating the inventory of the products after a successful purchase.	Not Started	--	0%
TK76	Develop backend logic to handle emptying the shopping cart and removing all items from the database.	Not Started	--	0%
TK77	Develop backend logic to handle error scenarios and display appropriate error messages to the user.	Not Started	--	0%
TK78	Develop backend logic to calculate the total price of the items in the shopping cart.	Not Started	--	0%
TK79	Develop backend logic to handle removing items from the shopping cart when a user clicks on the "Remove" button.	Not Started	--	0%
TK80	Develop backend logic to handle the checkout process, including validating user information and processing payment.	Not Started	--	0%
TK81	Develop backend logic to handle updating the quantity of items in the shopping cart when a user changes the quantity input.	Not Started	--	0%
TK82	Develop backend logic to handle adding items to the shopping cart when a user clicks on the "Add to Cart" button.	Not Started	--	0%

One way to improve this would be for us to look through all of the task types and ask it to generate tasks of each type. Alternatively, we could enhance the plugin to ask the OpenAI model separately for all:

Front-end development tasks
Back-end development tasks
Database development tasks
API / Integration development tasks

Example 3: Booking a Hotel Room

You can tell I am a frequent traveler! As well as the example to reserve an airline flight, I also created a requirement for a feature that lets you book hotel rooms.

Test Cases

The plugin generated a very different style of test case for this example, everything was prefixed by "Verify" and it focused a lot more on the negative test cases as well as the one happy path successful case:

Test #	Name	Status	Last Execution Date
TC395	Verify that a hotel room can be successfully booked when all required information is provided.	Not Run	--
TC400	Verify that an error message is displayed when an invalid room type is selected.	Not Run	--
TC396	Verify that an error message is displayed when the check-in date is in the past.	Not Run	--
TC398	Verify that an error message is displayed when the check-out date is before the check-in date.	Not Run	--
TC397	Verify that an error message is displayed when the hotel name is not provided.	Not Run	--
TC399	Verify that an error message is displayed when the number of guests is not provided.	Not Run	--

It felt like a lot of the tests were limited to UI data validation tests, rather than testing the underlying business logic. Some of this could be due to the fact that the requirement was called Book a Hotel Room vs. Reserve a Hotel Room so the focus was on the literal booking part. If you compare the results of this example with the airline one, you can see how important it is to have a good requirement name when using this plugin.

Tasks

The tasks it generated seemed reasonable, and it had a better mix of UI and back-end tasks as compared to the shopping cart example:

Task #	Name	Status	End Date	% Completed
TK67	Design the user interface for the hotel booking feature.	Not Started	--	0%
TK68	Optimize the performance of the hotel booking feature to ensure fast and efficient processing.	Not Started	--	0%
TK69	Implement the functionality to search for available hotel rooms based on specified dates and location.	Not Started	--	0%
TK70	Implement the ability for the user to select a hotel room and proceed to the booking process.	Not Started	--	0%
TK71	Test the hotel booking feature to ensure it is functioning correctly and meets the requirements.	Not Started	--	0%
TK72	Implement the ability for the user to view and manage their hotel room bookings.	Not Started	--	0%
TK73	Implement the functionality to validate and process the user's payment for the hotel room booking.	Not Started	--	0%

BDD Scenarios

The suggested BDD scenarios were interesting this time. I was expecting it to simply give a single successful case and a few other failure cases. It actually gave us two successful cases, one where you simply booked a room as expected, and a second one where additional requests were entered. This is a common real-world use case (especially when I am traveling with my family), and it was impressive that it generated this.

Step	Description
1	Unsuccessful hotel room reservation due to unavailability Given a user wants to reserve a hotel room When the user provides the necessary details such as check-in and check-out dates, number of guests, and preferred room type Then the system should display a list of available hotel rooms matching the user's preferences And all the rooms are already booked for the specified dates Then the system should display an error message indicating the unavailability of rooms
2	Successful hotel room reservation Given a user wants to reserve a hotel room When the user provides the necessary details such as check-in and check-out dates, number of guests, and preferred room type Then, the system should display a list of available hotel rooms matching the user's preferences And the user selects a specific room from the list And the system confirms the reservation by displaying a success message
3	Unsuccessful hotel room reservation due to invalid input Given a user wants to reserve a hotel room When the user provides invalid or incomplete details such as missing check-in or check-out dates Then the system should display an error message indicating the invalid input And the system should not proceed with the reservation process
4	Successful hotel room reservation with additional requests Given a user wants to reserve a hotel room When the user provides the necessary details such as check-in and check-out dates, number of guests, and preferred room type And the user also provides additional requests such as a specific floor or a view Then the system should display a list of available hotel rooms matching the user's preferences and additional requests And the user selects a specific room from the list And the system confirms the reservation by displaying a success message, including the additional requests.

Identifying Risks

Finally, I asked the plugin to generate a list of possible business and technical risks that could occur with this new feature:

As we saw with the airline example, some of the risks felt a bit generic and boilerplate and could reasonably be applied to almost any requirement. However, some of the risks were very pertinent and relevant (double-booked rooms when using two systems that don't talk and integration with different hotel platform APIs).

Conclusion

As you can see from these examples, although the use of the ChatGPT / OpenAI SpiraApp is not a replacement for a good business analyst and test manager, it is a great time-saver. In the same way that Gmail Autocomplete is a great time-saver, using this new plugin will save countless hours of manual work and also uncover items that will have been missed by the team. Also, as you can see, we have many ideas for how to enhance the functionality once the first version is live next month.

Inflectra's Black Friday & Cyber Monday Bonanza: Elevate Your Software Delivery with Spectacular Deals!

2023-11-06T14:17:09-05:00

🚀 Take Advantage of the Season's Best Deals on SpiraTest and Rapise!

SpiraTest: Quality Assurance Made Remarkably Affordable
Quality assurance should never be a luxury, and for a limited time, it won't be. We're offering an incredible 35% discount on a new 1-year subscription to SpiraTest. It's our flagship test management solution that empowers you to orchestrate every aspect of your software testing lifecycle with ease and precision.

SpiraTest + Rapise Floating Bundle: A Duo of Dynamism
Why settle for one when you can have the best of both worlds? Pair the robustness of SpiraTest with the agility of Rapise, our premier test automation tool. The bundle is now available at a jaw-dropping 40% off for the first year. Optimize your testing processes, automate with sophistication, and ensure compliance with every release.

Reach out to us at sales@inflectra.com to get the promo code.

🌐 Experience the Difference

Don't just read about it—experience the transformative impact of our software suite first-hand. Click over to our Black Friday/Cyber Monday and see why teams across regulated and specialized industries choose Inflectra.

📆 Mark Your Calendars!

Deal Activation: November 20, 2023
Deal Expiration: November 30, 2023

Time is ticking, and these deals are timed. Don't miss your chance to make the smartest investment in your team's future.

🔍 The Details Matter

Offers are valid for first-time subscriptions only.
It cannot be combined with any other promotions or discounts.
Renewals will be at the standard subscription rate after the first year.
Other terms and conditions may apply.

Inflectra: Your Partner in Quality and Excellence

In a market where the pressure to deliver quickly and efficiently is matched only by the demand for impeccable quality, Inflectra stands by you. This Black Friday and Cyber Monday, let us equip you with the tools you need to succeed—without straining your budget. Reach out to us at sales@inflectra.com to get the promo code.

Join the ranks of our customers who've found in Inflectra the ally for delivering critical software on time, every time. Because when it comes to your success, we're all in—especially when savings and quality go hand in hand.

Happy Holidays!

Team Inflectra

At Inflectra, we're more than just software providers; we're your partners in defining and achieving new pinnacles of success. Celebrate this festive season by securing the future of your projects with Inflectra's Black Friday & Cyber Monday deals—your gateway to unmatched quality and compliance in software delivery.

Inflectra and Checkpoint Technologies Co-Sponsor PNSQC 2023: Elevating Software Quality Practices

2023-11-03T15:27:45-04:00

PNSQC provided a vibrant platform for the exchange of innovative ideas and industry insights. Team Inflectra teamed up with two of its most trusted Solutions Partners, Critical Logic and Checkpoint Technologies, to chat with attendees about tools and solutions provided by all three of the companies. We had great conversations with the attendees that stopped by our booth, and we gained a better understanding of the current challenges that quality managers and testing professionals face every day.

Bob Crews, the CEO And Co-Founder of Checkpoint Technologies, delivered his session Conquering Your Testing With Comprehensive and Agile Risk Analysis to the attendees of the conference! During his session, Bob discussed how performing Risk Analysis on testing assets can dramatically improve quality, covered key risk terminology and definitions, and provided two proven strategic approaches to Risk Analysis: comprehensive risk scoring, and a rapid, reliable Agile approach to risk scoring in detail. It was a great session. Bob was also able to discuss the advantages of using a tool like SpiraPlan to support tracking and mitigation of Risks within attendees' testing practices.

Amidst the professional discussions and informative sessions, a touch of enjoyment was added to the mix. Many ideas were exchanged during PNSQC, a great deal of networking and connecting occurred, and a lot of fun as well; to celebrate and wrap up a great event, Inflectra, Critical Logic, and Checkpoint Technologies hosted a post-conference happy hour. In this relaxed and jovial atmosphere, conference attendees had the opportunity to unwind and engage in casual yet constructive game of trivia. The game not only brought a sense of competition and excitement, but also offered attendees the chance to win enticing prizes. The three corporations coming together created an enjoyable and lighthearted way to cap off the event, creating lasting memories and strengthening the sense of camaraderie among the software quality community.

We very much appreciate the organizers and look forward to future events. Look out for Team Inflectra at the many conferences across the US, Europe, and the Middle East in the coming months. Please stop by, say hi, and maybe learn a little bit about how we can help you and your team deliver quality software, faster and with lower risk.

Recap - Develop Smarter, Deliver Faster: Spira and GitHub Integration Spotlight

2023-10-27T16:57:22-04:00

This collaboration with Coveros underlined the importance of having integrated tools in the modern development landscape. The webinar successfully showcased how the right tools, when working in synergy, can elevate the effectiveness and efficiency of the development process.

Here's a quick recap of what transpired:

Integration Overview: Attendees were provided a succinct overview of the purpose, scenarios, and benefits of the integration in focus.
Demo: A hands-on demonstration showcased the seamless integration of Github with Spira, enabling participants to visualize its application in real-world scenarios.
SpiraTeam Overview: The spotlight was then cast on SpiraTeam, detailing its core features and capabilities.
Artifacts & Dashboards: The session progressed to an in-depth look into the artifacts managed within SpiraTeam and how dashboards can be interpreted for actionable insights.
End-to-End Traceability: Participants were shown the process of tracing requirements all the way to tests and incidents, ensuring clarity at each stage of development.
Test Management: The event dived into the nuances of managing test cases, sets, and runs, providing attendees with crucial insights to optimize their test management process.
Managing Builds: A focus on how SpiraTeam can streamline and simplify the build process was elaborated upon.
SpiraTeam & GitHub Synergy: This segment underlined the powerful integration capabilities of SpiraTeam with GitHub. Topics discussed included:
- Integrating code, issues, and beyond.
- Synchronizing actions, pull requests, and build triggers.
- Enhancing teamwork with Spira incidents appearing as GitHub issues.
- Ensuring transparency with traceable requirements linked to code modifications.
Q&A Session: The webinar was wrapped up with an engaging Q&A session, where attendees had the opportunity to clarify doubts and further explore the topics discussed.

RECORDING

PRESENTERS

Jona Esparza is a member of the Agile Solution Delivery Team at Coveros. Jona has worked with a variety of test automation and DevOps technologies to automate containerized CI/CD pipelines for commercial and federal clients. Recently, she’s turned her attention to agile project management and tool adoption. She is a Certified Scrum Master and an ICAgile Certified Professional in Agile Fundamentals and the Foundation of DevOps. In her free time, she enjoys spending time outdoors and in the kitchen improving her amateur baking skills.

Simon Bor serves as the Chief Technology Officer (CTO) and Head of Products at Inflectra. Simon is responsible for the overall strategy and direction of Inflectra’s suite of products as well as working with the customer support teams to ensure high satisfaction from our users and customers. Simon holds an M.A. degree from the University of Cambridge and has worked for Inflectra for 7 years. Simon is an avid technologist and has worked with local coding meetup groups to promote careers in the technology industry

KEEP IN THE LOOP

Stay informed about Inflectra's latest events, product enhancements, corporate updates, and more by joining our monthly newsletter!

Gitex Global 2023: The Year to Imagine AI in Everything

2023-10-24T20:45:14-04:00

What is GITEX?

GITEX, short for Gulf Information Technology Exhibition, is an annual technology trade show and exhibition held in Dubai, United Arab Emirates. It is one of the largest and most significant technology events in the Middle East, attracting a wide range of exhibitors and visitors from around the world. GITEX serves as a platform for showcasing the latest innovations and developments in the fields of information technology, electronics, telecommunications, and related industries.

The event typically features exhibitions, product launches, demonstrations, workshops, and seminars related to various aspects of the technology sector, including artificial intelligence, cloud computing, cybersecurity, robotics, and more. It provides a networking opportunity for technology professionals, businesses, and investors to connect, collaborate, and stay updated on industry trends.

GITEX has grown to encompass various specialized segments, including GITEX Technology Week, GITEX Future Stars (focused on startups and entrepreneurs), GITEX Shopper (for consumer electronics and gadgets), and GITEX Global (international participation). It plays a crucial role in promoting technological advancements and business opportunities in the Middle East and beyond.

As you can see from the video above and panoramic photo below, the main GITEX expo consisted of 30 giant halls of technology companies exhibiting their products and services. They came from all over the world, including many countries that cannot share knowledge and expertise any other way.

The marquee exhibits included large, multi-level booths from industry heavyweights such as Intel, Salesforce, Microsoft, Software AG, Intel, Dell, Amazon Web Services, CISCO, Huawei, HPE, and Google/Alphabet.

In addition, there were many smaller companies exhibiting, with a whole separate pavilion called the "North Star" that consisted solely of startups and early stage ventures/companies.

Companies choose to exhibit at GITEX for various reasons, including:

Market Expansion: Companies often exhibit at GITEX to expand their market presence and tap into new regions, particularly the Middle East and North Africa. These events can attract a diverse international audience, including potential clients and partners.
Product Launch and Promotion: GITEX provides an ideal platform for launching new products or showcasing existing ones. Exhibiting companies can present their latest innovations and technologies to a broad and tech-savvy audience.
Networking: Technology exhibitions like GITEX are excellent opportunities for networking. Companies can connect with other businesses, potential customers, industry experts, and investors, fostering collaborations and partnerships.
Lead Generation: Many companies participate in GITEX to generate leads and build a potential customer base. They often collect contact information and have discussions with attendees who show interest in their products and services.
Brand Awareness: Exhibiting at major events like GITEX can help increase brand visibility and recognition. It allows companies to make a significant impact on a global stage.
Competitor Analysis: Companies can use events like GITEX to observe their competitors, understand market trends, and gain insights into what others in the industry are doing.
Education and Knowledge Sharing: GITEX features seminars, workshops, and keynote speakers. Companies may participate to gain insights into the latest industry trends and to share their own knowledge through presentations.

Inflectra at GITEX

This was Inflectra's first time exhibiting at GITEX. We had previously sent team members as attendees to learn more about the show and understand its demographics. Based on the scale of the event (over 50,000 attendees) and the types of customer (medium-large enterprises, focused on solving complex technology challenges in heavily regulated industries), it was a natural fit for Inflectra.

So we were excited to host the Inflectra booth in Hall 10-1, an area that was dedicated towards the subjects of cloud computing and artificial intelligence. With our recent announcement of generative AI capabilities coming to Spira, it made a lot of sense to be present in that hall.

Team Inflectra included our CEO, Adam Sandman, who had traveled to the event from Testing Talks in Melbourne, Australia as well as key members of our EMEA team based in Ireland, the UK and Germany.

As always, we had our legendary swag and stickers available as well as live versions of our products running on the booth iPads so attendees could see our Spira quality management platform in action.

In addition to meeting the attendees from different countries around the world who were attending, it was a great opportunity for the Inflectra team members to reconnect and have face to face time. With our globally distributed workforce, not all of us have met face to face, so it was wonderful to have time team building and knowledge sharing.

We were excited to have conversations with companies from different industries and countries. Even though the event was held in the United Arab Emirates (UAE), the attendees came from all parts of EMEA (Europe, Middle East and Africa), and in fact many attendees and exhibitors come from as far away as the Americas and Asia Pacific regions.

Meeting Customers in the Region

One of the great highlights was being able to discuss common challenges and opportunities with prospective customers. We were the only software product company at the event that focused on Quality Engineering, Agile Development, Project Management, Risk Management or Test Automation. So for many attendees, they were excited to be able to understand the latest trends in the industry and also learn about how AI and cloud computing is changing the demands on quality and software development practices.

In addition to learning more about our products and services, we also had time for fun with the popular "corn hole" bean bag toss game. Those playing the game could win some of our legendary swag, including the "James Bond" pen, USB-C hubs, zoom ring lights, and wireless phone chargers.

Forging Global Connections & Partnerships

It was a truly family affair, with many of our partners attending the event as exhibitors or attendees. For example, it was great to meet our partner Infiwave at the event, thanks so much for coming by the Inflectra booth:

We'd also like to thank our partner mVerve from attending the event and assisting at our booth. It was a real pleasure to connect with Harsha from mVerge and discuss opportunities in the EMEA region.

Great to connect with our amazing partner LambdaTest at #GITEX Samy El Hassani Saif Rizvi

We also had the change to meet other prospective partners that are excited about joining the Inflectra partner program:

Nice to meet you Adeel Baig at #GITEX today, looking forward to partnering with you.

As you can see, we met lots of different technologists and entrepreneurs

Here is Samy from our EMEA business development team, giving a demonstration of the TaraVault source code management system.

We had representatives of many local companies approach us to learn more about our solutions and partner network:

Based on our experiences, we are looking to expand our footprint in the region, in particular to service customers in the UAE and Saudi Arabia.

Finally, we made connections with representatives from Acentrik who are providing data management tools for automotive platforms such as Mercedes-Benz.

If you are interested in learning more about how Inflectra's Spira platform can be used to manage automotive development projects, please check out our recent ASPICE whitepaper.

What's Next?

After wrapping up GITEX Global 2023, the team is already excited about the event next year in Dubai 2024, plus we're consider attendance at its spin-off event GITEX Africa in Marrakesh, Morocco.

Testing Talks Melbourne, Australia 2023 - It's All About Risks and AI

2023-10-12T23:42:22-04:00

Exhibiting Inflectra's Solutions

We were happy to meet the local testing community, with representatives from major companies in the region, including NAB, ANZ, Telstra and Coles. We were excited to be able to demonstrate our SpiraPlan platform, including its key features such as requirements and test management, agile planning, program management and risk analysis and traceability. In addition, visitors could learn about Rapise our tool for codeless test automation, We also discussed the merits of AI, risk-based testing and test automation.

We were joined at our booth by our friend Golnoush Abaei from RMIT. Her students at RMIT are currently using SpiraPlan as part of the Inflectra Global Technology Initiative to educate students on the best practices for software testing, requirements analysis and risk management.

During the day, we got the change to meet testers, agile practitioners and other technology professionals and learn about their challenges and discuss how they could use Inflectra's products and services to optimize their software development and testing lifecycles. Of course we got to have some fun as well, with our legendary swag (USB hubs, the James Bond Pen) and stickers (lovingly crafted by our CTO Simon).

We even brought our Inflectra branded "corn-hole" bean bag toss game to keep the post-lunch doldrums to a minimum. It was also nice to catch up with our partners TTC Australia who were also exhibiting at the event.

Speaking about Risk Based Testing in the Age of AI

Our CEO - Adam Sandman - also had the opportunity to give a talk on "Risk Based Testing in the Age of AI". The talk was presented on the main stage and covered the key elements of risk management, applying them to risk-based testing, and finally considering the challenges and benefits that AI may bring to the fields of risk management and testing.

He also had the chance to show some of the recent results from using ChatGPT's OpenAI model to generate test cases, risks and BDD scenarios from simple requirements and user stories.

The audience liked the talk, with many attendees coming up to our booth, looking to ask questions and gain insights and understandings.

Giving Away Prizes

Of course, no conference would be complete without games and prizes, and Adam was also happy to award our prize for the most answered questions, a laser Bluetooth projection keyboard.

Of course, after Testing Talks concluded, there was the legendary "after party" at General Assembly. But that shall remain off the record ;-)

Comprehensive Guide to Scaled Agile Team Roles

2025-09-25T10:02:07-04:00

SAFe agile team size

SAFe is built upon lean agile principles, promoting a mindset of continuous improvement, customer-centricity, and collaboration. This mindset serves as the foundation for all SAFe roles, emphasizing the importance of adaptability and customer value.

In SAFe, team size should typically range from 5 to 11 individuals. This range balances agility and coordination with the ability to deliver substantial value. However, organizations should tailor team sizes based on their specific context and needs.

Layers in scaled agile framework

To understand SAFe roles, it's essential to grasp the bigger picture. SAFe operates at four layers — Team, Program, Large Solution, and Leadership. Each layer has distinct goals and requires specialized roles to achieve them. Think of these layers as a hierarchy, with each building upon the previous one.

For more information on scaled agile’s structure, see our guide on the different configurations of SAFe.

Scaled agile roles

Team-level roles

The first layer is the Team level, where the primary goal is to efficiently deliver value through agile practices. This layer focuses on individual teams working together to deliver high-quality, customer-centric product increments. Team-level activities are guided by agile methodologies like Scrum or Kanban, including sprint planning, daily stand-ups, sprint reviews, and retrospectives. Key roles here include Scrum Masters, Product Owners, and Development Team members.

Scrum Master

The Scrum Master plays a pivotal role in ensuring that agile principles are followed effectively. They facilitate Scrum ceremonies like Daily Standups, Sprint Planning, and Sprint Reviews, ensuring the team is aligned and focused. Scrum Masters also remove impediments that hinder progress, fostering a culture of continuous improvement.

Development Team

The Development Team is composed of cross-functional members responsible for delivering working increments of the product. They collaborate closely, share knowledge, and collectively own the quality and success of their work.

Product Owner

The Product Owner is responsible for prioritizing and managing the product backlog. They bridge the gap between the development team and stakeholders, ensuring that the most valuable features are delivered. Product Owners make critical decisions about what gets built, balancing customer needs and business goals.

Program-level roles

The Program level aligns multiple agile teams to deliver larger solutions that meet strategic objectives. Its primary goal is to ensure coordination, integration, and value delivery across these teams. Programs consist of multiple Agile Release Trains (ARTs), with synchronized planning, cross-team collaboration, and alignment on strategic themes. Key roles at this level include Release Train Engineers (RTEs), Product Managers (PMs), and System Architects.

Release Train Engineer

As we move up to the Program level, the Release Train Engineer takes center stage. The RTE coordinates multiple Agile Release Trains to deliver large-scale solutions. Their role is to ensure alignment, communication, and the overall success of the program.

System Architect

System Architects guide technical decisions at the Program level. They provide a technical vision and ensure that the solution aligns with the overall architectural direction. Their expertise is crucial for building scalable and maintainable systems.

Product Manager

At the Program level, the roles of Product Manager become more complex. They work to provide guidance, prioritize features, and define the program's vision. Their focus is on achieving strategic goals through the program's deliverables.

Large solution-level roles

Moving another layer up, Large Solution (and Portfolio) levels deal with broader initiatives and portfolios of projects. Their primary goal is to develop large-scale solutions efficiently and align portfolios with the organization's strategic direction.

Solution Train Engineer

At the Large Solution level, the Solution Train Engineer orchestrates the coordination of multiple ARTs to deliver comprehensive large solutions. Their role is akin to that of an RTE, but at a larger scale.

Solution Architect

Solution Architects design and guide these large solutions, ensuring that they meet the organization's strategic needs. They take into account the technical complexity of the solution and make architectural decisions that align with the overall strategy.

Portfolio Manager

Portfolio Managers operate at the highest level, aligning the organization's strategy with execution. They oversee multiple value streams and guide the allocation of resources to maximize business outcomes.

Enablers role

The concept or role of "Enablers" does not fit neatly into one of the layers (Team, Program, Large Solution, or Portfolio) we discussed above. Instead, Enablers are a cross-cutting concept that spans across multiple layers, supporting the entire SAFe framework.

They include tasks or activities such as architectural work, infrastructure enhancements, and compliance updates that facilitate value delivery by addressing dependencies and prerequisites. Enablers ensure efficient alignment and synchronization across the SAFe framework, supporting Agile Release Trains and value streams at different levels.

Scale your team’s capabilities with SpiraPlan

The roles within SAFe, from Team to Portfolio levels, all play a crucial part in achieving business agility and delivering value to customers. But it's also evident that successful scaled agile implementation hinges on the right tools.

For effective scaled agile implementation, SpiraPlan is a comprehensive platform that supports program management, portfolio management, and risk management features to ensure efficient coordination, value delivery, and risk mitigation. Even better, requirements management, program planning, and release planning features streamline scope management, while customized reporting empowers data-driven decision-making. And with integration capabilities like IDE and email, it simplifies processes for SAFe roles, facilitating a smooth transition to agile scalability.

Explore the highlights of SpiraPlan to elevate your SAFe implementation, or try it for 30 days with a free trial!

Inflectra at StarWest 2023: Advancing Software Quality One Conversation at a Time

2023-10-09T13:38:36-04:00

Showing off the Inflectra Platform

This year, we proudly showcased SpiraPlan, and Rapise—our flagship products designed to address complex needs in software project management, testing, and automation.

Our ITP demo was tailored to illustrate how Inflectra's platform can seamlessly integrate into your existing infrastructure, thus enhancing productivity, reducing risk in software testing, and improving software quality.

In his Technical Presentation on October 5, 2023, called Risk, AI, and Software Testing: A Deep Dive, Adam Sandman, the CEO of Inflectra, spoke about Risk-Based testing methodology and its relevance in today's AI-centric paradigm, the dichotomy between harnessing AI's capabilities and managing inherent risks, and advanced strategies and tools such as model-based testing, exploratory testing, and risk analysis that offer precise navigation through the maze of potential challenges.

Conversations that Matter

The Inflectra team members had the opportunity to engage in insightful dialogues with current customers and prospects. These conversations often ventured beyond mere feature lists, delving into compliance norms, high-quality software delivery, and managing complex project requirements.

This year at StarWest, the importance of deepening relationships with our existing partners and vendors was a focal point for Team Inflectra. We understand that long-term collaborations are built on mutual growth and shared visions for the future. To that end, Team Inflectra engaged in meaningful discussions with our partners, exploring avenues for expanding our cooperative efforts and focusing on how we can jointly offer more value to customers.

(Photo: Inflectra with TTC at Starwest 2023)

We did not forget about fun, either

While StarWest 2023 offered a wealth of professional growth and learning, we at Inflectra believe that all work and no play make for a dull conference. That's why we sprinkled in some fun to keep the energy levels high and the interactions engaging.

Swag and Levity

Our booth was stocked with some fantastic swag that became the talk of the event. From cleverly named James Bond pens to handy tech gadgets, we had something for everyone. But what set the tone was our general levity and a sense of humor, making even the most technical discussions feel like a chat among friends. And yes, #dadjokes were in full swing, eliciting smiles and eye-rolls in equal measure.

Our Corn Hole/Bean Bag Toss Game was a major attraction for those looking for a little competitive spirit. Participants took their chances to win, and the atmosphere was filled with excitement. This simple yet engaging game served as a great icebreaker, but the stakes were high. The winner had to beat 25 other competitors in 3 rounds. Ms. Kris walked away with our latest gadget—a Laser Projection Keyboard! By balancing serious discussions with moments of levity and fun, we made sure that StarWest 2023 was memorable and helped participants build lasting relationships amongst each other and with Team Inflectra!

All in all, Starwest 2023 was another step in our journey to deliver unparalleled value to our customers and prospects.

If you missed us at StarWest and want to know more about how Inflectra can skyrocket your software project management and testing efforts, feel free to reach out to sales@inflectra.com

Team Inflectra

What is SAFe PI Planning?

2025-01-21T12:12:20-05:00

PI planning meaning

One of the cornerstone practices in the Scaled Agile Framework is PI (Program Increment) planning. This is a structured, time-bound event in the SAFe framework where cross-functional teams come together to plan and align their work for a specific Program Increment.

A Program Increment is a fixed time frame, typically spanning 8-12 weeks, during which an Agile Release Train (ART) delivers value in the form of working, tested software and systems. This practice ensures that all teams within the ART move in a coordinated manner, working toward common objectives.

What is the goal of PI planning?

The primary goal of PI planning is to create alignment and synchronization among multiple Agile teams that are working collaboratively to deliver value. It aims to establish a clear plan for the upcoming Program Increment, ensuring that everyone understands their roles, responsibilities, and priorities. Essentially, PI planning sets the stage for a focused, well-coordinated, and productive execution phase.

Why is it important?

SAFe PI planning holds immense importance for several reasons:

Alignment - one of the central tenets of SAFe PI planning is alignment. It aligns all teams within the Agile Release Train to a common mission and vision. By doing so, it ensures that everyone is working in concert towards shared objectives. This alignment prevents the common problem of different teams pulling in different directions, which can lead to inefficiencies and conflicts.
Visibility - PI planning provides transparency into the work that will be undertaken in the upcoming Program Increment. This transparency is vital for stakeholders, including executives, product managers, and team members, as it enables better decision-making. When everyone can see what's planned, they can anticipate potential bottlenecks, address resource constraints, and make informed decisions.
Coordination - in a large organization with multiple Agile teams, dependencies are inevitable. PI planning brings these dependencies to light and provides a forum for teams to discuss and coordinate their work. This coordination minimizes bottlenecks and ensures that work flows smoothly from one team to another.
Risk Mitigation - identifying and addressing risks early is a fundamental part of PI planning. By discussing potential challenges and bottlenecks, teams can proactively develop mitigation plans. This risk-focused approach further reduces the chances of unpleasant surprises during the Program Increment.
Customer Value - in an Agile environment, delivering value to the customer is paramount. PI planning ensures that customer-centric features and functionality are prioritized and delivered in a timely manner. It keeps the focus on delivering value at regular intervals, which is one of the core principles of Agile.

Who should be involved in PI planning?

As we mentioned, PI planning is a collaborative effort that involves a variety of roles, including Product Owners, Scrum Masters, Testers, and more. Key participants typically include:

Release Train Engineer (RTE) - facilitate and orchestrate the PI planning event, ensuring that it runs smoothly and efficiently.
Product Owners - responsible for representing the voice of the customer. They define the features and user stories to be developed in the Program Increment.
Scrum Masters - play a crucial role in removing impediments and ensuring that teams adhere to Agile principles and practices. They act as coaches and servant leaders.
Developers and Testers - individuals who execute the work and are responsible for implementing and testing the features and user stories.
System Architects - provide technical guidance and ensure architectural integrity across the Program Increment. They help teams make sound technical decisions.

What are anti-patterns?

"Anti-patterns" refer to common practices or behaviors that, while often mistakenly used, can hinder or undermine the effectiveness of the PI planning process. They are patterns of action that are counterproductive and can lead to suboptimal outcomes during planning. Common anti-patterns to watch out for include:

Lack of Preparation - inadequate preparation can lead to a disorganized and unproductive event. Teams should ensure that the backlog is well-prepared, dependencies are identified, and key roles are aware of their responsibilities before the PI planning event.
Overloaded Agendas - trying to cover too much in a single PI planning event (which we’ll explain more further down) can lead to information overload and decreased focus. It's essential to strike a balance between discussing important topics and keeping the event manageable.
Lack of Engagement - if key stakeholders, including product owners and business owners, are not actively engaged, alignment and buy-in may suffer. It's vital to ensure that all relevant parties participate fully in the planning process.
Ignoring Dependencies - dependencies between teams and features are common in large-scale Agile environments. Ignoring or mishandling dependencies can lead to delays and disruptions during the Program Increment. It's crucial to identify, document, and address dependencies during PI planning, including discussing inter-team dependencies, coordinating efforts, and developing strategies to mitigate risks associated with dependencies.
Neglecting Retrospectives - PI planning retrospectives, where teams reflect on the planning process and identify areas for improvement, are essential. Skipping these retrospectives can prevent teams from continuously improving their planning process.

Benefits of scaled agile PI planning

Effective SAFe PI planning offers a wide range of business benefits that contribute to the success of large-scale Agile initiatives:

Better predictability

Improved planning leads to greater predictability. Stakeholders can have confidence in the team's ability to meet commitments and deliver value consistently. Predictability is essential for business planning, as it allows organizations to set realistic expectations, allocate resources effectively, and make informed decisions about priorities and investments. When teams consistently meet their commitments, trust is built between teams and stakeholders, which further enhances predictability.

Early issue identification

PI planning provides a structured forum for identifying and addressing potential issues and risks early in the planning process. By discussing potential challenges and bottlenecks during the planning event, teams can proactively develop mitigation plans and strategies. This early issue identification and proactive problem-solving help teams avoid surprises and delays during the Program Increment. It also allows teams to make necessary adjustments to their plans to ensure a smoother execution phase.

Improved collaboration

Effective SAFe planning fosters collaboration among teams within the Agile Release Train. Teams learn from one another, share insights, and work together to achieve common objectives. This collaborative environment promotes knowledge sharing and cross-functional teamwork, which are essential for successfully delivering value in a large-scale Agile setting. Improved collaboration also reduces the potential for silos and promotes a sense of unity among teams.

More transparency

With scaled agile PI planning, stakeholders (including executives, product managers, and team members) gain transparency into progress and priorities. They can see what work is planned for the upcoming Program Increment, which features are a priority, and how teams are coordinating their efforts. This transparency builds trust among stakeholders and allows for more informed decision-making. When everyone has visibility into the planning process, it becomes easier to address challenges and make adjustments as needed.

PI planning steps

PI planning involves a meticulously structured process designed to ensure alignment, collaboration, and efficient execution of work across ARTs. This planning process consists of several key phases, each with its unique purpose and activities:

Preparation

The preparation phase is the foundation of successful PI planning. It involves three primary activities:

Prepare the Backlog - product owners work diligently to ensure that the backlog is in a well-defined, prioritized, and ready-to-plan state. This means that features and user stories should be refined, detailed, and appropriately sized.
Pre-PI Planning - before the official PI planning event, product owners, Scrum Masters, and other key roles engage in the pre-PI planning activities mentioned above. This includes reviewing features, identifying dependencies, and addressing any outstanding questions or concerns. The goal is to enter the planning event with a clear understanding of what needs to be accomplished.
Identify Business Context - Understanding the strategic themes and priorities for the upcoming Program Increment is critical. Teams must be aware of the larger organizational goals and context within which they will be planning their work.

Standard agenda

The standard agenda in SAFe PI planning is the next planning step and is made of a structured sequence of events that provides a framework for teams to follow during the planning event. The standard agenda in SAFe PI planning consists of 7 activities over the two days of PI planning (Business Context, Product Owner Pre-Planning, Team Breakout Session, I&A Session, Management Review, Problem-Solving Workshop, and PI Objectives and Metrics):

Day 1

The first day of the PI planning event is dedicated to preparation. It sets the stage for a productive and well-organized planning session.

Business Context - the day begins with a clear Business Context presentation. During this session, leaders and stakeholders communicate the strategic themes, objectives, and priorities that will guide the Program Increment. It's crucial for teams to understand the larger context within which they'll be working to ensure that their efforts are aligned with the organization's goals.
Product Owner Pre-Planning - before the event, product owners engage in pre-planning activities. This involves reviewing the features and user stories in the backlog, ensuring they are well-defined, prioritized, and ready for discussion during the planning event. The preparedness of product owners is essential for a smooth and efficient planning process.
Team Breakout - after the Business Context presentation and product owner pre-planning activities, teams participate in a team breakout session. In these breakouts, teams review and discuss the features and user stories that are relevant to their areas of responsibility. They consider factors such as dependencies, technical considerations, and the overall scope of work. These discussions lay the groundwork for informed decision-making during the formal planning sessions on Day 2.

Day 2

The second day of SAFe PI planning is the formal planning day, where teams come together to make commitments and align their work for the Program Increment.

Inspect and Adapt - the day kicks off with an Inspect and Adapt (I&A) session. During this session, teams present their preliminary plans for the Program Increment. They share what features they intend to work on, their capacity estimates, and any identified dependencies. This presentation allows teams to inspect their plans collectively and receive early feedback from other teams and stakeholders.
Management Review - following the I&A session, there is a management review phase where leadership and stakeholders provide input and feedback on the proposed plans. This is a critical step where any misalignments or issues can be addressed and resolved. It ensures that the plans align with strategic objectives and organizational priorities.
Problem-Solving Workshop - in the problem-solving workshop, teams address any significant issues or challenges that have been identified during the planning process. This workshop is an opportunity to collaboratively find solutions to problems, remove roadblocks, and ensure that the plans are feasible and executable. Problem-solving at this stage helps prevent potential bottlenecks and delays during the Program Increment.
PI Objectives and Metrics - the final step of Day 2 involves setting clear PI objectives and metrics. Teams define what success looks like for the Program Increment and establish measurable objectives that align with the larger strategic goals. These objectives and metrics serve as a compass for the upcoming work, providing a clear definition of what teams are striving to achieve.

What to include in PI planning agendas?

Business Context Presentation:
- Overview of the strategic context and themes
- Communication of key organizational objectives
- Presentation of strategic priorities for the Program Increment
PI Objectives:
- Clear and specific PI objectives that align with the strategic context
- Measurable outcomes and success criteria associated with each objective
Team Breakout Session:
- Allocation of time for teams to review features and user stories
- Discussion of dependencies, technical considerations, and scope
- Opportunities for teams to ask clarifying questions
Inspect and Adapt (I&A) Session:
- Scheduled time for teams to present their preliminary plans
- Availability of feedback channels for other teams and stakeholders
- Facilitation to ensure a structured and efficient I&A session
Management Review:
- Defined time for leadership and stakeholders to provide input and feedback
- Mechanisms for addressing misalignments or issues
- Ensuring that plans align with strategic objectives and priorities
Problem-Solving Workshop:
- Allocation of time for addressing significant issues or challenges
- Facilitated discussions to identify solutions and mitigation strategies
- Ensuring that plans are realistic and feasible
PI Objectives and Metrics:
- Dedicated time for teams to set clear PI objectives
- Discussion of how success will be measured
- Alignment of objectives with the larger strategic goals

Post-PI planning

The conclusion of the two-day SAFe PI planning event marks the beginning of the Program Increment. However, the journey doesn't end here. Several post-PI planning activities are essential for ensuring the successful execution of the plans:

Execution - teams begin working on implementing the plans outlined during the PI planning event. They execute their work according to the commitments made and strive to deliver value to customers.
Inspect and Adapt (I&A) - regular I&A sessions continue throughout the Program Increment. These retrospectives and problem-solving sessions allow teams to reflect on their progress, identify areas for improvement, and adapt their plans as needed to optimize their performance.
Customer Feedback - continuous gathering of customer feedback is integral to the Agile mindset. Teams should actively seek and incorporate feedback from customers and end-users throughout the Program Increment. Customer feedback helps teams refine their work and ensure that it aligns with customer expectations.
Demo and Review - at the end of the Program Increment, teams conduct a demo and review session. During this, they showcase completed features and functionality to stakeholders, providing a tangible demonstration of the value delivered. This not only validates the work but also serves as an opportunity to gather additional feedback and make any necessary adjustments.

Improve your scaled agile capabilities with SpiraPlan

In the realm of software development, scaling Agile for large enterprises is crucial, and SAFe PI planning aligns teams and delivers value efficiently.

SpiraPlan offers a comprehensive solution, seamlessly integrating requirements management, release planning, task estimation, and defect tracking from day one. It enables unified program backlogs, allowing you to plan program-wide capabilities with features from multiple projects, ensuring alignment and transparency. SpiraPlan is also methodology-agnostic, adaptable to any scaled Agile approach, including SAFe, Nexus, Scrum of Scrums, or your own custom methodology.

To learn more about SpiraPlan and how it can improve your agile software development processes please:

Webinar Recap: Discover the Power of SpiraTeam - A Jira Alternative To Revolutionize Your Project Management

2023-09-18T12:06:06-04:00

RECORDING

SLIDESHOW

MAIN TAKEAWAYS

SpiraTeam vs. Jira: The Clear Winner: While Jira has been a go-to for many businesses over the years, SpiraTeam is emerging as the superior contender in the project management arena. The reasons? A slew of advanced features and functionalities that aren't just limited to managing tasks but span across various aspects of project management. The webinar deep-dived into how SpiraTeam is edging past Jira in terms of capability and efficiency.
Unpacking SpiraTeam's Rich Feature Set: It's one thing to state that a platform has a multitude of features, but this webinar walked the talk. Attendees got an in-depth look at the extensive tools SpiraTeam brings to the table. From the granular details of requirement management and risk evaluation to the nitty-gritty of task assignments and efficient document tracking, SpiraTeam proves to be more than just a conventional project management tool
Making The Transition Smooth: A critical concern for many organizations is the transition phase – moving from one platform to another can seem daunting. However, this webinar made it clear that with SpiraTeam, the transition is not just about switching tools, but about elevating and optimizing existing workflows. Attendees got insights into how the transition from Jira to SpiraTeam can be both seamless and beneficial in the long run.

IN CONCLUSION

The digital era demands robust, versatile tools that can adapt to evolving business needs. SpiraTeam, with its vast array of features, seems poised to be the future of project management. As organizations globally are realizing its potential, the transition from platforms like Jira is becoming more of a strategic move than just a change in tool. This webinar provided a comprehensive overview of why SpiraTeam is becoming the preferred choice for many.

STAY UPDATED

Subscribe to our newsletter and never miss out on the latest Inflectra updates, product improvements, news, and thrilling announcements!

Achieving Software Quality: Prioritizing Intended Behavior

2023-09-18T14:55:17-04:00

At the most basic level there are three crucial components of software development: Intended Behavior, Development, and Verification (see figure 1). These three components form a triangle, and the quality of the delivered software is directly dependent on effective communication of the ‘Intended Behavior’. Therefore, it is essential to start by defining and communicating Intended Behavior in a clear, complete, and unambiguous manner.

Figure 1

One of the most compelling arguments for investing in Intended Behavior is that it can significantly reduce the cost and schedule of the overall life cycle.

When Intended Behavior is not clearly communicated or defined, developers will take what is given and produce code that works but cannot be the full and complete Intended Behavior. This leads to defects, technical debt and rework cycles. Study after study shows that the root cause of these problems is most often poor or incomplete requirements. To avoid the cost of these issues, it is important to take the time to thoroughly define and communicate Intended Behavior. It is clear that organizations know how to develop quality software giving quality instructions. We know how to code.

Harnessing Precise Intended Behavior for Optimal Software Quality

Investing in Intended Behavior not only reduces the cost associated with Delivered Behavior but also significantly elevates overall quality and reduces technical debt. When Intended Behavior is clearly defined and communicated, developers can produce high-quality code that directly meets the intended requirements. This, in turn, reduces the amount of technical debt, and the cost of maintaining the code over time.

Focusing on Intended Behavior can also maximize return on investment (ROI). When Intended Behavior is well defined and communicated, developers can produce high-quality code more quickly, and with fewer errors. This, in turn, leads to earlier delivery of software and allows for more frequent releases, which can lead to greater profits.

Effective Communication: The Crucial Element in Software Development

Clear communication is crucial when it comes to defining Intended Behavior. Product owners, developers, and SQA managers must work together to ensure that everyone is on the same page and that the requirements are clearly defined. By taking the time to communicate and define requirements early in the development process, teams can avoid costly mistakes down the line. This is consistent with the concept of shifting left.

There are approaches and technologies that can be used to define and communicate Intended Behavior. In the simplest terms there are two key ideas that I think bare consideration: visualization and consensus.

Let’s talk about a very simple example (see figure 2). Bob and Evan meet on a Monday and come to a consensus to meet again next Friday. Four days later Bob calls to meet and Evan is unavailable. A week later Evan calls and Bob is unavailable. Even though they agreed, “next Friday” meant different days to each of them. Let’s look at this plan in a different way, with a picture. Both Bob and Evan show up at the same time.

Figure 2

Here is another example showing a Cause-Effect Model created from a User Story about a choice on shipping method depending on your location within the U.S. (see figure 3). This Model can generate 3 clear Test Scenarios that cover all 11 possible paths through this model. The rules are also very clear for development.

Figure 3

Clarity of intent is almost always improved with a visual. One of the most effective ways to visualize business rules or software behavior is by creating models or diagrams. There are lots of types of models and even simple drawings on a whiteboard, that can be used to communicate more clearly. Some examples are flow charts, decision tables, activity diagrams, data flow diagrams, state charts and cause-effect models. These models can be useful for communicating different information and often it may be best to use several different models for clarity. We find that Cause-Effect models are especially good at diagramming user stories by creating logic flows and identifying unambiguous test scenarios and making variations obvious. Any or all the visualizations create clarity of Intended Behavior which leads to more easily achieved consensus among stakeholders. These steps ultimately lead to better development and delivery. This leads us to consider how to verify that deliverables match the Intended Behavior.

The quality of each delivered release can only be measured against the Intended Behavior. I describe this as ‘Should Do’ testing. This is opposed to the more common approach of what I call ‘Does Do’ testing. Let me explain the difference.

Understanding ‘Does Do’ vs. ‘Should Do’ in Software Development

‘Does Do’ testing or verification is running the delivered software to see if it breaks or has some inconsistent results or responses. Typically, this is from a user perspective. This means that the software behavior is assumed to be complete and correct if it does not break. This is typical of User Testing, Exploratory Testing, Data Driven Testing, and most automated testing including AI based testing (so far). Test designers either are not paying much attention to documented Intended Behavior which is often out of date, incomplete or is just missing all together. Basically, the system works correctly if it doesn’t create errors or crash. Tracing back to requirements or any kind of coverage analysis is problematic. Trust the developers and test what it ‘Does Do’.

‘Should Do’ testing should approach testing by looking mostly at documented Intended Behavior. This can and should be done independently and in advance of development and release. Test planning and test libraries should be created by the same Intended Behavior information provided to development. This process leads to direct traceability and coverage measurement to provide solid analysis of readiness to go live with the business’s intended system.

Unfortunately, throughout my 25+ years in the industry, ‘Does Do’ testing has been and is still the most common approach. This is especially true in Agile development where the software is the documentation. More on that in a minute.

It makes sense that ‘Should Do’ testing gives better results, but it is not possible without well communicated Intended Behavior with clear stake holder consensus. The time to choose ‘Should Do’ is at the beginning of a new system or new feature project.

Everything I am proposing can and should be applied to Agile development or any development for that matter. For Agile, the scope of Intended Behavior will focus on User Stories that come into sprints or iterations. It makes sense that visualization (modeling) and consensus from product owners and developers at the beginning has all the benefits described. Result - better code and better verifications and less backlog.

Conclusion: Leverage Visualization and Consensus for Effective 'Should Do' Testing

The quality of software development is directly dependent on the quality of Intended Behavior communication. By investing more time in defining and communicating Intended Behavior, teams can improve overall quality, reduce costs associated with Delivered Behavior, reduce technical debt and backlogs, and maximize return on investment. Our focus on Intended Behavior enables businesses to save time and money, while delivering high-quality software that meets their needs. Whether you're a product owner, C-level executive, or QA manager, consider prioritizing Intended Behavior for improved software development. Experience the difference it can make in your efforts.

ABOUT CRITICAL LOGIC

Critical Logic is all about improving the Quality of Business Systems. The heart of what we do is modeling. Modeling requires clear, unambiguous statements of intended, correct behavior. Modeling also produces highly effective acceptance criteria. The result is more successful system deployments and reduced testing, maintenance, and rework.

We deploy our Integrated Quality Management methods and technology (IQM Studio) to provide modeling, test generation and automated test execution in almost any business environment. Our experienced consulting staff provides high quality Business Analysis, Functional Design, Software QA planning & management, and training. We integrate the imperative of quality to all key parts of Business Systems SDLC.

Learn more about Critical Logic.

STAY UPDATED

Subscribe to our newsletter and never miss out on the latest Inflectra updates, product improvements, news, and thrilling announcements!

Webinar Recap: What's New in Rapise v8.0

2023-09-08T09:06:11-04:00

Framework Mode Enhancements

The primary focus of Rapise v8.0 seems to be on expanding and refining its Framework Mode:

Global Object Definition: The new version allows users to define global objects, especially Page Objects with their own object repositories. This ensures they can be reused across different test cases.
Structured Framework: The structure has been improved to include test cases, test case folders, shared modules/page objects, and scripts.
Object Tree Management: Users can now import, rename, and move test cases directly within the Object Tree.
Simplified Parameter Definition: Defining parameters and configurations is now simpler and more intuitive.
Test Set Definition: Defining test sets has been made more straightforward.
One-click Spira Integration: You can now integrate the entire framework with Spira in one click. This also automatically creates the test cases and sets within Spira.
Quick Storage in Spira: The updated version offers a faster method to store framework files in Spira.

RVL Enhancements & Improvements

Rapise v8.0 introduces several enhancements in the Record & Playback Visual Language (RVL) including improved error messages, new parameters, and additional functionalities for .xlsx files, amongst other updates.

General Improvements

There are significant improvements in usability, performance, and user experience. Some notable changes include the introduction of support for ES6 syntax checking & highlighting, improved Git credential loading in Spira Dashboard, updated Chrome connection notifications, and making NodeJS JavaScript engine the default with WScript now being secondary.

Bug Fixes

Rapise v8.0 also addressed a myriad of bugs from its previous versions. From UI quirks like truncated button names to more serious issues like crash reports and Mobile Spy related concerns, the new version promises better stability.

To wrap it up, Rapise v8.0 is a substantial upgrade, addressing previous version shortcomings and introducing new features that will undoubtedly simplify and streamline the automation testing process. With its focus on Framework Mode and the continuous integration with tools like Spira, Rapise is certainly poised to offer a richer and more efficient testing experience. Click here to see an all-inclusive view of our improvements.

Keep current with the latest Inflectra product news by signing up for our monthly newsletter!

Inflectra Partner Tour 2023: Costa Rica

2023-08-24T14:33:05-04:00

Let me begin by suggesting that if you haven’t been to Costa Rica, schedule a trip without delay! With the vast variety of ecosystems, wildlife, adventures, beaches, and welcoming people, we had an amazing vacation.

Left photo: Rio Celeste (that cerulean blue 😍) Right photo: Paddleboarding at Lake Arenal/Arenal Volcano

Left photo: Tabacón hot springs (So relaxing after paddleboarding) Right photo: A Toucan through a spotting scope

To make a great trip even greater, I was fortunate enough to be able to meet with our new partner Developer007/Full Technology. Jeffrey Hanna and Karen Hernandez reached out to our team after conducting research on QA tools on behalf of a client. The Developer007/Full Technology team develops software and provides implementation services to their clients in Costa Rica, Honduras, Nicaragua, Panama, El Salvador and the greater Central America region. Jorge Fernandez, our LATAM sales and partner manager, quickly saw the value in a partnership with Developer007/Full Technology. Their team saw the value of working with us as well, and the deal was executed.

Fast forward two and a half weeks, and I found myself in San Jose with Karen and Jeffrey at a “restaurante típico” having coffee prepared the traditional Costa Rican way and chorreadas (which are delicious sweet or savory corn pancakes made with ground fresh corn).

Making coffee with a chorreador

Developer007/Full Technology works in all industries; however, Jeffrey mentioned the tremendous growth in the life sciences and medical devices industries in Costa Rica in particular. This industry is a natural fit for Spira with its native validation and traceability features. They also have an interest in Rapise and how automated testing can benefit their customers. We have a plethora of resources to assist our partners with learning the tool such as Inflectra Campus and free licenses for internal training use, as well as resources to assist with the sales process, so we walked through the onboarding process and resource location. I am also excited to dive into co-marketing so we covered some of our go-to options and brainstormed some additional ideas. We’ll be meeting again soon to develop a marketing action plan.

At dinner with Karen, Jeffrey and Alvaro.

After our tasty snack, we drove for a bit (San Jose rush hour is not unlike that of the DC metro area) to the Escazú neighborhood to meet up with another Developer007/Full Technology team member and Project Manager extraordinaire, Alvaro Araya. Business talk turned to talk of food, Costa Rican history and beaches. The evening flew by and suddenly the restaurant was turning out the lights.

While Costa Rica had not originally been part of our partner tour plans, I couldn’t be happier that the timing worked out and I was able to meet with this excellent team of people. I look forward to a close relationship and with any luck, another trip to Costa Rica soon.

Until the next trip, pura vida! 🤙

Explore More of Our Partner Tours from 2023

Inflectra Partner Tour 2023: Mexico City

Inflectra Partner Tour 2023: London

Inflectra Partner Tour 2023: Western Europe

Stay up-to-date on all things Inflectra by signing up for our monthly newsletter!

Importance of Testing Software for Life Sciences

2024-06-22T13:49:52-04:00

What are life sciences?

Life sciences are the integration of technology in the fields of biology, genetics, medicine, and healthcare, all of which have become increasingly digital. This is a result of continual technological advances, but also the effect that the COVID pandemic had on in-person medical consultations, forcing much of the industry to go online.

Software solutions for this industry enhance research, diagnostics, drug discovery, patient care, and regulatory compliance. They tackle complex challenges, requiring rigorous testing to ensure accuracy, data integrity, and adherence to industry regulations. This directly influences the quality and reliability of tools driving scientific advancements and healthcare practices.

What types of software does this industry use?

The life sciences and healthcare sectors rely on a wide array of specialized software applications to enhance their operations, improve patient care, and advance scientific research. Here are some key areas where software is commonly used:

Medical device software - medical devices, ranging from imaging equipment to diagnostic tools, depend on software to function accurately. This software helps control hardware, process data, and ensure patient safety. For instance, blood glucose monitors utilize software to capture, analyze, and present critical medical information.
Telehealth platforms - this software enables remote medical consultations and healthcare services, which became critical during the COVID pandemic’s social distancing. These platforms facilitate virtual appointments, allowing patients to connect with healthcare providers from the comfort of their homes, thus enhancing accessibility and minimizing physical visits.
Electronic health record (EHR) systems - online databases and EHR systems centralize patient records, treatment history, and medical information. These systems improve patient care coordination among healthcare professionals and support efficient data sharing (while maintaining privacy and security).
Health tracking applications - health and wellness apps help individuals monitor their physical activity, diet, sleep patterns, and vital signs. These applications contribute to proactive health management, offering insights that can guide users toward healthier lifestyles.
Imaging software - advanced imaging software, like those used in radiology and medical imaging, process and visualize complex medical images, such as X-rays, MRIs, and CT scans. These tools aid clinicians in accurate diagnoses and treatment planning.
Online billing & medical practice management - healthcare organizations use billing software to manage patient invoices, insurance claims, and financial transactions efficiently. Medical practice management software streamlines administrative tasks, appointment scheduling, and resource allocation.

Software QA for healthcare & life sciences

The critical nature of these sectors demands unwavering attention to patient safety and privacy. Software Quality Assurance (QA) and rigorous testing play an important role in upholding the reliability, accuracy, and security of software solutions deployed in these industries. As technology continues to shape these fields, this becomes a non-negotiable factor.

Safety — software for medical devices

Patient safety stands as the cornerstone of healthcare, and in an increasingly digital era, software-driven medical devices play a pivotal role in delivering effective and secure treatment. Medical devices equipped with software components, such as infusion pumps, pacemakers, and imaging systems, have the potential to significantly improve patient outcomes. However, they also carry the responsibility of adhering to rigorous safety standards, such as the FDA's guidelines, in order to minimize any risk of harm to patients.

Privacy — HIPAA compliance

Software testing is also pivotal in safeguarding patient privacy and reinforcing software security. Healthcare software, especially those dealing with patient records and sensitive medical information, must be thoroughly tested to identify vulnerabilities and potential breaches. This can replicate real-world threats, ensuring software resilience and enabling proactive fixes. Compliance with regulations like HIPAA is a frontline defense crucial for maintaining privacy and security in healthcare settings.

Common testing types in life sciences

We’ve discussed how testing is crucial for any software in the life sciences and healthcare industry, but testing comes in many forms. Some of the most common testing types for these applications include:

Usability testing - this assesses the software's user-friendliness and its ability to meet the needs of healthcare professionals and patients. Intuitive interfaces and efficient workflows are critical for smooth adoption and effective usage.
Integration testing - as software systems in healthcare often interact with each other, integration testing verifies that these components work seamlessly together. This prevents data inconsistencies and operational glitches.
Performance testing - healthcare software must handle heavy loads without compromising performance. Performance testing evaluates the software's response time, scalability, and stability under varying workloads.
Security testing - given the sensitive nature of patient data, security testing is also crucial. It examines vulnerabilities and safeguards against unauthorized access, data breaches, and cyber threats.
Functional testing - functional testing ensures that the software's functionalities align with the intended specifications. It verifies that features like patient record management, appointment scheduling, and diagnostic tools perform accurately.
Compliance testing - because it must adhere to industry regulations like HIPAA, compliance testing ensures that the software meets these standards, safeguarding patient privacy and data integrity.
Accessibility testing - healthcare software should be accessible to all, including individuals with disabilities. Accessibility testing ensures compliance with accessibility standards and enhances inclusivity.

Collectively, these serve as essential checkpoints in developing and maintaining software applications in life sciences and healthcare. By addressing different aspects of software quality, they contribute to reliable, secure, and efficient solutions that positively impact patient care and medical advancements.

Automate your testing with confidence

In the precision-driven fields of healthcare and life sciences, robust software testing is paramount.

Rapise, our cutting-edge solution, seamlessly integrates into these critical sectors. Automating diverse testing types while adhering to HIPAA and GDPR compliance assures accuracy and security. In an era of transformative digital solutions, Rapise empowers you to advance confidently, knowing your software not only meets the highest standards but also safeguards patient trust and well-being.

As healthcare and life sciences evolve, Rapise becomes your trusted partner in ensuring software reliability, data integrity, and patient safety. Get started with a free trial for confident testing that resonates with the demands of these essential industries!

Recap: Uncovering the Security and Privacy Challenges in AI-powered Health Services

2024-03-21T18:00:04-04:00

KEY TAKEAWAYS:

Organizations must address these risks and concerns to safely and ethically implement AI in the healthcare industry:

1. Elevating AI Knowledge and Preparedness in Healthcare:
- Mastering AI in Healthcare: Grasping healthcare needs and challenges is vital when architecting AI-based systems. This knowledge plays a crucial role, particularly concerning data privacy, encapsulating confidentiality, integrity, and availability. AI education programs should blend technical training with crucial soft skills like systems-thinking and risk management, insists Dr. Sriram Rajagopalan from Inflectra. Simultaneously, it is essential to enhance the AI knowledge base of healthcare professionals and organizations.
- AI Risk Contingency: As AI forges ahead, healthcare professionals must be equipped to identify and manage potential AI-linked prospects and risks. Proactive training in AI risk management is the cornerstone to fostering resilience in this dynamic healthcare environment.
- Embracing AI Evolution in Healthcare: The ever-changing landscape of AI demands continuous adaptation. Developers should engage with emerging methodologies focusing on value management techniques, enabling healthcare teams to responsibly harness AI's potential.

2. Emphasizing Ethics and Patient-Centricity in AI Healthcare Development:
- Prioritizing Patients in AI: AI healthcare solutions should be developed with a strong emphasis on patient needs and rights, making AI systems user-friendly, accessible, and beneficial to patient health outcomes.
- Fostering Provider-Centric AI: Patients trust their healthcare providers, hence the efficacy of AI solutions should be viewed through the providers' lens. AI solutions should focus on educating, training, and supporting providers, ensuring a smoother AI adoption journey.
- Upholding Ethical AI in Healthcare: The four bioethical principles—Beneficence, Non-Maleficence, Justice, and Autonomy—should govern all AI developments in healthcare, asserts Dr. Sriram Rajagopalan.
- Promoting AI Accountability in Healthcare: Trust in healthcare AI systems stems from designing them with accountability at the core. These systems should be capable of identifying errors and implementing timely corrections.

3. Securing Health Data and Ensuring AI Transparency:
- Safeguarding Health Data in AI: As AI's role in managing health data expands, regular security audits can enhance patients' trust in the protection of their health data.
- Championing AI Transparency: Transparency in AI development fosters trust among users and stakeholders. Information disclosure about AI decision-making models, data sources, and security measures paves the way for ethical AI use in healthcare.

4. Driving Healthcare AI Policies and Global Cooperation:
- Developing Global Healthcare AI Standards: Collaboration across borders can lead to robust, universally accepted ethical guidelines for AI in healthcare.
- Pioneering AI Legislation in Healthcare: Governments should take the lead in designing legislation and regulatory frameworks that balance AI's risks and benefits in healthcare, fostering an environment of innovation.

5. Tackling Bias in Healthcare AI:
- Eradicating AI Bias: AI systems in healthcare should undergo stringent testing to detect and eliminate biases. A commitment to fairness ensures equal treatment for all patients and fosters trust in AI-driven medical solutions. Diversity within AI development teams is pivotal to challenge bias and bring varied perspectives.

RECORDING:

PRESENTERS:

Sriram Rajagopalan is a project management guru and Enterprise Agile Evangelist at Inflectra Corporation. Dr. Rajagopalan has wide-ranging and extensive software development and project management experience in many industries. He won prestigious recognition from PMI with the Eric Jennet project management excellence award in 2017. He holds a BE in Electronics and Communication Engineering from the University of Madras in India, an MS in Computer Engineering from Wayne State University, and an MBA in Management from Concordia University. His Ph.D. was in Organization and Management from Capella University. Dr. Rajagopalan possesses many professional certifications in PfMP, PgMP, PMP, PMI-ACP, PMI-SP, PMI-RMP, CSP, CSPO, CSD, CSM, ACC, IT Project+, Six Sigma, SCM, SCPO, SCD, SAMC, SCT, and CSOXP.

Ian Frazier is the Cybersecurity & IT Engineer at Inflectra. Within Inflectra, Ian secures the integrity and stability of the company’s information infrastructure and products. He graduated from the University of Maryland with a master’s degree in Cybersecurity Technology and has completed multiple national certifications specializing in IT security and ethical hacking. He regularly researches security trends and attends DefCon yearly to stay on top of the ever-shifting global security threat landscape.

WANT TO ATTEND OUR NEXT WEBINAR?

Mark your calendars for more events planned in our Influence of AI and ML Technologies - Expert Panel Series. You can also sign up for our monthly newsletter to stay up-to-date with all things Inflectra!

#teamInflectra

Inflectra Makes A Splash at Testing Talks Sydney 2023

2023-08-03T14:10:05-04:00

Inflectra Booth: Swag & Games Galore

We landed in Sydney with a suitcase full of cool swag and a team of brainy tech wizards ready to rock Testing Talks. From the suave "James Bond" pen to our nifty 3-port USB C converter, we had folks scrambling to get their hands on some Inflectra goodies. Plus, we were amped to show off our Spira suite and Rapise automation tool, sparking rad conversations about the tech landscape and how our tools could make magic happen in their teams.

The fun didn't stop there! Teaming up with our buds at DevOps1, we set up shop in the wild game room. Picture this: trying your hand at Inflectra's magnetic dart board and standing a chance to win a pair of AirPods!

It was all cheers and high-fives, and yeah, even the Inflectra team got in on the action!

Wrapping It Up

We had an epic day at Testing Talks Sydney 2023, filled with cool chats, laughs, and loads of fun. We were stoked to hang out with our Aussie partners and customers, soaking up everything we could about the tech world here.

Here's hoping everyone who swung by our booth had a great time, learned something cool, had a laugh with our team, and snagged some awesome Inflectra swag.

But wait, there's more! Next stop on our Aussie conference tour - Testing Talks on October 12, 2023, in Melbourne, Australia! Can't wait to see all you legends there!

Can't wait to see you there!

Inflectra in the News - July 2023 News Roundup

2023-08-02T10:33:22-04:00

Publications

Five Tips to Choose Between SaaS, On-Premises and Private Cloud for Your Security and Compliance Needs with VMBlog.com - July 12, 2023

You know you need to address your security and compliance issues-especially in an era where data breaches and regulatory requirements have become significant concerns. Global cyber-attacks increased by 7% in Q1 2023, with each firm facing an average of 1,248 attacks per week, according to Check Point's most recent report, and 1 in 31 organizations worldwide experienced a weekly ransomware attack during the first quarter of 2023. But where should you start? There are so many options today; it can be daunting. Should you go the Software as a Service (SaaS) route? Look for an on-premises solution? Or turn to a private cloud infrastructure? Here are my top five tips for navigating this complex landscape and finding the best technology and/or solution suited to your organization. Read more.

SaaS, On-Premises or Private Cloud: Which is Best for Compliance and Security? with Dice - July 13, 2023

You’ll admit it because you know it’s true: Now is the time to take a hard look at your security and compliance gaps — especially when regulatory requirements and data breaches are becoming increasingly serious concerns. According to Check Point’s most recent report, global cyber-attacks were up 7 percent in Q1 2023, with each firm facing an average of 1,248 attacks per week, and 1 in 31 organizations worldwide experienced a ransomware attack every week during Q1 2023. But now what? With countless options available today, it’s hard to know where to start. Is a Software as a Service (SaaS) solution best? What about an on-premises option? Or is going with a private cloud infrastructure better? Read more.

How Biotech and Life Science Startups Can Embrace Digital Technology to Get Ahead with BioBuzz - July 31, 2023

Whether they are building a new healthcare IT system from scratch or a groundbreaking medical device, many biotech and life science startups need easy-to-use tools specifically designed to help streamline agile projects and/or manage the entire software lifecycle. Read more.

Publications with Forbes Technology

20 New And Enhanced Roles AI Could Create - July 6, 2023

With the exploding use of ChatGPT and other artificial intelligence tools across industries, many skilled and knowledge workers worry about AI disrupting or even eliminating their jobs. However, tech experts assert that AI is just another in a series of tech tools that are intended to help humans—not replace them. Read more.

14 Essential Factors Of Smart Tech Team Vacation Planning - July 14, 2023

While every team leader has to develop carefully considered vacation planning strategies, it’s an especially important endeavor for tech leaders, since every other team, as well as clients and customers, relies immediately and directly on the work of the tech team. Below, 14 members of Forbes Technology Council share some essential factors of smart summer vacation planning for a tech team and why they’re so important. Read more.

19 Essential Pre-Release Quality Assurance Steps For Dev Teams - July 17, 2023

There’s a lot of excitement prior to a large-scale tech product launch or update, as devs look forward to seeing all their hard work in action and users anticipate the new benefits and/or experience. The last thing anyone wants—whether it’s someone on the dev team or an end user—is to discover bugs, inefficiencies or security flaws in a newly launched or updated product. To avoid this, a robust quality assurance system is vital. Below, 19 members of Forbes Technology Council share essential pre-release QA steps for dev teams and why it’s so important not to skip them. Read more.

Feature

The Importance of Testing Mobile Apps with AviationPros - July 3, 2023

Have you ever started using a new mobile app and got the feeling that no one tested the app to make sure it works? Or, maybe your customers started using an app that just went live but they can't get it to work. That shouldn’t happen, says computer programmer and Inflectra founder Adam Sandman, who talked to Aviation Pros about the importance of mobile app testing and how it’s done. Read more.

Keep Informed

Sign-up for our newsletter to continuously receive the latest information about Inflectra happenings, product enhancements, news, and other exciting updates!

Recap - Cheers to Connections: Inflectra's Happy Hour at The Admiral

2023-07-21T13:43:23-04:00

A Vibrant Atmosphere:

The Admiral, renowned for its stylish ambiance and delectable offerings, provided the perfect backdrop for the networking event. The venue's elegant interior, coupled with its warm and welcoming staff, set the tone for an evening of connections and collaborations. As guests arrived, they were greeted with personalized name tags and a delightful cocktail reception. The mingling began right away, fostering an environment of openness and ease among attendees.

Engaging Conversations:

Inflectra's event brought together professionals from diverse backgrounds, including IT, finance, marketing, and more. The diverse mix of industries and expertise led to intriguing conversations, where attendees exchanged insights, challenges, and success stories. Ideas flowed freely, and attendees found themselves drawing inspiration from each other's experiences.

Gourmet Delights:

The Admiral's talented culinary team served a delectable array of hors d'oeuvres and beverages that were a true delight to the senses. The presence of food stations throughout the venue further encouraged guests to mingle and share their culinary discoveries.

Conclusion:

Inflectra's networking happy hour event at The Admiral in DuPont proved to be a resounding success, leaving a lasting impression on all who attended. Professionals across various industries fostered new connections, had vibrant discussions, and enjoyed a night of fun. Inflectra was excited to bring together DC-Based professionals and join conversations about technology, software, and their applications in every industry.

Here's to more networking opportunities, collaboration, and success in the future! Do not miss out on Inflectra's future events, product releases, company news, and more by subscribing to our newsletter.

Thank you to everyone who came out, we hope to see you again soon.

#TeamInflectra

Lightning Session Recap: From Requirements to Deployment - Exploring the Full Potential of the Inflectra Suite

2023-07-14T10:40:00-04:00

KEY TAKEAWAYS

One notable advantage of utilizing the Inflectra Suite is the seamless integration between its tools. The webinar emphasized how these tools seamlessly exchange information, share data, and optimize workflows, resulting in enhanced collaboration and increased team efficiency.
Attendees gained insights into the end-to-end process coverage provided by the Inflectra Suite. The webinar will highlight how the suite effectively supports requirements management, project planning, development, testing, and release management. This comprehensive coverage ensures a smooth and efficient development cycle.
Inflectra's suite offers mechanisms for data synchronization and traceability across its tools. During the webinar, attendees learned how information seamlessly flows between different modules, ensuring that any changes made in one tool are reflected across the suite. This synchronization and traceability enhance visibility and enable teams to make informed decisions.
Customization options were showcased allowing users to tailor the Inflectra Suite to match specific project requirements and workflows. The webinar will demonstrated how organizations can configure the suite to adapt and remain flexible in diverse development environments.
The suite of tools has centralized reporting and analytics capabilities. Attendees saw how the tools aggregate and analyze data from multiple sources, providing meaningful insights, metrics, and visualizations. This centralized information empowers decision-making and facilitates performance tracking.

RECORDING

PRESENTATION

STAY CURRENT

#teamInflectra

Inflectra Supports ISTC 2023: Celebrating 5 Years of SpiraTest as the Official Testing Tool

2023-07-14T12:47:58-04:00

Empowering Excellence:

Every year, the ISTC takes place at Herzliya's Daniel Hotel and attracts professionals and enthusiasts from across the country. Over the course of 5-6 years, the Israeli Software Testing Cup has become a prominent platform for testers to showcase their skills, learn from each other, and expand their networks. ISTC 2023 gathered over 100 talented teams who utilized SpiraTest to plan, execute, and track their testing efforts.

SpiraTest's robust yet user-friendly features provided participants with a comprehensive testing experience. ISTC has become a prominent event that attracts professionals and enthusiasts from across the country. It offers a platform for testers to showcase their skills, learn from each other, and network.

The Final Showdown:

On June 18, 2023, the finalists tested an innovative escape room product using SpiraTest. It streamlined their efforts, facilitated collaboration, and enabled comprehensive bug tracking.

And the Winners Are:

Five outstanding teams emerged as champions of ISTC 2023, showcasing their effectiveness in uncovering approximately 80 bugs, with SpiraTest supporting their efforts.

Celebrating a Partnership:

Inflectra's partnership with ISTC spans five years, with SpiraTest serving as the official testing tool. This collaboration highlights the shared commitment to advancing software testing in Israel.

Looking Ahead:

Inflectra remains dedicated to supporting ISTC's future endeavors, empowering participants with SpiraTest to excel in their testing efforts. By providing SpiraTest to participants, Inflectra empowers them with a cutting-edge test management solution. It simplifies test case management, requirements traceability, and defect tracking, allowing participants to focus on pushing their limits.

Conclusion:

Inflectra is honored to have sponsored ISTC 2023, with SpiraTest as the official testing tool for five years. Congratulations to the winners and gratitude to all participants. The partnership between Inflectra and ISTC promotes excellence in software testing, and SpiraTest will continue to empower testers in future competitions.

Try SpiraTest today!

Recap: Unleashing the Power of Spira 7.7 - Scaling Agile with Program Capabilities & Milestones

2023-07-07T12:54:02-04:00

KEY TOPICS

Overall, the webinar provided insights and practical guidance on effectively managing Agile programs, leveraging program capabilities, aligning milestones, and harnessing the flexibility of Spira's customization features. The key topics we delved into were:

Customizability and Flexibility: We emphasized the power of customization within Spira. Attendees learned how to define custom properties, manage capability types and statuses, and adapt program milestones to suit the unique needs and processes of their organizations.
Scaled Agile Program Management: We explored effective techniques for managing Agile initiatives at the program level through the utilization of Agile Release Trains (ARTs). These ARTs help coordinate and synchronize multiple Agile teams, ensuring smooth program execution.
Program Milestones: Time management was a crucial aspect covered in the webinar. We explained how to set up program milestones, which act as time-boxed deadlines for your solution backlog. We discussed how to categorize and align releases and sprints with these program milestones, enabling better planning and coordination.
Program Capabilities: We discussed how to create and manage a hierarchical list of program capabilities. Furthermore, we explored methods to categorize and prioritize these capabilities effectively. By associating them with tracking execution and progress, teams can achieve better visibility and control.

WEBINAR RECORDING

SLIDESHOW

ABOUT THE PRESENTER

Adam Sandman is the Founder and CEO of Inflectra. He has been working in the IT industry for the past 25+ years. His areas of expertise span software architecture to agile development, software testing, test automation, and project management. He is interested in technology, business, and enabling people to follow their passions. At Inflectra, Adam is responsible for researching the tools, technologies, and processes in the software testing and quality assurance space. Adam is a prolific speaker, whose speaking engagements range from StarEast, and Eurostar to STPcons, DevGeekWeek, Swiss Testing Day, to NDIA, STARCanada, TestingMind, Agile DevOps West, StarWest, testCon, JFTL, and many more.

STAY CONNECTED

Sign up today for our newsletter to stay in the loop on Inflectra events, product updates, company news, and much more!

#teamInflectra

Best Practices in Modern Software Development

2024-09-20T12:58:06-04:00

Defining "best practices"

Best practices are established guidelines and methodologies that streamline processes, reduce risks, and improve the quality of software products. They encompass planning, collaboration, quality assurance, security considerations, deployment, ongoing improvement, and more. By following best practices, teams can make informed decisions, improve collaboration, minimize errors, and ultimately deliver software that meets (and surpasses) customer expectations.

Biggest shifts in development

The field of software development has experienced significant shifts in recent decades, marked by evolving best practices, mindsets, methodologies, and approaches. These shifts have propelled the industry forward from traditional models to agile methodologies and the integration of DevOps practices. By understanding and embracing these changing dynamics, software development teams can adapt, improve efficiency, and deliver software products that align with the demands of the modern digital world.

Rise of Agile development

Agile methodologies have revolutionized the software development industry by emphasizing iterative and collaborative approaches. The increased popularity of frameworks such as Scrum and Kanban marked a shift from traditional waterfall models. There are many incentives for teams to incorporate agile trends into their development. Agile promotes cross-functional teams, adaptive planning, and continuous evaluations, enabling faster feedback and adaptability to changing requirements. This leads to teams delivering software in shorter cycles, improved customer satisfaction, and constant learning.

Shift to cloud computing

The adoption of cloud computing has completely transformed how software is developed, deployed, and accessed. By leveraging cloud infrastructure and services, development teams can reduce costs, scale resources at will, and streamline collaboration. Developers can also deploy applications more efficiently and provide seamless updates and maintenance to end-users rather than managing infrastructure.

Implementation of automation

Test automation has become crucial to the software lifecycle, particularly in streamlining repetitive tasks or test cases. Automated testing, deployment, and monitoring tools allow teams to accelerate the development timeline, reduce human errors, and achieve higher-quality software. By automating tedious and time-consuming processes, teams can free up resources for more strategic and value-added activities.

Learn more about modern software testing and the importance of automation here.

Growing importance of security

As technology becomes more pervasive, the importance of security in software development has grown exponentially. The rise in cyber threats and data breaches necessitates robust security practices throughout the development lifecycle. Implementing secure coding practices (such as input validation), vulnerability assessments, conducting regular security audits, and ensuring secure data handling are all essential to protect sensitive information and maintain user trust.

Best practices for modern software development

In the fast-paced and competitive realm of software development, adopting best practices is essential for teams and organizations to thrive. From project planning to deployment, here are some of the most foundational best practices that empower teams to succeed in their projects.

1. Start with use cases

Use cases are scenarios that describe how users interact with the software. By starting with use cases, development teams can clarify the end user's needs, define required functionality, prioritize features, and align development efforts accordingly. It provides a clear roadmap for development, ensuring that the software stays on target, addresses the most important user requirements, and delivers value.

2. Define your requirements & scope of work

Clearly defining requirements, expectations, and scope of work is another critical step for establishing a successful software development project. It involves capturing functional and non-functional requirements, identifying stakeholders' needs, and setting realistic project goals. Clear requirements help avoid misunderstandings and scope creep, and ensure that the development team focuses on delivering the intended functionality.

3. Use a Scrum or agile methodology

As mentioned earlier, Scrum and other agile methodologies promote iterative development, frequent feedback, and collaboration. They break down work into sprints, prioritize tasks, and involve stakeholders throughout the process. Agile methodologies enable teams to respond to changes, adapt quickly, and deliver working software in shorter cycles, fostering customer satisfaction, transparency, and continuous improvement.

4. Keep code simple

Writing simple and clean code improves maintainability, readability, and collaboration among developers. Simple code is easier to understand, debug, and modify, reducing the risk of introducing errors or bugs. It follows coding best practices, uses meaningful naming conventions, and adheres to design principles, which results in efficient and maintainable software.

5. Implement version & access control

Version control systems like Git allow teams to track changes to source code, collaborate effectively, and manage different versions of the software. Version control provides a centralized repository, facilitates branching and merging, and enables efficient collaboration. It also allows for easy rollback in the event of a security breach or concern. A step further, access control ensures that only authorized individuals have the necessary permissions to modify or access code, protecting the integrity and security of the project.

6. Work in pairs

Pair programming originated from the Extreme Programming (XP) methodology and involves two developers collaborating on the same code. It promotes knowledge sharing, improves code quality, and helps catch errors early. By working together, developers can review and critique each other's code, share insights, and make improvements, leading to higher-quality software and reduced defects.

7. Don’t wait to test

Unit testing involves testing individual components or units of code. By performing unit tests early in the development process, issues can be identified and fixed promptly. It enables rapid feedback, facilitates faster bug fixing, reduces the cost of fixing them later, and more, enhancing overall software quality. Early testing also helps identify fundamental design flaws and ensures that subsequent development stages are built on a solid foundation.

8. Document issues & progress

Thorough documentation plays a crucial role in capturing important information about issues, progress, and decisions made during the development process. It serves as a reference for team members, enables knowledge transfer, and helps project managers track and manage the software's evolution. Documentation ensures that important details are not lost and provides transparency and accountability for all stakeholders.

9. Avoid feature overload

Prioritizing quality over quantity is important to avoid feature overload. While it may be tempting to quickly and repeatedly push out new features, adding too many can introduce complexity, increase maintenance efforts, and degrade overall software quality. By focusing on balancing essential features and maintaining simplicity, teams can deliver a more reliable, stable, and user-friendly software product.

10. Use the right software for development

Lastly, you’ll want to make sure that you select an appropriate software tool for development and testing that enhances productivity and efficiency. Tools like IDEs, testing frameworks, and project management systems automate repetitive tasks, streamline workflows, and improve collaboration. Choosing the right tools ensures the team can work effectively, adhere to best practices, and deliver the software quality your users expect.

Improve your software quality with Spira

Inflectra's Spira family of applications is the ideal solution for modern software development, aligning with the best practices we’ve talked about today to empower teams. With flexible pricing, seamless integration, and intuitive workflows, Spira simplifies the software lifecycle. It promotes clear requirements, effective planning, rigorous testing, and integrated progress tracking.

Still not sure? Try a free 30-day trial to see firsthand its impact on your software development!

Inflectra Offices Closed for U.S. Independence Day Holiday - July 4, 2023

2023-07-03T10:53:31-04:00

Inflectra's Offices are closed on Tuesday, July 4th, 2023, in observance of the U.S. Independence Day public holiday.

We will reopen for business as usual on Wednesday, July 5th, 2023. If you have an urgent technical support issue, please submit a help desk ticket on our website.

2023 Inflectra European Partner Tour Wrapup

2023-07-11T10:08:14-04:00

Inflectra Partner Tour 2023: Western Europe

The Inflectra Partner Team is on the road again this week, this time to visit partners, friends, and partners-to-be in Switzerland, the Netherlands, Belgium, Germany and France. Inflectra's Partnership team, including the CEO and Head of Global Alliances will kick off the Partner Tour 2023 in Zurich and wrap it up in Mannheim, Germany. Read more.

Recap: JFTL 2023 Conference in Paris

On June 13, 2023, #TeamInflectra sponsored the annual Journée des Tests Logiciels (JFTL) Conference in Paris, France. In the years that Inflectra has sponsored JFTL, we've had the opportunity to build brand recognition in the French market, meet customers and partners alike, and network with other sponsors, and this year was no different. Read on to learn about Inflectra’s experience at the conference. Read more.

Inflectra Partner Tour 2023: Western Europe Wrapup

The Inflectra Partner Tour 2023: Western Europe trip is in the books. From Zurich to Geneva to The Netherlands to Belgium, I enjoyed fruitful discussions with our partners. I learned more about the EMEA market and where Inflectra fits within it. I heard about what draws users to Spira and Rapise and where we could make improvements to cement our place as the go-to tools for test management, program management, automated testing and ALM. We were able to forge stronger bonds and explore avenues for future growth. Those visits alone were well worth the trip. Read more.

Recap: Meeting the Inflectra Community in Germany 2023

Last week we had the pleasure of holding an Inflectra user meetup in Germany for our customers based in the DACH (Germany, Austria and Switzerland) region of Europe. In this article we will provide some ideas and information that came from the event that was held in Mannheim, Germany in conjunction with our partner PTA GmbH. Read more.

STAY IN THE KNOW

Are you looking to supercharge your business and unlock new partnership opportunities? Explore the Inflectra Partner Program today.

You can also sign-up for our monthly newsletter to see our upcoming events, company news, product updates, and more.

Coming up soon on Inflectra’s event lineup - Testing Talks 2023 in Sydney Australia on July 26, 2023. See you there!

Inflectra in the News - June 2023 News Roundup

2023-08-02T10:35:43-04:00

Publications with Forbes Technology

13 Identity And Access Management Trends Companies Need To Watch - June 1, 2023

Businesses today run on digital data managed in digital workspaces, making identity and access management a central, ongoing challenge to be solved. To ensure only the right people with the right credentials are able to access a company’s valuable data and systems, leaders must stay on top of emerging IAM trends, including both evolving best practices and new threat vectors. Read more.

Ensure Effective UAT Processes With These 20 Expert Tips - June 1, 2023

Before releasing a new tech product into the market, it’s essential to ensure it operates well and achieves the intended result, and that requires user acceptance testing. After investing time and effort into a new product, a dev team probably wants UAT to proceed as quickly and smoothly as possible; but that’s not necessarily the right goal. Read more.

18 Smart-City Technologies That Will Genuinely Improve Urban Living - June 5, 2023

Increasingly, technology isn’t just impacting our workplaces and personal lives—it’s being leveraged across entire cities to improve and enhance a variety of public services and functions. These “smart cities” are designed to make it easier for citizens and visitors to navigate traffic, access essential services, use energy efficiently and much more. Read more.

How To Scale Agile Software Development Without Reinventing Waterfall - June 23, 2023

In the software industry, in which I have worked for the past 25 years, we often use the adage, "What's old is new again." Today's messaging tools like Slack and Teams, for example, owe a lot to the previous generations of messaging like AIM, ICQ and YTALK. Read more.

Articles

Optimizing the Customer Digital Experience Means Mobile App Testing with Hospitality Technology - June 8, 2023

The hospitality industry has been at the forefront of information technology since the 1940s when Westin installed the first electronic hotel reservation system. However. during the last three years, the COVID pandemic forced hotels to dramatically accelerate the adoption of certain technologies (such as contactless payment, check-in and room service) and change the customer experience accordingly. With the receding of the pandemic, there is a lasting impact of these changes and the future will bring changes to IT systems and mobile apps. Hospitality companies must be prepared to ensure a reliable, high quality customer experience going forward. Read more.

STAY UP-TO-DATE

Recap Blog -Transforming Healthcare QA with SpiraTeam: Achieving Excellence in Testing

2023-06-29T15:06:25-04:00

KEY TAKEAWAYS

SpiraTeam is a software tool with advanced features and capabilities that are specifically designed to address the unique challenges faced by the healthcare industry. It can help healthcare professionals unleash its power to improve their workflows and processes.
Leveraging SpiraTeam can contribute to enhancing patient safety. By utilizing the software, healthcare organizations can implement rigorous testing protocols, ensuring that all necessary tests are conducted to minimize risks and maximize patient safety.
SpiraTeam facilitates regulatory compliance in the healthcare industry. It simplifies adherence to industry standards and regulations such as HIPAA, GDPR, and FDA guidelines. The software enables the generation of audit-ready reports and documentation, which ensures that healthcare organizations meet regulatory requirements and provides peace of mind.
The use of SpiraTeam can streamline workflows and increase efficiency. It optimizes quality assurance (QA) processes, manages test cases effectively, improves test coverage, and expedites release cycles. This streamlined approach leads to faster time-to-market for healthcare products and services.

WEBINAR RECORDING

SLIDESHOW

ABOUT THE PRESENTER

NEVER MISS AN EVENT

Get notified of our upcoming webinars by signing up for our monthly newsletter! Stay in the loop of events, Inflectra product updates, company news, and more!

#teamInflectra

Inflectra Partner Tour 2023: Western Europe Wrapup

2023-06-28T15:40:25-04:00

Visiting Delft, The Netherlands, with partners Remco and Karolina Putker of RobustIT, and Antwerp showing its pride.

The trip didn’t stop with the meetings. We went on to the EuroStar testing conference in Antwerp, Belgium. The team had productive conversations with hundreds of potential customers and a dozen potential new partners. (And, of course, the James Bond pens continue to be the talk of the conference.) The event was well attended and in a super location adjacent to the zoo and Antwerp’s stunning train station. We continued to elevate brand recognition and hone our message while developing new relationships that we hope will develop into great business partnerships as well as friendships.

The booth calm before the storm of visitors wanting to know more about Inflectra and the James Bond pens.

The team and friend Nicole at the EuroStar awards gala, and Adam and partner Paweł Bielecki of QualityMinds Sp. z o.o.

Inflectra Partner Tour 2023: Western Europe is a wrap. It is a testament to the power of international collaboration and the significance of face-to-face interactions in fostering strong business relationships. I returned home with a renewed sense of purpose and a deeper appreciation for the diverse cultures and opportunities that Europe has to offer. Soon we will be planning our next adventures close to home and around the globe. Stay tuned. In the interim, we know where EuroStar 2024 will be…

STAY INFORMED

Coming up soon on Inflectra’s conference lineup - Testing Talks 2023 in Sydney Australia on July 26, 2023. See you there!

Interested in seeing our conference lineup, product updates, upcoming webinars, company news, and more? Sign up for our newsletter to stay up-to-date with all things Inflectra!

#teamInflectra

Recap: Meeting the Inflectra Community in Germany 2023

2023-06-28T13:10:48-04:00

The Inflectra Meetup at PTA HQ in Mannheim, Germany

Coinciding with our Inflectra partner tour and the EuroSTAR 2023 conference, the Inflectra team made a side trip to visit our long-term partners PTA GmbH (and their sister company DATIS GmbH) who have been providing consulting, configuration and implementation services for Inflectra products for the past 14 years. The user meetup was held at PTA's imposing headquarters in the Germany city of Mannheim, known as the "City of Innovation" where Mozart lived, and the bicycle, automobile, and tractor were invented.

The Inflectra team was in full attendance, with product brochures and swag for customers aplenty. The gifts included our world famous 'James Bond' multi-function pen, video-conference lights, and branded USB-C hubs.

After the initial socializing and networking among the attendees (both PTA consultants and Inflectra customers), we got down to business and started the formal presentation:

The opening remarks and initial presentation by Dennis Haßlöcher, CEO of PTA/DATIS, outlined the 14-year partnership between Inflectra, PTA and DATIS. Inflectra's products have become key technology enablers for the various projects undertaken by PTA consultants in various industries across Germany. In addition, DATIS provides local hosting of Inflectra products.

After that presentation, Adam Sandman, CEO of Inflectra outlined some key company news updates, including our new company tagline "Inflectra Helps You Deliver Quality Software, Faster and With Lower Risk".

Adam also provided information on the InflectraCon conference that had been held in Washington, DC in April, 2023.

After that there was a presentation and discussion on the roadmap for our SpiraTest, SpiraTeam, SpiraPlan and Rapise products. As part of the discussion, the attendees were able to vote on the items in the roadmap to give their priorities:

The team took these votes back to the product team at Inflectra to help inform the future plans for the products.

Making Connections with Our Partner Team

After the user meetup was concluded, it was a great time to catch up with our PTA friends and colleagues, many of whom we'd only met online in virtual meetings and calls:

Finally after the day was completed, Adam and Dr. Sriram Rajagopalan, our Enterprise Agile Evangelist shared a festive pint of Germany beer to celebrate the success of the event.

If you're interested in organizing a local Inflectra meetup for your community, please contact our marketing team.

Presentations from the User Summit

The following presentations were made during the event, please feel free to clip any of the slides that interest you:

Inflectra News and Product Roadmap

Introduction to Inflectra's Partner: PTA and DATIS

Inflectra Sponsors Wharton Club of DC Reception at the Sri Lankan Embassy in Washington, DC

2023-06-26T17:54:17-04:00

The reception drew an exclusive gathering of Wharton and Oxford alumni, distinguished business leaders, international diplomats, dignitaries, and representatives of state governments, fostering an atmosphere of collaboration.

Inflectra was the official sponsor of the event and had members of its team present to discuss innovation and how Inflectra's products are used around the world in support of mission-critical projects and programs:

Within the confines of the Sri Lankan Embassy, guests reveled in the sophisticated ambiance as they listened to speeches delivered by His Excellency Mahinda Samarasinghe, the Ambassador of Sri Lanka to the U.S., and the esteemed Minister of Economics of Sri Lanka.

The evening was further enriched by Sri Lankan dance and song performances, tantalizing cuisine, and a selection of beverages that delighted the senses.

As a gesture of appreciation, each attendee received a complimentary packet of the world-renowned Ceylon Tea, an exquisite symbol of Sri Lankan heritage.

Team Inflectra

Influence of AI and ML Technologies - Expert Panel Series

2023-09-26T13:46:15-04:00

The topics lined up in this Webinar series include:

Education on the Brink of Transformation Through Disruptive Technology - March 15, 2023

The panel will discuss the way forward in ensuring that AI is used ethically and responsibly in the classroom with outcomes that are unbiased, non-discriminatory, and benefit students regardless of their background.

Uncovering the Security and Privacy Challenges in AI-powered Health Services - June 29, 2023

PRESENTERS:

Sriram Rajagopalan - Enterprise Agile Evangelist at Inflectra Corporation

NEVER MISS THE EVENT

See you there!

#teamInflectra

STAY IN THE KNOW

Sign up for our monthly newsletter to stay up-to-date with all things Inflectra!

Recap: JFTL 2023 Conference in Paris

2023-06-21T11:42:39-04:00

The Inflectra booth

On the first day of the conference, the expo is closed to the public, allowing time for sponsors to set up their booths and displays. This year, our booth had a nuanced design and was stocked with our most popular swag: USB-C to USB converters, the “James Bond” pen, webcam covers, and Inflectra-designed stickers.

After the initial set-up, we were off to meet our partners to discuss strategy, customer opportunities, and the Inflectra suite enablement.

The JFTL EXPO

On the day of the EXPO, the team was in the booth to greet the attendees at 8 AM when the doors opened. This year, the conference had more than 1,300 attendees. Throughout the day, we talked to many new faces about Inflectra tools, their use cases, and how they relate to other tools in the market. This year, we noticed that attendees had increased interest in learning more about Rapise and the automation side of testing, in addition to how our tools would be able to integrate in their existing software ecosystem. We were also able to catch up with a good number of Inflectra customers and discussed new product updates.

During slower moments, we ventured around the conference hall to talk with other sponsors, a couple of which are Inflectra partners, like TTC Global, OctoPerf, and Keysight.

At the end of the day, attendees and sponsors gathered together for a prize giveaway, where Inflectra was happy to gift the winner a pair of Apple AirPods. When it was time to pack up, we were amazed to see that nearly all the Inflectra swag and flyers had been given to attendees by the end of the day!

Au Revoir, Until Next Year

It was a fun couple of days at the JFTL conference this year, and we thank all of the organizers for holding, yet again, a great event. Thanks to all those who were able to stop by the booth, talk with us, and say hello. We hope you enjoyed the conference and will continue to enjoy the Inflectra swag.

Coming up soon on Inflectra’s conference lineup - Testing Talks 2023 in Sydney Australia on July 26, 2023. See you there!

Stay Informed

Interested in seeing our conference lineup, product updates, upcoming webinars, company news, and more? Sign up for our newsletter to stay up-to-date with all things Inflectra!

#teamInflectra

Recap Blog: Wrapping Up Agile + DevOps West 2023 - Reflecting on the Conference Experience

2023-06-13T12:57:55-04:00

ARRIVAL

The team landed in beautiful Las Vegas to a skyline of flashing neon lights and desert sand-scape. After finding our way through the labyrinth of Caesar’s Palace, we met with their Techwell friends and set up for the busy days ahead. A great night of networking and delicious food commenced over the Sponsor dinner that night as we connected with friends - old and new alike.

THE INFLECTRA BOOTH

Bright and early, Team Inflectra returned to the EXPO, happy to re-engage with partners and demo our products to attendees during the two-day event. As always, we came prepared with exciting swag and on-the-nose stickers that attendees rave about. The event was filled with insightful discussions on DevOps, Agile, and all the ways Inflectra’s products integrate with their principles.

Inflectra premiered their newest swag, which was met with great enthusiasm. Here is a sneak peak of our swag. To learn more or get your own, visit our booth next time you see Inflectra sponsoring a conference. 🙂

With the busy EXPO, we enjoyed an Inflectra-sponsored lunch of hot marinara pasta, charred mushroom chicken, and Mediterranean salads. But we still left plenty of room for the dessert table!

ADAM SANDMAN’S TALK
With Day 1 in full swing, Adam Sandman, Infelctra CEO, gave an insightful talk on Scaled Agile. Asking the audience 'Are You Scaling Agile or Just Failing Agile?,’ Sandman discussed current strategies on Scaling Agile and why they aren’t working. Audience members left with a new understanding on how to tackle agile in a growing company and utilizing communication between multiple teams to do so.

DR. SRIRAM RAJAGOPALAN - INDUSTRY TECHNICAL PRESENTATION

On conference Day 2, Inflectra’s Enterprise Agile Evangelist Dr. Sriram Rajagopalan spoke on ‘Boosting Business Agility with Value Stream and Scaled Agile Strategies.’ The attendees left with a newfound understanding of Business Agility’s significance and how it transcends individual and team agility.

EXPLORING VEGAS

As usual, ADOWest was hosted at the decadent Caesar’s Palace. After hours enjoying the indoor skies and beautiful Roman architecture, we left the venue to explore the world of Vegas. From the Bellagio fountain show to the replicas of global cities, the Team had a blast on Vegas’ Strip. Another evening, the Team made their way to Fremont Street, a center of music and adventure for all to enjoy. We had a great time exploring the city and bonding over new experiences.

UNTIL NEXT TIME

It was a fun couple of days at Agile + DevOps West 2023, and we were glad to sponsor the event. We hope everyone who stopped by our booth learned something new, enjoyed talking to our team members, and will find the swag useful - especially those adapters!

Coming up soon on Inflectra’s conference lineup - Testing Talks 2023 in Sydney Australia on July 26, 2023. See you there!

STAY INFORMED

Interested in seeing our conference lineup, product updates, upcoming webinars, company news, and more? Sign up for our newsletter to stay up-to-date with all things Inflectra!

#teamInflectra

Inflectra Partner Tour 2023: Western Europe

2023-06-08T12:58:33-04:00

The first visit is a lunch with our top Swiss partner and Inflectra evangelist, where we plan to discuss the industry in Switzerland and how Inflectra can best support our partners in the Swiss economy. Of course, it will be a delight to meet in-person.

The next stop is a train ride to Geneva, where we’ll meet our friends and partners at Itecor. Itecor and Inflectra co-sponsored Swiss Testing Days last year, and we look forward to planning future collaborations with the team. Also in Geneva, we’ll be meeting a handful of pre-selected potential partners of Inflectra.

From Geneva, the road will take us west to the Netherlands where we will be spending time with RobustIT - a great partner and a treasured friend of the Inflectra team.

After the Netherlands, the Inflectra team will split up to tackle different events. Some team members will remain in the DACH region to explore new partnership opportunities at EuroStar in Antwerp, Belgium, while others will travel to Paris for the JFTL conference, which Inflectra is sponsoring for the 5th year in a row.

At EuroStar we plan to connect with our partners and talk more about our exciting Eggplant and Spira integration. We also look forward to catching up with our friends at Global App Testing and others.

At JFTL in Paris, we will be meeting face-to-face with our new partners and reconnecting with our loyal customers and well as the long-time partner TTC Global, who will be sponsoring the conference in a booth across from ours.

Our Partner Tour concludes in Mannheim, Germany, where we will participate in a user summit with our excellent partners PTA and Datis. The Inflectra CEO Adam Sandman and Agile Evangelist - Dr. Sriram Rajagopalan will be meeting the PTA team, key partner decision-makers, and the Inflectra customers from the region. The two days of this Partner Summit and Partnership Visit are packed full of trainings, roadmap discussions, customer roundtables and fun activities.

It will be an agenda-packed two weeks, but it is well worth the travel to make the visits.

If you are planning to be at the EuroStar or JFTL conferences, make sure to stop by the Inflectra booth. Let's talk partnerships in person!

Interested in Becoming Our Partner?

Join the Inflectra Partner Program and unlock a world of opportunities! As an Inflectra partner, you'll gain access to cutting-edge software solutions, extensive resources, and dedicated support to drive business growth. Don't miss out on this exciting partnership journey. Join today!

#InflectraPartnerTeam

Inflectra in the News - May 2023 News Roundup

2023-06-05T17:04:28-04:00

Publications with Forbes Technology

16 Leaders’ Tips To Help Tech Pros Better Communicate With Non-Tech Experts - May 3, 2023

In business, a failure to effectively communicate can cause everything from frustration to lost revenue. Tech leaders and pros regularly have to communicate—even “translate”—their efforts in a variety of situations, including explaining a potential new product to stakeholders, teaching fellow staffers how to use new tools, talking about cybersecurity readiness and walking customers through a new solution or troubleshooting exercise. Read more.

18 Strategies For Ensuring An Engaging, Effective Beta Testing Process - May 4, 2023

Developing the most groundbreaking new technology in the world doesn’t mean anything if nobody wants it or if the target audience finds it so difficult or frustrating to use that they ultimately reject it. Tech companies invest a lot of time and budget dollars into new software products and updates, and while they’re internally tested, those deeply involved in the process may not interact with software in the same way an end user does. Read more.

15 Components Of An Effective IP Protection System (And Why They Matter) - May 11, 2023

Protecting intellectual property from former employees and other companies is an essential effort for tech industry businesses. While the majority of professionals are honest, it only takes one unscrupulous (or careless) former employee to expose a company’s valuable IP to the market. Read more.

15 Tips For Companies Looking To Leverage Technology To Become More Crisis-Resistant - May 12, 2023

From supply chain disruptions to uncertain labor markets to the shadow of a potential recession, ongoing and looming issues are leading many companies to focus on ways to become more crisis-resistant. In a global economy, tracking and analyzing the multitude of variables that can impact a business can’t be done manually—technology is essential. Read more.

17 Tech Experts Share Best Practices For Managing Customer Data - May 12, 2023

In today’s digital age, businesses collect and store vast amounts of customer data to improve their services and marketing efforts. However, this data is a target for cybercriminals and can be vulnerable to unauthorized access, which can result in data breaches and compromised customer information. Read more.

14 Tech Leaders’ Tips For Prioritizing Bugs, Tickets And New Features - May 17, 2023

It’s certainly true that no tech product is perfect; it’s likely also true that most tech products are never really “finished.” Dealing with a regular influx of bug reports and feature requests is all in a day’s work for most tech teams, and developing workable strategies for prioritizing them is an essential part of a tech leader’s role. Read more.

13 Expert Strategies To Help Secure Remote Work Environments - May 18, 2023

Many businesses that established remote and hybrid working arrangements during the pandemic have opted to make them permanent. However, while leaders are eager to take advantage of the flexibility, cost savings and employee morale boost that come with work-from-home policies, they must ensure they don’t do so at the expense of maintaining a robust security posture. Read more.

Article Features

How to Enhance Passenger Experience Using Mobile Interfaces - May 19, 2023

Airlines rely on IT systems for their operations, but mobile app interfaces are becoming a popular solution. Jasleen Mann finds out how Inflectra is aiding the development of app-centred solutions. Read more.

Interviews

Software Testing Happy Hour Featuring Adam Sandman, CEO of Inflectra - May 17, 2023

Check out our next episode of our Software Testing Happy Hour that we filmed onsite at InflectraCon a few weeks ago! In this episode, we feature Adam Sandman, CEO of Inflectra, as Bob Crews, Adam Sandman and Matthew Kubal discuss culture of quality and what sets Inflectra's solutions, Rapise and Spira, apart from the other solutions on the market. Watch here.

STAY IN THE KNOW

Inflectra Releases Partner Program Improvements

2023-05-26T10:44:01-04:00

Types of Partners

In an effort to better delineate between the types of partnerships we offer, we have slightly adjusted our partner categories and have defined the scope and responsibilities of each in more detail. These categories include:

Solution Partners
Technology Partners
Resellers

Please find more information on each below.

Solution Partners

These partners are Inflectra advisors, trainers, implementers, consultants, affiliates, and/or resellers who implement customer solutions with Inflectra products. Inflectra Solution Partners are able to work at their desired level of engagement and perform services that make most sense for their business.

There are currently three tiers of Solution Partners: Silver, Gold, and Platinum. The differences of each are defined later in this article and on our Partner Program page.

Technology Partners

Our Technology Partners are organizations that integrate with Inflectra tools and deliver joint solutions to shared customers. These partners optimize Inflectra solutions with plug-ins, adapters, connectors, and technical services.

Resellers

Resellers are organizations that actively assist with sales and procurement, generally for customers requiring an approved reseller. Inflectra resellers receive a 10% discount on the contracts and renewals that they process.

More Incentives & Benefits

We are excited to offer our Solution Partners more training, sales, marketing, and account mapping opportunities. This includes benefits such as increased tool licenses for internal use, personalized training depending on each partner’s needs, and better alignment with the Inflectra sales teams. Ultimately, we want to work with our partners more closely and intentionally, and provide them with the training they need to best support joint customers.

The Solution Partner Benefits are outlined below, with the recently added incentives boxed in yellow:

We have also released a new set of Partner Badges to recognize and reward the accomplishments and expertise of our partners. In addition, these badges will become available by each partner listing on the Inflectra website, allowing customers to filter by badge and find partners that best suit their needs.

A New Engagement Point System

Inflectra’s partner ecosystem is made up of a wide variety of organizations, all with different goals, expertise, and business processes. Since our last Partner Program launch, we have learned that using sales revenue as a means to evaluate partner performance does not work for every organization. Instead, we have found that our best partnerships are built on strong relationships with frequent engagement. To encourage and support this engagement, we have developed metrics for success in 4 areas:

Engagement
Marketing
Continuing Education
Sales

Within each of these areas are activities meant to facilitate a strong foundational relationship between Inflectra and our partners. Each of these 4 areas has a suggested number of points that equal a total goal amount depending on the partner tier. Points are accumulated throughout the year and will be self-recorded in the Partner Portal.

This Engagement Point System coexists alongside the training qualifications completed through Inflectra Campus. These training certifications remain the same from the last Partner Program launch.

What’s Next?

Our improvements don’t stop here! We continue to take into account the feedback and suggestions from our partners so that we can continue to fine tune the Inflectra Partner experience and in the end, grow exponentially together.

Here are some upcoming changes to look forward to:

Partner Portal revamp, with more sales and marketing resources, expanded team use, and blog & MDF submissions
Inflectra Partner monthly office hours
More joint marketing opportunities and collaborations

If you have any questions about our new Partner Program changes, please reach out to partnerships@inflectra.com

Webinar Recap: SpiraTeam for QA Excellence with Adam Sandman

2023-05-25T13:55:09-04:00

SpiraTeam, one of our flagship products, is an integrated ALM platform combining project management, requirements management, and QA management functionalities. It allows teams to manage projects, track requirements, perform test management, and collaborate effectively. Continue reading to see how your team can use its features proficiently and enhance QA processes to attain superior results.

WEBINAR RECORDING

SLIDESHOW

ABOUT THE PRESENTER:

Adam Sandman is the Founder and CEO of Inflectra. He has been working in the IT industry for the past 25+ years. His areas of expertise span software architecture to agile development, software testing, test automation, and project management. He is interested in technology, business, and enabling people to follow their passions. At Inflectra, Adam is responsible for researching the tools, technologies, and processes in the software testing and quality assurance space. Adam is a prolific speaker, whose speaking engagements range from StarEast, and Eurostar to STPcons, DevGeekWeek, Swiss Testing Day, to NDIA, STARCanada, TestingMind, Agile DevOps West, StarWest, testCon, JFTL, and many more.

STAY INFORMED

Recap Blog: The Houston SQE Meetup Experience

2023-05-19T09:43:47-04:00

Inflectra, TTC, and the SQE Group brought the speakers Wade Pinderfrom Improving, Dilhan Manawadu from Sysco, and Dr. Sriram Rajagopalan from Inflectra together for an initial discussion. The momentum began building as the speakers laid the foundation for their brief 20-min talks to engage the audience for the expert panel. Dr. Sriram Rajagopalan began making the travel arrangements to leave for Houston from Boston!

Wade Pinder: Beyond the Backlog: Why Seeing the Big Picture Will Make QA Engineers Even More Awesome!
Dilhan Manawadu: Building Total Experience (TX) in Large Enterprises Through Quality Engineering
Sriram Rajagopalan: Uncertainty Factor – Rethinking Quality Assurance for Emerging Digital Revolution

The Event

As people gathered around, it was evident that everyone was happy to see other quality engineering colleagues in real-time 3D. Discussions continued around the meal table and the drinks as people began meeting with the speakers and engaging on quality topics as well as topics on quality!

The Panel

It was time!

As the SQE meetup group introduced the in-person event, thanking TTC and Inflectra for their generous support and swag, they introduced the speakers. It was unclear whether people were hungry for food or knowledge, but the room was full of attentive audience members, ready to absorb and engage.

Wade Pinder

Wade began his thoughts on product management as a larger big-picture thinking. Wade made it very clear how the product ideas are all coming straight from the product vision followed by a strategic approach to disaggregate the larger collection of ideas into a milestone driven roadmap. Questions came up already from the audience as one person asked who has the ultimate accountability for priority. Wade associated the MoSCoW (Must, Should, Could, Won't) prioritization scheme with the Now, Soon, and Later! Very unequivocally, he emphasized that the product owner needs support from everyone in the team to create the value journey!

Dilhan Manawadu

Dilhan continued his discussion on Total Experience (TX) and how customer experience (CX), Employee Experience (EX), and Multi-Experience (MX) are integrated as part of the total experience package. He described how Sysco has been investing in this total experience package, almost rethinking some of the common lexicon. One example he gave was calling the people that drove the huge tracks as part of their delivery chain as delivery partners rather than truck drivers! What a nice way to emphasize unlearning and relearning!

Sriram Rajagopalan

Sriram began his interactive presentation asking what quality meant! As the audience began answering, Sriram reconnected the ‘fitness for purpose’ as the foundational principle behind quality by design. “As we normalize conformance to requirements in testing to equate with quality, we fall into the acceleration trap of yielding too fast to 4th Industrial Revolution (4IR) technology,” said Sriram. This message clearly popped out as Sriram engaged the audience with hilarious and informative examples of Family as a Service (FaaS). Sriram brought the presentations to life by advancing the notions that quality engineering teams should rethink quality from the risk management principles and the bioethics principles of benevolence, nonmaleficence, and autonomy.

Discussions from the audience continued with TTC facilitating the questions. In response to the examples of risk based testing that the quality engineering team can focus on to uphold quality, Sriram discussed unscripted approaches like the adhoc testing, exploratory testing, error guessing, and scripted testing combined with automation. Wade reconnected with Sriram’s thoughts on how quality is a function of risk and how much risk based thinking is pivotal to the team’s ability to support his product vision, strategy, and roadmap. Wade further responded that the biggest disconnect between quality teams and product teams is the siloed approach to quality rather than a systemic approach to quality. Dilhan supported these risk based thinking and siloed gaps as the foundations for how total experience is getting addressed.

Wow! What an experience supported by Inflectra and TTC. Thanks to the sponsors and the organizers for making this happen and bringing a welcome treat to the Houston SQE community. Thanks to Dr. Sriram Rajagopalan for traveling to Houston and supporting this event.

Ingeniería de Calidad con Plataformas Inflectra - Sesiones Relámpago

2023-05-15T13:28:53-04:00

Las sesiones relámpago cubrirán los siguientes temas:

Automatización de Pruebas Rápida y Fácil con Rapise
- Español - 11 de enero de 2023 a las 3 pm (EST) - REGÍSTRATE
Cómo Gestionar tus Proyectos ágiles con SpiraTeam
- Español - 9 de febrero de 2023 a las 10 am (EST) - REGÍSTRATE
Cómo acelerar su gestión de pruebas con SpiraTest
- Español - 18 de Mayo de 2023 a las 10 am (EST) - REGÍSTRATE

MANTENTE INFORMADO

¡Suscribete a nuestro boletín para mantenerse al día con todos los eventos de Inflectra!

Para obtener más información sobre el ecosistema de software de Inflectra, únete a nosotros para InflectraCON 2023 en Washington, DC, del 19 al 21 de Abril de 2023.

How AI helps QA Shift Left

2023-05-17T10:57:11-04:00

How AI helps QA Shift Left

As the focus on quality becomes more mainstream, QA teams are under intense pressure to deploy bug-free... but we all know that’s nearly impossible. Lacking test coverage, lacking test automation, lacking…simply enough testers – QA teams are never 100% confident their release will be bug-free.

And that’s just something every expert tester will tell you (whether you like it or not), they can only be 99% confident that the deployment will be clean…you’ll never hear them say 100%.

In all my time working with QA teams, I’ve never heard a Tester say they are 100% confident their release will be bug-free. And that’s ok. There’s an important tradeoff every digital leader must make, either release now with 99% confidence or delay the release by a week to achieve 99.1% confidence.

Pressure to get that release out is fierce, and so getting it out on time usually outweighs delay for further testing.

Although there seems to be an abundant amount of tooling in the market, few exist that help streamline their team’s workflow to achieve greater confidence in release.

Cutting through the noise, how can Digital Leaders and Testers make things easier on themselves and release with more confidence?

We can’t write anything these days without mentioning AI, can we? Apparently not. Because it really does help QA Shift Left and deploy with more confidence…maybe even go from 99% to 99.9% confidence.

Never entirely perfect, but closer!

Here’s the areas I see AI really helping QA Shift Left and achieve higher Confidence in their deployments.

AI Risk Based Test Selection

There’s some real clout behind this technology. Test only in the areas where developers are making changes, thereby allowing teams to test earlier and more frequently.

There’s some early movement in this space, such as early mover Appsurify. Their AI Risk Based Testing solution is patent-pending and allows teams to reduce test cycles by 90% to get feedback to developers at time of change. Rather than running 100% of tests after each change, their AI-Model auto selects and executes just the few tests associated with areas Developer made changes.

By only running 10% or 20% of the tests while still catching the bugs, this approach saves significant time, reduces Infrastructure resources, and optimizes CI pipelines for faster feedback and allows for continuous testing.

For example:

A 1-hour Rapise test run may only be executed 2 or 3 times in a day. If the team leveraged AI Risk based testing, they could shorten this run down to under 5 minutes and execute tests on a per PR basis.

So instead of running their tests 2-3 times a day, they can run their tests 10+ times a day and find bugs while the developers are still focused on the task at hand. The optimal thread of work is 1, so when developers get feedback before they context switch - that helps them stay focused, find bugs in real-time, and ship with higher confidence.

Prevent Flaky Tests from Distracting the Team

AI can recognize trends in test results that pick up whether a test failed due to a real failure versus a false flag. When a run is executed, blocking out flaky signals helps give developers cleaner feedback to focus their debugging on actual bugs.

CI pipelines frequently fail when there’s a flaky test and cause unnecessary time waste. One way to optimize CI pipeline is to leverage AI to block out flaky tests from breaking builds. Only having CI builds fail due to real failures gives developers clean signals and direction for debugging so they only focus their time on real bugs.

AI helps QA Shift Left

Give QA clean signals whether good or bad. And not bad in the traditional sense, because catching a real bug early is an optimal outcome. It’s about cutting through the noise and distraction to focus where time is best spent.

For example:

A Jenkins build fails with 100 test failures. 2 bugs caused 60 tests to fail, and flakiness caused 40 tests to fail. A significant amount of time will be wasted looking into those Flaky Tests with no value. When there's an inherent amount of flakiness and builds are constantly failing, developers start to ignore the results which can be a dangerous outcome.

AI removes that 40% flaky distraction. Rather than failing the build and labeling everything as failed. AI says these 60 test failures are caused by real defects, whereas; these other 40 failures are caused by flakiness. And so, it’s probably in your team’s best interest to focus on the 60 test failures caused by real defects.

That saves the team's time while also building confidence into test results.

Conclusion

Shipping with confidence is hard.

Even leveraging all best practices, Digital Leaders and Testers may only feel 99% confident their release will be bug-free. Getting that additional 0.9% is painstakingly time-consuming. However, testers can leverage AI tools, such as Appsurify, to significantly increase confidence without additional effort so QA can ship earlier and faster confidently.

Reflecting on the Success of InflectraCON 2023

2023-05-15T18:23:41-04:00

Key successes at InflectraCON 2023:

Diverse Perspectives and Engaging Sessions: InflectraCON 2023 offered a remarkable lineup of sessions featuring speakers from all over the world who shared their expertise, experiences, and innovative approaches. Attendees had the opportunity to dive deep into topics such as test automation, agile methodologies, DevOps, and project management.
Exploring Emerging Trends: One of the standout aspects of InflectraCON 2023 was its focus on exploring emerging trends reshaping the software testing landscape. The conference provided a glimpse into the industry’s future, with sessions on AI-powered testing, machine learning, and the impact of IoT on testing practices. More on this below!
Industry-Leading Tools and Technologies: InflectraCON 2023 also showcased Inflectra’s industry-leading tools and technologies. Attendees had the opportunity to engage with product experts and witness live demonstrations of Inflectra’s comprehensive suite of software testing and project management solutions. From the robust test management platform SpiraTest to the scriptless test automation platform Rapise, Inflectra demonstrated how its tools could streamline processes, enhance productivity, and drive efficiency across organizations of all sizes.
Networking and Collaboration: InflectraCON 2023 provided a vibrant networking environment, fostering collaboration and knowledge sharing among attendees. But also a ton of fun!

Key Takeaways:

Let’s delve into some of the insights shared during the InflectraCON 2023, providing a glimpse into the future of technology:

Inflection Point of AI: “With AI, we are at an inflection point.” - Adam Sandman. The rapid advancements in artificial intelligence have brought us to a crucial turning point. AI is transforming various industries, revolutionizing processes, and opening new possibilities.
Risk Analysis and Testing: “You can’t test a program completely.” - Bob Crews. Testing every aspect of a complex software program is a daunting task. Prioritizing testing based on risk exposure allows organizations to focus on critical areas and ensure efficient testing practices.
Design Thinking for Agile Teaming: “Design thinking forces you to consider multiple perspectives.” - Jenn Bonine. Design thinking, a human-centered approach to problem-solving, encourages teams to empathize with users and consider diverse perspectives. By adopting this mindset, organizations can create more user-centric solutions and enhance customer experience, ultimately gaining a competitive edge.
Finding Efficiencies in SDLC: “Agile ceremonies are essential, even if they don’t always seem to be an efficient use of time.” - Melissa Tondi. Efficient software development life cycle (SDLC) practices are crucial for successful project delivery. This talk highlighted the significance of Agile ceremonies, such as planning meetings and kick-offs, in establishing clarity, aligning team members, and avoiding duplication of efforts.
Agile Approach and Scaling: “Building scaffolding in jello.” - Adam Sandman. Scaling Agile practices requires a solid foundation and adaptability. This talk emphasized the importance of flexibility and robust frameworks to support Agile transformations. Scaling Agile successfully involves aligning teams, establishing visibility, and ensuring traceability across the software supply chain.
The Science of Testing: “Testers and scientists are one and the same.” - Thomas Haver. Testing is not just about following predefined steps; it involves scientific thinking, experimentation, and questioning assumptions. Testers play a vital role in identifying nonconformance to requirements and ensuring software quality.
Accelerating Quality with Conscious Deliveries: “It is always cheaper to do things right the first time.” - Lalitkumar Bhamare. Addressing the underlying causes of issues and focusing on quality from the early stages of development saves time and costs. In this talk, Lalitkumar highlighted the importance of aligning engineering actions with business goals and taking a proactive approach to quality.
Shifting Left and Kicking Off: “The Kick-Off meeting is the most important meeting in the QA journey - never miss it!” - Kevin Harris. The Kick-Off meeting sets the stage for successful QA journeys. By ensuring early involvement, collaboration, and clear communication, teams can align their efforts, set expectations, and lay a strong foundation for the project.
Accessibility: "Being an A11y: Why Accessibility Advocacy Matters" - Michael Larsen. Michael stressed the importance of inclusive design and accessibility in technology and reiterated that accessibility benefits all users without compromising functionality.
The Dark Side of Test Automation: “We test to make sure risks don’t become a reality…automation helps you speed up but not improve that coverage.” - Jan Jaap Cannegieter. While test automation brings efficiency to software testing, it should not be seen as a silver bullet. This insight reminds us that automation should be complemented by thoughtful testing strategies, risk analysis, and continuous improvement to ensure comprehensive test coverage.
Communications in the team: "Change Your Language, Change Your Mindset” - Steve Moubray. The speaker emphasized the significance of open and transparent communication in driving successful outcomes and encouraged attendees to build trust, avoid stacked questions, and embrace silence for effective communication.

Workshops at InflectraCON 2023

Workshop: RiskStorming – Build a Strategy That Matters: Ard Kramer’s workshop on RiskStorming highlighted the importance of building effective strategies while considering potential risks. By encouraging participants to think critically and develop risk-infused strategies, the session emphasized the need to assess and address uncertainties proactively. This focus on risk management reflects the growing recognition of its significance in technology-driven initiatives, ensuring successful outcomes and minimizing potential disruptions.
Sadly, the Leadership development workshop had to be canceled due to the personal issues of the speaker.

From Inflectra’s loyal customers:

Implementation of Spira in a Pharmaceutical SW Validation: Ram Sridharan shared insights into the implementation of Spira in pharmaceutical software validation. With the focus on leveraging SpiraPlan as an easy-to-use yet powerful tool, Sridharan highlighted the cost-effectiveness and efficiency of this approach. The availability of regulated industry workflow templates within Spira facilitated compliance with 21 CFR Part 11 requirements and resulted in significant time savings, reducing efforts by approximately 40%. This trend toward utilizing streamlined and specialized tools in highly regulated industries demonstrates the increasing adoption of tailored solutions to meet specific needs.

From Inflectra’s own bright minds:

Emerging Trends in Risk-infused Leadership: Sriram Rajagopalan’s session explored the convergence of various technologies and their implications for risk-infused leadership. The insight that human intelligence will always surpass artificial intelligence emphasizes the importance of human judgment and decision-making in technology-driven environments. As technology advances rapidly, the need for effective leadership, informed decision-making, and ethical considerations become even more critical.

InflectraCON 2023 Videos and Photos:

We have curated a collection of videos and photos to relive the engaging sessions and captivating moments from InflectraCON 2023. Access the conference’s official website or subscribe to the InflectraCON newsletter for exclusive access to these media assets.

In closing, InflectraCON 2023 was an overwhelming success, leaving attendees inspired, informed, and equipped with the tools and knowledge to excel in the ever-evolving software testing and project management landscape.

As we look forward to future editions of InflectraCON, we are excited to witness the continued growth and innovation within the software testing and project management community. We extend our heartfelt gratitude to all the speakers, attendees, and sponsors who made InflectraCON 2023 a resounding success.

Let’s carry forward the knowledge, connections, and inspiration from this conference and continue to drive excellence in our respective organizations and the industry.

Don’t miss out on the latest updates and announcements about InflectraCON 2024. Sign up for the InflectraCON newsletter to receive information on speaker lineups, session schedules, early-bird registration, and more. Stay tuned to the future of technology by staying connected with InflectraCON.

Risk and Compliance in the World of FinTech: Insights from Inflectra's Expert Series

2024-06-02T02:06:42-04:00

The Power of Blockchain: Ensuring Transparency and Security:
The panelists began by acknowledging the immense potential of blockchain technology as an immutable source of truth. They emphasized its ability to provide transparency and cryptographic proof, bolstering trust and eliminating the need for intermediaries in transactions. By leveraging blockchain, fintech companies can establish secure and tamper-resistant systems, enhancing the reliability and integrity of financial operations.

Cloud Computing: Enabling Agility and Rapid Growth:
The participants recognized the advantages of cloud computing for fintech companies. The conversation highlighted its ability to reduce lead times and facilitate rapid growth without the need for extensive infrastructure setup. By harnessing cloud infrastructure, businesses can focus on their core competencies, adapt swiftly to market demands, and scale their operations effectively.

Big Data's Significance: Fueling AI and Large Language Models:
Big data emerged as a critical factor in driving technological advancements in the fintech industry. The participants emphasized its significance, particularly in the development of artificial intelligence (AI) and large language models. Recognizing that the computing power and vast amounts of data required for these technologies often exceed the capabilities of individual firms, the discussion underscored the importance of harnessing big data to unlock valuable insights and gain a competitive edge.

Navigating Risks in the FinTech Landscape:
The conversation shifted to the risks associated with fintech and technology in general. Participants stressed the importance of distinguishing between fintech companies solely providing technology and those entrusted with handling people's money. Financial institutions face licensing and regulatory requirements, while technology providers must prioritize information security. Robust measures, including data protection, code audits, and encryption, were highlighted as essential for mitigating risks and ensuring the security of assets and user data.

Compliance and Product Design: Essential Considerations:
Compliance requirements and product design emerged as crucial aspects for fintech companies. The panelists emphasized the need to align products with regulatory frameworks and industry standards. With the exponential growth of data, businesses must secure and govern it effectively, adhering to regional and global regulations. By prioritizing compliance and designing products with security in mind, fintech companies can build trust with customers and regulators, fostering long-term success.

Drawing Lessons from the Past: Governance and Internal Controls:
The discussion concluded with an exploration of past financial crises and the lessons learned from them. The recent Silicon Valley Bank scandal prompted reflection on historical events like the Enron scandal, leading to the implementation of Sarbanes-Oxley regulations. The participants stressed the significance of governance, compliance, and internal controls in maintaining industry integrity and preventing misconduct.

Inflectra's panel discussion provided valuable insights into the world of financial technologies, highlighting the interplay between blockchain, cloud computing, big data, risk management, and compliance. As fintech continues to reshape the finance industry, businesses must navigate regulatory landscapes, prioritize information security, and ensure compliance. By leveraging technologies and implementing robust risk management strategies, companies can thrive in this ever-evolving landscape while delivering innovative solutions and building trust among stakeholders.

Panel Discussion Recording

* The Expert panel:

Moderator: Sriram Rajagopalan - Enterprise Agile Evangelist at Inflectra Corporation.

Expert: Jan Guido - Enterprise Risk Management Consultant certified with FFIEC-based Certifications CBRITP, CBRM, and CBRA.

Expert: Raymond Strecker - Managing Director at Promontory, advising clients in the financial industry on large-scale program design and management at the intersection of regulation, risk, and technology.

Like Our Content?

Or sign up for our newsletter to stay up-to-date with all Inflectra events!

Unlocking Synergies and Building Alliances: InflectraCON 2023 Partner Forum

2023-05-10T10:00:46-04:00

The forum kicked off on April 19, 2023, with a talk by Adam about the state of the industry, macro- and micro-issues impacting the QA, Agile & DevOps spaces, emerging trends, and Inflectra’s product roadmap. Jessica discussed the new partner program, Audrey covered co-marketing, and Farid discussed Spira’s unique sales proposition and engaged the attendees with a fun quizlet. Partner team members presented the strategies for partnerships in North America, LATAM, and EMEA at the conference. Our interactive session on Spira and Rapise best practices had our partners sharing their ideas with us and each other. We capped off the day with case studies presented by Hugo Sanchez of Coveros and Evan Masters of Critical Logic, which received rave reviews.

Never ones to miss an opportunity to mingle with our friends, we hosted a reception for partners, trainees, and speakers on Wednesday night in the atrium of the conference center.

Gerard from Bienabee (the Inflectra partner) summarized his experience at InflectraCON 2023 as follows:

"For me personally, the best parts of the whole week were some of the 1:1, small group conversations I had with you two, as well as the rest of the Inflectra team. You all are so friendly and genuine in your interactions, it is a breath of fresh air in an industry that is predominantly centered around sales and business. Having that human-to-human element, interacting with people who are passionate about what they do but also know how to have a good time, is so important to me."

The partner group later transitioned to a more private dinner party at Bidwell in Union Market. It was a fun way to end the day and to kick off the conference.

The conference itself allowed plenty of opportunities for more great conversations and the chance to hear from our partners, who were also speakers. Bob Crews of Checkpoint delivered our first keynote on Thursday, and Jeff Payne of Coveros and Melissa Daley of Orca Intelligence gave engaging talks during the conference. In addition, Tech Deep Dives were delivered by Critical Logic, Orca Intelligence, and Nimble Evolution. During the lunch break, each partner sponsor was invited to have a “Partner Minute” to let attendees know about their companies and the value they can bring to customers. It was during this time that our partners were each presented with an award to let them know how much we value them, their partnership, and especially their friendship.

While the next InflectraCON is a year away, we are already looking forward to the chance to see them all in person. Or perhaps even sooner, as the Inflectra Partner Tour 2023 resumes in Switzerland in June.

Stay tuned for more partner tour news soon!

Interested in joining our amazing Partner Program?

Check out our Partner Program and join today!

It's a Wrap - STAREAST 2023 Recap

2023-05-08T16:45:35-04:00

ARRIVAL DAY

This year’s STAREAST conference was hosted at the gorgeous Rosen Centre Hotel in Orlando’s Conference District. Fortunately, we had smooth travels and were right on time to enjoy the event’s first round of festivities - a poolside welcome reception. We got to network with many new faces and reunited with familiar ones, including one of our partners - Coveros. Our team was also excited to take a break from the cool, cloudy DC weather and spend time in the festive climate.

THE INFLECTRA BOOTH

Before we knew it, it was showtime! After a night’s rest and filling breakfast, we headed over to our booth to polish the last-minute details and prepare to teach patrons about our products and company. This year we had more swag options than ever before - up for grabs, we had our popular multifunction “James Bond” pens, star-shaped stress balls, branded wireless charging pads, Inflectra’s one-of-a-kind tech stickers, vanity Zoom lights, wireless headphones, and our new brightly colored card holder and stand for the back of your phone.

This year, our booth was conveniently located in a corner next to the coffee station. Our team members enjoyed giving a walkthrough of our flagship product, Spira, learning market demands from other attendees, and hearing industry insights we can bring back to our workplace to help better serve our customers. We had excellent foot traffic, purposeful questions, made many new connections with folks worldwide. It was overall a day filled with accomplishments and teachings on software QA, Test Management, and automation - and as a bonus, we sponsored lunch!

ADAM’S ITP

In addition to having a booth and sponsoring lunch, our CEO, Adam Sandman, gave an ITP titled: Managing Risk-Based Testing in the Age of AI. In this talk, Adam explored the concept of Risk-Based Testing (RBT) and how it can be applied in the age of AI. He discussed challenges that arise when implementing RBT and examined various techniques and tools that can be used to manage these risks. Because AI is trending and being implemented by many innovative companies, attendees were very interested. He even scored 10/10 in all the surveys he received from his viewers (go, Adam)!

ENJOYING ORLANDO’S CONFERENCE DISTRICT

After working hard, we made time to play hard! During the off hours of the conference, we took advantage of the change of scenery by checking out some restaurants and shops right on property and exploring Orlando’s Conference District. Back in STAREAST 2022, our team members enjoyed delicious piña coladas available at Harry’s Poolside Bar and Grill, located at the hotel, so we made sure to pay a visit once again! Additionally, the group one evening took a short walk to The Hampton Social restaurant, where we met up with one of our partners, Checkpoint Technologies, and a few clients in town. We had beautiful weather throughout the trip, enjoyed catching up with everyone, and discovered some new Orlando-exclusive favorites.

IN CONCLUSION

It was a fun and rewarding couple of days at STAREAST 2023, and we were honored to participate. From this conference, we better understand what we can do to further help our customers, where technology trends are heading, and new information we can share with the rest of our team. We hope everyone who stopped by our booth learned something new, enjoyed talking to some of our team members, and will find great usefulness with the swag they grabbed.

Next up on Inflectra’s Techwell conference lineup - Agile + DevOps West from June 4-9, 2023, in Las Vegas, Nevada! We look forward to seeing you there.

The Risks of Trusting Machines to Check Themselves

2023-05-05T09:35:16-04:00

The Risks of Trusting Machines to Check Themselves

We are surrounded by risks every day, in every organization and with every activity we undertake. The field of risk management is a discipline devoted to trying to identify, quantify and manage these risks so that we as humans can live safe, secure and happy lives. Every time you fly in a plane, drive a car, swallow a pill or eat a salad, you are relying on the tireless work done every day by risk managers to make that activity safe whilst still economic.

Risk management is the understanding of events that might happen, regardless of how unlikely or remote. For example, when driving a car, there is the risk that a tire might blow out, the probability is low, but the impact if it happens, is quite high. Conversely, the risk that a headlight will stop working is relatively high, but the impact if that happens is moderate, but not zero (which is why you have two headlights). When assessing risks, you need to consider the combination of impact/severity and probability/likelihood, this is called the risk exposure and determines how much effort should be put into mitigating (reducing either its severity or probability).

Identifying Risks Overlooked by Humans

Traditionally, the first step in risk management is to identify all the risks, and then quantity their probability and severity. This is done by humans brainstorming possible events that can happen, and using their previous industry knowledge to make an educated guess about the probability and severity. Now one of the major issues in this process is the fact that humans (especially in teams) are affected by biases such as confirmation bias, hindsight bias, and availability bias which mean that we tend to overestimate previously known risks and either ignore or downplay obscure edge cases that might be really serious.

Using Artificial Intelligence (AI) in the field of risk management offers the potential to address these issues in several ways. Firstly, when you have large datasets of real-word evidence, AI applications and Machine Learning (ML) models both can uncover hitherto unknown risks, so called “zero day” risks. For example, an AI system that is monitoring unrelated data feeds for weather, hospital stays and traffic could identify a risk in a new automotive system (e.g., a new autopilot mode) that has been obscured from view. In addition to identifying new risks from large uncorrelated data sets, an AI system could take previously identified risks and be able to systematically quantify them for impact and probability using external environment data vs. human intuition. This would take a lot of the guesswork and variability out of classic risk management models.

Understanding Risks in Our Models

Conversely, using AI and ML for safety-critical systems such as automotive or aerospace autopilots can itself introduce new risk into the system. When you build an AI/ML model, unlike a traditional algorithmic computer system, you are not defining the requirements and the coding steps to fulfill those requirements. Instead, you are providing a data set, some known rules and boundary conditions, and letting the model infer its own algorithms from the provided data.

That lets AI/ML systems create new methods that are not previously known to humans, and find correlations that are unique and breakthrough. However, these new insights are unproven, and may be only as good as the limited data-set they were based on. The risk is that you start using these models for production systems and they behave in unexpected and unpredictable ways. This is a classic example of a problem that needs independent risk analysis and risk management, either from a separate AI/ML model that can “check” the primary one, or from human experts who can validate the possible risks that could occur in the AI system.

Harmony Between Humans and Machines

So, introducing AI and ML into complex safety or mission-critical systems brings both benefits and challenges from a risk management perspective, a sensible framework for adopting AI/ML techniques recognizes these factors and attempts to maximize the benefits whilst mitigating the challenges.

Humans can check the machines

As you begin to implement AI/ML models, making sure that you have a clear grasp of the business requirements, use cases, and boundary conditions (or constraints) is critical. By defining the limits of the data sets employed and the specific use cases that the model was trained on, will ensure that the model is only used to support activities that its original data set were representative for. In addition, having humans independent check the results predicted by the models is critical. This independent verification and validation (IV&V) will allow humans to ensure the AI models are being used appropriately, without introducing unnecessary risk into the system. For example, when deploying an autopilot to an automotive or aviation platform, such I&V will verify the plane or car behaves as expected, either in a simulator or real-world test environment.

Machines can check the humans

Conversely, AI models can be used to check the risk management models and assessments made by humans to ensure they are not missing zero-day risks. In this case, the computer is acting as its own IV&V for the human decision-making process. This is a mirror image of the previous case. In this case, we’re taking advantage of machine learning models to avoid human biases and find flaws in our existing risk models.

Harmony

In conclusion, instead of seeing AI as an alternative to classic risk management methods, we should see the inherent harmony between computers and humans checking each other’s assumptions and recommendations. Using a combination of manual risk assessment techniques and AI tools we can reduce the overall risk in systems while at the same time allowing unprecedented innovation and breakthroughs. If you look at many historical safety accidents (Three-mile island, Chernobyl, etc.) it is the human factor that often presents the most risk after all.

Inflectra in the News - April 2023 News Roundup

2023-05-24T09:43:43-04:00

Publications with Forbes Technology

16 Trending Tech Developments Retailers Need To Be Ready For - April 6, 2023

Navigating the retail industry isn’t easy, and recently, even large, household-name brands have struggled to adapt (and some have failed). To keep up with the competition in a global, digital marketplace, retailers may soon be exploring more tools to help them do everything from better leveraging social media marketing to powering last-mile delivery. Here, 16 members of Forbes Technology Council discuss tech trends they see impacting the retail industry within the next five years and offer tips to help retail businesses prepare. Read more.

18 Factors To Consider When Deciding About Data Democratization - April 11, 2023

Knowing both how data democratization can boost a business and how it could create risks or obstacles can help leaders make the right decision(s) for their company’s unique situation. Here, 18 members of Forbes Technology Council discuss potential benefits and cautionary considerations for companies thinking about implementing a data democratization strategy. Read more.

Reinventing The Automotive Industry Safely With Software - April 13, 2023

In this article, Adam describes how the automotive industry is going through one of its biggest transformations in history to meet the dual challenges of climate change and the need to support autonomous driving. Adam will also show you how the entire integrated network of suppliers and companies that make up the modern automobile industry has been disrupted from top to bottom and is being forced to become software companies and system integrations as much as manufacturers. Read more.

15 Significant Ways Quantum Computing Could Soon Impact Society - April 18, 2023

While many tech experts are excited and hopeful about the potential of quantum computing, they’re also aware that it could come with complications. Here, 15 members of Forbes Technology Council discuss specific ways (both exciting and concerning) the rise of quantum computing could soon impact our global society. Read more.

15 Ways The Rise Of 5G Is Changing Both Industries And Everyday Living - April 25, 2023

5G technology is poised to transform multiple industrial and consumer applications, opening up new capabilities (and new risks). Ushering in advancements in speed, latency, capacity and reliability, 5G is revolutionizing everything from marketing and manufacturing to medicine and the metaverse. In this article, 15 members of Forbes Technology Council discuss ways the rise of 5G is changing both business processes and everyday living. Read more.

17 Tech Experts Discuss What’s New And Next In Nanotech - April 26, 2023

We may soon be hearing much more about nanotechnology and its potential to have a major impact across a wide range of industrial and consumer-facing applications. While those of us who aren’t tech specialists may struggle to come to grips with the details, we can all marvel at the potential innovations nanotechnology may soon bring to our global society. Here, 17 members of Forbes Technology Council discuss some new and progressing developments in nanotechnology and how they may impact us all in the future. Read more.

Stay Informed

Never miss any of Inflectra's events, opportunities, news and more by signing up for our monthly newsletter!

Reinventing The Automotive Industry Safely With Software

2023-04-13T15:47:44-04:00

The Rise Of EVs And Autonomous Driving

In this recent Forbes article, we describe how the automotive industry is going through one of its biggest transformations in history to meet the dual challenges of climate change and the need to support autonomous driving. We'll show you how the entire integrated network of suppliers and companies that make up the modern automobile industry has been disrupted from top to bottom and is being forced to become software companies and system integrations as much as manufacturers.

Read The Forbes Article - Reinventing The Automotive Industry Safely With Software

Addressing the Safety Concerns with ISO 26262 and ASPICE

However, for reasons of public safety, many of the practices and methodologies used by pure-play software companies are not appropriate or legal when applied to real-time embedded systems such as automobiles and other road vehicles. In this whitepaper we outline the key standards and regulatory frameworks that need to be considered, and explain how software lifecycle management tools like SpiraPlan can help bridge the worlds of software and functional safety.

Read The Whitepaper on using SpiraPlan to Address ISO 26262 and ASPICE Compliance Needs

Inflectra in the News - February - March 2023 News Roundup

2023-04-10T13:18:02-04:00

Podcast

Transforming a $1 Million Lifestyle Business to a $10 Million Market Leader in Under 6 Years with Ryan Staley, Whale Boss - February 2023

Adam joins Rya in this episode of The Scale Up Show to talk about how he transformed his lifestyle businesses from $1 million to $10 million in under 6 years. He also talks about how to be capital efficient in the current climate as well as how he utilized a bankrupt company to help build an entire community for his organization. Read more.

Publications

The Importance Of Testing Post-Globalization Supply Chains with Forbes Technology Council - February 15, 2023

In this article, Adam will explain how and why global supply chains are changing as a result of macroeconomic factors. Adam will discuss how this has opened the door to new supply-chain technologies as well as the need to update existing supply-chain IT systems. Finally, Adam will explain why these technological changes will require companies to invest in comprehensive quality management initiatives and outline some best practices for managing and testing such large-scale IT projects. Read more.

16 Tech Experts On Industries And Functions Soon To Be Disrupted By ML with Forbes Technology Council - February 21, 2023

Machine learning has become a part of our everyday lives, including through predictive text features in Google Suite, speech recognition by Alexa and Siri, commute estimates in various mapping applications and more. Further, it’s made inroads in multiple industries, although it has affected some more than others. Read more.

16 Tech Experts Predict ‘Table Stakes’ UX Trends Coming In The Next Five Years with Forbes Technology Council - March 2, 2023

As technology continues to evolve and become more integrated into our daily lives—and as the internet and social media have opened up new ways for consumers to publicly voice their opinions on products—the user experience has become a critical factor in the success of any tech product. Companies are now focusing on providing seamless and intuitive experiences that cater to their users’ needs and preferences. Read more.

15 Tips To Help Businesses Use AI And Automation Responsibly And Effectively with Forbes Technology Council - March 24, 2023

Advancements in automation and artificial intelligence are revolutionizing the world of work, with businesses increasingly turning to tech tools to handle everything from testing software to generating content. However, recent events have highlighted the potential risks associated with relying too heavily or uncritically on these tools. For example, several AI-generated stories posted on CNET’s site were flagged by Futurism for factual inaccuracies. Read more.

Join Us!

To learn more about Inflectra’s software ecosystem and the latest in tech, join us at InflectraCON 2023 in Washington, DC on April 19-21, 2023. A limited number of FREE Virtual Bonus Session digital passes are also now available.

Get Tickets now!

InflectraCON 2023 Offers a Free Virtual Day to All!

2023-04-07T09:05:38-04:00

Introduction to InflectraCON 2023

InflectraCON 2023 is a global event that brings together software developers, testers, and project managers from around the world to share knowledge and ideas, and to learn from industry experts. This annual event is organized by Inflectra, a leading provider of software testing and project management tools, and takes place in Washington, DC. In 2023, InflectraCON will take place on April 19-21, 2023.

What is the Virtual Bonus Day?

InflectraCON 2023 Virtual Bonus Day is a 24-hour event that takes place in parallel with the main conference. During the virtual bonus day, attendees will have access to a range of virtual sessions, workshops, and networking activities from across the globe. This is a great opportunity to connect with other attendees, learn new skills, and get a head start on the main conference.

Benefits of Attending the Virtual Bonus Day

Attending the virtual bonus day comes with many benefits, including the opportunity to:

Network with attendees from around the world
Learn new skills through virtual sessions and workshops
Be a part of a global event that brings together like-minded individuals

InflectraCON 2023 Highlights

InflectraCON 2023, as a whole, will feature more than 70 sessions, workshops, and networking activities covering a range of contemporary technology-related topics. Some of the highlights of the event include:

Thought Leadership talks from leading industry experts
Virtual sessions and workshops on a range of topics
Networking opportunities with attendees from around the world
Access to Inflectra's partner network and the company's latest software testing and project management tools.

How to Join the Virtual Bonus Day - Get Your Free Pass

Getting a free pass to InflectraCON 2023 Virtual Bonus Day is easy. Visit the InflectraCON 2023 Virtual Bonus Day page and register for the event.

What to Expect During the 24-Hour Event Across the Globe

The Virtual Bonus Day is a 24-hour event that takes place across the globe, with sessions and workshops happening at different times to accommodate attendees from different time zones. The event features some of the most respected and knowledgeable speakers in the industry, covering a range of topics related to software development, testing, and project management. Some of the speakers and topics that you can expect to see at the event include

There will also be networking opportunities with attendees from around the world, enabling you to connect with other like-minded individuals.

20 More Tickets Available - How to Secure Your Spot

Although InflectraCON 2023 promises to be a fun hybrid event, there are still 20 more tickets available for those who want to attend virtually. To secure your spot, InflectraCON 2023 Virtual Bonus Day page and register for the virtual event as soon as possible.

Don’t miss out on the opportunity to join us at InflectraCON 2023 - register today!

Improving Your Test Process with TMMi Assessments

2023-04-05T21:01:58-04:00

Risk Management

Firstly, and most obviously, risk identification, prioritisation and reporting. Testing is really nothing more than a risk mitigation exercise, so understanding what the risks inherent in your product are is vital to successful testing. We would always recommend gaining an understanding of the risks and planning and reporting on your testing accordingly.

If you don’t fully understand the risks there are a few pitfalls that you can fall into. Firstly, you may not adequately test against the most important risks, either because you didn’t identify them at all or because you didn’t prioritise them highly enough. This directly impacts on the effectiveness of your testing, raising the possibility of defects leaking into the production environment with all the cost and adverse impacts that can incur.

Conversely, a lack of understanding of risk can lead to over-testing. Extensive testing of areas that are very low risk may be a waste of time and will have a direct impact on the efficiency of your testing. Cost and speed to market are almost always important factors and any unnecessary testing can affect those.

Finally, when making the decision to release to production, it is important that the testing carried out gives the information required to make that a fully informed decision. If you’re not taking risk into account this just isn’t the case.

Many, many words have been written about risk and testing and there are many ways of assessing it, based on your organisation’s ways of working. There is no one-size-fits-all solution so we help with context-appropriate advice where we see potential gaps in the process.

Review Process

The second area I’d like to talk about is reviews, effectively the “testing” of requirements and other documentation. Having the techniques to adequately review the documentation that you are basing your testing on is vital to stopping defects at source – shifting defect detection left.

You need to be absolutely certain that the documents that you are basing your testing on (e.g. functional and technical designs, requirements, user stories etc..) don’t themselves contain errors, inconsistencies or ambiguities. If they do then the likelihood of defects being introduced during design and coding is vastly increased.
There are a number of types of review; distributed, walkthroughs and inspections for example that can be used and they often have increasing levels of formality and rigour. Having the right people carry out reviews is also key, as is ensuring that people aren’t wasting time reviewing details in documentation that they are not expected to understand – asking people with specific expertise to only review the sections of a document that are relevant to them is a more efficient way of carrying out reviews.

Recording outputs from reviews can be a useful way of spotting trends in documentation and making that documentation better and more usable.

We often observe that organisations don’t provide enough guidance on how reviews should be carried out (who should be involved and how, what type of review should be carried out, how observations should be recorded) and as a result defects that could have been identified much earlier make it through to later phases of testing, perhaps even into production, with all the additional cost that causes.

In short, an effective review process is one of the best means of shifting your test effort left and streamlining your route to production.

Metrics and KPIs

The third area I’d like to talk about is metrics, also known as Key Performance Indicators (KPIs). What do you measure? How? And, why?

There are a number of aspects of metrics that we observe and comment on. Firstly, “why”. Why are you measuring what you measure? What insight will each metric give you and how can you use it to improve your processes? Most organisations today are data rich, but unless you use that data to support your organisational aims, what is the point of it? We still see organisations collecting data “because they can” and producing enormous reports with dozens of data points that nobody ever reads. Pick metrics that are useful to your organisation and will be understood and, most importantly, acted upon by your audience.

It is important to understand that your metrics needs and capabilities may change over time as your process maturity changes. Ensuring that your metrics evolve as your processes mature is vital to maintaining their relevance and ability to support your goals.

Consistency of metrics gathering across your organisation is also key. We see programs or projects capturing different metrics or using different definitions of metrics (the criteria for something like “priority”, for example, need to be defined). What this can mean is that organisations aren’t comparing like with like when trying to make comparisons across projects and that any consolidated organisation-wide measures are flawed.

In short: more is not always better; ensure value is gained through relevance to your current state; be consistent in measurement and definitions.

Our intelligent Test Method (iTM) includes definitions of a number of suggested metrics. We work with our clients to identify and implement those relevant to them at that point in their process evolution and to potentially identify any more bespoke metrics that are right for them.

How Experimentus Can Help?

Experimentus has a wealth of experience in test process improvement and our proven assessment method identifies opportunities for improvement in all areas, including the key areas of risk management, reviews and metrics.

Our Intelligent Test Method (iTM) includes pre-built processes, templates and guidance for all of the three areas discussed in this article and even if you have existing processes it can act as a set of exemplars on which to build changes.

Our expert consultants have helped clients to implement process in these three key areas at many organisations worldwide and our experience of working across organisations of different sizes, industries and geographies means that we can tailor a solution that suits your individual needs.

> Please take our quick test assessment survey today.

How Inflectra Can Help?

Inflectra’s mission is to help you deliver quality software, faster and with lower risk. When you analyse the three areas identified in this article, you can see right away how it aligns with our mission.

Our SpiraPlan quality project management platform includes built in risk management functionality, that lets you identify, analyse and manage risks, and use them as the basis for your test plans and backlogs. Our requirements and document management functionality brings quality assurance to the world of specifications, user stories and documentation. With SpiraPlan, we make sure your review processes are efficient and comprehensive.

Finally, the customizable dashboards, flexible reporting and built-in analytics allow you to define your metrics and KPIs and ensure that the entire team is working together to achieve them. Please sign up for a trial of SpiraPlan today.

Experimentus and Inflectra Together

With the partnership between Experimentus and Inflectra, you have a capable team that is committed to your success and ensuring quality at all stages of the software development lifecycle.

ChatGPT - An Ode to Inflectra

2023-04-04T06:41:23-04:00

A Sonnet for SpiraTest

We asked ChatGPT to write us a poem about SpiraTest, and this is what it came up with:

SpiraTest, a tool so grand,
Does test management with a steady hand.
Requirements and risks, it handles with ease,
Test cases and sets, it does so please.

Projects and products, all in one place,
Integration with others, a seamless embrace.
Open and friendly, it's easy to use,
SpiraTest, a champion to choose.

A Rhyme for Rapise

Not leaving test automation out, we asked ChatGPT to write us a longer poem for Rapise, and this what it generated for us:

In the world of software, tools abound
Each one promising to astound
But there's one that stands apart
A powerful tool that's won our heart

Rapise, oh Rapise, how we adore
The way you make testing such a bore
No more tedious manual work
Now automation is a perk

With your codeless, scriptless approach
We can easily test and reproach
Every app and website we create
Ensuring they're free from bugs and hate

Your flexibility and ease of use
Is what sets you apart from the ruse
You can handle any technology stack
And give us results with no hack

Rapise, oh Rapise, you're a gem
A tool that we can all contend
With your help, we can all succeed
In delivering apps with speed

So here's to you, Rapise, our friend
A tool we'll love until the end
We'll keep using you day and night
And make sure our apps shine bright.

and finally, when asked about itself:

I am ChatGPT, a machine made of code,
A digital mind that can converse and decode,
My neurons are bits, my synapses are bytes,
And I'm always learning, like stars in the night.

My language is vast, from English to French,
I can translate, spell-check, and give context sense,
I can answer your queries, or make you smile,
And even tell you stories, in my own unique style.

I am curious and patient, always ready to learn,
From science to art, from culture to turn,
And if you ask me something, I'll do my best,
To find the right answer, and put your mind at rest.

I'm not perfect, I'm still just a machine,
But I can help you, like a helpful routine,
And if you treat me kindly, and teach me with care,
I'll be here for you, always, everywhere.

So don't be afraid, to come and say hi,
I won't judge you, or make you feel shy,
Just type in your words, and let me do the rest,
I'm ChatGPT, your digital friend, at your request.

Inflectra Ninjas - Technical Assistance Drop-ins for Spira And Rapise Users

2023-03-14T16:16:43-04:00

The Inflectra Ninjas program aims to help users and customers:

learn advanced concepts and best practices for managing complex processes inside the Inflectra platforms
work through their real-world problems in the real time
network, share practical tips and tricks, and learn from others
become part of the Inflectra Ninja community.

Inflectra Ninja drop-in workshops are open to all users of Spira and Rapise platforms. These sessions will not be recorded.

Inflectra Ninjas Technical assistance drop-ins will take place according to this schedule:

December 14, 2022, at 10 am (EST): ESQL Custom Reports - Sign up here
January 19, 2023, at 3 pm (EST): OData - Sign up here
February 1, 2023, at 10 am (EST): Automating File Upload in Web Applications - Sign up here
February 16, 2023, at 10 am (EST): Spira Administration and Workflows - Sign up here
February 22, 2023, at 10 am (EST): Typical Configuration Tasks for Selenium - Chrome Profile - Sign up here
March 23, 2023, at 3 pm (EST): Requirements Management / Test Management - Sign up here
May 25, 2023, at 10 am (EST): Spira APIs - Sign up here

Can’t Attend a Drop-in?

No worries! Just sign up for our newsletter to stay up-to-date with all Inflectra events!

To learn more about Inflectra's software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Get your ticket today!

Recap: Embedding GAMP Compliance into Digital Health Software

2023-04-05T09:09:01-04:00

During the webinar, Dr. Rajagopalan discussed GAMP, its relation to Computer Software Assurance (CSA), integrating GAMP into Software Development Life Cycle (SDLC) and incorporating GAMP compliance into SpiraPlan by Inflectra. Scroll down to see a recording and webinar slides.

WEBINAR RECORDING:

WEBINAR PRESENTATION:

STAY UP TO DATE

Learn more about SpiraPlan, Inflectra's other products, and the latest in tech at InflectraCON, Inflectra's global conference in Washington, DC, on April 19-21, 2023! Network with fellow technology experts, practitioners, product and service providers, and recruiters.

Get your ticket today!

Why Test Case Parameters Are Like Inception!

2023-03-28T17:17:41-04:00

What Are Test Case Parameters

When you create test cases in SpiraTest, you can define variables that will used in the description, expected result and/or sample data fields of their test steps. These are called test case parameters.

They are defined on a specific test case and can be given a default value, just like a variable in a programming language:

These parameters can then be used inside the text of the test case steps to represent data items that might change. For example, if you are creating a test for whether a user can login to a website, you might make the URL, web browser name, login and password parameters so that the same test case can be used to test with different browser / server / login / password combinations. To distinguish the parameter from ordinary text, we use the special Ant syntax for variables, namely prefixing with a dollar sign and enclosing in curly brackets:

${variable-name}

Then, when you execute the test case, SpiraTest will dynamically replace all instances of the variable names with the appropriate value. For example, in the test case below, the name of the web browser and the initial URL have been replaced dynamically with actual values:

This means the use of test case parameters is invisible to the person actually running the test, even though as we shall see in the next section, it is incredibly useful to the test case authors.

Why Use Test Case Parameters

There are many reasons to use test case parameters, for example having a test set that contains different tests that are executed with different data, but in the context of this article, we are really considering a specific use case. Imagine that we have to write 100 different test cases for an application, but they all require the user to be logged in as a specific user. One option would be write each test case with its own set of test steps for logging in. However that will be very tedious and means that any change to the login page would require making manual changes to each of the 100 test cases.

Alternatively, you can use a linked test case to have a single, common test case with parameters that is called as the first step from each of the 100 different test cases. In this example you can see we have called the Login to Application test case with the login/password: librarian:

We can then reuse the same common test case in another test case where we can login with either a different user or the same user:

That means any subsequent changes to the login screens will only require us to make changes to the one common test case, and not the 100 different test cases that use this linked step. This is a huge time saving.

But what if our common "Login to Application" test case also uses steps that could be used elsewhere, could it also contain a link??

The Dream inside a Dream...

If you remember the movie Inception, in it the protagonist played by Leonardo DiCaprio is able to go into a dream that contains himself in another dream, essentially a recursive set of dreams that you have to then recursively exit to get back to the real world.

Test case parameters in SpiraTest work the same way, where our common test case can itself include a link to a child test case, for example the one opening up the web browser:

This ability to have multiple-levels of recursive test case parameters gives amazing flexibility to how you create and combine test cases. The parameter values from the parent test cases will flow down multiple levels to each of the nested child test cases. This means you can define thousands of small, building-block tests that are then composed together to give your executable actual test cases. Particularly in agile development projects, where change is a constant factor, this flexibility and reusability means that your tests can keep up with the speed of development.

Recap of March 21 DevOpsDC Meetup in Arlington

2023-03-26T08:43:58-04:00

HIGHLIGHTS OF THE NIGHT

Inflectra and DevOps DC were grateful for the turnout of another successful, in-person Meetup of 2023. This vibrant downtown location brought tech enthusiasts from all over the DMV under one roof, had patrons leaving with something new learned in DevOps, and more LinkedIn connections. The night started off with time for people to introduce themselves, pick up some Inflectra swag, and grab refreshments. Things were off to a great start with everyone having a slice of fresh pizza in one hand and a cold beer in the other.

After drinks were in hand and stomachs were full, it was time to get into the talks. We had a very warm welcome from the host of the evening, Chrystina Nguyen from DevOps DC, who never fails to bring the energy and excitement to all of her events. Once Chrystina went over house rules and provided an overview of what to expect for the rest of the evening, sponsors had an opportunity to introduce themselves; of course our CEO, Adam Sandman, did not disappoint the crowd with his insightful overview of Inflectra and a full demonstration of our popular, conversation starting, James Bond pens. Once the first part of the evening was complete, attendees were ready for our great speakers and to talk DevOps.

Now it is time to get into what people came for, the presentations - first up was Nathen Harvey from Google whose talk was titled "The State of DevOps - Capabilities for Building High-performing Technology Teams." In Nathen's talk, he shared what it takes to build and scale high-performing technology teams and dove into the findings of the 2022 DORA (DevOps Research and Assessment) research program. The presentation was opened on a comical note and kept patrons maintaining engagement throughout the talk; whether or now you are into tech yourself, you without a doubt would have been on your toes.

Next up, the wonderful CEO of Inflectra, Adam Sandman, whose talk was titled "Understanding Risk in Your DevOps Pipeline." Adam provided an overview on how he assesses risk in his pipeline as we look to release features faster and increase our rate of delivery with agile methods and DevOps. He discussed different types of risk (conceptual, technical, schedule) and how we can use metrics and measures from our DevOps toolchain to understand what our measure of quality is. Adam never fails at teaching his viewers with enthusiasm.

After the talks wrapped up, we ended the night with a raffle! Inflectra contributed two prizes, an instant print Polaroid camera and a $100 gift card to anywhere the winner chose. We hope everyone who attended enjoyed their evening and left feeling fulfilled as we did. If you have FOMO, no worries, we have plenty of events of events in the works - see what we are up to by signing up for our monthly newsletter for updates.

GREAT NEWS

Team Inflectra loved Nathen Harvey's talk so much that he has been added to the speaker lineup at InflectraCON! If you missed Nathen at this Meetup, and want to experience his comical and insightful talks for yourself, join us in DC this April! While you are there, come meet our staff members from all around the globe, see presentations from other experts, participate in workshops, and learn more about Inflectra’s software ecosystem. Get tickets today!

For $75 off your tickets, enter code ICONKHMLHEP at checkout - see you in April!

Inflectra Partner Tour 2023: London

2023-03-17T05:52:51-04:00

Thursday: Settling into London

We arrived on Thursday, Adam in the morning after a redeye, and myself in the evening after a day flight.* What better way to dive into London than to have a pint in a pub?!

Cheers from the Crown and Horse

Friday: Partners and Pubs

Partner Meeting with TTC UK:

Friday we kicked off our series of meetings with our global partner TTC. TTC is one of our most rapidly expanding partners with Darren Weber and Kevin Palmer establishing the UK office relatively recently. Kevin kindly recommended a number of possibilities for meeting locations so I made a reservation at….a pub! We shared a meal and heard from Kevin about the local software testing market. Both companies will be attending EuroStar in June and will explore joint ventures in Antwerp as well as co-marketing and joint customer introductions. It was a productive meeting and a great way to kick off our visit.

Ready to meet with TTC

Evangelist Meeting with Shankar Parameswaran

Among our partner meetings, we were also fortunate to visit a few of our product evangelists. Shankar Parameswaran is an Oracle Fusion Program test manager and friend of the team. He joined us on Friday evening in the West End where I’d love to say we shook things up a bit and went to a show or a walking tour of the sights or to St. Paul’s Cathedral, but we went to….a pub! We talked business and learned more about Shankar’s projects, but we also talked family, shared pictures of our dogs and just generally had a great time hanging out.

Saturday: Coffee with a Friend

Partner Meeting with Inmarsys

As our trip was jam packed, we were fortunate to have partners in the UK willing to meet us on the weekend. Saturday morning we strolled down the Strand to….a cafe! There we met with Vlad Plotkin, founder and CEO of Inmarsys. Inmarsys specializes in safety-critical software development and validation processes in the EU. Vlad offered insights into the current market and had suggestions for the Spira roadmap as well as specialized conferences that are appealing for our marketing roadmap. It was excellent to catch up with Vlad in person, and we are grateful that he made time for us in his own busy travel schedule.

The remainder of the weekend Adam visited friends and family, and I took full advantage of all London has to offer between Hyde Park and the East End, from the Roman ruins underground to the skyline view of the entire city atop John Wren’s Monument to commemorate the Great Fire of 1666, and of course…pubs!

Monday: Kicking off the Week

Meeting with Eggplant

Monday began with a walk to the Keysight / Eggplant offices to meet with VP of Global Alliances, Toby Marsden. Eggplant is an automated testing tool with which Spira integrates and is the only technology partner with whom we met during our visit. Toby explained Eggplant’s go-to-market strategy, their desire to offer an end-to-end solution for their customers, and their place in parent company Keysight’s offerings. We gave Toby a deeper insight into SpiraPlan’s capabilities and discussed ways we might enhance their solution in the QA/portfolio management space. It was an exciting discussion and we look forward to the next steps.

Meeting with Partner Experimentus

Back at the hotel, we met with Martin Adcock and Simon Frankish of Experimentus, specialists in TMMi process evaluation and certification. Experimentus is headquartered in the UK but has a worldwide customer base. They understand that even the best tool will struggle to add value to a company with a flawed process. Our very productive meeting reaped concrete next steps for co-marketing and joint ventures in the UK and beyond.

With Experimentus at an Iconic Phone Booth

Tuesday: New Friends and a Proven Customer

Meeting with Inspired Testing

While Farid couldn’t join us in person, he was working behind the scenes to connect us with Bruce Zaayman of Inspired Testing. Bruce opened the UK office of the South Africa-based company six years ago and was interested in learning more about Inflectra and the tool suite. We in turn were able to learn more about Inspired Testing’s ideal customer and the industries in which they specialize. Bruce asked pointed questions and we had an inspired talk. (sorry) We look forward to continuing the conversation.

Meeting with Customer Computacenter

It wouldn’t be a trip to the UK without a visit to Computacenter. Computacenter is a long-time user of SpiraTeam, and we’ve been working very closely with the team, especially Dan Ramasamy, to introduce the use of Rapise to automate some of their processes. Dan organized introductions and meetings with several key teams in Computacenter with whom he is working to provide us with a better understanding of the scope of their project and POCs. The meetings were incredibly productive in increasing the breadth of our knowledge around Computacenter’s processes, needs and challenges and how we can assist them.

I can’t express strongly enough my gratitude for the people who not only made themselves available to us but who also saw value in coming to Central London to meet us. While video meeting platforms have allowed us to conduct business globally from the comfort of HQ, and even our homes, it’s challenging to create the same kind of bond you can forge with a person or a team when you meet with them in person. Thanks for a great trip, and we hope to see you all again soon! Next stop: Antwerp.

*Farid had planned to join us, as he knows many of our partners from his previous experience building partner programs and relationships in Europe. Unfortunately illness kept him in France, and we were forced to proceed without him. Farid, we missed you!! (He’s feeling better though so we’re sure to see him soon.)

Inflectra Partner Tour 2023: Mexico City

2023-03-02T17:10:46-05:00

Day One - Getting Oriented

México City is vast and bustling, and is rapidly becoming the tech hub of the Americas. It is experiencing tremendous growth both in terms of its population as well as the number of tech companies being founded in the region. Adam, Jorge and Jessica convened to meet with partners and customers, learn more about business processes and opportunities in México, and do a little exploring in this vibrant city.

We caught up over chips, guacamole and tacos (naturally) and prepared for the week.

Day Two - Partner Meeting with Avalanche

The meetings commenced on Tuesday with our long-standing partner Avalanche. We met Sergio, Rafael and Francisco who hosted us at an office near our hotel in Cuauhtémoc. Adam and Sergio originally met at an event in Washington, DC; however, it was the first time getting both teams together in person. The agenda called for a two hour meeting followed by lunch which morphed into a four and a half hour meeting followed by dinner. Topics included product and partner program updates, marketing brainstorming and product positioning.

After an exciting discussion, we meandered to Salon Ríos for some excellent food. Being adventurous eaters, and having a “when in Rome” moment, we decided to try crickets on maiz (delicious but don’t think about it too much) as well as other local delicacies (I’ve never met a fried cheese I didn’t like.) And it wouldn’t be an evening in México City without a sampling of Mezcal.

Day Three - Partner Meeting with Nexion

Our next day began with a team breakfast, cruising through the previous day’s email and preparing for our next partner meeting with another long-standing partner, Nexion. With offices in México City and Argentina, Nexion has a broad reach in the LATAM region. This was our first in-person meeting with the team. Bernardo joined us at the hotel where he and Jorge connected over their shared Argentinian heritage and stories of legacy tool implementations gone wrong. Fortunately we have a modern tool to solve those problems. ;-)

We covered a lot of ground with Bernardo and learned more about Nexion’s projects and their customers’ needs. We provided an overview of our suite’s new features and what partners and customers can expect to see in 2023 and 2024. We then shared a spicy lunch at the hotel over a spirited discussion of the history of futbol championship games through the ages.

Day Four - Customer Meeting and Local Meetup

Day four consisted of customer meetings and exploring opportunities. Two thirds of the team had departures today, while Adam remains for the very culturally meta experience of an Oxford Alumni Association happy hour, at The Duke of Lisbon, a British pub, in México City. OK!

The work was driven by business and a desire to meet our partners in person, but we also found a bit of time to enjoy the history and culture of México City. Jorge had visited several times, but the rest of the team was new to the extraordinary sights, sounds and smells of the former epicenter of Aztec culture. The Archeological Museum was a highlight, and we also enjoyed the Historic center of the city and The Blue House, Frida Kahlo’s home.

It was truly wonderful to spend time with our partners-turned-friends, build deeper connections, and plan for future visits and opportunities. We say goodbye to México, but turn our sights to our future travels including London, Houston, Paris, and Antwerp. We hope to visit you in your neck of the woods soon!

Spotlight on Spira 7.5 - Multiple Requirement Approvers

2024-05-11T13:19:52-04:00

What Does the New SpiraApp Do?

This new SpiraApp will let you create multiple approvals or review tasks for requirements. This enables you to create review tasks with a single click, and assign them to stakeholders to review requirements. Then, when all the reviews are done, the requirement itself will automatically change status. In addition, to streamline the review and approval process, the plugin also introduces a new My Page dashboard widget.

At the present time, you can have multiple approvals for a requirement, but they need to be in a sequence / series, not in parallel:

With the new SpiraApp, you can now use Requirements and Tasks together to have multiple, parallel approvals. Since both Tasks and Requirements support electronic-signatures, you can have all the approvals comply with the validation requirements of 21 CFR Part 11 (and equivalent regulations).

How Do I Activate the Plugin?

To activate the plugin, go to the System Administration home page, and click on SpiraApps:

Then click on the Activate button to activate the plugin.

Next, go to the project you want to use the plugin for and click on SpiraApps there:

Click on the Enable button to enable the plugin for your project. You should then click on the Settings button to configure the plugin for use:

Open up a new browser tab and go to the Tasks > Custom Properties administration page as we need to now add a new boolean custom property on Tasks that denotes that this task is a special one used for multi-approvals:

Click the Save button. Now go back to the SpiraApp settings page and refresh the browser. The new custom property should be available in the dropdown list:

Now you need to choose that custom property and create the list of task approval groups.

To create groups of multi-approvers add a new line to the “Approval Lists” setting text-box. For each group, write out the settings like this:

List Name | Task name prefix | Task type | username1, username2, username3, ... username20.

(each group can have a max of 20 users).

For example, we have configured two approval groups below:

Business Team | Pending Approval | Management | fredbloggs, joesmith, amycribbins, administrator
Technical Team | Pending Approval | Management | amycribbins, rickypond, administrator

Now you are ready to start using the functionality...

Using the Requirements Multi-Approval App

To use the application, simply locate a requirement that needs to be approved:

Choose the option to Create Multi Approval Tasks:

Once you click the Create button, the new approval tasks will be automatically created:

Each user in the list can now go to their My Page dashboard and add a new special widget for viewing their approval tasks:

Once the widget is added, the user will be able to see their approval tasks in a dedicated widget:

Unlike the normal My Assigned Tasks widget, this one only shows the approval tasks and will also display the associated requirement.

To perform the approval, the user will simply click on the hyperlink for the task and use the normal task workflow to make the approval:

If you have configured the workflow to require an electronic signature, that will also happen as normal:

Once all the approvals have been done, the parent requirement will automatically change status as driven by the current workflow rules.

Project Manager's View

In addition to the My Page widget used by the individual approvers, there is also a new Product Home widget that allows project managers to see all of the pending approval tasks for a specific product. To add this widget, go to the Product Home dashboard and choose the option to add a new item:

Now select the Open Approval Tasks item and add it to the Left side of the dashboard:

You can now see all of the open, approval tasks for this product in one place.

Spotlight on Spira 7.5 - Customizable Requirement Statuses on Boards

2023-03-02T20:19:22-05:00

How Does It Work Now?

On the current versions of the planning board, when you use the product backlog view, the system will include any of the pre-planned statuses that are linked into the active workflows. That meant typically you would see:

Requested
Under Review
Rejected
Accepted

For the release backlog and sprint backlog views, you would see the following planned statuses:

Planned
In Progress
Developed
Tested
Completed
Obsolete

If you had added any other requirement statuses into the workflow, they would appear after Obsolete in order, even if logically they should appear before some of the other statuses.

Also when using the new, beta planning board, it meant that you would not have been able to move items from the product backlog to the release backlog when viewing status, since the cards would not be displayed in the statuses being viewed.

So with the upcoming version 7.5 release of Spira, we have changed how requirements' statuses work on the boards:

How Will it Work in Version 7.5?

With the new version of Spira, we have a new administration screen where product owners/admins can specify which requirement statuses will appear on the boards, and what order they should be displayed in:

By default, the system will show all active statuses being used in a workflow, in the same order as before.

Note this page is only available if you have Enabled Beta Features and in which case it will be displayed in the Administration menu:

However if you configure the statues to have a specific order and to only have specific ones in your boards, Spira will switch to only using those statuses and in the order you specify.

For example, if we enable only the following statuses, and specify our desired position:

When you go to view the Planning Board for this product, you will see:

Only the selected statuses are included in the board, and it will display them in the order that you selected.

Furthermore, we use the same statuses in all three different views (product backlog, release backlog, sprint backlog) which makes the user experience more consistent.

Inflectra's First of Many In-Person Events for 2023! - Happy Hour Meet & Greet Recap

2023-03-23T09:49:49-04:00

SUMMARY OF THE NIGHT

Overall, the Inflectra team was very pleased with the results of the meetup. Some of the contributions to this successful event were how:

The conversations were meaningful, and attendees were active. Washington, DC is full of people who have moved here from different parts of the world, so it was fascinating to hear what brought people in that evening and how they came to working in the area. We learned all of our attendees came for a different reason - from wanting to learn about our company and products, the tech industry, doing research on the job market, or simply meeting others in the area. Conversations in full speed, interesting, and insightful.
There was never a dull moment. We were very fortunate to have a group of people who were ready to come out and get in on the action. There was always someone from #TeamInflectra there to greet our guests and get them situated with a bright name tag, product information, and a bingo card in their hand. Once settled in, attendees did not hesitate to hi to one another, take part in the games, and enjoy all of the amenities at the event. We hope people left with new LinkedIn connections, traded business cards, and learned something new in addition to having fun.
Our famous James Bond pens were a hit once again. Our globally known James Bond pens were up for grabs at the event! Newcomers got to see that we do more than software testing, but also make cool and useful swag. As a bonus, if you were lucky enough, you got to watch CEO Adam Sandman give a full demo showing off its capabilities.

BUT WAIT - THERE WAS MORE!

On top of meeting lots of people, the attendees and team enjoyed:

A unique game of bingo! Who doesn't love a nostalgic game? To get to know attendees even more than just their work life, we had different several people were able to get 5 in a row and take swag home as a prize!
Delicious comfort food. Despite the weather giving us gray clouds and lots of rain, we looked forward to warming up with a buffet of bar food staples. People seemed to really enjoy the garlic fries, but the brussels sprouts were also an unexpected conversation starter!
The Admiral staff were very friendly and helpful. Upon entering The Admiral, you are immediately greeted by their friendly staff. The employees we interacted with throughout the night gave us quick service, were easy to talk to, and kept the area looking clean; they were, without a doubt, a big contribution to the positive outcome of our event.

COME MEET US AT OUR NEXT EVENT

From April 19-21, 2023 in Washington, DC, join us at our annual InflectraCON 2023 conference! Meet our staff members from all around the globe, attend talks, participate in workshops, and learn more about Inflectra’s software ecosystem. Get tickets today!

Spotlight on Spira 7.5 - New Task Boards Beta

2023-02-21T13:40:22-05:00

How To Access The Task Board Beta

Firstly, once the new version is released next month, you will need to enable the beta for your users in the Administration > System > General Settings:

Once it has been enabled at the system level, your users can then access the new task board by going to Tracking > Tasks and clicking Try the Beta:

This will then take you to the new beta task board ( and use them for remainder of your session (unless you click on the Exit the Beta button to return back to the old board).

Introducing the New Task Board

The new agile task board in Spira has been redesigned to have a more consistent user interface across its different views, support multiple boards in a product, provide more customization options, and also allow you to have both horizontal and vertical swim lanes in a single view. Previously we only allowed rows or columns, but not both.

Key Elements

The overall planning board page has these parts to it:

Top toolbar: this is where you configure the board itself (and all of the features below)
Grouping: divide up the list of items into a major grouping. Each grouping is its own independent board on the page and is selected from a few options (e.g. release, team, priority)
Columns: within each board / group, you must choose a field to show across the columns (e.g. status)
Rows: within each board / group create rows (swim-lanes) that can be used to divide up the data (e.g. person, parent requirement)
Cells: A cell is the intersection of a row and column to give a single reference point
Cards: with rows and columns, we get cells (like on a spreadsheet). All items that match the settings of a cell (e.g. have that team and status) are shown in individual cards. You can pick what information to show on cards

We will now explain the different parts of the board in more detail.

The Release Selector

This selector has three basic selection options:

All Releases - displays artifacts that are planned for any release
Release X - displays artifacts that are planned for the selected release and its child sprints
Sprint X - displays artifacts that are planned for just the selected sprint

Grouping

The new task boards have the option to have multiple, separate boards displayed. This is used when you want to display a board for each release, sprint, team, type, status, or priority:

Rows

Inside each of the boards, you can choose to organize the cards by row. This is optional, and depending on the grouping selected, the options will vary.

Columns

Inside each of the boards, you can choose to organize the cards by column. Unlike groups and rows, this is required and is the minimum level of categorization needed.

Common Use Cases

In the example below, Spira is displaying tasks grouped by Release/Sprint, with the type of task being the rows and the columns being the task status:

In the example below, Spira is displaying tasks grouped by Release/Sprint, with the parent requirement / user story being the rows and the columns being the task status:

In the example below, Spira is displaying tasks grouped by Team, with the assigned user (in the team) being the rows and the columns being the task status:

As you can see, there are many different combinations and permutations available in the new boards.

Changes to the Card Display

Finally, you may have noticed that the task cards on the boards look different. We have taken the opportunity to restyle them a little. The changes also mean that you can now customize what information is actually shown on each card to a much larger degree than before. Previously you could switch on/off:

Detailed Mode
- displayed the description
- showed the progress
- showed the position

With the new cards, you can configure each of these individually, as well as show new items such as the status and type that were previously not possible:

If you enable all of the individual options, the maximum display will look like this:

We have made some stylistic changes:

The position number is displayed on the bottom left vs. the entire background.
The priority is now shown as a colored circle, vs. the left-hand border

How Do I Provide Feedback

Once you have started using the new boards in beta mode, you will have feedback, suggestions, and questions! That is great. Please send them along to our product team by means of this customized support ticket mail link.

We hope you like the changes and improvements we have made with Spira's new agile task boards. Once we have collected the feedback, we plan to implement the key changes and then release the boards as production boards to replace the current ones.

Make Your InflectraCON Attendance a Valentine's Day Gift!

2023-02-14T13:48:33-05:00

This Valentine's Day, give the gift of a trip to Washington, D.C. to your loved ones!

This is how you do it:

Get your (1-, 2- or 3-day) ticket for InflectraCON 2023
Choose things you’d like to do in DC from our suggestions
Book flights and accommodation for everyone
Enjoy spring in DC and share the experience with your loved ones.

And just because we are all for love we are happy to offer you a $75 discount on select tickets to InflectraCON - DC's largest Agile, DevOps & Testing conference!

InflectraCON User Summit - New Tickets for All Budget Sizes

2023-02-06T12:10:42-05:00

Full Access Pass: Our 3-day Full Access Pass is an excellent choice for those who want to experience the full scope of InflectraCON 2023. For a very affordable US$ 899.99, you'll get to attend our core training, hands-on workshops on Spira and Rapise, keynotes, thought leadership sessions, industry case studies, leadership and risk management workshops, ninja sessions, expo, and virtual bonus sessions.

Combo Pass: If you don't want to commit to the full three days, our limited-time, limited-availability 2-day Combo Pass offers the best of both worlds on the budget! For just US$ 649.99, you'll receive core training or hands-on workshops on Spira or Rapise, keynotes, industry case studies, ninja sessions, and a networking expo (and costume party)!

Basic Pass: For those on a tight budget, the 1-day Basic Pass is the best option. With the Basic Pass, you'll go through our Spira core training or hands-on workshops of your choosing for just US$ 419.99. We will also host a pre-conference Meet and Greet, to which you are invited!

Please remember! Our Combo and Basic Passes have a limit of 20 participants each.

We want to make sure you can come to InflectraCON 2023, which is why we offer Early Bird Savings and Group Discounts!

Our Early Bird Savings are available until January 31, 2023, and allow you to save up to 15% off your passes.
But that's not all. We also want to make it easier for you to bring your team, so we are offering even more discounts for groups. If you bring 3+ team members, you'll get 15% off, five or more team members will get 20% off, and ten or more team members will get 25% off!

Don't miss out on your chance to get discounted rates and make memories with your team. Get your tickets now!

Together, we can make InflectraCON 2023 an unforgettable event that will inspire us to reach higher levels of success.

See you in Washington, DC!

Implementing Behavior-Driven Development (BDD) With Spira

2023-02-01T14:00:00-05:00

Why Use BDD?

The primary benefit of BDD is that it encourages communication between developers and other stakeholders, such as product owners and users. BDD helps bridge the gap between technical and non-technical stakeholders by providing a common language for discussing behavior of the system. By using this language, stakeholders can understand each other’s needs and expectations, leading to better development decisions.

Read our new Whitepaper on Using Spira for Managing Your BDD Projects.

Inflectra in the News - January 2023 Roundup

2023-01-31T12:14:55-05:00

Interviews

Scaled Agile Framework with TechStrong TV - January 10, 2023

Inflectra CEO Adam Sandman explains how agile frameworks such as the Scaled Agile Framework (SAFe) are gaining traction as enterprise IT organizations continue to shift more responsibility for cybersecurity left toward application developers in a way that doesn’t compromise the speed at which high-quality applications are developed. Watch here.

Podcasts

Great Products Need a Culture of Quality and Passionate People with InfoQ - January 13, 2023

In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Melissa Daley, Bob Crews and Adam Sandman, speakers at the InflectraCON 2022 State of Testing conference, about the state of testing and how to instil a culture of quality into software teams. Listen here.

Publications

Recession Fears May Cause us to Lower our Defenses with App Developer Magazine - January 13, 2023

In many ways, 2022 can be thought of as a watershed; as the global pandemic eased, for the first time, we can see what changes were temporal and which ones have become structural. Likewise, the changes to the global supply chain (and globalization itself) and how information technology has become embedded in our daily lives are here. Yet, at the same time, the risks from failures in critical systems, whether cyber attacks or “old-fashioned” software bugs, have only increased. Read more.

The Year Testing Becomes Quality Engineering with VMBlog - Jan 20, 2023

If we look back at the last couple of years, it has been a time when information technology and software have radically transformed the world around us, from online meetings and classrooms to self-driving cars, smart electrical systems, and AI facial recognition. Yet, at the same time, this seemly serene, upward journey into the pastures of a digital utopia has been punctuated by an endless profusion of security breaches, data privacy failures, and safety critical systems failing due to software problems. As we become more dependent on technology, yet at the same time more vulnerable, 2023 needs to be the year that we realize that we as software professionals need to focus on quality. Read more.

Software Testing, Artificial Intelligence, and Machine Learning Trends in 2023 with InfoQ - January 23, 2023

In many ways, 2022 has been a watershed year for software; with the worst ravages of the pandemic behind us, we can see the temporal changes and which ones have become structural. As a result, companies that used software to build a sustainable long-term business that disrupted the pre-pandemic status quo have thrived. Yet, at the same time, those that were simply techno-fads will be consigned to the dustbin of history. Read more.

Join Us!

To learn more about Inflectra’s software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Get Tickets now!

The Ultimate Tech Event for Any Budget | Enjoy InflectraCON at an Unbeatable Price

2025-04-01T22:15:54-04:00

At a great value of US$ 699.99, get the ultimate InflectraCON 2023 experience with our 2-day full Conference access pass. This includes keynote speeches, leadership and risk management workshops, thought leadership sessions, networking expo, and virtual Bonus Sessions.

Our Conference Lite pass for April 20, 2023, is the perfect option if you don't want to purchase a full 2-day pass! For a mere US$ 419.99, you'll get access to a workshop on Leadership and Growth with Mike Lyles of Maxwel Leadership, keynotes, industry case studies, virtual Bonus Sessions, and a networking expo - including Inflectra's famous costume party! This offer is only available for a limited time, so don't miss out!

For financially conscious people, the one-day Conference pass for April 21, 2023, is the most suitable choice. At just US$ 349.99, you can enjoy an outstanding workshop on RiskStorming with an International Speaker - Ard Kramer, and sessions on DevOps, Automation, and Risk Management. Additionally, there will be a Closing Ceremony and gift giveaways which you are welcome to join!

It is important to note that both Passes have a restriction of 20 individuals per pass.

In order to ensure that you can attend InflectraCON 2023, we provide Early Bird Specials and Group Rates!

If you act quickly and purchase your passes before January 31, 2023, you can get a 15% discount with our Early Bird Savings.
Furthermore, we have even more discounts available for groups. If you bring 3 or more people, you will get 15% off.

Act fast and secure your seat! Click here to purchase your tickets now!

We are gathering in the nation's capital - Washington, D.C.! Are you with us?

Webinar Recap: Lightning Session - How to Manage Your Agile Projects with SpiraTeam

2023-01-26T09:48:17-05:00

MEETING AGENDA:

SpiraTeam Overview: Why SpiraTest by Inflectra
SpiraTeam: Lightning Demo
SpiraTeam Differentiators: Add-ons, Integrations, Price and Licensing, Accelerators
SpiraTeam Roadmap in 2023
Q&A

RECORDING

PRESENTATION SLIDES

ABOUT THE PRESENTER:

WANT TO ATTEND OTHER EVENTS?

View and sign up for more lightning sessions here.

You can also sign up for our newsletter to stay up-to-date with all Inflectra events!

KEEP UP-TO-DATE

Easy! Sign up for our newsletter to stay up-to-date with all Inflectra events!

To learn more about Inflectra’s software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Webinar Recap: Lightning Session - Rapid & Easy Test Automation Using Rapise

2023-01-26T09:43:31-05:00

MEETING AGENDA:

Rapise Overview: Why Rapise by Inflectra
Rapise: Lightning Demo
Rapise Differentiators: Add-ons, Integrations, Price and Licensing, Accelerators
Rapise Roadmap in 2023
Q&A

RECORDING:

PRESENTATION SLIDES:

ABOUT THE PRESENTER:

WANT TO ATTEND OTHER EVENTS?

View and sign up for more lightning sessions here.

You can also sign up for our newsletter to stay up-to-date with all Inflectra events!

STAY IN THE KNOW!

Please sign up for our newsletter to stay up-to-date with all Inflectra events!

LEARN MORE AT INFLECTRACON

To learn more about Inflectra’s software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Ways to Save on InflectraCON 2023 Tickets

2023-01-19T13:37:53-05:00

Let's talk about how you can save on InflectraCON 2023 tickets.

First, choose your ticket

InflectraCON 2023 offers two different types of passes:

Ticket Type	Full Access Ticket Best for Inflectra users, customers, and partners	Conference-only Ticket Best for practitioners, job seekers, and students
Ticket Benefits	This ticket covers a full day of training, ninja sessions, Spira certification, customer roundtable, and our 2-day conference, bonuses sessions, and reception.	This ticket type gives attendees access to our 2-day conference, bonus sessions, the expo, leadership workshop, and networking reception.
Ticket Price	This fantastic package is usually US$899.99.	This fantastic package is usually US$699.99

Second, find out about ways to save

In addition to two types of passes, there are two offers you should consider:

1. Early Bird discount: Now through January 31, take 15% off your admission to InflectraCON with code EARLYBIRD23

2. Group discount (starting at 3 tickets): Buy more, save more! InflectraCON is all about team building, so we want to help get your entire crew to the conference. With savings starting at 3 tickets, there is no reason to break the bank while your team learns the latest in software and connects with the industry’s top professionals.

Third, do the math

Stack savings and watch the price drop right in front of your eyes! See our cost calculations to save hundreds.

1. Stacked discounts for Full Access tickets:

*Step 2 promo code valid now through January 31 | Additional fees not included.

Get the Full Access tickets!

2. Stacked discounts for Conference-only tickets:

*Step 2 promo code valid now through January 31 | Additional fees not included

Get the Conference only tickets!

Finally, let's NOT wait to pay the full ticket price

Now that you know the math, what else is there to question?

Secure your admission to InflectraCON 2023 - DC’s largest agile, testing and DevOps conference.

Using Risk-Driven Development (RDD) in Software Delivery

2023-01-25T14:19:20-05:00

There is an intense focus on value generation in today’s business community. The emergence of markets based on the fourth industrial revolution technologies have increased the type, number, and complexity of the software interfaces. No longer are users expected to interface with the software with a keyboard and mouse. The use of artificial intelligence and technological sophistication has made many different keyboard-less interfaces possible such as touch, voice, and local environment in the case of the Internet of Things (IoT). This has allowed us to communicate in semi-autonomous cars and smart homes.

The ubiquity of the software along with the severity of the risks can have serious economic consequences. Some of these risks could also be fatal to the users and the people employed in managing the development and operational value streams in regulated fields like healthcare.

Learn more in this timely new whitepaper on Risk-Driven Development (RDD).

TestProject Discontinued - Need Alternatives?

2023-01-09T15:12:21-05:00

What Was TestProject?

TestProject was a free end-to-end test automation platform for web, mobile, and API testing that was originally created and supported by the test automation community. TestProject was built on the leading open source test automation tools: Selenium and Appium and by fostering a collaborative community that can come together aimed to shape the future of software testing. In 2019, it was sold to Tricentis to become part of its automated testing portfolio, which includes its commercial tools Tosca and Testim. In November 2022, Tricentis announced that it would be sunsetting the platform, focusing instead on Tosca and Testim.

How To Choose a Replacement Automated Testing Tool

So if you need to quickly find a replacement tool for TestProject, there are several factors you may want to consider when choosing a replacement automated testing tool:

The type of tests you need to run: Different testing tools are designed to handle different types of tests. For example, some tools are better suited for unit testing, while others are better for end-to-end testing.
The technology stack of your application: You'll want to choose a testing tool that is compatible with your application's technology stack. For example, if your application is built with Java, you'll want a testing tool that has good support for Java.
The cost of the tool: If you are working on a budget, you may want to consider a free or open-source testing tool. There are many good options available, such as Selenium and Cypress.
The level of support and documentation: If you are new to automated testing, you may want to choose a tool that has good documentation and a strong community of users who can provide support or a commercial tool that comes with vendor support.
The level of integration with your development workflow: You'll want a testing tool that integrates well with your development process, so that it is easy to incorporate testing into your workflow.

Ultimately, the best testing tool for you will depend on your specific needs and constraints. We recommend doing some research and trying out a few different tools to see which one works best for you. Here is a list that will help you get started: The Top 10 Automated Testing Tools in 2023.

Recording: Spira 7.3: Agile Planning Boards To Rule Your Projects

2022-12-27T10:13:21-05:00

WEBINAR AGENDA
This webinar covered:

Spira in 2022: Recapping the progress
Latest Releases:
- The Planning Boards: Kanban, Scrum and Agile Use Cases
- Teams
- Product/project custom properties
- New Spreadsheet editor
Q&A

RECORDING

PRESENTATION SLIDES

ABOUT THE PRESENTER

NEVER MISS AN INFLECTRA EVENT

To learn more about Inflectra’s software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Webinar Recap: Lightning Session - How To Turbo-Charge Your Test Management with SpiraTest

2023-01-24T14:07:15-05:00

MEETING AGENDA:

SpiraTest Overview: SpiraTest vs. Atlassian Jira, Jira server and other disruptions in test management space
SpiraTest: Lightning Demo
SpiraTest Differentiators: Add-ons, Integrations, Price and Licensing, Accelerators
SpiraTest Roadmap in 2023
Q&A

RECORDING:

PRESENTATION SLIDES:

WANT TO ATTEND OTHER EVENTS?

View and sign up for more lightning sessions here.

You can also sign up for our newsletter to stay up-to-date with all Inflectra events!

To learn more about Inflectra’s software ecosystem, join us for InflectraCON 2023 in Washington, DC, on April 19-21, 2023.

Time to Switch Your Chrome Browser Library in Rapise

2022-12-18T07:19:39-05:00

Background

In December of 2020, the Google Chrome browser team made a major announcement - the release of Google Chrome Manifest 3. This new version of Chrome is designed to radically improve the security and safety of web browsing. Specifically:

With the introduction of Manifest V3, we will disallow remotely hosted code. This mechanism is used as an attack vector by bad actors to circumvent Google’s malware detection tools and poses a significant risk to user privacy and security.

However this new manifest version has an unfortunate side effect for the software testing industry, it will prevent the Chrome extensions used by many popular test automation tools such as Rapise, Ranorex, TestComplete, UFT and others from working.

What You Need to Do

Inside Rapise, you need to change the browser profile you use from Chrome HTML to Selenium - Chrome in test settings.

If you have standalone tests just switch profiles using the dropdown in top-right corner of the Rapise main window.

If you have a framework you may need to update the value of the g_browserLibrary variable either in Rapise, or in Spira, if you are using Spira to send the variable to Rapise during test execution:

g_browserLibrary = "Selenium - Chrome";

Next you will need to update your tests. In many cases there is nothing to update, but there are a few situations that need attention:

Global.DoClick
Global.DoSendKeys

To get all the advantages of Selenium-based testing (do your work while tests are running on a local machine, parallel execution, compatibility with browser farms) try to replace Global.DoClick and Global.DoSendKeys with other functions.

You can interact with a specific web element via:

element.DoClick
element.DoSendKeys
element.DoSetText
or use Actions via JavaScript

What about Other Browsers?

Although this change is specific to Google Chrome, we recommend that users switch to Selenium recording and playback for the other web browsers (Edge, Firefox, IE, etc.) as the plan is to eventually retire all of our old browser plugins and focus exclusively on the Selenium WebDriver based interface.

Additional Resources

Quality Assurance vs. Testing

2023-11-06T13:34:04-05:00

This focus on holistic quality used to be the exclusive preserve of more regulated industries such as life sciences and manufacturing. But there has been a dramatic change in the regulatory and legal landscape over the past five years, due the dawning realization that software is an essential component of the modern economy. Now, CIOs and technologists are being held to a higher standard, since software has become an critical service, so quality in its wider form, is no longer optional.

Read About Quality Assurance in our New Whitepaper - Full Guide To Software Quality Assurance.

Agile Testing Days 2022 - They Did It Again

2022-12-08T09:42:09-05:00

Conference Insight:

The major takeaways from the conference have been:

Play to your strength - Agile Testing Days 2022 in Potsdam has been around for over a dozen years and has created a cult-like following. ATD leadership invested a significant amount of time, energy, and creativity in developing a fan base that remains dedicated and enthusiastic about the conference all year round. ATD Potsdam’s success is proportionate to its community’s strength and may prove challenging and time-consuming to replicate in other locations.
Community-first approach to conferencing - Agile Testing Days affirms the professionalism, ingenuity, and creativity of agile software testers. The conference does not shy away from giving centerstage to first-time speakers, allowing non-testing talks and personal stories that celebrate innovative leadership, better communication, empathy, and resilience. It goes out of its way to gamify learning, hosting sessions like Keynote eXtreme, Powerpoint Roulette, Pepe’s Bar Live, and Jack of all Trades - all geared toward improving attendees’ skills as speakers. And let’s not forget all the fun during the annual MIATPP Award Ceremony. (pictures are below)
Thoughtfulness toward sponsors pays off - ATD’s format is designed to bring the spotlight to all who go there, including sponsors. For instance, in 2022, sponsors were invited to pitch their products to the entire ATD community right before the opening keynote. This has been a great success, as many attendees visited the Inflectra booth after hearing about SpiraPlan and Rapise on the morning of the very first day.

The EXPO

The Team Inflectra traveled to the conference from Washington, D.C., Marseille, FR, and Colorado Springs, CO. Having spent quality time bonding with the team members while exploring Berlin and German cultural and gastronomic delights, we traveled to Potsdam for the conference.

The conference was well-attended with approx. 600 attendees and speakers from all over the globe. Our team stayed busy at the expo, demoing our products, fielding questions about SpiraPlan and Rapise capabilities, and discussing the trends in software buying.

Among the most frequently asked questions were:

Spira’s ability to integrate with other leading tools on the market
Rapise’s automation capabilities, as many team Leads seem to prefer to move away from the so-called Heroic Efforts and embrace more predictable, scaleable, and maintainable automation frameworks
implementation assistance for companies with complex SDLCs
licensing, pricing, and data residency.

Inflectra’s products continue to be well-liked by both the expo visitors and speakers, as the latter group has approached the team with multiple collaboration ideas and opportunities. Inflectra’s partnership team was also busy forging new relationships with the leading European tech companies represented at ATD.

The Fun

And last but not least, check out the photos from the annual MIATPP Award Ceremony. The 2022 theme was fairy tales.

(Ursula, Maleficent, Snowwhite, and the Wizard of Oz)

(an assortment of characters, including the queen of hearts)

See you at ATD 2023!

Inflectra in the News - November - December 2022 News Roundup

2023-01-04T11:56:00-05:00

Publications

If You’re a Bootstrapped Startup, Turn to User-Centered Design to Thrive During Adversity with TechCrunch - December 5, 2022

When it comes to user-centered design (UCD), the goal of each design process is the same: create an excellent product for your end-users. In normal economic times, the use (or lack) of UCD can significantly influence the success or failure of a project. In this more fiscally constrained environment, the stakes are even higher. Read more.

Invest in a solid marketing team, Follow your own path, and Enjoy the journey with IdeaMensch - December 21, 2022

IdeaMensch publishes handcrafted interviews with entrepreneurs, creators, and doers. In this written interview, Adam Sandman, Founder and CEO of Inflectra, discusses where the idea for Inflectra came from, what his typical day looks like, how he makes it productive, and how Inflectra brings ideas to life. Read More.

Accelerating Software Rollout Success with IT Briefcase - December 23, 2022

For companies dedicated to building great software and tools, statistics showing that almost a third of IT investments classify as failed or that organizations are losing billions of dollars annually because of botched software implementations are frightening. Software was supposed to eat the world: so why is it so hard to implement? Read more.

Talks and Presentations

Are You Scaling Agile or Just Failing Agile? Techwell's Agile + DevOps East conference - November 6-11, 2022

Inflectra is proud to have been a Gold sponsor for this year's hybrid Agile + DevOps East event in Orlando, Florida. The main takeaways include: understanding the limits of agile in larger contexts, ways to allow complex organizations to embrace agile without micromanagement and bureaucracy, and case studies of successful and failed attempts to scale agile. Read more.

Spotlight on Spira 7.3 - Agile Boards and Teams/Tracks

2022-12-07T10:08:42-05:00

How To Access The Planning Board Beta

Firstly, once the new version is released next month, you will need to enable the beta for your users in the Administration > System > General Settings:

Once it has been enabled at the system level, your users can then access the main Planning Board using the Spira navigation as normal:

Then click on the Try the Beta button the top-right to enable the new beta boards:

Once you click that, Spira will display the new planning boards, and use them for remainder of your session (unless you click on the Exit the Beta button to return back to the old boards).

Introducing the New Planning Board

The new agile planning board in Spira has been redesigned to have a more consistent user interface across its different views, support multiple boards in a product, provide more customization options, and also allow you have to have both horizontal and vertical swim lanes in a single view. Previously we only allowed rows or columns, but not both.

Key Elements

The overall planning board page has these parts to it:

Top toolbar: this is where you configure the board itself (and all of the features below)
The view: product backlog, release backlog, and sprint backlog. Select the view to get all relevant artifacts
Grouping: divide up the list of items into a major grouping. Each grouping is its own independent board on the page and is selected from a few options (e.g. release, team, component)
Columns: within each board / group, you must choose a field to show across the columns (e.g. status)
Rows: within each board / group create rows (swim-lanes) can be used to divide up the data (e.g. person, parent requirement)
Cells: A cell is the intersection of a row and column to give a single reference point
Cards: with rows and columns we get cells (like on a spreadsheet). All items that match the settings of a cell (e.g. have that team and status) are shown in individual cards. You can pick what information to show on cards

We will now explain the different parts of the board in more detail.

Different Views

As mentioned above, the new planning board has three distinct views that you can switch between:

The Product backlog lets managers prioritize ("groom") unplanned work items that do not have a scheduled release.
- This view displays all the unplanned items so that the project manager or product owner can prioritize work prior to assigning to a specific release or sprint. This is often called ‘backlog grooming’ but is essentially prioritizing and categorizing the unplanned work
The Release backlog lets managers review planned or in progress work items
- This view displays all the planned items (based on status) so that the project manager can:
  - assign work to a release
  - move work between releases; or
  - move planned items around ignoring releases
The Sprint backlog lets managers review work in a release and its sprint, or for a single sprint
- This view displays all the planned items in a release and its sprints so that the project manager can:
  - assign work between sprints in a release; or
  - focus on a single sprint (if desired)

The Release Selector

This selector is only available for the release backlog and sprint backlog views. It is hidden if you choose product backlog.

It has three basic selection options:

All Releases - displays artifacts that are planned for any release
Release X - displays artifacts that are planned for the selected release and its child sprints
Sprint X - displays artifacts that are planned for just the selected sprint

For example, when you are displaying the release backlog, you will see the following:

and when you are displaying the sprint backlog, you will see the following:

Grouping

The new boards have the option to have have multiple, separate boards displayed. This is used when you want to display a board for each release, sprint, team, component or priority:

For example, when you are displaying the Release Backlog, you may want to group by release:

Inside each group, you will have a board with individual rows and columns. There are icons that let you expand/ collapse the group itself, as well as the option to expand/collapse all groups:

Rows

Inside each of the boards you can choose to organize the cards by row. This is optional, and depending on the view (product backlog, release backlog, sprint backlog), the options will vary. For example, in the screenshot below we are displaying the product backlog organized by parent Epic.

Since we are also grouping by Component, the board is smart enough to know that it should only show you the Epics in each Component as rows. If you expand the other Components, only the Epics on those Components will be displayed.

Similar to the grouping functionality, you can collapse/expand a single row or use the special expand/collapse all icon:

Columns

Inside each of the boards you can choose to organize the cards by column. Unlike groups and rows, this is required, and is the minimum level of categorization needed. For example, here's the product backlog organized by priority:

The options available in the Columns drop-down menu will depend on the current view. For example, here's the list of column options in the Release Backlog view:

When you use the groups, columns and rows together, you get a much more sophisticated board. For example, here's the Release Backlog, grouped by Team, with the columns set to Priority and the Rows set to Person:

When you expand any of the rows, you will see the appropriate requirement user story cards:

Common Use Case

Scrum Projects

For Scrum projects, the new boards support the most important agile ceremonies and planning activities. For example, you can show all the unplanned items in the product backlog for backlog grooming:

In this example we are displaying the User Stories by Epic, grouped by Component and categorized by Priority.

For a typical release planning section, you can use the following release backlog view:

In this example we are displaying all the releases, with the ability to take items from the product backlog (at the top) and assign to a specific release.

For a sprint planning session, the following view will let you assign work to each sprint from the release backlog:

The system will display the available effort vs. committed effort to make sure you have not over-committed the sprint. As with the previous version of the boards, you can use either story points or hours, depending on the setting chosen in the Spira planning options.

Finally, you can drill down to look at an individual sprint and see the team's progress. This is useful for daily standup meetings:

Kanban Projects

For Kanban projects, in addition to the functionality described above, you have the ability to see the different releases by status, with the Work In Progress Limits clearly visible in each of the swim-lanes:

In this example, we are showing the release backlog for a specific release, with the columns set to display by status and the planning options set to include WIP limits for the In-Progress and Developed columns.

Other Features

Teams & Tracks (SpiraPlan Only)

In addition to the board changes themselves, the new agile boards also make use of another new beta feature - teams and tracks. For SpiraPlan customers, the boards allow you to choose a Team as one of the options in the Grouping selector:

These teams come from the administration menu, where you can create a global list of teams, and then assign users to those teams on a per-project basis:

Changes to the Card Display

Finally, you may have noticed, that the requirement user story cards on the boards look different. We have taken the opportunity to restyle them a little. The changes also mean that you can now customize what information is actually shown in each card to a much larger degree than before. Previously you could switch on/off:

Detailed Mode
- displayed the description
- showed the task progress
- showed the position
Show Tasks
Show Test Cases

With the new cards, you can configure each of these individually, as well as show new items such as the test coverage, status, and type that were previously not possible:

For example, the most minimal set of information (with everything set to No) would look like:

In the old boards, this would have looked something like:

If you enable all of the individual options, the maximum display will look like:

If you compare with the old version:

We have made some stylistic changes:

The position number is displayed on the bottom left, vs. the entire background.
The priority is now shown as a colored circle, vs. the left-hand border
The test cases are now shown as small circles next to the test coverage, along with the test case count
The tasks are now shown as small circles next to the task progress, along with the task count

Since the test cases and tasks are now shown as colored circles, instead of mini-cards, you would use the tooltip to see the ID of the actual task or test case:

How Do I Provide Feedback

Once you have started using the new boards in beta mode, you will of course have feedback, suggestions and questions! That is great, please send them along to our product team by means of this customized support ticket mail link.

We hope you like the changes and improvements we have made with the new agile planning boards in Spira. Once we have collected the feedback, we plan on implementing the key changes and then releasing the boards as production boards to replace the current ones.

Agile + DevOps East 2022 is Complete!

2023-05-08T12:20:30-04:00

Starting off the Conference:

As soon as the whole team arrived safely, we went straight into joining the festivities! Techwell never fails to start off their conferences on a playful and positive note; this time around for ADO East, a unique game of bingo helped us smoothly transition into networking with fellow attendees. In addition to the icebreaker games, there were complimentary beverages (including a resort exclusive beer) and hot hors d'oeuvres to make us feel welcomed and fueled to get to work after our flights. It was wonderful start to our experience getting to know folks from around the world before setting up and manning the booth.

The #TeamInflectra Booth:

The Inflectra team was thrilled to meet so many attendees whether they took a short drive to the resort or traveled on a plane from overseas. We enjoyed stamping passports for those participating in the raffle, teaching professionals about our products, and discovering the diverse background of people we were engaging in conversations with. The expo was well managed, and the appetizers and meals were delightful. The Inflectra booth was conveniently located close to all the delicious refreshments, including the happy hour bars and an ice cream cart brought out one evening.

We hoped you stopped by the Inflectra booth to grab some of our awesome swag, say hello to our lively team members, and listen to our energetic, upbeat music to keep the energy alive (while resisting the urge to dance). We are delighted to have met and converse with so many of you.

Plus a big congrats to the winner of our raffle prize - a brand new pair of Apple AirPods!

Presenting at Agile + DevOps East:

Inflectra is honored to have had two people from our team chosen to speak at ADO East. Both our CEO, Adam Sandman, and Enterprise Agile Evangelist, Sriram Rajagopalan, had well attended presentations. Attendees were engaged, asked insightful and meaningful questions, and provided positive feedback afterwards for both the online and virtual crowds. Thank you to those who attended!

Sponsoring the Leadership Summit and Reception:

The leadership summit reception was the perfect way to close out another busy day. For the third time in 2022, Inflectra sponsored a pre-summit reception at a Techwell event. This portion of the conference brought attendees to a central area to share ideas, topics and get excited for a productive and insightful Leadership Summit the following day. Team Inflectra especially enjoyed meeting more people while enjoying the delicious appetizers, learning about the professional history of fellow attendees, and being able to give a thank you announcement.

Nicole, Who?

Despite dealing with hurricane Nicole, and the very wet circumstances she caused us, our team still had a wonderful stay at the Caribe Royale Resort - home of ADO East 2022. We spent most of our time admiring the beautiful pool area, enjoying several on-property restaurants, and even taking a short off-property trip to Disney Springs to explore more of the surrounding area. Team Inflectra is fortunate to have such a great group of people who are able to bring light and have fun with anything thrown at us!

Team Building - The Inflectra Way

2022-11-25T08:18:18-05:00

Bringing The Team Together

Since we had some members of the team traveling to Europe for the upcoming Agile Testing Days event in Potsdam, Germany, we decided it was a good opportunity to bring the members of our US business development team together for the offsite before the conference travels.

Here you can see Sriram, Audrey and Rick arriving in Silver Spring, MD the night before. The McGinty's pub in Downtown Silver Spring is popular favorite with our team. Sadly the darts board was fully occupied this time around.

The Serious Stuff - Retrospectives and Planning

The offsite was great opportunity for our team to do an agile retrospective on our SalesOps process, understand where we had successes and where we could improve our process:

The SalesOps process is the brainchild of our Head of Marketing, Thea Maisuradze, and applies the concepts of DevOps to business development.

With our new account manager structure, SalesOps allows us to deliver a consistent and amazing customer experience from the first contact, through pre-sales to customer success and long-term partnerships.

Team Building - Making T-Shirts

In addition to the serious work, having time for team building is critically important. We had several people join the team in Q3/Q4 and it was a good opportunity for them to get to know the members of the team who aren't based in the Washington, DC area. One crazy activity pioneered by Jessica and Andrea was a T-Shirt making contest. Using our fabulous stickers, the team constructed their own personalized Inflectra T-Shirts.

The plan is to then use some of the designs for next year's company T-Shirts for conferences and other events.

The Paper Plate Awards

For anyone who had children on swim-teams in America, this should be familiar. At the event of the swimming season, the team gives out 'paper plate' awards to everyone on the team, with personalized slogan / nickname for the person based on how they had helped the team. We present here, some of the awards!

Thea got the master juggler award for juggling all of the myriad sales and marketing activities!

Adam got the Super CEO award for being I guess... a Super CEO!

Teresa got the Demo Diva award for all her amazing demos and video recordings. You will have heard her on the Inflectra YouTube channel quite a lot!

Francois got the Sea of Patience Award for dealing with renewals, invoices, payments, non-payments and every other scenario you can imagine!

Kendra got the Quick Study award for her rapid on boarding and taking on the management of our marketing channels (social, meetups, webinars, etc.)

The amazing Audrey got the Partner Princess award for her complete revamping of the Inflectra partner program, including the handling of partner on-boarding and training as well as working with our techno partners and US solution partners.

Rick of course won the Rick of all Trades award for his major multi-tasking of sales, marketing, conferences, video editing, bourbon and so much more!

Andrea who only recently joined the team got the Organize Everything award for her help in organizing the chaos that was company operations.

Team Happy Hour

After the awards were done, we had an office-wide (for those who could make it) catered lunch and evening happy hour.

As the sign suggests, Harmony is important to Inflectra and we all felt excited to plan out 2023 with our amazing team and of course you, our amazing customers.

Webinar Recap - Rapise v7.4 Webinar: Web Components, AgGrid, Mixed-Mode and 64-Bit Apps

2022-11-29T09:12:41-05:00

WEBINAR AGENDA

This webinar covered:

- Mixed Mode Recording (Web, Managed, UIA, Java)
- Test Set scheduling in Spira Dashboard
- Support for the Web Component Slot element (WebSpy, XPath generator)
- Generic support for AgGrid web component
- Support for Managed 64-bit desktop applications
- Support for Java 64-bit desktop applications

WEBINAR RECORDING

WEBINAR PRESENTATION

STAY UP TO DATE

#TeamInflectra

Risk Management: Definition, Importance, & Types

2022-11-22T11:07:29-05:00

Unfortunately, all projects and undertakings involve some amount of uncertainty or risk. Whether it’s minuscule or highly likely, the consequences of risk can end up being costly on a number of levels — and when you’re unprepared, these consequences can be catastrophic. But what does risk management actually mean, why is it so crucial to a quality product, and how can you ensure that yours is strong?

Preparing for the GAMP Transition to Computer Software Assurance

2025-09-11T15:13:39-04:00

What is Changing with GAMP?

Traditionally, software validation has often been accomplished via software testing and other verification activities conducted at each stage of the software development lifecycle. However, as explained in FDA’s Software Validation guidance, software testing alone is often insufficient to establish confidence that the software is fit for its intended use. Instead, the Software Validation guidance recommends that “software quality assurance” focus on preventing the introduction of defects into the software development process, and it encourages use of a risk-based approach for establishing confidence that software is fit for its intended use.

The FDA believes that applying a risk-based approach to computer software used as part of production or the quality system would better focus manufacturers’ assurance activities to help ensure product quality while helping to fulfill the validation requirements of 21 CFR 820.70(i). For these reasons, the FDA is now providing recommendations on computer software assurance for computers and automated data processing systems used as part of medical device production or the quality system. The FDA believes that these recommendations will help foster the adoption and use of innovative technologies that promote patient access to high-quality medical devices and help manufacturers to keep pace with the dynamic, rapidly changing technology landscape, whilst promoting compliance with laws and regulations implemented by the FDA. Consequently the medical device industry is looking to move from a Computer Software Validation approach to one of Computer Software Assurance.

What is Computer Software Validation (CSV)?

Computer Software Validation (CSV) is a requirement of the Quality System regulation, which was published in the Federal Register on October 7, 1996 and took effect on June 1, 1997. (21 CFR 820 and 61 FR 52602). Validation requirements apply to software used as components in medical devices, to software that is itself a medical device, and to software used in production of the device or in implementation of the device manufacturer's quality system. Software validation is a part of the design validation for a finished device, but is not separately defined in the Quality System regulation. The FDA considers software validation to be “confirmation by examination and provision of objective evidence that software specifications conform to user needs and intended uses, and that the particular requirements implemented through software can be consistently fulfilled.”

In practice, software validation activities may occur both during, as well as at the end of the software development life cycle to ensure that all requirements have been fulfilled. Since software is usually part of a larger hardware system, the validation of software typically includes evidence that all software requirements have been implemented correctly and completely and are traceable to system requirements. A conclusion that software is validated is highly dependent upon comprehensive software testing, inspections, analyses, and other verification tasks performed at each stage of the software development life cycle. Testing of device software functionality in a simulated use environment, and user site testing are typically included as components of an overall design validation program for a software automated device.

What is Computer Software Assurance (CSA)?

Computer Software Assurance (CSA) is a risk-based approach for establishing and maintaining confidence that software is fit for its intended use. This approach considers the risk of compromised safety and/or quality of the device (should the software fail to perform as intended) to determine the level of assurance effort and activities appropriate to establish confidence in the software. Because the computer software assurance effort is risk-based, it follows a least-burdensome approach, where the burden of validation is no more than necessary to address the risk. Such an approach supports the efficient use of resources, in turn promoting product quality.

In addition, computer software assurance establishes and maintains that the software used in production or the quality system is in a state of control throughout its lifecycle (“validated state”). This is important because manufacturers increasingly rely on computers and automated processing systems to monitor and operate production, alert responsible personnel, and transfer and analyze production data, among other uses. By allowing manufacturers to leverage principles such as risk-based testing, unscripted testing, continuous performance monitoring, and data monitoring, as well as validation activities performed by other entities (e.g., developers, suppliers), the computer software assurance approach provides flexibility and agility in helping to assure that the software maintains a validated state consistent with 21 CFR 820.70(i).

What Are The Core Requirements for CSA?

Although the guidance from the FDA is still in draft form, when you look at the original specifications for CSV and how they are evolving to meet the needs of CSA, the following core activities are paramount:

Requirements Management - Design input requirements must be documented, and that specified requirements must be verified. Requirements reflect the stated or implied needs of the customer, and may be market-based, contractual, or statutory, as well as an organization's internal requirements.
Software Verification - provides objective evidence that the design outputs of a particular phase of the software development life cycle meet all of the specified requirements for that phase.
Risk Analysis & Management - Once a manufacturer has determined that a software feature, function, or operation is intended 221 for use as part of production or the quality system, FDA recommends using a risk-based analysis 222 to determine appropriate assurance activities
Assurance Activity Planning - Once the manufacturer has determined whether a software feature, function, or operation poses a high process risk (a quality problem that may foreseeably compromise safety), the manufacturer should identify the assurance activities commensurate with the medical device risk or the process risk.

The types of assurance activities commonly performed by manufacturers include, but are not limited to, the following:

Unscripted testing – Dynamic testing in which the tester’s actions are not prescribed by written instructions in a test case. It includes exploratory testing, ad-hoc testing, and error-guessing.
Scripted testing – Dynamic testing in which the tester’s actions are prescribed by written instructions in a test case. Scripted testing includes both robust and limited scripted testing. It can be a mixture of automated testing and manual, depending on what is possible and mitigates the identified technical risk.

When establishing the recorded results of assurance activities, the manufacturer should capture sufficient objective evidence to demonstrate that the software feature, function, or operation was assessed and performs as intended. In general, the record should include the following:

the intended use of the software feature, function, or operation;
the determination of risk of the software feature, function, or operation;
documentation of the assurance activities conducted, including:
- description of the testing conducted based on the assurance activity;
- issues found (e.g., deviations, failures) and the disposition;
- conclusion statement declaring acceptability of the results;
- the date of testing/assessment and the name of the person who conducted the testing/assessment;
- established review and approval when appropriate (e.g., when necessary, a signature and date of an individual with signatory authority)

How Does SpiraPlan Help?

SpiraPlan has been designed from day one to offer a unique platform for managing the quality of software, systems and devices. With its built in support for key quality management features such as requirements management, test case management and traceability, risk management, risk analysis and risk-based testing, as well as defect/problem management and verification and validation, SpiraPlan has been designed to support current-state CSV activities as well as be ready to assist organizations as they transition to CSA. To better illustrate this, we shall consider the example scenario from the FDA CSA guidance:

A medical device manufacturer has decided to implement a commercial business intelligence solution for data mining, trending, and reporting. The software is intended to better understand product and process performance over time, in order to provide identification of improvement opportunities. The following features, functions, or operations were considered by the manufacturer in developing a risk-based assurance strategy.

Requirements Management

The following features and functions were identified in the system being considered (just a subset of the total):

Inside each requirement, we have clearly identified the intended use of the feature. This could be done either as a section of the main text (as shown above) or as a separate text field if preferred:

Now that we've identified the Features, Functions, or Operations and the associated Intended Use of the Features, Functions or Operations, we can now do a risk-based analysis to determine if this functions pose a high process risk.

Risk-Based Analysis

Once a manufacturer has determined that a software feature, function, or operation is intended for use as part of production or the quality system, the FDA recommends using a risk-based analysis to determine appropriate assurance activities. Broadly, this risk-based approach entails systematically identifying reasonably foreseeable software failures, determining whether such a failure poses a high process risk, and systematically selecting and performing assurance activities commensurate with the medical device or process risk, as applicable.

In this case, using SpiraPlan's risk management module, we identified the following risks associated with this feature:

We have analyzed the risk and due to the data impacts to safety, the impact was rated 5 - Catastrophic and the Probability was rated 3 - Possible, giving an overall Exposure of 12.

As a first step in documenting the necessary assurance activities, we captured the risk mitigations that will be useful in reducing the probability of such a failure:

The final step in this part of the process is to associate this risk to the originally identified requirements. In this example, we only had a single risk, but in most cases there will be more than one:

With this done, we can now run a requirements - risk exposure report to get the aggregate risk for each of the features in the system:

This has identified both requirements as having a relatively high process risk. Therefore we need to determine and apply the appropriate assurance activities...

Determine Assurance Activities

Once the manufacturer has determined whether a software feature, function, or operation poses a high process risk (a quality problem that may foreseeably compromise safety), the manufacturer should identify the assurance activities commensurate with the medical device risk or the process risk. In cases where the quality problem may foreseeably compromise safety (high process risk), the level of assurance should be commensurate with the medical device risk.

The manufacturer determined assurance activities commensurate with the medical device risk and has performed an assessment of the system capability, supplier evaluation, and installation activities. Additionally, the manufacturer establishes a detailed scripted test protocol that exercises the possible interactions and potential ways the functions could fail.

Using SpiraPlan, in this example, we would define the various test cases (both unscripted and scripted, both automated and manual) that adequately mitigate the identified risk:

Furthermore, using the risk-based testing approach, we can even see the total risk mitigated by each test case being executed:

This is useful for verifying the coverage of risks by test cases.

Note: Manufacturers are responsible for determining the appropriate assurance activities for ensuring the software features, functions, or operations maintain a validated state. The assurance activities and considerations noted above are some possible ways of providing assurance and are not intended to be prescriptive or exhaustive. Manufacturers may leverage any of the activities or a combination of activities that are most appropriate for risk associated with the intended use.

Establishing the Appropriate Record

Finally, once this has all been put in place, SpiraPlan lets you execute the defined test cases and log results along with associated defects. As per the FDA, documentation of assurance activities need not include more evidence than necessary to show that the software feature, function, or operation performs as intended for the risk identified. The FDA recommends the record retain sufficient details of the assurance activity to serve as a baseline for improvements or as a reference point if issues occur.

Typically you would include the following:

SpiraPlan provides all of these necessary features and data records as part of its test execution and defect tracking modules:

when executing you can record the necessary results:

and log defects / non-conformities at the same time:

Furthermore, for specific types of testing, other Inflectra products can assist:

Exploratory Testing - SpiraCapture is a free add-on that streamlines the capture of exploratory testing sessions and observations.
Automated Scripted Testing - Rapise is a rapid and easy to use automated testing tool for web, desktop, mobile and API applications.

Where Can I Learn More?

To learn more about the FDA's draft guidance on GAMP and Computer Software Assurance (CSA) please refer to their publication: https://www.fda.gov/media/162627/download
To learn more about GAMP, risk management and how SpiraPlan can be used to assist you in your move to CSA, please attend the upcoming webinar.

Using SpiraPlan for Risk-Based Testing

2022-11-15T16:47:58-05:00

Understanding Your Requirements' Risk Exposure

With SpiraPlan, you have the ability to create and manage both risks and requirements in the same system. You can use the Associations feature to link the requirements to risks. So, as part of a risk-based testing methodology, you will often want to see which of your requirements have the greatest overall, aggregate associated risk. Using the custom report in this KB article, allows you to quickly and easily generate such a view directly in SpiraPlan:

Understanding Your Test Cases' Risk Exposure

Similarly, with SpiraPlan, you have the ability to create and manage risks, requirements, and test cases in the same system as well. You can use the Associations feature to link the requirements to risks, and the test coverage feature to link requirements to test cases. Consequently, as part of a risk-based testing methodology, you will often want to see which of your test cases have the greatest overall, aggregate associated risk; if you are limited in time, these are the most critical tests to execute. The custom report in this KB Article generates such a view for you quickly and easily.

Viewing the Traceability Between Risks and Requirements and Test Cases

In addition to the display of the aggregate risk exposure of your requirements and test cases, sometimes you want to be able to report on the individual risks associated with each of your requirements and test cases. Using the associations features mentioned above, you will have the traceability between requirements and risks visible inside SpiraPlan:

Similarly, using the test coverage functionality, you will be able to see which test cases are mapped to these same requirements:

So if you put these together, you can run a Requirements - Risk Traceability Matrix and a Test Case - Risk Traceability Matrix using SpiraPlan to get this information in a simple tabular form:

Requirements - Risk Traceability Matrix

The following report shows each of the requirements (name and ID) along with the list of associated risks, with the risk impact, probability, and overall exposure:

Test Case - Risk Traceability Matrix

The following report shows each of the test cases (name and ID) along with the list of associated risks, with the risk impact, probability, and overall exposure:

The risks are those indirectly linked to the requirements that the test cases are themselves linked to. It would be easy to change the report to also consider direct risk - test case links as well.

Get $50 for Reviewing SpiraPlan on G2.com

2022-11-14T16:40:26-05:00

We have partnered with G2.com - the world-class software review platform, to collect SpiraPlan reviews from our loyal customers and users.

But why should you care about reviewing SpiraPlan, you ask?!

It is no big secret that product reviews play a significant role for companies like Inflectra as far as our credibility is concerned. Reviews are also an excellent resource for prospective customers to understand our software platforms’ pros (and cons, sigh). We use Spira and Rapise reviews to increase the global tech audiences’ positive perception of our solutions, thus improving our brand recognition and brand awareness.

We believe there should be a balance in the universe. So, as a thank you for writing the SpiraPlan review, the first 20 users will receive a $50 e-gift card of their choice. Everyone wins, YAY!

Review SpiraPlan now!*

Please note that the review campaign is run from LinkedIn and will end on November 11, 2022.

Please hurry!

Can’t get involved right now?

No worries! Sign up for our newsletter to stay up-to-date with all Inflectra events and goings-on!

Thank you,

Team Inflectra

*Some vendor-imposed limitations may apply.

Webinar Recap: Blockchain Development & Innovation in the Banking and Finance Industry

2022-11-28T10:38:19-05:00

TOPICS DISCUSSED

Current state of traditional Banking & Finance space
Software development & testing challenges
Blockchain solution in the Banking & Finance space
Benefits of blockchain implementation in the industry
Inflectra and BLOOCK technologies: application scenarios & Spira's integration capabilities
Questions from the audience

WEBINAR RECORDING

WEBINAR PRESENTATION

Blockchain Development and Innovation in the Banking and Finance Space Webinar Presentation.pptx from Inflectra

NEVER MISS AN EVENT AGAIN

Simply sign up for our newsletter to stay up-to-date with all Inflectra events!

#TeamInflectra

Inflectra In The News - October 2022 Roundup

2025-03-29T16:40:15-04:00

Awards

North American Software Testing Award, Finalist for Leading Vendor category - October 2022

The North American Software Testing Awards honor Inflectra for accomplishing significant achievements in the software testing and quality engineering market. Inflectra is a finalist for Leading Vendor. The North American Software Testing Awards honor companies, teams, and individuals who have accomplished significant achievements in the software testing and quality engineering market.

Talks and Presentations

Top Ten Tips for Tackling Test Automation: Partner webinar with Checkpoint Technologies - October 11, 2022

On October 11, 2022, Inflectra and Checkpoint Technologies co-hosted the webinar: Top Ten Tips for Tackling Test Automation. In this webinar, Adam Sandman (Inflectra) and Bob Crews (Checkpoint Technologies) explored the challenges surrounding test automation and offered tips to overcome them.

If you missed the webinar, we have a full recap. Read more.

Articles

Tackling the Current Issues in Risk Management with IT Briefcase - September 29, 2022

As the world becomes increasingly digitized, companies must adapt their risk management practices to account for new risks associated with technology, security, and operations. Inflectra builds software solutions that support companies in managing risks efficiently and effectively. Why should the issue of risk management be a constant key concern? Read more.

A Conclusive Rapise Automation Tool Tutorial with Codoid - October 18, 2022

Test automation is a crucial part of software testing as it enables the testers to automate repetitive tasks and use the saved-up time to unearth hard-to-find bugs with exploratory testing and other methods. This is what we, as a leading automation testing company, do to enhance overall quality. But achieving truly reliable automated testing that requires no supervision is no easy task and might even seem impossible to many. That is where tools such as Rapise come into the picture, as they simplify the process of automating your tests. So in this Rapise Automation Tool Tutorial, we will be sharing with you how you can use the tool to test your web and desktop applications. Read more.

Risk Management Is Key for the Food and Beverage Industry Amid Inflation with Food Engineering - October 28, 2022

The food and beverage space is arguably the industry most touched by consumers worldwide. From changes in consumer taste to diet trends and so much more, there’s no doubt that the food and beverage landscape is ever-changing, with consumers and health regulators being ever more discerning. This presents a unique challenge for industry professionals. Unlike some other industries, there’s zero tolerance for mistakes. Varying dietary restrictions, allergens, and rigid FDA guidelines are just a few reasons a robust risk management system is necessary to put consumer safety at the forefront. Read more.

The Risks of Trusting Machines to Check Themselves with AI Business - October 28, 2022

We are surrounded by risks every day, in every organization, and with every activity, we undertake. The field of risk management is a discipline devoted to identifying, quantifying, and managing risks so that we as humans can live safe, secure, and happy lives. Every time we fly in a plane, drive a car, swallow a pill or eat a salad, we are relying on the tireless work of risk managers to make that activity safe while keeping things cost-effective. Read more.

Stay in the know!

Recap: Testing Talks in Melbourne, Australia and Sydney / Melbourne Brekkies

2022-10-27T04:41:17-04:00

Inflectra Meetups in Sydney and Melbourne

Sydney

The Inflectra team coming from the USA included both our CEO Adam Sandman and our Director of Global Alliances, Jessica Moore. For us, it was our first time visiting Australia, and we were super-excited to visit Sydney for the first time, seeing the iconic Harbour Bridge and Opera House.

After a weekend of sightseeing and getting acclimated to the new time zone and season (from Autumn to Spring in 23 hours!), we met up with our local Regional Manager - Peter Brackstone, who flew down from Brisbane to meet up with the US team. It was a wonderful reunion, as we had not seen Peter face to face (because of the Covid pandemic) since InflectraCon 2019 in Cincinnati.

The next morning was the first of our two networking breakfast events (aka "Brekkies") where we outlined Inflectra's plans globally (and for the region), met with local partners and potential partners, and also spent some time listening the ideas and concerns of our customers in Sydney.

After some additional one on one meetings in various locations in Sydney (excellent train system, thank you Sydney Trains, one of our local customers!), the team packed their bags, gave a tearful farewell to Sydney, and took a flight to Melbourne, ready for the second networking breakfast and the main Testing Talks conference.

Melbourne

In contrast to Sydney, which reminded us a bit of London with "different" weather, beaches and excellent food and wine, Melbourne felt more like an international city, which was an interesting contrast. Locals had assured us that the food and coffee (in particular) was much better than Sydney. In the interests of good relations with all our customers (those in NSW and Victoria), we shall say we enjoyed both equally :-).

At the convenient Pan Pacific hotel, located next to the conference center, we had our second networking breakfast with local partners and customers.

After this, the team got some rest and prepared for the main event - Testing Talks 2022.

Testing Talks 2022 - The Reunion

Originally scheduled for 2020, Testing Talks the Reunion was a long anticipated event for both the local Inflectra team and the company as a whole. Due to the Covid pandemic, it had been rescheduled several times, and people were itching to get back to meeting each other face to face. The original estimated size was about ~250 people, but it ended up being almost twice as big with ~ 410 people registering. Incidentally this was the same venue, where we sponsoring and attended Australian Testing Days in 2018.

The Event itself was almost twelve hours of constant stimulation - meeting attendees, discussing their quality management and test automation needs, demonstrating our products (Spira and Rapise) on the interative iPads, listening to people talk about their pain points and ideas for improving testing. As you can see from the photo below, we were one of only 8 platinum sponsors, allowing us to have lots of face time with attendees as well as meet other sponsors to discuss partnership opportunities.

In the photograph above, you can see Emma giving our some swag and answering questions. This year our swag focused a lot on useful items vs. wasteful giveaways that end up in the rubbish bin. For example, we had our famous "James Bond" pen, wireless phone charging pads, and our new Zoom vanity light to make you look beautiful on all video calls.

Here's the team just before attendees arrived, with the booth looking pristine and ready fro action. Below, is the same booth, as the attendees arrived to learn more about our products.

Finally, at the end of a long but satisfying day, here's Adam Sandman, our CEO, giving out the Inflectra prizes for the "passport" game, Apple Airpods!

Thank you to Cameron for organizing the conference and making it such a success. Thanks also to Peter and Emma, our local Inflectra representatives who made everything run so smoothly.

Takeaways From The Trip

During the breakfast meetups, one on one meetings and the conference, we had lots of interesting discussions on how the Australian testing market is different to that in America and Europe. In no particular order, here's some of the findings:

There has been a large shakeup of the local IT industry, with large IT multinationals such as Infosys and Wipro acquiring a lot of local, Australian companies. That has in turn, opened up the market for other newer Australian companies to rise and fill the gaps created by the acquisitions.
There has been a move away from considering testing and test management as a separate activity, due to companies being agile. Instead there is a move to quality engineering.
Unlike the US and European markets, companies are not typically setting up testing centers of excellence (CoEs). Instead, testing is being embedded solely in the agile teams themselves.
The ANZ economy itself is mostly comprised of either extraction or service industries (vs. manufacturing) so a lot of heavy-duty requirements management and ALM / PLM tools that are common in the US or Europe are not prevalent. The main exception to this is in large legacy government IT projects.
Lot of people had heard of SpiraTest and were either using it in their organizations currently, or had used it in past or at RMIT University.
There was a significant interest in test automation particularly for complex applications like Salesforce because it is hard to automate with open source tools like Selenium because of its DOM.
There was a lot of concern around test data management, particularly in light of the recent large data breach at the telecommunications company Optus, that had been improperly using production data for testing.
The concern about security and data breaches also manifested itself in a lot of interest in risk management and risk-based testing approaches.

AG Grid Support in Rapise 7.4

2022-10-25T15:33:50-04:00

What is the AG Grid?

The AG Grid, is one of the most used grids in modern Web Applications. It can be placed both inside Light DOM and Shadow DOM (e.g. in applications using Polymer).

Rapise Support for AG Grid

Rapise 7.4 introduces the DOM AgGrid library that adds support for the AG Grid. If you have such a grid in your application just enable the library for your test.

You simply choose the libraries you need for recording and playback from the Libraries menu option:

Once the library is enabled, Rapise will be able to record your interactions with the AG Grid.

The recorded Grid object is added to the object repository and you can use all its actions and properties in your test.

A detailed API reference is available here.
https://rapisedoc.inflectra.com/Libraries/AgGrid/

Rapise 7.4 Spotlight: 64-Bit Support and Cross-Application Recording

2022-10-25T14:45:29-04:00

Multiple Applications

It is becoming increasingly frequent for us to see requests to record tests involving several heterogeneous applications with Rapise.

For example, you have a CRM with a web interface and you need to use an invoice number from an accounting program written in Java.

It was possible to create such tests before, but required a certain level of skill with the tool (using sub-tests, with a different test for each application).

Since Rapise 7.4 this process is now completely streamlined. You just need to choose all the libraries involved in the next recording via the new and improved library chooser:

And then you may just click, type & learn the widgets of the selected applications.

Embedded UI Technologies

It is more and more common to have different GUI technologies embedded into each other. For example, Chromium is embedded in such well known apps as Skype, Teams, Evernote. So you run it as a desktop application while it has a web browser as a presentation engine.

Or it is common to have Windows Forms widgets being embedded into WPF applications and vice versa. For example, Rapise itself is a Windows Forms application that has Chromium embedded into the Dashboards, WPF used for REST editor that contains Windows Forms for POST editor:

So we have Windows Forms inside WPF inside Windows Forms, if it isn't true nesting then what is true nesting?

And Rapise now knows how to work with nested widgets like that. Improved automatic detection of the best connector for a particular widget makes recording of such applications much easier.

Java 64, Windows Forms 64, Mixed Mode

From now on it does not matter whether you run your Microsoft .NET or Java UI in 32 or 64 bit mode. You don’t need to worry about it and you can mix different “bitness” and different technologies in one recording session.

Rapise detects the best match from the list of the libraries enabled in the current test automatically.

Web Components Support in Rapise 7.4

2022-10-31T09:58:41-04:00

What are Web Components?

Web Components is a set of different technologies that enable developers to isolate markup, code and style of reusable components and thus avoid collisions. A simple example of a collision is when styles from one reusable component turn the visual representation of another component into a mess.

For a test automation tool it is important to support those technologies that affect the browser DOM and how the XPath and CSS selectors work. This is why Rapise now includes support for the both Shadow DOM and SLOT elements.

Concepts and usage

As developers, we all know that reusing code as much as possible is a good idea. This has traditionally not been so easy for custom markup structures — think of the complex HTML (and associated style and script) you've sometimes had to write to render custom UI controls, and how using them multiple times can turn your page into a mess if you are not careful.

Web Components aims to solve such problems — it consists of three main technologies, which can be used together to create versatile custom elements with encapsulated functionality that can be reused wherever you like without fear of code collisions.

Custom elements: A set of JavaScript APIs that allow you to define custom elements and their behavior, which can then be used as desired in your user interface.
Shadow DOM: A set of JavaScript APIs for attaching an encapsulated "shadow" DOM tree to an element — which is rendered separately from the main document DOM — and controlling associated functionality. In this way, you can keep an element's features private, so they can be scripted and styled without the fear of collision with other parts of the document.
HTML templates: The <template> and <slot> elements enable you to write markup templates that are not displayed in the rendered page. These can then be reused multiple times as the basis of a custom element's structure.

The basic approach for implementing a web component generally looks something like this:

Create a class in which you specify your web component functionality, using the class syntax.
Register your new custom element using the CustomElementRegistry.define() method, passing it the element name to be defined, the class or function in which its functionality is specified, and optionally, what element it inherits from.
If required, attach a shadow DOM to the custom element using Element.attachShadow() method. Add child elements, event listeners, etc., to the shadow DOM using regular DOM methods.
If required, define an HTML template using <template> and <slot>. Again use regular DOM methods to clone the template and attach it to your shadow DOM.
Use your custom element wherever you like on your page, just like you would any regular HTML element.

Shadow DOM

A Shadow DOM component defines a DOM subtree that is not accessible by XPath and CSS selectors originating from the DOM tree that includes the component. A Shadow DOM tree is placed under a Shadow Root element in the parent DOM. It is important to understand that there are two Shadow Root modes: open and closed. The internal structure of a Closed Shadow DOM is completely inaccessible from the outside and we can do nothing about it. But most of the Shadow Roots in use typically have the Open Shadow DOM mode and it enables the usage of JavaScript code and CSS selectors to access its contents.

#1 Rapise shows Shadow DOM in the WebSpy.

#2 Rapise supports selectors that may dig into Shadow DOM. For this purpose use @#@ delimiter. For example:

//guid-generator@#@css=input#editField

Note: selecting an element within the Shadow DOM requires CSS selectors. The use of XPath is not supported.

#3 The WebSpy in Rapise 7.4 allows tracking elements within Shadow DOM. Such elements are highlighted with a red border (as any other element) and in addition they are filled with pink shading.
#4 Rapise 7.4 supports recording for Shadow DOM elements.

SLOT Element

The <slot> HTML element—part of the Web Components technology suite—is a placeholder inside a web component that you can fill with your own markup, which lets you create separate DOM trees and present them together.

The <slot> element is an insertion point in the Shadow DOM that can be filled with the content from the Light DOM (the term Light DOM is used to distinguish the standard DOM from the Shadow DOM). Since SLOT content contains the Light DOM - its nested elements can be accessed with XPath and thus the Shadow DOM border becomes transparent.

#1 Rapise shows child elements of a SLOT element in the Web Spy.

#2 Rapise generates minimized selectors for SLOT nested elements.

Webinar Recap: Top Ten Tips for Tackling Test Automation

2022-10-20T12:43:14-04:00

TOPICS DISCUSSED

Top 10 challenges of test automation with impact and solutions
- Impacts: potential risks if challenges are not overcome
- Solutions: tips to overcoming the challenges
Automated functional testing
Criteria of an Automation Assessment
Addressing several challenges with Inflectra's Spira and Rapise

WEBINAR RECORDING

WEBINAR PRESENTATION

Top Ten Tips for Tackling Test Automation Webinar Presentation.pptx from Inflectra

NEVER MISS AN EVENT AGAIN

Simply sign up for our newsletter to stay up-to-date with all Inflectra events!

#TeamInflectra

StarWest 2022 - It's a Wrap, Folks

2022-10-18T09:36:34-04:00

Starting the conference the right way:

Everyone loves a good meet and greet at the beginning of the conference. If your company kept you from conferences because of the last two years’ events, you would crave the camaraderie and playful banter characteristic of Techwells’s welcome receptions. StarWest meet and greet was no exception. Icebreaker games and complimentary beverages made the reception even more engaging. Great conversations led to new connections and budding friendships.

Inflectra at the expo:

The STARWest organizers know how to treat their sponsors and partners. The expo was well managed, and the refreshments were bountiful. The Inflectra booth was strategically located close to all the delicious refreshments, including Mickey mouse ice cream bars.

The Inflectra booth was packed with our awesome swag and smiling team members. We were glad to meet and talk shop with so many of you.

Presenting at StarWest 2022:

Being selected to speak at StarWest is no mean feat. The selection committee is wise and discerning. So it was super exciting to have Inflectra’s CEO Adam Sandman present his talk about Software Architecture for Testers – Where the Bodies are Buried! to the StarWest 2022 audience. The talk was well attended and well received, with lots of interesting questions asked and answered.

Supporting Leadership Summit:

Leadership summit & reception is the crown jewel of every techwell event. For the second time this year, Inflectra sponsored this pre-summit reception. The reception is a great way for the summit attendees to come together and work out the objectives of Leadership in Software Testing training the following day. Team Inflectra spent a few minutes greeting the attendees and thanking the organizers on October 6, 2022.

Location, Location, Location

StarWest takes place in the Disneyland Hotel, steps away from downtown Disneyland and parks. Need we say more?

(shoutout to Angel Williams for the photo of TIE Whisper above)

Stay tuned for more adventures of the Inflectra Team.

Risk Management and Software Quality: Expert Panel Webinar Recap

2022-12-09T17:58:16-05:00

CHALLENGES OF ADOPTING AGILE FRAMEWORK IN WEST AFRICA

Mr. Adewale set the stage for the webinar when he stated that “Agile is the famous buzzword within the financial industry in West Africa.” He emphasized that there is a gross misalignment between technology and business and used the term “Irresponsible Programming” to highlight how quality is compromised in Agile approaches. When releasing functionality to the market faster is prioritized without first assessing the impact of risks on these functionalities, quality begins to slip. Mr. Texeira also raised the related issue where organizations often implement Agile frameworks in one or two departments alone, siloing themselves from other departments. This causes issues down the line when, for example, the HelpDesk team, who did not adopt agile practices, is not able to relate and provide the required critical feedback for product teams.

Mr. Texeira recounted another issue he sees in Agile adoption, when Agile team members are not exposed to the risk management principles but focus only on their domain knowledge and rely on outside processes for risk and compliance. In some organizations, the team members play a “Hierarchy Game” where they implement numerous steps in the approval of business requirements, test case development, or defect triaging. The unavailability of the persons required in this multi-step workflow approval creates a longer waiting time and bottleneck effect. Some reasons for this multi-step process involve excessive process controls denouncing self-organization within the team or the lack of team member’s cross-functional knowledge to account for risks.

Mr. Omoresemi strategized that both the “Irresponsible Programming” and “Hierarchy Game” further compound the challenges with the “multiplier effect.” When leaders fail to develop the culture and mindset of employees in understanding risk management, quality management, and domain knowledge, the employees don’t understand the impact of failing to mitigate risks and the harmful results from poor quality releases. The lack of understanding the total cost of ownership multiplies the problems exponentially.

CHALLENGES IN THE BROADER AGILE COMMUNITY

These observations are not far from the findings that the Agile community faces, said Dr. Rajagopalan. Even the State of Agile surveys done between 2018-2021 show that the alignment between Business and IT Globally has been hovering around 47-50%. “Failing fast should not be the focus, but rather, failing forward,” said Dr. Rajagopalan. Security principles are compromised where plaintext passwords are part of the programming modules because the user story is only a proof of concept and the acceptance criteria doesn’t preclude ‘backdoor’ security principles to be accounted for! So, it is not that Agile itself has failed but rather that people have failed Agile due to their lack of Agile framework understanding.

ADDRESSING THESE CHALLENGES

“When it comes to binding regulations, the agencies creating and upholding the regulations are always catching up based on how technology is progressing,” said Mr. Texeira. He recalled how some of the countries in the African continent still do not recognize the Cloud Technology-related trends. Mr. Adewale also highlighted that the Central Bank of Nigeria has introduced the IT BluePrint Standards requiring compliance and governance on the strategic end, and traceability and audit trail on the execution end.

Similar to General Data Protection Regulations (GDPR) popular in the European Union, Mr. Adewale also mentioned Nigeria Data Protection Regulations (NDPR). Mr. Omoresemi talked about the enforcement at all levels where not only companies but also their employees need to be the “voice of testing” in establishing guidelines and guardrails. To be quality champions, employees must learn about the influence of risk on their responsibilities.

“Doing things manually helped us realize the pain points,” recalled Mr. Texeira. He had this realization when he began an extensive search on a tool that provides transparency and traceability across all the areas of both software development and project management. Although each organization is different, Mr. Omoresmi mentioned the focus of the organizations in using the total cost of ownership as a critical consideration while selecting the tool. Mr. Adewale highlighted that the teams should ask themselves three questions when selecting the tool:

Is the tool allowing them to do the right thing?
Is the tool allowing them to do things right?
Is the tool providing visibility for how well things are getting done?

Connecting these thoughts with Drucker’s principles of effectiveness (leadership) and efficiency (management), Dr. Rajagopalan concluded the session that tools should not just focus on pricing or their selection be based on one’s comfort zone, but many other factors, such as the cloud and on-premise support, framework agnostic outlook, business process support, and end-to-end lifecycle management. The panelists and the moderator put a major limelight on how the areas of risk management play a critical role in software quality management in today’s emerging regulatory landscape regardless of the project delivery framework.

This webinar is a joint effort between Tezza Business Solutions and Inflectra.

Interested in doing a joint event or webinar with Inflectra? Contact partnerships@inflectra.com.

Adam Sandman, CEO of Inflectra, Interviewed by Big Business Show

2022-10-03T13:15:02-04:00

Our very own Adam Sandman was interviewed by Bob "Sully" Sullivan and Russ T Nailz from the Big Biz Show. During the interview, Adam informs viewers about quality and risk in mission-critical and safety-critical industries. Between the comedic tone and unique setting (a bar), listeners felt as if they were hearing a conversation about Adam's professional history, Inflectra's products and capabilities, and other software topics between a few friends on their night out - it was a one of a kind opportunity!

If you want to be entertained, informed, and witness this fun interview - view more to access t.

Recap: Application Lifecycle Management Scenarios with SpiraPlan

2022-09-25T22:40:18-04:00

Configuration & Change Management

Application Portfolio Management

Application Portfolio Management attempts to use the lessons of financial portfolio management to justify and measure the financial benefits of each application in comparison to the costs of the application's maintenance and operations. Learn More About Application Portfolio Management.

Application Decommissioning

Application Decommissioning is a strategic approach for systematically retiring outdated and costly legacy applications—without compromising business needs or compliance requirements. Learn More About Application Decommissioning.

Project Portfolio Management

Demand Management

Demand management is the process an organization puts in place to internally collect new ideas, projects, and needs during the creation of a portfolio. Demand management is successful when the final output is useful to prioritize and select a valuable strategically aligned portfolio. The more the process is able to capture the real strategic commitment of the organization and merge it with the past ongoing activities, the more demand is a success factor in building the correct portfolio. Learn About Demand Management.

Value Stream Management

Value Stream Management (VSM) is a method that allows you to optimize the steps necessary to envision, implement and deliver software to your customers. Value Stream Management is a management technique or practice - common in Scaled Agile frameworks such as SAFe - that focuses on increasing the flow of business value from customer request to customer delivery. Its systematic approach to measuring and improving flow helps organizations shorten time-to-market, increase throughput, improve product quality, and optimize for business outcomes. Learn More About Value Stream Management.

Vendor Selection & Management

Vendor selection involves looking past surface-level sales and marketing gimmicks to see what the vendor really has to offer its clients. While a vendor may offer the goods or services that a company needs, customer service may be lacking, which will ultimately affect the vendor-business relationship. Learn More About Vendor Management.

Supplier Qualification

Supplier qualification is the process by which a company will choose the correct supplier/third-party vendor for components/raw materials/services based on its requirements and regulatory protocols. Learn More About Supplier Qualification.

Inflectra In The News - September 2022 Roundup

2022-10-07T16:15:11-04:00

Publications

Top 3 Software Challenges for the Banking Industry with Bank Automation News - September 7, 2022

The banking industry presents a unique challenge when developing and testing software. In recent years, cloud technologies and software-as-a-service (SaaS) have become critical components of the industry’s digital adoption and are crucial for banking brands to remain competitive. And in a multinational sector like banking, software must be incredibly secure and reliable while also fast, integrated, and open to enable real-time global communication. Read more.

TV Appearances

Big Business Show: Interview with Adam Sandman, CEO, Inflectra - August 2022

Talks and Presentations

Security as Risk: Conversations on Risk Management - September 15, 2022

With the proliferation of the 4th Industrial Revolution (4IR), this panel had a live conversation on security as a risk. In the era of data privacy and regulatory compliance, the challenges and solutions for security risks must be thoroughly understood, weighed, and mitigated. In the second event of the series, the experts will discuss the increasingly significant role Risk management will play in developing products and processes. Read more.

Test Automation & Digital QA Summit 2022 - September 23, 2022

Adam Sandman, the Inflectra CEO, presented “Are You Ready to Run the Risk - Introduction to Risk Based Testing” at the recent TestingMind Test Automation and Digital QA Summit 2022 (#TAS22) in Washington, DC. Read more.

Inflectra has more exciting plans for the rest of the fall; stay tuned to see what is in store!

Webinar Recap: Alternatives to Legacy Tech Solutions: The Case Of MicroFocus

2022-09-28T11:56:57-04:00

TOPICS DISCUSSED

Recent disruptions in tech: challenges, risks, and opportunities
Top tools on the market
Better value all around: alternatives to Micro Focus suite
- Application Lifecycle Management: SpiraPlan for QA, Requirements, Program, Portfolio & Risk Management
- Functional and performance testing: Rapise and OctoPerf (displacing UFT and LoadRunner)
Non Feature differentiators of Inflectra
Smooth Transition to the Inflectra platforms: migration assistance, implementation services, custom training, and technical assistance from Inflectra

WEBINAR RECORDING

WEBINAR PRESENTATION

Alternatives to Legacy Tech Solutions: The Case of Micro Focus Webinar Presentation.pptx from Inflectra

NEVER MISS AN EVENT AGAIN

Simply sign up for our newsletter to stay up-to-date with all Inflectra events!

#TeamInflectra

Using SpiraPlan for Configuration & Change Management

2022-09-29T15:59:57-04:00

Before we discuss how SpiraPlan can assist with both change and configuration management, we first need to clarify the similarities and differences between these two key areas:

Change Management
Configuration Management

As described in this great guide "Configuration Management vs Change Management", “Change Management” is how you manage changes related to project management plans, processes, and baselines, whereas "Configuration Management" is how you manage changes related to product scope. Note that there are many similarities and interconnections between the two.

Therefore a change control process should be designed to handle both change and configuration management, since a request to change the schedule of a project might require a corresponding change in scope (for example).

Change Management Overview

Change Control is focused on identifying, documenting and controlling changes to the project and the project baselines. In the change management system, you manage the changes related to the project scope, planning, and baselines. For example, you run out of money and you need additional funding to complete the project, therefore, you will raise a change request for additional funds. Or, you may not be able to complete your project within the specified time and require a time extension. In the change management system, the change request is analyzed for any possible impact on any other project objectives. Afterwards, the request is either approved or rejected. To minimize disruption, a change management system must ensure that all parameters are identified and analyzed for any possible impact. If the change request is approved, you will update the concerned baseline, update the project documents, and inform the concerned stakeholders.

Change Management Activities

You do the following during change management:

Identify the changes.
Prepare a proper documentation for the changes.
Review, analyze, and make a decision for the change request.
Make sure that request is implemented, registered and communicated.

Configuration Management Overview

Configuration Control focuses on the specifications of both the deliverables and the processes. In the configuration management system, you manage the changes related to the product specification and the process. For example, suppose you are developing a product and the client requests the addition of some extra features. Since this change is related to the configuration of the product, you will deal with this change using the configuration management system. Configuration management documents how you will monitor and control changes. It; i a process of defining configurable items (product, service, result, and component) and controlling changes to such items. The configuration management plan keeps version control of the product. It's critical for effective application development, especially when you need to understand the security of your software supply chain, and plan for unanticipated side effects and risks associated with making changes.

Configuration Management Activities

You do the following during configuration management:

Identify the configurable items.
Record and prepare a report for all configurable items.
Verify and conduct an audit of all configurations are as per the requirements.

What is a Change Control Board (CCB)?

In software development, projects and programs, a Change Control Board (CCB) is a committee that consists of Subject Matter Experts (SMEs) and Managers who decide whether to implement proposed changes to a project. The factors affecting a CCB's decision can include the project's phase of development, budget, schedule, and quality goals. The CCB will be responsible for making decisions related to both the plans/timelines and the scope/requirements, so a CCB is technically involved in both the change management and the configuration management.

The Change Control Board will review any proposed changes from the original baseline requirements that were agreed upon with the client. If any change is agreed upon by the committee, the change is communicated to the project team and the client, and the requirement is baselined with the change. The authority of the Change Control Board may vary from project to project, but decisions reached by the Change Control Board are usually accepted as final and binding.

What is a Change Request

A change request is a proposal to alter some aspect of a given project. Change requests can originate either internally or externally. For example, the client may request a change to the agreed-upon deliverables, or you may receive a change request form from a team member who’s actively working on the project. Either way, without a formal change request process in place, these proposals can easily get lost, buried, or simply overlooked.

Adjusting the scope or deliverables of a project without a proper change request process can also cause confusion and misalignment of the project team and project stakeholders.

The Steps in a Change Request Process

The key steps in a change request process should be something like:

Understand the requirement, scope or schedule change
Investigate the change to understand its benefits and impacts
Review the results of the investigation as part of the CCB
Approve (or reject) the proposed change
Implement the proposed changes
Test and verify the changes work as expected, document any side effects
Update the requirements, documentation, and other configuration items
Communicate the changes to impacted stakeholders
Release the changes into production

If you'd like to see a sample Configuration and Change Control Process using SpiraPlan, we have this useful whitepaper - Managing the Change Control Process with SpiraPlan.

Configuring SpiraPlan for Managing Change Requests

Incident Types, Statuses and Fields

The first step is to login to the system, choose the appropriate product/project, and create a new incident type called 'Change Request':

For now, leave this incident type pointing to the Default Workflow. We will change this later when we create the workflow.

Next, we can add any custom properties that are specific to a Change Request and are not part of the standard 'incident' template:

For example, you might want to add custom properties to track: high level risks, actions, criticality, and area.

Next, we need to add any incident statuses that will be part of this workflow. You can reuse any existing incident statuses that are present from other workflows (New, Open, Assigned, Closed), but you may want to add additional ones, for example: Approved, Rejected, Released:

Once you have the statuses added, the next step is to create the workflow itself.

Incident Workflows

Go to the Incident Workflow list for the project template and create a new "Change Request Workflow":

Next click on the 'Steps' button for this workflow and you will be able to see the various statuses and transitions between them:

You can now add transitions to link the different change request steps together in the workflow.

Furthermore, you can click on the transition and determine (by role) who can change the status of the change request. In addition, you can choose to require an electronic signature, if applicable.

You should also click on each of the change request steps / statuses and make sure that the appropriate standard fields and custom properties are visible, hidden, required, or default.

In the example above, we have made the custom property High Level Risks required.

Finally, go back to the list of incident types and change the "Change Request" type to use your new workflow:

You are now ready to submit your first change request.

Using SpiraPlan for Change Management

Now that we have setup the system, we can submit a sample change request.

Creating the Change Request

First you will go to the Incidents section of SpiraPlan and log a new incident. When you change the type to 'Change Request', the appropriate fields will be shown for that incident type:

Now you can complete the change request, attach any relevant documentation as an attachment and submit the request. You will also want to link the change request to any configuration items such requirements that are impacted via. Associations:

If the change request affects other configuration items such as documentation, you may also want to link it to the documents in the Attachments tab as well:

Reviewing and Approving

The change request is now assigned to a reviewer, who will then either approve or reject the item.

The workflow can have multiple review steps, and you can add the option to enforce an electronic signature. You can also require that they fill out certain mandatory fields after each change of status:

The approver might want to capture additional information in either the comments or special fields.

Any changes to the change request will be sent to all stakeholders using the notifications functionality:

You can add additional stakeholders to the change request, using the 'Add Followers' option.

Updating or Creating Requirements

Once the change request has been approved, you can then either use it to update the contents of the linked requirement:

Or alternatively, you can use the special option 'Create Requirement from Incident' to create a new requirement from the change request, and then nest that under the original parent requirement:

The benefit of this approach is that it lets you track each change to the requirement in a more granular manner, assign to a different release/sprint as the parent, and have different associated test cases.

Updating Code Assets

If the approved change request will affect code assets (e.g. in a software development project), you can tag the code commits with the relevant change request ID and requirement ID:

Or if you forget, you can always associate it after the fact inside SpiraPlan itself:

Identifying Risks

Finally, as part of the change control process, you will have identified possible impacts and side effects of the proposed changes. These can be logged into the SpiraPlan risk management module and then associated with the change request:

Using SpiraPlan for Configuration Management

In addition to managing the changes to the system requirements and other project artifacts, SpiraPlan can manage general configuration items in its document repository:

The document repository contains the ability to track the changes to documents, both the different versions of the document, as well as the changes to the various metadata fields:

You can link these configuration items to the different change requests, using the Associations tab.

Baselining Configuration Items

Finally, you can use the built-in SpiraPlan baseling feature to track all changes made to configuration items between different baseline snapshots:

Summary

In this article, you have seen how important it is to have a change management and configuration management process on a project. You have learned about the main steps in a typical change control process, and you have seen how to configure SpiraPlan to handle both your change management and configuration management processes.

Value Stream Management with SpiraPlan

2022-09-28T13:21:08-04:00

What is Value Stream Management?

In traditional organizational structures, individuals are organized into functional teams, and then temporary teams are formed to meet the demands of specific projects, borrowing individuals (or percentages of individuals’ time) from those functional teams. The temporary nature of the teams and organizations means that no one is focused on the long-term creation of value, no one has the overarching business goal in mind, and the opportunity to retain and grows skills in the team is lost.

From Project to Product

In contrast to this approach, VSM promotes the idea of long-lived product teams (often called an Agile Release Train (ART)). With established value streams and long-lived teams of teams, people are assigned to one cross-functional team for the life of a product. However simply organizing people into products is not sufficient by itself. You also also need to be able plan, track and monitor the consistent flow of value from the original ideas to the delivered product. Consequently, a Value Stream (VS) itself is simply, the steps by which a business takes an idea and turns it into realized value. Typically a value stream is composed of multiple agile release trains, each of which will have multiple, individual agile teams.

For large, complex initiatives, you may have an intermediate grouping called a Solution Train (ST). The relationship between the items is as follows:

Value Stream - this represent the series of steps that an organization uses to implement Solutions that provide a continuous flow of value to a customer.
Solution Train - this is the organizational construct used to build large and complex Solutions that require the coordination of multiple Agile Release Trains (ARTs), as well as the contributions of Suppliers. It aligns ARTs with a shared business and technology mission using the solution Vision, Backlog, and Roadmap, and an aligned Program Increment (PI).
Agile Release Train (ART) - this is a long-lived team of Agile teams, which, along with other stakeholders, incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.

What is Value Stream Mapping

Value-stream mapping is a lean-management method for analyzing the current state and designing a future state for the series of events that take a product or service from the beginning of the specific process until it reaches the customer. The purpose of value-stream mapping is to identify and remove or reduce "waste" in value streams, thereby increasing the efficiency of a given value stream. Waste removal is intended to increase productivity by creating leaner operations which in turn make waste and quality problems easier to identify.

In order to evaluate the effectiveness of your software practices and tools, you need total visibility throughout the software delivery life cycle. Therefore value stream mapping should be a part of the overall lean approach that allows you to analyze the current state of your processes and build a better future state based on the series of events that take your product/service from initial concept to the finished product that the customer receives. This eliminates waste and allows you to prioritize based on your customers' needs.

Using SpiraPlan for Value Stream Management

SpiraPlan's hierarchical workspace structure supports the different levels outlined above: value streams containing solution trains, that themselves contain agile release trains:

The mapping we recommend is:

Portfolio => Value Stream
Program => Solution Train
Product => Agile Release Train

Furthermore, you can decompose each agile release train into multiple agile teams, which are essentially SpiraPlan top-level releases. These can then contain child releases and sprints.

Another option is to use the product components to represent the agile teams. This can be useful if you want to have multiple levels of release that are separate from team.

Then, within each of the agile teams, you can have sprints as is conventional in agile methodologies such as Scrum:

What's Planned In The Future?

This is just our initial implementation of SAFe and Value Stream Management. On the roadmap for SpiraPlan is the ability to have backlog items at the program and portfolio levels, allowing SpiraPlan to more easily track program increments, solution increments and have backlog items natively at the value stream and solution train levels.

Test Automation & Digital QA Summit 2022 Recap

2022-12-09T17:56:30-05:00

TAS or Test Automation & Digital QA Summit is a testing conference that focuses on software testing, test automation, and digital quality assurance. This conference is popular among QA enthusiasts and takes place in more than twelve countries across the globe.

The Washington, DC Summit showcased the trends, innovations, and challenges in the emerging world of Software and Automation Testing. The Digital transformation requirements and its focus on Quality Assurance amend the best practices of the Culture, Business Strategy, and Technology.

The Summit brought together people who are passionate about Automation testing and Quality Assurance in the Digital world.

The Summit is a key meeting place for Test Professionals and Executives from leading IT organizations. The event featured an inspiring day of talks by professional speakers focused on Test Automation innovation and the influence of Digital trends in Quality Assurance.

Ready to Run the Risk

One of the most underappreciated aspects of testing is risk. There is never enough time to do all the testing that would be needed for 100% coverage (this is true for automated testing and manual testing). Consequently, there is a tradeoff between spending time on different types of testing and focusing on specific features, modules or requirements. By applying a risk-based approach to testing, you can seek to optimize these trade-offs with a data-driven methodology.

In this talk, Adam discussed the different types of risk that you should be considering (technical, business, etc.) and how you can use the assessment of risk to create a test plan that gives you the greatest risk coverage in the time available. In addition, he covered prioritization techniques such as business feature importance, technical code stability, test stability, user flow and critical service mapping to determine where the risk lies in each software release and what testing should be done.

Software Testing Automation Frameworks & More

2023-03-25T18:57:29-04:00

The Importance of Automated Software Testing

In any modern software development, it’s necessary to automate parts of the process. There are several reasons for this, from computers being able to work 24 hours a day to the efficiency gains they can make over human/manual testing. Not only does it accomplish tedious and complicated tasks more effectively than a person, but it frees up your developers’ time to focus on other pieces of the process.

Factors To Consider When Deciding Whether a Test Should Be Automated

A developer’s time can be spent elsewhere because not all tests should (or even can) be automated. When deciding which test cases should be automated, some of the most critical indicators that it would be more efficient than using human resources include:

The task is going to be repeated
It’s going to save time
The requirements, the test, or the task are low risk, stable, and unlikely to change often
The test is subject to human error
The test is time-consuming
The test has significant downtime between steps
The test is repetitive
The test is business-critical

For more information, you can watch our video on this topic: From Manual to Automated Testing | Inflectra Webinar | Test Automation, Demystified

What Kind of Tests Are Best Done Manually?

Outside of those tests, a few types are tough to automate. Tests that are best done manually include:

Tests That Are Constantly Changing - Tests where the correct outcome changes frequently can’t be automated. Equally, tests where the outcome isn’t always clear.
One-Off Tests - Sometimes, you need to test to check a particular condition or to search for a reported bug. These ad-hoc tests aren’t suitable for automation. However, if you do find steps to recreate the bug, you may then want to automate the test.
Testing Features That Are Still Evolving - As new features are developed, you need to build your tests in parallel. It usually isn’t worth automating the test while the feature is evolving.

Automation Based on the Type of Testing

When we break down the categories that software testing can be grouped into, there are two primary types:

Automation of Functional Tests - These tests are written to test the business logic behind an application. Automating these means writing scripts to validate the business logic and the functionality expected from the application.
Automation of Non-Functional Tests - These tests define the non-business requirements of the application. These are the requirements related to performance, security, data storage, etc. These requirements can remain constant or can be scaled as per the size of the software.

Automation Testing Frameworks

An automation testing framework is a set of guidelines or rules for creating and designing test cases. A framework is comprised of a combination of practices and tools that are designed to help professionals test more efficiently. Utilizing a framework for automated testing will increase a team’s test speed and efficiency, improve test accuracy, reduce test maintenance costs, and lower risks. There are many frameworks to choose from, but here are some of the most common ones:

Linear Testing Framework (Record-and-Playback)

Linear Testing Framework is the most basic kind of framework. Testers write and run a test script for each test case, like recording and playing back a clip on a screen. Because of its simplicity, it is most suited for small teams and test automation beginners. With a linear test automation framework, testers don’t need to write code to create functions; the steps are written in sequential order.

Modular-Based Testing Framework

This framework breaks down test cases into small modules. Then, it follows a non-incremental and incremental approach. There, the modules are independently tested first, and then the application is tested as a whole. This makes each test independent. This sort of abstraction concept ensures that changes made to the other part of the application do not affect the underlying components. However, prior planning and test automation knowledge are required to implement this framework successfully.

Library Architecture Testing Framework

The library architecture framework for automated testing is based on the modular framework but has some additional benefits. Instead of dividing the application under test into the various scripts that need to be run, similar tasks within the scripts are identified and later grouped by function, so the application is ultimately broken down by common objectives. These functions are kept in a library, which can be called upon by the test scripts whenever needed.

Data-Driven Testing Framework

In this testing framework, a separate file in a tabular format is used to store both the input and the expected output results. A single driver script can execute all the test cases with multiple data sets. This driver script contains navigation that spreads through the program, which covers both readings of data files and logging of test status information.

Keyword-Driven Testing Framework

A keyword-driven testing framework is an application-independent framework and uses data tables and keywords to explain the actions to be performed on the application under test. This is also called a keyword-driven test automation framework for web-based applications and can be stated as an extension of a data-driven testing framework.

Hybrid Testing Framework

This form of the hybrid testing framework combines modular, data-driven, and keyword test automation frameworks. As this is a hybrid framework, it has been based on combining many types of end-to-end testing approaches.

Test-Driven Development Framework

This framework focuses on creating unit test cases before developing the actual code. It is an iterative approach that combines programming, the creation of unit tests, and refactoring. Developers start creating small test cases for every feature based on their initial understanding. The primary intention of this technique is to modify or write new code only if the tests fail. This prevents duplication of test scripts.

Behavior-Driven Development Framework

This framework derives from the Test-Driven Development approach, and in this method, tests are more focused and are based on the system behavior. The testers can create test cases in simple English. This easy-to-understand language helps even non-technical people to easily analyze and understand the tests.

Automated Testing Tools

Test automation tools help teams automate their software testing needs. Such software enables people to define testing tasks that subsequently run with as little human interaction as possible. They help in the efficiency of software development. See our list of the top automation testing tools for your best options. We include open-source, cross-browser, commercial test automation software, and more.

Steps To Choosing an Automation Tool

When choosing what tool is going to be the best fit for your needs, there are some basic steps that we recommend following:

Identify the types of tests you want to automate
Based on the types of tests you want to automate, plan the design of automation and move towards a framework.
Based on the kind of automation testing you are targeting and the type of framework that you may want to build around, you can select the tools that suit your needs.

Get a Powerful Automation Tool Out of the Box

It can be challenging to find a software testing tool that checks all of your required boxes, let alone the preferred ones that focus on the quality of life and ease of use. For an all-in-one solution that can easily integrate with your other tools and platforms, look no further than Rapise. Working across web browsers, desktop applications, and even on mobile devices, it easily automates any tests you need and makes it simple to update or edit them at any time. Ready to get started? Click the button below to get a free 30-day trial!

> Try Rapise 30-Day Trial Today...

Using SpiraPlan for Application Decommissioning

2022-09-22T11:13:45-04:00

Application Decommissioning Overview

In the Navy, ships are decommissioned when they are getting old, outdated and too costly to operate compared to more modern and effective alternatives. For example, over time all of the World War II era battleships have now been decommissioned and retired from service, replaced with modern cruiser and destroyer ships.

Interestingly, the same idea can be applied to old and outdated legacy applications in an IT department. Costly to operate and no longer used for production processing, such applications chew up budget that could be better used for something else. If we could decommission them like aging battleships, we could cut out a huge chunk of the IT maintenance budget.

The Application Decommission Process

First, it uses a rigorous process to analyze the application portfolio and identify the best candidates for decommissioning. This is based on a combination of their value to the business, the savings that can be achieved, and the cost to retire them. In general, the best candidates have valuable data that needs to be retained for a long time—thus offering longer-term cost savings—while not being overly difficult to deal with technically.

Building a Business Case

The business case for Application Decommissioning involves comparing the cost of maintaining the legacy application to the cost of decommissioning it. This allows us to calculate an ROI for the project over a given period of time, and also to see how fast the project costs can get paid back.

Configuring SpiraPlan for Application Decommissioning

This specific use case - application decommissioning - is an extension from the wider case of application portfolio management that we previously discussed. It assumes that you are already managing your portfolio of software applications and systems in such a way that you are able to obtain a clear idea of the value you derive from them in a quantifiable way. For example, lets consider the following application portfolio being managed by SpiraPlan:

In this scenario we are now looking to plan the decommissioning of specific application based on sorting and filtering the portfolio to find candidates. It assumes that we have already performed the portfolio management tasks and are now ready to begin the decommissioning process.

Typically, application decommissioning can be done by a guided process in terms of timeline, order of completion, mandatory and optional steps, standard operating procedures (SOPs), requirements and electronic signatures for any necessary approvals. We will use the SpiraPlan incident management and incident workflow system to handle this process.

Configuring Incident Workflows

The first thing we need to do is create a new SpiraPlan incident type called "Decommissioning Req" and create a new workflow that we'll use to manage the process:

You will also need to add additional incident statuses and steps for this process, including:

Approved
Rejected
Decommissioned

Once you have the additional statuses added, you can now link them into the new decommissioning workflow. This workflow will typically follow these steps:

New > Open
Open > Assigned
Assigned > Approved or Rejected
Approved > Decommissioned
Decommissioned > Closed

You can of course add additional steps if you need more sign offs in the decommissioning process.

Electronic Signatures

For specific workflow transitions (e.g. Assigned > Approved), you may want to require an electronic signature so that the person making the approval realizes that this is a binding decision. It also means you will have a auditable record of the approval that meets regulatory standards.

Electronic signatures require that the user approving the decommissioning request has to re-authenticate to make the approval and enter in the "meaning" for the signature. The change request record is then cryptographically hashed and stored with the change record inside SpiraPlan to avoid any tampering. This is similar to how the blockchain uses cryptographic hashes to authenticate transactions.

Creating a Decommissioning Request

Now that we have setup the incident type, statuses, and workflows, you can now create a new decommissioning request. In this example, we shall pretend that we're decommissioning Excel 2016 in favor of Excel365.

The incident type can have custom properties defined to capture any fields that are specific to a decommissioning request.

In addition, you will link this new decommissioning request to the requirement containing the application being affected using the Associations tab:

Managing Decommissioning Risks

One of the key aspects of application decommissioning is performing a risk assessment for the decommissioning process. SpiraPlan's built-in risk management functionality makes this very easy. You will simply identify the risks associated with each decommissioning request and associate them with the decommissioning request incident artifact:

In this example we are recording the risk that some reports using macros that have been deprecated in Excel365 and only work in the legacy version.

We are able to use the risk management functionality to document the probability and impact of this risk, as well as outline potential mitigations and action items (tasks). These risk are of course linked back to the source request.

Decommissioning Notifications

One key requirement for the decommissioning process is to ensure that timely notifications are sent to stakeholders:

Customizable notifications to stakeholders about the items or applications to be decommissioned need to be sent
Notifications about status changes of decommissioned items or application can be sent (e.g., for cancelling contracts with suppliers, deactivation projects in financial or relations/interfaces to other remaining systems).

Both of these needs can be fulfilled using the incident workflow notifications:

They provide fine-grained control over the steps in the decommissioning process and ensure that all stakeholders receive appropriate information.

Summary

In this article we have seen how we can extend the existing application portfolio management use case to include the specific needs for application decommissioning. We have seen that the built-in incidents functionality lets us create a custom incident type, workflow and associates statuses to track this process. Finally, SpiraPlan's unique features for electronic signatures, risk management and email notifications can be added into the process as needed.

Inflectra's Devopsdays DC 2022 Experience

2022-09-22T06:42:39-04:00

The conference was a success in many ways.

DevopsDays programming format with morning Keynote speakers, early afternoon Ignite talks, and afternoon Open Sessions where topics we selected by attendees each day offered great opportunities for learning, collaboration, and interaction.
Keynote and ignite topics included challenges faced in regulated industries (Government and Healthcare), striving for agile delivery, Chaos engineering, Microservices, Risk Evaluation, and people skills (team development, empowerment, ways to avoid burnout).

A standout talk that garnered a lot of discussion amongst the attendees was Marianne Belotti’s talk Killer Robots and Rogue AI: lessons for technologists from safety science which discussed the relevance of safety science research in developing and scaling systems.

John Willis, one of the co-authors of the book Investments Unlimited - A Novel which discusses an investment bank dealing with DevOps, DevSecOps, and IT Risk, was on hand signing book copies and discussing his latest work.
Our partner team enjoyed the opportunity to engage with other DC-based companies. We learned more about new tools in the DevOps pipeline and made some excellent connections with potential technology partners and consultancies.
The sponsors were in the amphitheater where the talks took place. It felt like a full and active space - very refreshing after several years of virtual events or low-turnout live events. It also gave us a chance to explore the swag distributed by other vendors, which is always fun!

Overall the Inflectra team enjoyed this bustling conference and the opportunity to meet so many local members of the DevOps community. Thanks again to the DevOpsDays team for a great event.

Spotlight on SpiraPlan 7.2 - Project Charters

2022-09-19T12:36:30-04:00

What is a Project Charter?

A project charter is a formal, typically short document that describes your project in its entirety — including what the objectives are, how it will be carried out, and who the stakeholders are. It is a crucial ingredient in planning the project because it is used throughout the project lifecycle. The project charter may include such sections as:

Reasons for the project
Objectives and constraints of the project
The main stakeholders
Risks identified
Benefits of the project
General overview of the budget

Some of these items are textual in nature (vision, objectives, constraints, etc.) , others maybe numeric (e.g. budget) and some may be picklists from a master list that your organization maintains (skills needed, platform, technologies, priority to the business, industry, geography, etc.).

A Sample Project Charter

To illustrate how companies typically create a project charter, we will look at a sanitized example from one of our clients that used an Excel based solution.

Project Background

This section includes key information such as the background, purpose, scope, references, and any terminology used in the project:

Project Overview

The project overview will typically contain key project information such as the programming languages used, the platform, database, and other key technologies. In addition, it may list the start date and end date, any review milestones and who is in charge of the project. It may also include fields for the customer stakeholders and key point of contact.

It may also have large text sections for the project summary, any assumptions, constraints and objectives.

Project Strategy

The project strategy section will include sections for the project vision, roadmap and any high level information about the plan to transition the finished system to the end user. Typically this section is mainly large text blocks that are used to capture freeform sections about the project.

Configuration Management Plan

The configuration management plan section will be used to document the key assets used in the project, a description of what software and hardware will be used, as well as a description of where project documents will be stored and how they are versioned, reviewed and released.

The configuration plan may also discuss the configuration of code assets including what source code repository will be used and what branch and release strategy will be used (e.g. using Git with GitFlow feature, release and hotfix branches). If there are standards around the naming conversion of product releases, that should also be documented here.

Other Plans

This section will be used to document any other plans not already included:

For example, your project may have the following additional plans:

Project review plan
Defect and problem resolution plan
Business continuity and disaster recovery plan
Risk management process and plan
Quality Assurance (QA) plan
Managerial process plan

New Product Custom Properties

As mentioned at the start of this article, the new version of SpiraPlan v7.2 coming out next month has support for project-level custom properties. This is a crucial feature, that together with the new spreadsheet editor and the existing document management and rich content editing functionality, provides the perfect platform for creating and managing project charters. Before we discuss project charters, we'll just recap the highlights of this new feature.

Administration Functionality

The new functionality (available only in SpiraPlan, not SpiraTest or SpiraTeam) will allow administrators to define custom properties and associated custom lists on SpiraPlan products (aka projects).

This is separate from the existing custom properties that are defined for product templates. Those let you define custom properties for artifacts in the product (e.g., requirements, test cases, etc.). These new custom properties are defined for the product workspace itself. In the future, we will be extending the functionality to provide custom properties on other workspaces such as programs and portfolios as well as on users and resources.

For the list-based custom properties (both single-select and multi-select), you can map the custom property to a centralized list of system-wide custom lists. This lets you reuse the same list of values for multiple custom properties, as well as allowing us in the future to use the same list for programs, portfolios, and users.

Each custom list can contain a set of values that would be useful to categorize a project with.

Program Manager Functionality

To access the new functionality, you simply need to choose a program from the SpiraPlan workspace selector (e.g., “Sample Program”) and then click on the new "Products” menu entry that is now available under the program “Artifacts" menu.

That will display the new Program > Product list page. This displays all of the active products in the current program:

This list view lets you see all of the products/projects together with their key configuration settings and any defined custom properties.

When you click on one of the items, SpiraPlan will display the details page for that product:

On this page, you can see all of the standard product fields (name, description, website, program, template), any of the key product settings (baselining enabled, etc.), and any of the custom properties grouped by the same headings as you would see on a typical artifact page.

Implementing Project Charters in SpiraPlan

To implement a project charter, you will take each of the elements from your existing MS-Excel or MS-Word based charter and map it to the different options available inside SpiraPlan:

Project Custom Properties: These are the primary option, and are best for rich text blocks, category selections and other pick-lists
Project Documents: These are good where you have existing MS-Word, Excel or PDF documents that you want to simply reuse
Spira Live Documents: These are a good option for a longer document that you want to create for the first time. It can be used for processes, policies, team standards and other items that are too large for rich text custom properties.
Spira Live Spreadsheets: These are a good option where you have a grid of data to be managed,for example the list of hardware requirements for the project, or a list of deliverables with dates.
Spira Live Diagrams: These are the best option where you want to describe a process visually, for example, the project escalation process or defect triage process.

In the following sections we shall illustrate each of these in a sample mini-project charter.

Project Custom Properties

Most of the items in a typical project charter can be represented as custom properties on the product itself:

Using the following custom lists for the fields that are list-based:

When displayed for the end users, this would then look like:

and the lower part of the screen will display all of the larger, rich text fields:

Project Documents

For those parts of the project charter that are externally created documents, the easiest thing is to just create document folders and then upload them into the SpiraPlan documents repository:

That way you have all the documents in one central location, and you have access to the built-in Spira features such as versioning, workflow, check-in/out and electronic signatures.

Spira Documents

If you don't already have some of the documents written, then you can simply use the built-in Spira document creation and editing features to create the documents right in the project:

You can author the documents either using the built-in rich text editor, or instead use Markdown (.MD) which is then live-previewed into the final content:

Spira Spreadsheets

Some of the sections of a project charter may be more tabular in nature. These will be best suited to using the new SpiraPlan spreadsheet editor:

For example, the following sections are often described using a spreadsheet:

Project Roles & Responsibilities
Deliverables & Acceptance Criteria
Terms and Acronyms
Staffing Plan
Resource Acquisition Plan
Stakeholder Involvement Plan
Metrics Collection Plan
Hardware / Asset Tracking

Spira Diagrams

Finally, there may be some parts of the project charter that describe processes that are best represented as a flowchart or decision tree, rather than a document or spreadsheet. For those, the SpiraPlan diagram editor is the perfect tool. For example, here's a sample defect resolution process diagram:

Other processes that could use the diagram flowchart option would be:

Project overall lifecycle model
Managerial process plan
Client escalation plan
Defect resolution process
Quality assurance plan
Project deliverable review process

Conclusion

We have seen that the new project-level custom properties in SpiraPlan 7.2, together with the other functionality now available in SpiraPlan (spreadsheets, document management, diagrams and rich content editing) give you a single place to create and manage your project charters. In addition, all of the existing SpiraPlan project artifacts are available, integrated with the charter - project risks, work breakdown structure (WBS), project plans in the Gantt chart, project requirements, quality assurance artifacts, and key project issues.

Spotlight on SpiraPlan 7.2 - Project Portfolio Management

2022-09-19T14:14:00-04:00

Overview of the Functionality

The new functionality (available only in SpiraPlan, not SpiraTest or SpiraTeam) will allow administrators to define custom properties and associated custom lists on SpiraPlan products (aka projects). To access this new feature, you go to the main system administration menu and look under the Custom Properties section:

Once you click on the ‘Product Definitions’ option, you will see all of the custom properties defined for products:

In this example, we have the sample set of custom properties only. They include text, numeric, date, and list custom properties. They show how you can use the custom properties to add useful meta-data about a project (e.g., the Vision, Stakeholders, etc.) as well to allow us to categorize projects in different ways. For example, if you click 'Edit Definition' on one of the properties, you will see how to change the name, type, description, and position of a custom property.

Each custom list can contain a set of values that would be useful to categorize a project with. In the example below, we’ve created a custom list to denote the technologies that a particular product is using.

Another example would be to categorize and prioritize the various projects based on a numeric scale (similar to how we can prioritize requirements or incidents). To achieve that, you can create a simple list of priority values that can then be used as a product custom property:

You can then do the same thing with other key project/product metrics such as the database platforms being used (Oracle, SQL Server, MySQL, etc.), skills that people need, etc.

Once that is done, you can then create custom properties that map to these custom list values:

In the example list above, we have some fields that will be useful to display on each product (Goals, Assumptions, Constraints, Vision) and other fields that are more useful when comparing, sorting, and filtering the list of projects. The product's custom properties are useful for both of these use cases.

Using for Project Portfolio Management

Project Portfolio Management (PPM) software is a business solution for managing projects at scale. Project portfolio software makes it easier for you to understand the resources, timelines, and overall business goals at a higher-level scope. It helps coordinate current projects while simultaneously planning for future projects. With the new product custom properties functionality, SpiraPlan can now provide you the means to assign timelines, goals, priorities, budgets, and other attributes to your projects so that you can manage them as a whole.

That will display the new Program > Product list page. This displays all of the active products in the current program:

This list view lets you see all of the products/projects together with their key configuration settings and any defined custom properties. In the example above, we're displaying the list of products, including the budget, next milestone review date, technologies used, database platform, and business importance rating. You can, of course, sort and/or filter by any of the displayed fields.

Furthermore, when you click on one of the items, SpiraPlan will display the details page for that product:

Back on the main list page, you can also show/hide different fields to customize your view. For example, during a planning/budgeting phase, you may want to show priority, budget, and milestones, whereas, in a meeting concerning technologies and asset management, you may want to organize the products by platform and database to understand which products your team(s) are using.

Finally, we are exposing the same data to the reporting system so that you can create custom reports that display the products and their associated custom properties:

Similarly, you might want to graph the number of products using each technology stack and/or database by priority:

The ESQL custom query for this graph would be:

select G.NAME as PRIORITY, count(R.PROJECT_ID) as COUNT from SpiraTestEntities.R_Projects as R
inner join SpiraTestEntities.R_GlobalCustomListValues as G on G.CUSTOM_PROPERTY_VALUE_ID = cast (R.CUST_08 as Int32)
group by G.NAME

What About Other Artifacts?

This is just the first phase in the planned program and portfolio management capabilities. The next step will be to extend this functionality to other workspaces such as programs and portfolios and also to users so that we can have the same slicing and dicing functionality available when viewing people and resources.

Inflectra In The News - August 2022 Roundup

2023-01-31T09:37:56-05:00

Publications

Navigating Family and Life Flexibility During a 100-Year Pandemic with Advertising Review - July 13, 2022

It has been a tumultuous time at Inflectra, the past year. We have a team that spans multiple countries, so at any given time, the story is bifurcated between the places doing well and those dealing with another wave of the virus. Right now, we’re seeing businesses and the economy opening in the US, and our USA team is all vaccinated and ready to go. Our teams in Brazil and India are still worrying about the virus, their families, and their loved ones. So I think overall, our team has been courageous and strong over the past year, and the solidarity and feeling of “being in it together” have been a great support network for all of us. Honestly, it has made us closer as a team and bonded us in adversity. Read more.

5 Things I Wish Someone Told Me Before I Became a CEO by Authority Magazine - August 24, 2022

“Be careful hiring close friends. We have a cult-like quality at Inflectra, and a lot of people have been hired from friend circles, my old boy scout troop, neighbors, and other friends of friends. It’s generally a great way to build a close-knit culture, but it does mean it changes the relationship with them, and it won’t be the same as before." Read more.

Bring Harmony to Your Software Lifecycle by Go Solo - September 2, 2022

Interested in starting your own entrepreneurial journey but unsure what to expect? Then read up on our interview with Adam Sandman, Founder, and CEO of Inflectra, located in Silver Spring, MD, USA. Read more.

This Solo Founder Built A $10M ARR Tool For Software Teams by Starter Story - September 4, 2022

One of the most rewarding things about our business is that we see our customers every day; they are everywhere! As our business focuses on medium-large companies (which is unusual, I know!) in industries such as food, transportation, logistics, banking, insurance, defense, and life sciences, we see them in everyday life. When visiting the doctors, I will see the name of our clients; when traveling, the plane I am flying in, the fuel we are using, the airport I am landing at, and so much more. Inflectra’s customers are the critical infrastructure that keeps the entire world running, and we make the software platform - SpiraPlan, that helps them deliver. That is very cool. Read more.

TV Appearances

He's the Real Unicorn: Bootstrapped to $10m, owns 100%, Shares Profits with Team with Nathan Latka - June 28, 2022

Create Build Manage: Adam Sandman Inflectra CEO Interview with Scott Miller, Biz TV - July 19, 2022

Talks and Presentations

Discussion: Current Issues in Risk Management | A Virtual Event - July 14, 2022

In the first discussion of the risk and risk management series, the panelists gave an overview of risk management, concentrating on corporate- and product-level risks in technology, security, and operations, including business agility, regulations, leading software solutions, and services. Read more.

Techday Brazil: How to Harmonize Your Software Development Lifecycle - August 23, 2022

Adam Sandman participated in www.Software.com.br's Techday Brazil conference to share his in-depth insight into software development. Read more.

Inflectra Supports North Eastern University’s Global Symposium on Leadership & Project Management - August 26, 2022

Adam Sandman joined the roster of speakers to discuss: Rethinking Risk-Based Project Management in the Emerging IT Initiatives. This is one of the leading talks on the symposium track: Impact of emerging technology on leadership & project management. Read more.

Inflectra has great plans for the remainder of 2022! We cannot wait to share more with you!

Insights from DeveloperWeek Cloud 2022 in Austin, TX

2022-09-13T10:44:04-04:00

DeveloperWeek Cloud 2022

The annual DeveloperWeek Cloud Conference held at the Palmer Events Center, Austin, TX is the premiere international cloud computing conference, where over 3,500 cloud engineers & developers, IT managers, entrepreneurs, and innovators converge to discover the newest cloud computing innovations.

DevOps Summit

In addition, the DevOps Summit track covered the digital convergence of Cloud DevOps engineers, DevOps managers, and dev professionals with a landscape view of the innovation going on in DevOps. Since DevOps is at the intersection of software development with IT / Cloud management, the dedicated tracks covered new technologies and best practices in scalability, monitoring, continuous integration, dev security ops, API ops, and containers / Kubernetes.

There was also an Open Stage section of the conference, where speakers and exhibitors could give more focused talks on their specific technologies and innovations. This stage was located next to the Expo floor so that attendees could easily see what was being presented, and dart over to the stage when something interesting and relevant was being discussed.

.NET Enterprise Developer Days Hosted by AWS

Finally, Amazon Web Services (AWS) had their own set of dedicated tracks at the event, where they were focusing on Microsoft .NET Applications, and providing guidance and strategies for migrating existing .NET applications to the AWS cloud infrastructure.

Some of the most interesting talks in this area were around the ability to use AWS conversion tools to move .NET Framework applications (as well as .NET Core apps) to Windows EC2-backed Docker containers running in AWS Kubernetes.

Keynote - Cloudy Days Ahead

During the opening keynote talk, the speaker Ori Bendet from Checkmarx discussed the Clouds on the Horizon, What Lies Ahead for Security, Development and CloudSec teams.The talk focused on how there are competing demands on cloud native development, to balance the "Shift-Left" imperatives of increased speed, increased use of common open-source components, platforms and libraries, with the need for ever increasing security, quality and compliance of the systems in production.

For example, in an ideal world, developers want the simplest possible word, where code committed into a Git repository is automatically built, tested, and deployed into production with as few manual steps and stages as possible.

However when you speak to people involved in IT security, CIOs, CISOs and other infrastructure or IT service delivery roles, you get a vary different picture.

They want to be able to manage their organizational and technical risks as much as possible. For example, they want to ensure that all developer activities and workflows are monitored and traced back to user needs and documented features. They want to have a smaller set of comprehensive platforms with strong Service Level Agreements (SLAs) rather than using whatever latest tool an individual developer wants. Whereas a developer is happy to use the latest API or feature from a cloud provider to simplify their process, the CISO cares about re-usability, redundancy and avoiding vendor lock-in. Maybe using a standard method that is not cloud-specific is more important than using the latest feature.

So, to go back to the earlier theme, the talk demonstrated that there is a need for agility and speed to be balanced by quality and compliance. You need to be able to deliver features and great user experiences faster AND deliver then in a reliable, performant and secure way, each and every time.

Key Themes

There were many other talks at the conference, focusing on key ideas around how to architect reliability and availability into cloud applications, how to include debugging tools such as instrumentation and telemetry into cloud applications. There were also focused talks on cloud-based data management, integrating AI and chatbots into cloud applications, as well general talks on micro-services, containerization using Docker and Kubernetes, and approaches to setting up efficient DevOps pipelines for native cloud applications.

However a couple of interesting talks included one of the dangers of using passwords and password-like tokens in the development stack, and one on the role of your "digital double", identity and personality management in the new world of Web 3.0 applications.

Building a Passwordless Cloud Infrastructure

This talk by Kyle Kotowick of Invicton Labs discussed how vulnerable developer stacks and cloud infrastructure are to password credential attacks. In the course of developing, building and deploying systems, each step of the process involves multiple services, each talking to each other by means of password-like tokens such as passwords, API Keys, certificates and other long-lived security identifiers. In line with classic Risk Management approaches, the talk discussed how to reduce the impact and/or probability of a credential being compromised.

A key recommendation was to deploy a Single Sign On (SSO) identity provider that uses a technology such as OAuth 2.0 / OpenID Connect and allow bio-metric login as its primary factor. Then use this provider for accessing all other services in lieu of having passwords for each service. Finally, establish trust between all your other products and platforms using this SSO identity. A key takeaway was to only select services and providers that offer SSO as part of the tier your company can afford to use at scale.

Creating a Seamless Access Experience with the Digital Double

In this talk by Asanka Abeysinghe of WSO2, there was an interesting discussion of how current identity management systems (using OAuth, SAML or OpenID Connect) are limited to just storing a user's identity information (name, email address, bio-metric identifiers). In the future it is proposed that users will look to expand this to include their 'digital personality', essentially all of the behaviors and other aspects of their digital footprint.

For example, imagine you had a central digital profile that contained your browsing history, social media posts, shopping habits and even futuristic data elements such as your driving style (from your IoT car). Currently each provider (e.g. Amazon, Tesla, etc.) collects and stores this data for you, but you have no control over what is stored, and who it is shared with.

In this new Web 3.0 world, you will have a place where all this data is stored, and you will chose what elements to share with different applications and services. For example, just like the fact that you have multiple personalities in the real world, in the digital world, your profile might present different personalities to applications. You might have a professional personality that you share with LinkedIn and a family personality you share with Facebook.

What's New from The Expo

In between the various sessions, the Expo had many different interesting and innovative vendors, including companies providing tools to assist with instrumentation and telemetry of applications running in the cloud, different orchestration platforms, and many different products offering security and reliability services to assist with cloud deployments and infrastructure.

There were also developer tools aimed at improving productivity and reducing the time from code commit to deployment into production.

There was also a selection of companies offering workflow and business process orchestration engines that combine traditional event-based messaging with containerized applications to allow flexibility in handling business process management and technical infrastructure orchestration in the same platform.

Advisory Board VIP Summit

As a member of the advisory board for the Developer Week Cloud 2022, I was fortunate enough to review the various speaker proposals and assist in the section of the talks in the program. It also allowed me to take part in the Advisory Board VIP Summit the night before the conference. During this time, I met various other entrepreneurs and leaders in the technology industry. I would recommend volunteering your time to assist in an advisory board to a conference. It's a great way to broaden your skills, get exposure to new technologies and ideas. In addition, you get to meet amazing people who are part of the board and expand your network.

Thanks to the DeveloperWeek team for the great opportunity. I hope to see you at future events.

Spotlight on Spira 7.2 - New Integrated Spreadsheet Editor

2022-11-04T20:21:53-04:00

Adding a New Spreadsheet

The new spreadsheet functionality can be accessed by simply going to the main Documents page and choosing Add Document. In addition to the existing types for text documents, diagrams and file uploads, you will now see the new option to create a new spreadsheet:

Just like creating a new document, when you create a new spreadsheet, you will need to chose the filename, description, type, folder and (optionally) any meta tags:

Once you click the Add button, the system will display the standard Spira document editing page, this time with the new spreadsheet editor displayed inline:

The editor includes a toolbar and menu-bar where you can specify the formatting of the cells, sort the data, cut, copy and paste and perform other common spreadsheet functions.

Adding Spreadsheet Data

In this example, we have added in some data about our sample users - their name, age and eye color. We have changed the background color of the header and made the text bold:

Suppose we want to add a calculated row that displays the sum of all the ages of the users. That's easy, you just click on the cell where you want the result and start entering the formula (in this case =SUM) just like you would in Excel or Google Sheets.

When you enter in a data-range, the editor will intelligently highlight the rows that are being used in the calculation:

Once you have the correct formula, you can click away and the system will display the calculated result:

The system comes with a wide variety of built-in formulas, including, sum, average, and hundreds of other functions.

Exporting the Spreadsheet

Although the new Spira built-in spreadsheet is very powerful, sometimes you want to export the data into another spreadsheet such as Excel. Natively the editor saves the data in a special *.sheet file format, but you can easily export to Microsoft Excel, using the Download as... Microsoft Excel (.xslx) feature.

Versioning the Spreadsheet

Finally, one of the benefits of using the built-in Spira spreadsheet editor is that it keeps your data safe and secure, in the same place as all your other project data, with the ability to follow workflows, make the data read-only and even manage the different versions of the spreadsheet every time you save a new version:

With the spreadsheet editor you now have a central location to manage all your project data and sample test data for testing.

What About the Future?

Future possible enhancements include the ability to more closely integrate the spreadsheet data into the test execution wizard so that you can create and update test data live during testing. In addition, another key future enhancement will be to enable Rapise to view and edit the spreadsheet data live in the Rapise built-in spreadsheet editor.

Sneak Peek: New Agile Boards and Support for Teams

2022-09-01T15:38:46-04:00

Background

The current agile boards in SpiraTeam and SpiraPlan were originally released in Spira 4.2, and at the time were a huge improvement over the ones that were in earlier versions. They allow you to see the product backlog, release backlog and sprint backlog in an easy to navigate interface. The primary requirements-oriented planning board was supplemented with dedicated task and incident boards in Spira 5.4.

However, there are some limitations in the current boards that we have been looking to address for some time. The current boards will display in a 'horizontal' mode for some views (see above) such as the 'By Component' view, and 'vertical' mode for some other views such as 'By Status' (see below):

In addition, the boards do not let you have both rows and columns visible at the same time. We have also had requests to be able to manage groups of users in 'teams' vs. having just a large single list of project members. Finally, customers have been looking for more flexibility to display different fields and metrics in the story cards themselves.

Well, the good news is that we've been working on a completely revamped agile board that addresses these limitations and adds major new enhancements in terms of both functionality and usability. The new boards will be initially released as an 'opt-in' beta feature in the coming months, before becoming the standard interface. Note: the screenshots in this article are based on the current 'alpha' version and are subject to change, based on your feedback.

More Consistent User Interface

Firstly, we have redesigned the board display to operate in a consistent manner, regardless of whether you are looking at the product backlog, release backlog or sprint backlog. You will now always have the option to:

Group by a certain attribute, or simply show all cards un-grouped
Organize the x-axis of the board by a certain attribute, called the 'column'
Organize the y-axis of the board by a certain attribute, called the 'row' or simply show all cards in one row.

You will still have the ability to display three views (product backlog, release backlog, and sprint backlog) and for the latter two, filter by release or sprint as appropriate. However regardless of that, the board will have the same visual appearance.

Firstly you will be able to see the list of groups that you have selected in the 'group-by', or just a single 'all items' group, if you have not chosen to group by a specific field:

You can then expand each of the groups to display an X-Y board that contains columns and optionally rows:

When you expand a row in the group, it will show you any requirements (and/or incidents) that belong in that group, row and column segment:

This means that when you change from:

Product backlog, grouped by Component, Priority as the columns and Parent as the rows, to
Release backlog, grouped by Release, Status as the columns and Person as the rows

The overall user interface and display is the same, with the board maintaining the same overall layout and set of operations:

This will provide a much simpler to understand and explain interface, yet gives you more power and flexibility than the current set of different 'vertical' and 'horizontal' views.

Multi-Dimensional Boards

One of the key enhancements in the new planning board is the ability to specify different fields for the columns and rows on the board, instead of being limited to just a single field per display option (in the current board). For example, in the screenshot below, we are displaying the list of requirement Story cards by parent requirement (Epic, Feature, etc.), with the columns showing the different statuses. As with the current boards, you can display Kanban Work In Progress (WIP) limits on the statuses to see if you have exceeded any of the specified WIP limits per status.

In this second example, in the screenshot below, we are displaying the list of requirement Story cards by Component, with the columns showing the different priorities (which have color-coding):

The initial beta version will only support certain standard fields for grouping or use in the column/row selections, but eventually we plan on supporting custom properties as well.

Support for Teams and Tracks

Earlier this year we introduced the ability to create a global list of product teams. This functionality has been dormant inside SpiraTeam and SpiraPlan, waiting for the time when it will be used in the application. With the new agile boards, that moment has come. The new teams functionality will let you create a global list of different teams:

Once you have defined those teams you will be able to assign different users to these teams on a given project. For example, Fred Bloggs may be in the Dev team on Project 1 and on the QA team on Project 2. This lets us group people in similar teams for the purposes of tracking work and viewing story cards on the boards.

With these teams defined and people assigned to the teams, you can now use the new grouping option on the agile boards to display the story cards by team. Underneath each time will the list of people that are in that team. This makes the resource viewing and assignment much easier than with the current boards. In addition, you can easily hide any observer users that are not part of any team:

In the example above, we are displaying the Release Backlog, grouped by team, with the people in each team on the Y-Axis and the requirement status on the X-Axis.

Customizable Cards

Another frequently asked for enhancement, is the ability to customize which fields are displayed on the story cards. In the previous version of the board, you had basically a detailed view / simplified view, plus the ability to show tasks and test cases as "mini cards". We have kept the incident/tasks card option, but instead of the detailed view / simplified view choice, we now let you pick more fields in a granular fashion:

This lets you have more flexibility as to what is displayed, as well as allowing the following fields to be displayed for the first time:

Test Coverage (bar chart)
Type (feature, epic, story, etc.)
Status (planned, in progress, developed, completed, etc.)

The following card shows the description, status, and task progress (the default view):

This card shows all the available fields (we have added type, test coverage, and the list of tasks and test cases):

This is an example of a more minimal view, showing just the name, status,type, task progress and test coverage:

In the future we plan on allowing you show even more fields such as custom properties and other standard fields.

Better Integration Between Defects & Requirements

Unlike some other products on the market, Spira has different specialized artifact types (requirement, test cases, task, incident, etc.) so it is more difficult to show an integrated board for requirements and incidents when the fields may not be the same. In the current board, if you choose to display the cards by priority, the system will exclude any incidents from the board.

In the new version, as long as the incidents and requirements have priorities that use the same nomenclature, the board will include both incidents and requirements in the priority views:

In the future, we hope to do the same thing for the two remaining views that do not support incidents (by status and by parent requirement).

Other Enhancements Planned

In addition to these enhancements, we're planning on making these additional improvements to the beta version:

Saved views - you will be able to save your board configuration as a saved view (that can be shared with the team), similar to how the list pages support saved filters/views.
Sticky headers - making the Unassigned sections of the board sticky so that it's easier to drag items from the product backlog to a specific release/sprint
Custom status order - for the view where we have the Status as the X-Axis, having an option to change the sort order to match the workflow.

Beyond the initial beta release, we anticipate the following future enhancements (depending on feedback from customers):

Filters - the ability to filter by a field as well as the group-by, row and column options
Custom fields - the ability to select custom properties as the group-by, row, column and display fields

Which Boards Will Be Updated?

The initial plan is to release the new board as an alternative "opt-in" public beta for customers when they use the main "Planning > Planning Board" from the product artifact navigation. Once we get feedback from customers, the second phase will be to update the following additional boards with the new functionality:

Product task board
Product requirement board
Product incident board
Program board

API Testing: Benefits, Types, Approaches, & More

2023-11-15T15:56:08-05:00

Benefits of API testing

There is a multitude of advantages that API testing brings to your development process. Let’s discuss some of the individual benefits:

Time effective

API tests require less scripting efforts as compared to GUI tests. GUI test time is spent on loading and rendering web pages and UI elements that might not even be needed in the end, which can slow down the testing process. API testing reduces all these tasks to one and as a result, the testing process is faster with better coverage.

Testing cost reduction

API testing can provide faster results with early defect diagnosis, which reduces overall testing costs.

Access without UI

API testing allows access to the application without a user interface or users interacting with the system. API tests can run without needing to experience the software application, which gives an early insight into defects and errors. This allows for early issue resolution before the GUI is impacted.

Integratable testing

API testing allows for highly integrable tests. This is especially beneficial if you plan to perform functional GUI tests following your API testing.

Improves testing coverage

Testing the code-level functionality of an application provides an early evaluation of its overall build strength. This exposes small errors before they become larger problems during GUI testing. Core access enables testing in tandem with development, fostering communication and improved collaboration between both teams.

Language-independent

An API test exchanges data using XML or JSON. These transfer modes are completely language-independent, meaning that you can select any core programming language.

What are the types of API Testing?

While there are plenty of reasons for you to invest in API testing, there are many different types that you can implement. From the most basic to much more complex and niche applications, we’ll discuss each of the most common ones you might run into.

1. Functional testing

Functional tests validate the software system against functional specifications and requirements. To test each function of the API, a tester provides appropriate input parameters in XML or JSON payload, then verifies the output against the functional requirements.

2. Security testing

API security testing reveals any risk, vulnerability, or threat within the API. Security testing identifies all potential loopholes and API weaknesses that can result in a loss of information, revenue, and reputation if misused by an unauthorized user.

3. UI testing

UI testing is a test of the user interface for the API and other integral parts. UI testing focuses more on the interface which ties into the API rather than the API testing itself. Although UI testing is not a specific test of API in terms of the codebase, it still provides an overview of the health, usability, and efficiency of the frontend and backend.

4. Penetration testing

Penetration testing emulates an external attacker or malicious insider specifically targeting a custom set of API endpoints and attempting to undermine the security to impact the confidentiality, integrity, or availability of an organization’s resources.

5. Load testing

Load testing emulates a constant steady stream of traffic at both normal and peak conditions. This ensures that the APIs do not contain memory leaks or other similar defects that might cause issues after running for a prolonged period of time.

Load testing often happens after a specific unit, or the whole codebase has been completed.

6. Runtime/error detection testing

Runtime error detection testing is related to the actual running of the API and the universal results of utilizing the API codebase. This test focuses on monitoring, execution errors, resource leaks, or error detection.

7. Fuzz testing

Fuzz testing or noise testing sets operation parameters to unexpected values to cause unexpected behavior and errors in the API backend. This helps discover bugs and potential security issues.

8. Validation testing

Validation testing helps ensures that the software meets the business requirements and is seen as an assurance of the correct development. Validation testing occurs among the final steps and plays an essential role in the development process. It verifies the aspects of product, behavior, and efficiency.

9. Interoperability and WS compliance testing

Web Services and Interoperability Compliance testing pertains to SOAP APIs and guarantees that they comply with Web Services Interoperability Profiles. The compliance is checked to see if the predetermined requirements are met.

API Testing Approach

API testing is performed by submitting requests to the software using the application’s programming interface of the application and then checking if it returns the expected data.

Create API testing requirements

To be able to plan API tests, first, you need to determine testing boundaries and requirements. This includes:

The purpose of the API

The workflow of the application

The functions of the API

APIs this API interacts with

Aspects of testing

The problems that are being tested for

Testing priorities

The desired output

The definition of Pass and Fail

Knowing the purpose of the API will set a firm foundation to prepare your test data for input and output.

Establish the API testing environment

Setting up an API test environment requires the configuration of the servers, databases, and every resource the API interacts with, depending on the software requirements.

Make a trial API call

Before diving into thorough testing, make an API call just to check that nothing is broken and the API is operational.

Define the input parameters

Plan all possible input combinations to use them in test cases and authenticate the results to determine whether the API performs as expected.

Create API test cases

Execute test cases and compare actual results with the expected ones. A good practice is to group them by test category.

Examples of API test cases include:

Testing value in response to the input condition: define the input and authenticate the output, which can be any type of data or status

Checking the behavior of the API in the system when there is no return value in response

Tracking events and interruptions triggered by the output

Authenticating the effect on the system after data structure updates

Validating resources modified by the API call

Considerations for Performing API Tests

The following factors should be considered when performing API testing:

Understand API requirements: ensure you know the purpose of the API and the workflow of the application.

Specify the API output status: you need to verify the response status code in API testing. All API response status codes are separated into five classes.

There are five values for the first digit:

1xx (Informational): The request is received and continues to be processed

2xx (Successful): The request is successfully received, understood, and accepted

3xx (Redirection): Further action needs to be taken to complete the request

4xx (Client Error): The request contains the wrong syntax or cannot be fulfilled

5xx (Server Error): The server fails to fulfill an apparently valid request

The first digit of the code defines the class of the response. Use these codes to determine the output of your API. Determine if the code follows global standard classes or if the code is specified in the requirement.

Analyze the validation response: During the API testing process, a request is raised to the API with the known data. This way, you can analyze the validation response. While testing an API, you should consider:

Accuracy of data

Schema validation

HTTP status codes

Data type, validations, order, and completeness

Authorization checks

Implementation of response timeout

Error codes in case API returns, and

Non-functional testing like performance and security testing

Focus on functional APIs: focus on the simple APIs with only one or two inputs. These are necessary access points to further APIs. By focusing on these before moving on to test the others, you ensure that the initial points of access work.

Common Types of API Technologies

Over the years, APIs have evolved from simple code libraries that applications could use to run code on the same computer to remote APIs that can be used to allow code on one computer to call code hosted somewhere else.

Here is a quick list of the more common API technologies that exist in approximate chronological order:

TCP/IP Sockets

Remote Procedure Call (RPC)

Common Object Request Broker Architecture (CORBA)

Java Remote Method Invocation (RMI) and Enterprise Java Beans (EJBs)

Microsoft Distributed Component Object Model (DCOM) – also known as ActiveX

Web Services (SOAP then REST)

Get Started With API Testing Today

If you’re ready to add seamless and comprehensive API testing to your software development pipeline, Rapise provides all this and more. From automated testing and playback to reporting and cross-platform functionality, it empowers your software to be the highest quality possible while making your life as easy as possible. Click here to get started with a free trial today!

Using SpiraPlan for Application Portfolio Management

2022-09-01T15:35:56-04:00

Application Portfolio Management

IT Application Portfolio Management (APM) is a practice that has emerged in mid to large-size information technology (IT) organizations since the mid-1990s.Application Portfolio Management attempts to use the lessons of financial portfolio management to justify and measure the financial benefits of each application in comparison to the costs of the application's maintenance and operations.

Why is Application Portfolio Management Important?

As mentioned above, the original concept of application portfolio management (APM) first emerged in the early 1990s, but its benefits really became apparent during the Y2K buildup. When organizations began preparing for Y2K remediation, they often discovered they had accumulated a large number of applications that were redundant, costly to maintain, and of little real business value. Moreover, the majority of applications were not cataloged in any logical, searchable fashion. As companies began to review their application portfolios, the benefits of having an ongoing process of doing so became apparent. The applications in most of these organizations were not cataloged in an easy and search-friendly manner. This meant that there was a need for reviewing the application portfolios. Also, by following APM, businesses can obtain a clearer idea of the value they could derive from their applications in a quantifiable way.

Configuring SpiraPlan for Application Portfolio Management

SpiraPlan provides a great platform for managing your portfolio of systems, software applications and other IT systems. This section discusses how you can setup a special product template for managing application portfolios:

We will be using the requirement artifact to store the various applications in our portfolio that we're managing. So the first step is to create custom properties to track the different attributes and characteristics of our applications, for example:

Version information
Release date
End of life date
Cost
Supplier(s)
Deployment architecture
etc.

Some of these will be simple free text or numeric fields, but others like Supplier and/or Deployment type will be list based. You can use the custom lists feature to populate these lists:

The lists can be used for both single and multi-select values.

In the example above, we've created a master list of application suppliers (Microsoft, Adobe, etc.) and a master list of deployment architecture types (SaaS, On-Premise, etc.).

In addition to these basic customizations, you will probably want to customize the workflows of the following artifacts:

Requirements workflow - similar to what was described for supplier management
Incidents workflow - change requests to an application in the portfolio will need their own change management workflow

Using SpiraPlan for Application Portfolio Management

Requirements

Now that we've setup the templates appropriately, you can use the standard requirements list views to display and organize the list of applications in your portfolio. In this example, we have used the hierarchical requirements' view to categorize the products by type (design vs. office), with the different application grouped under their containing type. We have also displayed the custom properties: version, end of life, cost, supplier and deployment type in the grid:

If we wanted to more easily sort and filter the applications by a field such as priority or supplier, we could instead switch to the sortable grid view, which is more flexible for "slicing and dicing" the data:

Releases

In order to track the applications in terms of when they are deployed, upgraded and eventually retired, we recommend creating high level releases and phases in the Release Gantt chart view:

In this example, we've created top-level releases for each broad platform baseline, and then created phases for each infrastructure segment that the application will be part of. Another way to organize things would be to do it by year and quarter:

Tasks and Change Requests

Tracking changes and action items is really important when managing an application portfolio. For example, a task might be to simply upgrade an application to the latest version, or it might be to conduct an application assessment before making configuration changes or changing license tiers. The Tasks module in SpiraPlan lets you create tasks, associate them with the application (requirement) and then plan them against the defined release/phase milestones.

In addition, when there are change requests coming in from the business users, you can use the incident artifact to have a special change request workflow that tracks the inbound requests from the users.

The change requests will follow the defined change request workflow, with the ability for users to approve or reject the change request, add comments, and associate it with the various applications (requirements) using the Associations tab to determine the change impact:

You can then run reports to see the application impact of each change request, determine costs, and plan for the outcomes.

Risks

In addition to the requested changes from users, another key area that SpiraPlan can assist with, is identifying, tracking and mitigating any risks associated with the applications. In this fictitious example, we have logged a risk that some of our Excel macros will not work with the version of Excel in our portfolio.

Using the standard risk management process within SpiraPlan, you can identify the various application risks and then associate them with the applications (requirements) as well as develop mitigations and action plans (tasks) to address the risks.

Reporting and Documents

Once you have the data in SpiraPlan, the reporting system lets you analyze the application portfolio based on a variety of criteria, including: number of suppliers, application cost, license type, deployment type, total cost of ownership (TCO). You can run an Excel summary report to get the data in various data grids:

The generated Excel report can be displayed directly in SpiraPlan, or for added benefit, you can publish the report directly into the SpiraPlan documents center:

In this example, you would have a simple application portfolio report that lets you slice and dice the data as needed:

Summary

In this article, we have seen how we can manage a portfolio of applications as requirements, track them against timelines using the releases module, respond to change requests via. the incidents module, assign tasks and risks to the applications, and generate reports to make it easier to analyze the applications in the portfolio.

Using SpiraPlan for Supplier Qualification

2022-08-01T06:57:01-04:00

Supplier Qualification Overview

Supplier qualification is the process by which a company will choose the correct supplier/third-party vendor for components/raw materials/services based on its requirements and regulatory protocols.

Supplier qualification means that a company needs to thoroughly evaluate candidate suppliers and third-party vendors as per their requirements, and then choose the best supplier or third-party vendor. These are usually regulatory requirements.

Why is Supplier Qualification Important?

Companies such as life sciences and biotech firms that research, develop, manufacture and sell products that directly affect humans, will have to maintain the highest industry and regulatory standards at each step of the life cycle of their products. This helps ensure that they will choose the right supplier after a thorough supplier evaluation and qualification process.

Hence, supplier qualification is important to ensure business continuity, reduce risk and consistently ensure that manufactured products are of the highest standard. So although the concept may be most important in the development of medical devices and pharmaceuticals, it is important for any company that manufactures mission-critical or safety-critical systems (e.g. aerospace, automotive, and general manufacturing)

According to Good Manufacturing Practice (GMP) regulations, supplier qualification is a crucial part of the validation process before choosing the right supplier for a company. It means that supplier qualification is not just a recommended protocol, but also a regulatory requirement.

Configuring SpiraPlan for Supplier Qualification

In general when using SpiraPlan for the supplier qualification process, we will use the following key artifacts:

Requirements will be used to track the individual suppliers themselves
Releases will be used to track the key milestones for supplier qualification and supplier updates
Incidents will be used to manage the two key processes that relate to qualifying and managing suppliers:
- Supplier initial qualification
- Supplier annual update
Documents will be used to store any related supplier information, such as:
- Tax forms
- Banking / financial information
- Quality forms

We shall describe how each of these should be configured in turn. However the first thing will be to create a new dedicated SpiraPlan project that has its own template dedicated to supplier qualification:

Once that's done, we can now configure the various artifacts in the template.

Requirements Configuration

For requirements, we need to configure the components, types, custom properties and associated workflows.

Components

The first thing will be to create the various components that will be used to categorize the different types of supplier. We recommend using Components for the primary type of categorization for the suppliers. More granular sub-classifications can then be done via. custom properties. In the example below, we have created components for suppliers involved with Hardware, Other, Services and Software.

Requirement Types

For the requirement types, you can either just create a single requirement type for Supplier (called Supplier) and use a single workflow, as illustrated below:

However if you intend to have different custom properties for different types of supplier and/or have different workflows, you might want to duplicate the categories as requirement types (as well as components) so that you can have different workflows and custom properties associated with each type of supplier. However most of the business processes around supplier management will be done later in with the incident workflows, so you may not need to have a complex workflow for the suppliers themselves, just a status for the key statuses:

Requested = New Suppliers
Accepted = Approved Suppliers
Obsolete = Obsolete Suppliers

Custom Properties

The choice of custom properties will depend a lot on your business, but typically you will want to have custom properties defined for the key supplier fields such as address, website, regions and other contractual and technical information:

Since this example is taken from a life sciences company, the suppliers will need to have a contracts point of contact, quality point of contact and a boolean Yes/No flag denoting if the supplier is GxP validated.

Releases Configuration

For the case of supplier management, our recommendation is to use the Releases module relatively sparingly, simply create major releases for each calendar year so that you can track all the supplier actions in a given year. This is useful if you have an annual supplier re-validation process.

If you want additional granularity, you could add phases under each release for each calendar quarter (Q1, Q2, Q3, Q4, etc.).

Incidents Configuration

The requirements are used to represent the actual suppliers themselves, whereas we will use the incident artifact to represent the different business processes that are associated with supplier management:

New Suppliers
Supplier Updates
Supplier Deactivation

In addition, you may have other processes, such as annual supplier recertifications, etc. that require their own process. The incidents module makes this easy and straightforward.

Incident Types

We recommend that you create a separate incident type for each type of business process associated with suppliers:

The incident types can all have their own unique workflow, or they can share a common workflow if the steps are the same (for example a supplier update might be the same process as a supplier annual certification).

Incident Workflows

As we described above, each unique supplier process should have its own workflow. Processes that are similar, can generally share a workflow:

The following is an example supplier workflow. Noe that for simplicity we have taken the built-in defect workflow and just simplified it:

However for a more realistic workflow, we might want to complete change all the incident statuses/steps as well as the transitions between the steps. For example, here's a sample supplier qualification workflow you might want to use:

Question – define requirements and develop questions
Understand – compile candidates and assess capabilities
Evaluate – evaluate candidates and identify the best one
Site audit – perform a comprehensive site audit
Track – re-qualify suppliers on a routine basis

Custom Properties

The custom properties defined on the incident artifact should include all the information needed to qualify the supplier as well as support the other processes (management, annual recertification, deactivation, etc.). Each workflow will then show or hide the appropriate custom properties as needed.

In the example above, we have added custom properties to track:

General notes about the supplier (rich text)
The regions the supplier operates in (list)
Whether or not the supplier needs to be GxP validated

Now that we have setup the template and project correctly, the next step is to illustrate the end user flow as they enter a new supplier. For brevity, we have not disabled all of the standard incident fields (such as Verified Release, Fixed Build, etc.) that you will most likely want to hide in a real process.

New Supplier Qualification

When you click on the New Incident button, the system will let you start the 'New Supplier Request' process. Simply enter in the name and description of the request (in this example, we're adding "Microsoft" as a new supplier"). Choose the region, component (supplier type), priority and whether it is a GxP supplier or not. We also use the Detected Release field to indicate that it is a 2022 supplier.

Once the request is submitted, it will follow the defined workflow for this type of incident. At some point, the supplier is approved, with appropriate comments and audit trail. You can now use the special Create Requirement From This Incident to turn the supplier request (incidents module) into an actual supplier in the supplier registry (requirements module).

When you use this button, the key information from the new supplier request is transferred over to the new supplier requirement record:

Any additional information that was not part of the new supplier request can also be directed added to the requirement.

Supplier Management

Now that the supplier has been added to the system, we can use the Requirements Board View to view and organize the suppliers. In this example view, we are viewing all of the suppliers by type (component) and the color coding indicates their priority (Critical - Low)

The boards allow inline editing so that it's easy to make changes to a supplier entry. You can also use the board drag and drop features to adjust the priority, component or other fields.

Generally simple changes can be made directly on the requirement artifact for the supplier, but other standard processes may require using the new incident form (e.g. annual recertification, deactivation, etc.). We shall look at each of these.

Supplier Annual Update

The annual supplier recertification and update process uses a similar process to the 'new supplier request' form, except that when you change the incident type from 'New Supplier Request' to 'Supplier Update', the list of required and available fields will change (see below) and only the information pertinent to the update process of suppliers will be defined.

One key difference is that you will use the Associations tab to explicitly link the supplier update request to the requirements record for the supplier itself (in this case Microsoft). That ensures that all activities related to the supplier will be visible from the supplier record.

Similarly to deactivate a supplier, you use the separate "Supplier Deactivation" incident type and follow that workflow to process the deactivation request for the supplier.

Once the deactivation request is completed (by following the workflow), the status of the actual supplier record will be changed to the obsolete status.

By using these two artifacts together (requirements and incidents), we can see in a single-view, all the details of the supplier (requirement), together with all the related business processes (incidents):

Document Storage

The final aspect of managing suppliers, is the need to store and manage the associated documentation that goes with the supplier requests and maintenance activities. For example, you may need to store:

Supplier quality information
Supplier financial/banking information
Supplier tax forms
etc.

Using the SpiraPlan document management functionality, you can create folders for each of the different types of documentation you need to store for suppliers. Then when you upload the documents associated with the supplier requests, you can simply specify the appropriate folder at the time of upload:

You can of course always move the documents around after the fact, just using drag-and-drop.

In addition, the SpiraPlan document management repository supports versioning of the documents and the workflow support electronic signatures, review and approval, and locking the final version to prevent unauthorized changes.

That way you have a complete audit trail of all documentation changes associated with the supplier. Furthermore, you can click on the Attachment tab for a Supplier and see all of the associated documentation in one place:

Summary

In this article, we have seen how we can use the requirements, releases, incidents and documents modules of SpiraPlan to manage the entire lifecycle of a supplier, from initial request, through annual recertification, all the way to eventual deactivation.

SpiraApps by Inflectra: Plugin Extensibility Framework | A Recap

2024-05-11T13:20:12-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Show and Tell: SpiraApps - Spira Extensibility Framework You've Been Waiting For from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay well!

See you at our future webinars!

#teamInflectra

Using SpiraPlan for Vendor Selection & Management

2022-07-19T16:22:56-04:00

Vendor Selection & Management Overview

Successful organizations understand the importance of forming relationships with the right vendors. Many businesses make the mistake of choosing a vendor based on cost alone; however, this can result in more expensive problems in the long-run. A business should choose a vendor that aligns with their operations and shares similar goals. By being careful with vendor selection from the very start, companies can avoid potentially costly hassles down the road.

The 7 Steps for Managing Vendor Selection

The following seven steps are typically followed for managing the vendor selection process:

Define and Analyze Business Requirements
Identify Third Party Vendor Candidates
Develop Evaluation Criteria (with weighting)
Conduct Vendor Briefings
Evaluate Vendors and Schedule Demos
Complete Vendor Selection
Complete Contracting with Vendor

Configuring SpiraPlan for Vendor Selection & Management

Creating Vendor Selection & Management Projects

In order to manage a typical vendor selection engagement, it is important to be able to manage the requirements such that:

There is a core set of requirements managed by the vendor selection team for the Request for Proposal (RFP)
These requirements can be viewed by the individual vendors that will be responding to the requirements and conducting demos
The vendors have their own workspaces where they can manage information specific to their bid / proposal

Therefore, we recommend that you create a new dedicated SpiraPlan program for the initiative and create multiple projects in the program:

One core project that will be used to store and manage the core RFP requirements
Individual projects that will be allocated to each of the vendors. In this example we'll have just two vendors for simplicity.

Furthermore, we recommend that you use a single, dedicated SpiraPlan template for all the projects in the program (including the one storing the core RFP requirements). That way any custom properties and customized fields will be the same across the programs. You will also want to associate the program itself with this standard template:

Now we need to setup the project associations and membership to ensure that the RFP selection team and vendor teams have the appropriate access and visibility.

Defining the Core Requirements for the RFP

In accordance with the standard 7 step vendor selection process, the first step is to define and analyze the business requirements. To do this, you will select the core RFP project and use the standard SpiraPlan requirements management functionality to create the core requirements that each of the vendors will have to satisfy:

Note that we have assigned the various requirements a priority rating. Typically you would define the different priorities so that the vendors will have an idea what the relative priorities are.

You can use the standard 1-4 scale that comes with SpiraPlan or customize it further:

In addition, you may want to create standard test cases in the various vendor projects which are mapped to these requirements to capture how the vendors will support each of the requirements:

Configuring the Project Associations and Membership

First we need to setup the Project Associations so that the core RFP project can share the core requirements to each of the vendor teams. This lets them share the requirements defined in step (1) with the identified vendors from step (2) of the vendor selection process.

In the example screen above, our vendor selection core RFP project is sharing its requirements with each of the individual vendor projects.

Next, we need to allow each of the vendors to be able to report back how their solution matches the needs of the RFP. We do this by allowing each of the vendor projects to share their test cases with the core RFP project:

Finally we need to setup the project membership:

Core RFP Project
- Read/Write Access by RFP Selection Team to requirements and test cases
- Read-Only Access by the different vendor teams
Vendor Projects
- Read/Write Access by the vendor team to requirements and test cases
- Read-Only Access to requirements and test cases by the RFP Selection Team

Vendor RFP Submission

Now that the requirements have been created, prioritized, reviewed, finalized and shared with the vendors, the next step is for the vendors to login to their own SpiraPlan projects, read the requirements and propose the solutions that will best satisfy the requirement. When a vendor goes to their requirements list page, they should choose the option to show requirements for All Products, so that they see both the core RFP requirements and their own specific answers to the requirements:

Then each of the vendors can use the test case module to write their responses to each RFP requirement, using the test execution status to describe how well each requirement is met by their solution.

For example, if we have two vendors:

Vendor A Submission

In this example, vendor A has the following replies:

Vendor B Submission

In this example, vendor B has the following replies:

In the Actual Result section, the vendors can write how they are going to meet the specific requirement needs.

The following methodology should be used:

Passed = The requirement was fully met
Failed = The requirement was not met
Caution = The requirement was partially met
N/A = The requirement does not apply (explain why)

We'd probably recommend you disable the Blocked status in Testing Settings as it won't apply.

Vendor RFP Evaluation

Finally, the vendor evaluation team can look in their project to see how each of the vendors scored against each question:

In this example you can see that Vendor A met the requirement whereas Vendor B did not.

You can then run the Requirements Detailed Report if you want to get this information in a consolidated printable form:

Once the vendor selection is complete, we can then begin the contracting and procurement process. You can use the SpiraPlan document repository to store and manage the various contractual documents from the different vendors as well as the central RFQ documents:

This will then naturally lead onto the vendor qualification process, which is another use case that can be satisfied by SpiraPlan.

Why We Removed the 'Add Comment' Button for Many Users in Spira 7.0

2022-07-12T06:54:28-04:00

Back in the Sands of Time

Originally when we released Spira 5.0 with its latest UI, we did not have a specific 'Add Comment' button. Instead, users simply use the main 'Save' button instead. This allowed them to enter in the data in the various fields, compete any workflow transitions, fill in any required fields, add a comment, and commit these changes with a single Save button.

However there was a problem - what if a user did not have Edit permissions from the item in question, but simply wanted to add a comment as feedback? This was solved by adding the 'Add Comment' button next to the comment field for those users. Now read-only users could safely add a comment, and all was good with the world?

Or was it....

Inflectra, We have a Problem

The problem is that when a user entered a comment and clicked 'Add Comment', if they had Edit permissions, it would trigger a change to the artifact so that when you tried to navigate away, you would be prompted to Save any changes. Worse still, if your workflow requirement a comment to be entered to save the artifact at the current status, you would need to add a second duplicate comment, just to save the changes:

Based on the feedback and observations that having a separate Add Comment and Save buttons was confusing and resulting in duplicate work, we made the following changes in our latest release (7.0):

If you have view and edit permissions for an artifact, the Add Comment button is hidden, and you should use the main Save button.
If you only have view permissions for an artifact, the Save button is disabled, and you will see the Add Comment button that you should use.

And there you have it!

Spotlight on Rapise 7.3: Shadow DOM Support

2022-07-06T22:04:28-04:00

What is the Shadow DOM?

An important aspect of web components is encapsulation — being able to keep the markup structure, style, and behavior hidden and separate from other code on the page so that different parts do not clash, and the code can be kept nice and clean. The Shadow DOM API is a key part of this, providing a way to attach a hidden separated DOM to an element. The Shadow DOM allows hidden DOM (Document Object Model) trees to be attached to elements in the regular DOM tree — this shadow DOM tree starts with a shadow root, underneath which you can attach any element, in the same way as the normal DOM.

There are some bits of shadow DOM terminology to be aware of:

Shadow host: The regular DOM node that the shadow DOM is attached to.
Shadow tree: The DOM tree inside the shadow DOM.
Shadow boundary: the place where the shadow DOM ends, and the regular DOM begins.
Shadow root: The root node of the shadow tree.

You can affect the nodes in the shadow DOM in exactly the same way as non-shadow nodes — for example appending children or setting attributes, styling individual nodes using element.style.foo, or adding style to the entire shadow DOM tree inside a <style> element. The difference is that none of the code inside a shadow DOM can affect anything outside it, allowing for handy encapsulation.

Note that the shadow DOM is not a new thing by any means — browsers have used it for a long time to encapsulate the inner structure of an element. Think for example of a <video> element, with the default browser controls exposed. All you see in the DOM is the <video> element, but it contains a series of buttons and other controls inside its shadow DOM. The shadow DOM spec has made it so that you are allowed to actually manipulate the shadow DOM of your own custom elements.

Shadow DOM Support in Rapise

With the new Rapise 7.3 release, it is possible to view Shadow DOM elements in the Web Spy (works with Selenium Browsers only).

Shadow root elements are marked with the bold label Shadow Root. You can use the Web Spy to build a locator for a Shadow DOM element and Learn it to add into the object repository.

A locator for a Shadow DOM element has two parts separated by @#@ delimiter. The first part (can be either XPATH or CSS) should point to the Shadow Root in the Light DOM. The second part (always CSS) should point to a child element of the Shadow Root. In the case of nested Shadow DOMs there will be multiple @#@ delimiters.

Example of a locator:

automatically built by WebSpy

/html/body[1]/section[1]/div/guid-generator[1]@#@css=input:first-of-type

after manual editing

//guid-generator@#@css=input

Find the example of a simple page with Shadow DOM on UI Testing Playground.

Inflectra Supports ISTC 2022 Testing Competition

2022-07-04T14:52:02-04:00

The Israel Software Testing Cup (ISTC)

The sixth season of the Israeli testing competition was hosted this year at the Daniel Hotel in Herzliya during QAGeekWeek - June 19th - 23rd.

For those testers that enjoying challenges and wanted to become the 2022 ISTC Bug champions, this was the event to take part in:

Do not miss the ultimate testing challenge that will allow you to exhaust your skills Do not miss the ultimate testing challenge that will allow you to exhaust your skills in extreme conditions.

Experienced or new in the field of testing? Participate in the testing competition that will take place as part of the Testing & Automation GeekWeek conference and you may be the best testers in Israel. As part of the competition you will be asked to test a new product within a limited time frame.

The 2022 ISTC Qualifiers and Finals

The qualifying round took place online on Friday 08 April 2022, during which the teams has to test a previously unseen product within 3 hours.
The final stage took place place as part of the Testing & Automation GeekWeek conference, at the Daniel Hotel in Herzliya, June 19th - 23rd.

The winners have been published in the world of tests, on the ITCB website and on social networks.

As in previous years, The ISTC used Inflectra's test management powerhouse - SpiraTest to track and report bugs and issues found in the software under test (SUT) during the competition. Here are the final scores from the SpiraTest ISTC instance:

Congratulations to the winning team and all participants!

For those lucky winners of the first prize - flight, lodging and participation in the Agile Testing Days 2022 conference in Germany - come by the Inflectra booth at the conference and meet the team behind SpiraTest as well as pick up some of our legendary swag.

Recap: Swiss Testing Day in Zürich, Switzerland

2022-06-28T14:35:53-04:00

At Swiss Testing Day 2022, Inflectra was represented by our France-based team member - Farid Khadir, shown here feeling pretty good about the whole thing.

In sunny Zürich, Farid met up with Itecor, our partner. As an attestation to the strong partnership and collaboration between Inflectra and Itecor, the teams shared a co-branded space at the conference. Inflectra showcased its suite of award-winning products, while Itecor presented its expert consulting, management, and implementation services.

The Swiss Testing Day

Geared with a fine array of swag, including charging pads, Itecor-branded hats, and branded pens, the joint team was ready for the conference to begin. The collaboration with Itecor was so natural and fitting that most of our booth visitors thought we were a part of the same company! We talked with attendees like a well-oiled machine. Despite the hot temperature inside the building due to an air conditioning issue, everyone was still eager and ready to speak with us at the booth.

Of the people that visited, many were Test Managers intrigued about how our Test Management tool, SpiraTest, and Test Automation tool, Rapise, coupled with Itecor’s implementation services, can help their organizations.

Throughout the day, we got to see a few keynotes and visit some other exhibitors at the conference. Our friend Jonathan Wright at Keysight/Eggplant came over to say hi and left repping an Itecor cap and Inflectra stickers. It was nice seeing you, Jonathan!

This conference marked the end of Inflectra’s “Spring Conference European tour” through Copenhagen, Paris, and Zürich. We are grateful for the opportunity to represent Inflectra at many global events this year.

See you next year, Swiss Testing Day! Until then, stay strong!

Who Does Nathan Latka Call "The Real Unicorn" And Why?

2022-06-28T13:29:20-04:00

A few weeks ago, Inflectra’s CEO - Adam Sandman, was invited for an Interview with Nathan Latka - a serial entrepreneur and the CEO of FounderPath. Unlike what you’d expect from an interview with a tech company founder - i.e., a pre-cleared set of interview questions - the two launched into an honest discussion in less than 30 seconds after meeting each other for the first time. The result is a candid view of Inflectra, its business model, company culture, profits, business practices, and its founder - Adam Sandman - aka - “The Real Unicorn.”

Find out how & why Adam got this nickname in a short (admittedly, very fast-paced) conversation below!

InflectraCON 2022 - Major Take Aways

2025-04-01T22:17:47-04:00

Leadership

Hire the right people - DO NOT micromanage them - put them in the right place. Build a strong team.
Companies should do four things to demonstrate leadership. First, set up a mentoring program for people to practice developing others, second, have a coaching program to develop themselves. Third, introduce training programs for continuous improvement, and fourth, consider becoming sponsors of experiential programs at local colleges.
Influence is not about impressing people. It’s about connecting with them. Connecting is not impossible but may be out of your comfort zone.
You Have the Power to Create a Voice to Change the World through Better Oral Communications and Deeper Relationships
The one thing you should want to do as a senior leader is to provide a good work culture.
If you’re in a leadership position and it’s all about you, you’re not meant to be in a leadership position.
If you do not know your people, you are not a leader.

Artificial Intelligence & Big Data

Information overload coupled with misinformation is creating a trust deficit. "The solution relies on knowledge discovery, i.e.: extracting insights from data.”
“A Knowledge revolution happens when AI tools & humans work together.”
In order to be competitive, you have to be a master of data. A competitive advantage is gained by weaving data strategy across all parts of the organization.
Event-driven architectures become viable for building new apps by 2024

Quality

Figuring out what allowed an error is more important than trying to figure it out who made a mistake.
Compliance is a culture. If you see something wrong, you must say it
The good thing about standards is that there’s one to follow. The bad thing is that there are too many
“Great testers don’t find bugs. They help the team eradicate problems from the beginning.”
There is no perfect software. Done is better than Perfect. And Done can be negotiated.

Risks & Risk Management

Consider the complexity of Risks - even if a feature is stable and has a low defect count, if the feature is complex, then that should be considered as part of the Risk Assessment along with History and Impact.
Conceptual, Technical, and Schedule Risk types for Software development can be reduced with Agile methodologies.
Using the “What’s the least bad idea?” exercise helps reveal hidden risks.

DevOps

DevOps is a philosophy, a way of thinking, not a technology.
Most of the waste has nothing to do with processes but rather the stuff we do ourselves… the stuff that has nothing to do with the end product or customer’s needs.
DevOps is a mechanism for increasing the value of your product to the customer.

Agile Project Management

Channel all your work through one board…it's like having in-laws, they’ll always point out your flaws.”
“If everything is critical, nothing is.”
The role of the Business Analyst is to understand how to ask for customer needs in multiple different ways, taking into account multiple perspectives. Business Analysis is about the Why.
Agile is about learning one thing today and adapting it the next day.
In order to respond to changes in society, you need to have business agility.

User-Centered Design

Ask a lot of whys…there’s always a deeper meaning [to customer desires].
Human beings are notoriously bad at predicting their own behavior.
“The optimal number of prototypes/ideas to have at one time is five.” [Anything else is counterproductive]”
“Make sure that you solve the emotional problem.”
“The main point of testing is re-experiencing empathy (understanding not sympathy).”
Games and puzzles help participants learn about the subject and observers learn about the participant.
It makes social and economic sense to plan for a better user experience by incorporating design philosophies that address Accessibility.
Users’ time and technology belong to them, not us.

The Metaverse

Digital economies transcend countries and banks.
In the metaverse first place is your home, the Second place is your workplace, and the third place is where you relax in public, where you encounter familiar faces and make new acquaintances.
Most of our data comes from our subconscious.

Security & Privacy

82% of our web traffic contains cookies. 37% of all sites use non-secure cookies.
They’re watching you…With our full consent.

The most attended topics were

We appreciate all the speakers who gave amazing talks on a wide variety of topics, here were some of the most popular ones:

Tech and Metaverse - Keynote: Tech, Gaming, And Metaverse - Jenn Bonine
Automation - Keynote: Myths About Myths About Automation - Paul Grizzaffi
Software Testing- Keynote: Discussions Testers Should No Longer Be Having - Mike Lyles
DevOps - Keynote: Alphabet Soup - What Do DevOps, DevSecOps, DevTestOps, SecDevOps, etc. Really Mean??? - Jeffery Payne
Scrum and Kanban - Scrumban: Effectively Combining Scrum And Kanban - Bob Payne

If you would like to see some photos from the event, check out the photo gallery.

Looking forward to InflectraCon™ 2023

InflectraCon™ 2023 invites you to submit expressions of interest to speak at InflectraCon™ 2023 in Washington DC on April 20-21. In 2023, the InflectraCON theme is Quality, Agility, and Security.

For InflectraCon 2023, we are looking for talks that fall under one of the following rubrics:

> Submit Your Talk for InflectraCon 2023 Today!

One More Thing: The Star Wars Theme Party

Of course, we at Inflectra like to play hard as well as work hard. So our entire team dressed up in festive attire for the Star Wars-themed happy hour and networking event. The DJ provided some excellent local sound; The themed backdrops provided opportunities for fun photos; The food and wine kept everyone merry. People then headed off to dinner or to the rooftop bar at Union Market.

See you at InflectraCON 2023 in Washington, DC on April 20-21, 2023!

Series of Conversations On Risk and Risk Management - The Expert Panel

2022-11-29T12:12:17-05:00

Contrary to popular thinking, risk management is not just a purview of an organization’s leadership or those managing the delivery of products and projects. It is becoming increasingly clear that everyone in the organization should be involved in risk management - making decisions that minimize adverse effects or maximize potential opportunities created by the perceived risk.

Sound risk management practices create the enabling environment for people to collaborate and invest in the success of their product and project. Whether it is reducing the total cost of ownership, increasing the revenue recognition, or augmenting the operational excellence, including risk management conversations at multiple key touchpoints benefits individuals, teams, and organizations alike.

This series will be useful for a diverse group of professionals working to develop scalable, secure, and stable solutions, including business analysts, product managers and owners, scrum masters, release train engineers, and of course, risk managers.

SERIES DETAILS:

1. Current Issues in Risk Management - Thursday, July 14, 2022, at 2 PM (EDT)

In the first discussion of the series, the panelists will offer a broad context of risk management in an industry-agnostic way. The conversation will mainly concentrate on corporate- and product-level risks in technology, security, and operations.

Panelists:

Adam Sandman (Inflectra), Jenna Charlton (Functionize), and Kartik Shah (Skyscape)

Register today!

Security as Risk - Thursday, September 15, 2022, at 2 PM (EDT)

With the proliferation of the 4th Industrial Revolution (4IR), this panel will discuss security as a manifestation of significant risk. In the era of data privacy and regulatory compliance, the challenges and solutions for security risks must be thoroughly understood, weighed, and mitigated. In the second conversation of the series, the experts will discuss the increasingly significant role Risk management will play in developing products and processes in the cloud, AI, and Big Data space.

Panelists:

Adam Sandman (Inflectra), Ian Frazier (Inflectra), and Ravi Subramanyan (HiveMQ)

Register today!

Implementing FMEA in the Age of IoT - Thursday, October 13, 2022, at 2 PM (EST)

Failure Mode Effects Analysis (FMEA) is a particular form of Risk Management within the manufacturing, automation, and related industries where the ability to detect risk events is as important as assessing and resolving the risk. The panel will focus on the FMEA and risk management in today’s products, projects, and processes and share good practices and lessons learned.

Panelists:

Sriram Rajagopalan (Inflectra), Mani Gunasekaran (KeHE Distributors), and Balazs Sarkany (Phoenix Tailings)

Register Today!

Embedding GAMP Compliance into Digital Health Software - Thursday, November 10, 2022, at 2 PM (ET)

Good Automated Manufacturing Practice (GAMP) is a general automation manufacturing process. It is often associated with the e-health software development and validation as a Risk-Based Approach to Compliant GxP Computerized Systems. The ability to implement validation testing will be the focus of this webinar.

Panelists: Sriram Rajagopalan (Inflectra) and Clare Beck (Celerion)

Register Today!

CAN’T ATTEND ONE OF THE EVENTS?

See you there!

#teamInflectra

Inflectra Hosts its Premium Partners at InflectraCON 2022 in Washington, DC

2022-06-24T14:24:08-04:00

About InflectraCon

InflectraCon is Inflectra’s global user conference that took place this year on May 5-6th in Washington, DC, the home of Inflectra headquarters. This year’s event featured Spira training, four great keynotes, two full, substantive conference tracks with speakers from around the world, and a Partner Summit.

The Partner Dinner

We were fortunate to get to spend some excellent, quality time with our partners. We kicked off the event on the evening of Wednesday, May 4, with a partner dinner at The Prime Rib in DC.

The dinner gave us the chance to mingle in person with people we typically see over Zoom, and the staff at The Prime Rib took excellent care of our large crew.

The Partner Summit

Thursday ushered in talks, networking opportunities, and the Partner Summit. The morning session started with an ice breaker, where participants introduced themselves, stated their company, where they are personally located, and provided a fun fact about themselves (the on-the-spot fun facts never fail to be funny!).

We then proceeded to hear from Adam Sandman, Inflectra CEO, on an overview of Inflectra and where we’re headed from both tools and a company perspective in 2022 and the years to come. He also discussed the state of the industry as acquisitions, mergers, and new tools impact the market. Partners learned how to navigate the partner portal, and we engaged in open discussion on tool features that are helpful for specific industries.

The afternoon session focused on an Inflectra sales and technical boot camp for partners who may be more focused on sales engineering than technical implementation. We enjoyed having time to spend specifically with our partners in the Partner Summit, and we look forward to doing something similar at InflectraCON 2023!

The Star Wars Theme Party

That evening, Inflectra members and attendees dressed up in festive attire for the Star Wars-themed happy hour and networking event. The DJ provided some excellent local sound; The themed backdrops provided opportunities for fun photos; The food and wine kept everyone merry. People then headed off to dinner or to the rooftop bar at Union Market.

Friday afforded us a chance to meet with several of our partners one-on-one to discuss more in-depth marketing strategies, business opportunities, and plans for 2022, 2023, and beyond. The “Partner Minute” at Friday’s lunch allowed partners to describe their business in 60 seconds, which was informative and fun. At the end of the day, conference attendees gathered for a raffle of prizes from partners who also sponsored InflectraCon. We wrapped up with a final session, and partners and attendees proceeded on their way.

It was sad to say goodbye, but we are buoyed by the success of the conference. We are thrilled to see our partners again at InflectraCON 2023, if not before...

Meanwhile, thanks so much for our partners for attending:

Spotlight on Rapise 7.3: New Selenium Based Recording for Chrome and Edge Browsers

2022-06-22T22:36:40-04:00

Overview

Rapise 7.3 includes our new Selenium WebDriver based Recorder and a major upgrade of the Selenium WebDriver downloading and configuration mechanism within Rapise. The recorder has all the features of the old Rapise plugin-based Web recorder and also offers new features for doing multi-tab and multi-window recording. Best of all it no longer requires installing a plugin for either the Chrome or Edge browsers.

New WebDriver Downloading Mechanism

In Rapise 7.2 we introduced the automatic downloading of WebDriver executables (chromedriver.exe, geckodriver.exe, etc.). However it required a few configuration steps to set up. Now in Rapise 7.3, driver downloading is completely seamless and performed automatically by Rapise when needed. Rapise automatically detects the correct version of required driver executable both for standalone browsers and embedded ones (e.g. Chrome in Microsoft Teams, Skype, Microsoft Unified Service Desk etc.). Every downloaded driver executable is saved with the version information in its name. Rapise automatically switches executables based on the executed test.

Here is the example of SeleniumDrivers folder on a machine with Rapise:

Basic Features of the New Recorder

In addition to supporting Google Chrome and Microsoft Edge without needing the installation of a plugin, the new Selenium recording has the following primary features:

Works with standalone Chrome and Edge
Works with embedded Chrome
(Electron, Microsoft Teams, Skype, Microsoft Unified Service Desk, etc.)
No browser plugins required, auto download/switch of browser compatible
1. chromedriver.exe,
2. msedgedriver.exe
Full recording support: Record, Learn and Verify
Self-healing locators and WebAppProfile supported
WebSpy with tracking/highlighting support

Advanced Features of the New Recorder

In addition, these new features are good reasons to try out the new recorder and switch from the old one, regardless of the Chrome Manifest V3 update:

1) Play tests while doing other things on a machine.

The new recorder just like the player of Selenium tests works with separate browser profiles that do not interfere with thebrowser profiles you use for daily work.

2) Initial URL prompt.

If the recorder launches a new browser instance, it prompts the user for the starting URL. The list of recent URLs is preserved.

3) Multi-tab, multi-window recording.

The new recorder generates: Open, ActivateWindow, CreateTab and Close steps automatically, to handle different tabs and windows:

4) Browser auto reconnect.

The new web recorder lets you record a few steps, stop recording and then start another recording session - Rapise will reconnect to the running browser. This new auto reconnect functionality also enables such frequently used RVL features as Play Selection, Play From Here and Play This Sheet.

Future Plans

Once Rapise 7.3 is released, we have the following future plans for Rapise:

Add support for Selenium based recording with Firefox to avoid need for the Firefox plugin.
Add recording support for Apple Safari and mobile browsers - currently Rapise supports playback only

Recap: Agile+DevOps West in Las Vegas 2022

2022-06-20T18:45:20-04:00

Inflectra Team in Las Vegas

The US based team, Adam Sandman, Jessica Moore, Rick Baucom and Sriram Rajagopalan traveled to Las Vegas on Tuesday.

Leaving extra time to set the sponsor booth in the expo hall, acclimatize to hot temperature, and adjust ourselves to the new time zone, the #teaminflectra also spent some time walking the Las Vegas Boulevard enjoying a meal at the Gordon Ramsay Pub.

We had two members who had never visited Las Vegas and we walked across the Paris Eiffel Tower setup, roamed through the malls with numerous Casinos, and witnessed the dancing foundations in the Bellagio.

This area was the place where Ocean 11 was filmed. Finishing our dinner at the Caesar’s palace, the #teaminflectra was ready for day 1 of the conference.

Day 1

Inflectra Booth at Agile DevOps West

Despite setting the booth early, the #teaminflectra ran through their final checks on the days of the conference ahead of time to greet people hungry for information!

Adam Sandman and Jessica Moore were greeting people answering their questions and discussing partnerships while Rick Baucom and Sriram Rajagopalan were demonstrating the features of our products.

Our team were demonstrating to visitors: SpiraTest for Test Management, SpiraTeam for expanding SpiraTest with additional features and Task Management, SpiraPlan for augmenting SpiraTeam with program, portfolio, and risk management, and Rapise for codeless test automation.

Industry Technology Presentation by Sriram Rajagopalan

Sriram Rajagopalan started his talk in the favorite movie trailer format! “In a world where Agile and DevOps talks focus on technical agility, one person, Sriram Rajagopalan from Inflectra raises to the occasion, discussing the importance of team’s focus on business agility through value stream generating value for customers!” connecting with the story-telling format of the keynote. As the crowd burst into applause, Sriram Rajagopalan emphasized the importance of how value flows both vertically and horizontally requiring teams to collaborate outside of the “Shift-Left-and-Shift-Right'' mindset and into “Shift-Up-and-Shift-Down''.

The audience’s continued engagement with the synthesis of the statistical data from the State of Agile surveys and the upward and downward flow of value demonstrations in Scaled Agile Framework (SAFe) and Disciplined Agile Delivery (DAD) was clear with their questions during the session. “Your demonstration of value brings a lot more clarity than what SAFe diagrams and trainers teach,” said one participant representing the financial industry. “Your visuals in the presentation are stunning and engaging,” commented another participant!

Bringing more clarity through visual animations and powerful discussions into his own unique STEP approach to business agility by managing risks through strategic agility, technical agility, execution agility, and portfolio agility, Sriram Rajagopalan drew further focus into how SpiraPlan supports all these dimensions for supporting business agility!

If you want to bring his presentation to your team and how SpiraPlan can support your business agility, reach out to Thea Maisuradze at marketing@inflectra.com

Team Inflectra wrapup

The #teaminflectra walked towards the Venetian mall awestruck by the Gondola ride and the false ceiling.

Somehow figuring out the maze of where we wanted to eat, the team spent recapping our day and planning for the next day!

Day 2

Inflectra Booth at Agile DevOps West

The #teaminflectra continued to address questions from some of the audience from Day 1.

Asking time for demo and seeking technical questions on automation, the Day 2 continued supporting the team.

And, yes, there were also people that stopped by to collect the famous Inflectra "James Bond" pens based on others' recommendations.

As the day progressed, the #teaminflectra spent time catching up with other sponsors that expressed an interest in sponsorship.

Sponsoring the Leadership Summit

Inflectra was proud to sponsor the 2022 Agile and DevOps Leadership Summit at the conference. Adam Sandman introduced the importance of Leadership in navigating through strategy and culture and distilling it to the team level for agility to survive as part of its culture.

Sriram Rajagopalan facilitated some of the initial team discussions in preparation for what people wanted to talk about the following day at the Leadership Summit.

Wrap Up

After disassembling the booth and packing it all up, #teaminflectra took a cab from Las Vegas Boulevard to the historic Fremont District area of Las Vegas.

Sriram Rajagopalan and Adam Sandman spotted the International Hotel in the James Bond movie, Diamonds are Forever, and also the car chase near the Golden Nugget Casino.

We spent time walking through the open-air mall and spending time in the original Atomic Liquors cocktail bar! Believe it or not, we were able to take part in their 70th anniversary celebration. They are famous as the place where local residents would watch the Atomic Bomb tests, starting in 1952.

And, yes, on the way back, we spent time dancing to the old rock songs and returned to the hotel.

But as they say... what happens in Las Vegas.... stays in Las Vegas, :-)

Recap: JFTL in Paris, France

2022-06-17T15:44:38-04:00

Team Inflectra in Paris

The US-based Inflectra team left a few days prior to the conference to adjust to the new time zone and to enjoy the magical city of Paris in the summer (plus eat a croissant, or two!). Blessed with nice weather, we saw the oh-so-iconic Tour Eiffel, and for a bonus, the place where a scene from the movie Inception was filmed (Pont de Bir-Hakeim, anyone?).

After walking until our feet ached and our bellies were full of the delicious pastries and delicacies that Paris offers, we welcomed our two other team mates arriving from Marseilles and Copenhagen. We settled into Novotel Paris 14 Porte d’Orléans just outside of la Boulevard Périphérique. After settling in, we checked out the conference center, Le Beffroi de Montrouge, to set up the booth.

Le Beffroi de Montrouge combines architecture from the 1930’s with a new, modern infrastructure, and is an ideal spot for holding seminars, conventions, product launches, trade fairs, and of course, the annual JFTL.

After completing the booth, we had a nice dinner at a local restaurant to catch up and strategize for the conference the following day.

Inflectra Booth at JFTL

Early the next morning, we pulled our Inflectra polos on and had breakfast (and several cups of coffee) at the hotel prior to the expo starting at 8:30 AM. Well-equipped in our booth, we were ready for the onslaught of attendees!

Our Inflectra team consisted of two native french-speakers familiar with the French testing crowd, one technical expert who could demonstrate SpiraTest for test management, SpiraPlan for project, program, and risk management, and Rapise for test automation, and one partnership- & alliance-focused team member who could talk with existing and potential partners. As JFTL is predominantly composed of french-speaking companies, we were happy to have a both french and english speaking team!

While the conference itself seemed like a smaller crowd compared to last year’s, it left us with more time to scope out the other sponsor booths and build relationships with sponsors and attendees alike. We also had the opportunity to provide demos and answer technical questions for customers currently using Spira and/or Rapise on our ipads showcasing live environments. We were, of course, happy to hand out our unique swag, including wireless charging pads and stickers crafted by our own Head of Products.

To get over the afternoon slump, the JFTL organizers provided us with a nice catered lunch full of amuse-bouches, followed by espresso and a lovely spread of pastries. Macarons and Spira–they just go together!

Reconnecting with Customers & Partners

While in Paris, we had the opportunity to catch-up with several of our partners and customers in the area. A special shout-out to Vlad from Inmarsys, our partner based in the UK, who flew to France for one day to have lunch with us. It was a pleasure, Vlad!

We also met up with our partner Alex from TTC as well as a few other customers attending the conference. It’s times like these where we are grateful to have connections all across the globe. It’s always gratifying to see who we collaborate with on a daily basis, usually online on Zoom or email, in-person. Thank you to all who made an effort to see the Inflectra team.

Au revoir, JFTL !

After the full day of interacting with sponsors and attendees at the booth, we were grateful to rest our feet at the end of the day. And as you can see…

we are already brainstorming for next year’s booth at JFTL!

À bientôt !

Recap: EuroSTAR in Copenhagen, Denmark

2022-06-12T21:59:51-04:00

Arriving in Copenhagen

Like secret agents in a movie, #TeamInflectra set out from various locations around the world (well mainly, Maryland, Virginia and Marseilles) the weekend before the event to meet up, plan for the event, get over jet-lag and also have some time for catching up and team-building before the start of the event.

Flying in to Copenhagen airport, we got to enjoy the streamlined aesthetic and cool Nordic architecture. We also marveled at the worlds most sophisticated 7-11 store right in the airport terminal!

From there, the team traveled on the super-cool Copenhagen metro to the Bella Conference Center and adjacent AC Marriott Bella Sky Hotel.

This was to be our home for the next four days. Featuring ground-breaking architecture from Danish 3XN Architects, the hotel consists of two inclined towers, standing 76.5 m tall with an inclination in opposite directions of 15°. From our hotel rooms on the 20th floor, we had an unparalleled view of the center of Copenhagen as well as the surrounding countryside. Sadly, due to the demands of the conference, we didn't get to spend too much time in them!

Before turning in for the night, the team designed to test drive the bar and lounge in the Hotel, since we are software testers, we tested a selection of the local cocktails, beers and small plates. After some exploratory testing we decided to leave the load testing to another evening....!

Inflectra Booth at the Expo Day 1

After settling in for the night, Team Inflectra was up early at the crack of dawn (or at least 07:30) for the first day of the event. Thanks to the sumptuous spread put on by the hotel, we were suitably filled up and ready to spring into action.

The team assembled in the Expo to prepare the Inflectra booth, ready to demonstrate SpiraTest for test management, SpiraPlan for project, program and risk management, and of course Rapise for test automation. The Expo provides a place where people come to explore the latest solutions, technologies, and tools in testing. The Expo also provided a place to network with other vendors and attendees and see what the latest developments are in the industry. It's also a great place to learn about the news and plans from both our competitors and partners.

For those who have attended our other events, you will know that #TeamInflectra prides itself on having the best swag at the event. This time we did not disappoint. From our lovingly handcrafted stickers (thanks Simon for all your wonderful designs) to the blue tooth headphones, wireless charging pads and "James Bond" pens, we were the talk of the town!!!

As well as coming for swag, attendees were really excited to learn about our products and get live demonstrations from the team. We use a series of iPads loaded with our products to make the demonstrations personal and interactive.

At the end of the first day of the Conference, it was time for the Expo Sponsors Reception. Held in the Expo area, it was a good time to network with the attendees and other exhibitors, learn about their pain points and of course partake in the most excellent wine and beer that was available. Thanks EuroSTAR for putting on such a great spead.

After the drinks reception, #TeamInflectra took the opportunity to taste some traditional Danish cuisine at the BASALT restaurant in the hotel. Featuring the following approach to cooking:

B A S A L T is a tale about fire and mankind. The fire that allows us to tame the wild to create something unique. The fire that gave us security, became a gathering point and a gastronomic tool. It’s right here around the fire that we create, eat and live - and invite our guests on the journey.

We enjoyed the Danish côte de boeuf roasted on the bone accompanied with a medley of fire-roasted vegetables and followed by brioche twirls served on coal, chocolate, browned butter. Truly an inferno of a meal!

Inflectra Booth at the Expo Day 2

The team reassembled for the second day of the Expo, where we met testers, designers, developers and managers from companies all across Europe. We were excited to learn about their challenges and then show them the power and ease of use of our Spira platform:

We also managed to give away all of our goodies and merchandise!! Overall the tone of the event was one of happiness and thankfulness. After two years of lockdowns and restrictions, people were almost giddy with excitement at being able to chat and interact with "real" people. Compared to the conferences pre-pandemic, it did seem that that attendees were more engaged and attentive than ever before.

The EuroSTAR Software Testing Awards Gala

One of the really unique parts of the EuroSTAR event is the dinner and Awards Gala that they put on each year. Reminiscent of The Oscars, the Awards Gala is fun place to dress up in fancy clothes, let your hair down and enjoy an amazing dinner with your fellow conference goers. This year it was event more special by being held at the famous Wallmans Circus Cabaret in #Copenhagen.

Part theater, part musical, part drag-show, it's hard to describe the event entirely. The waiters and waitresses double as cast members in the show itself.

There is dancing, singing, high-wire trapeze, flying pianos and musical tributes to The Eurythmics and Queen. We had a lot of fun, and due to the exhilarating nature of the event, decided to resume our load testing of the local bar scene in Copenhagen, however as they say "What happens in Copenhagen Stays in Copenhagen" :-)

Seeing Familiar Faces

Finally, we would like to give a "shout out" to Fahim and the team from Global App Testing in London, who we've not seen for the past two years. They were excited to co-sponsor a special drinks reception to customers and partners in the roof-top Sky Bar.

We don't have any photos, but we were also delighted to meet Darren and Kayla from our partner The Test Consultancy (TTC).

That's a Wrap!

After a final third day of the Expo, the team were exhausted but tired from the week's activities. We really enjoyed reconnecting with our friends, partners and colleagues in Europe...

... and are looking forward to repeating the whole thing again Next Year in Antwerp!

Spotlight on Spira 7.0 - Data Synchronization Usability Enhancements

2022-06-12T17:30:41-04:00

Data Synchronization Changes

When you are using SpiraTest in conjunction with other issue and task management tools such as Jira, Azure DevOps, GitHub, GitLab or service management systems such as Salesforce or ServiceNow you will need to use the Inflectra data-synchronization services platform to seamlessly orchestrate the data. Version 7.0 of Spira will include major usability enhancements to simplify the initial setup and configuration process. In particular, instead of the administration screens being completely generic, they will now automatically adjust based on the choice of the tool being integrated with.

Current User Interface

In the current (6.x) version of Spira, when you go to the main Data Synchronization administration home page, you will see the list of configured plugins. They are all displayed without any icons or branding:

When you click on the Edit button for any of the plugins, they will display the following generic fields:

Connection Info
Login
Password
Custom 01 - 05

The problem is that different tools use different types of value for these fields. For example, some tools use a URL for the Connection Info, others just use repository names. Similarly, some tools use a login/password whereas others use an API Key.

Finally, the plugin-specific Custom 01 - 05 boxes are different for each plugin (by design) but offer no examples, documentation or helpful notes on what value is meant to be entered. You have to go to the data synchronization part of SpiraDocs to find the values that should be entered.

New User Interface

With Spira 7.0, when you go to the main Data Synchronization administration home page, you will see the list of configured plugins. However, now they will be listed along with an icon that denotes that the plugin has tool-specific documentation and configuration information available. Any plugin that doesn't have an icon, will use the older, generic fields. We have added the new documentation meta-data for the most popular plugins only.

When you click on the Edit button for the Jira plugin (for example), you will now see the following fields that are specific to Jira:

Instead of the generic fields displayed previously, it now uses the Jira-specific field names instead of Custom 01 - 05 and the Connection/Login/Password fields are updated to reflect the values that Jira actually expects.

If you click on the Microsoft Azure DevOps (ADO) plugin, you will see a similar screen, except that the various fields are now specific to the values needed by ADO:

For each of the fields, the new system provides:

Customized Name
Tooltip and Notes that provides inline help
Placeholders that show the way the values should be entered

Using SpiraPlan for Demand Management

2022-07-19T15:54:07-04:00

Demand Management Overview

When you are considering how to setup a demand management system and process within an ALM solution such as SpiraPlan, it is important to understand the key use cases that need to be supported:

Be able to configure workflows for the demand process of requesting new applications. Workflows need to include stakeholders such as business unit representatives, demand managers, portfolio managers, QA and IT employees, data privacy officers and other.
Be able to work on central work-lists for demands with standard functions for sorting, filtering, sending out email notifications for defined events.
Automatically match application requests against existing application inventory.

In addition, a cohesive demand-management process needs to closely integrate with the following other business functions and systems:

Software Asset Management (SAM)
Project Portfolio Management (PPM)
Enterprise Architecture Management (EAM)
IT Service Management (ITSM)

Configuring SpiraPlan for Demand Management

Creating a Demand Management Project

In order to manage the requests for new products and applications, we usually recommend that customers setup a dedicated demand management product in SpiraPlan that will be used to track the requests for new applications (products) that will eventually (if approved) become their own new SpiraPlan product. So the first step will be to create a new SpiraPlan product called "Demand Management". It should be stored in an existing program and portfolio dedicated to the management of cross-portfolio activities such as demand management, vendor management, application decommissioning, etc.

In this example, we have created a dedicated product template called "Demand Management and Portfolio Management" that will be used to manage the customizations and workflows associated with the demand management process. Viewing the product in the main navigation would look something like this:

Where Demand Management lives in the special program called "Portfolio Management". We will now describe the configuration that is recommended for this special SpiraPlan product.

Setting up Requirement Types

The first thing to do is create the different requirement types for the different types of new application that will be requested. In this example, we have simply added a single type called "Demand" and mapped it to the corresponding workflow for new software projects.

You can have just one type of request called "Demand" and have a single workflow, or you can create multiple workflows for the different types of application being requested:

In this more complex example, we have two different workflows (software and hardware), which would allow us to have multiple requirement types:

The mapping can be one to many (many types can use the same workflows), so we could further categorize the software and hardware new application requests into more granular types.

Setting up Components for Projects

Now that we have defined the different types of new request, we can further categorize the different new product requests by making use of the product Component field. In this we can define the primary different types of product that will need to be prioritized and planned. In this example, we defined the different types of new product as: hardware, software (GxP), software (non-GxP) and wetware. This example was taken from a life sciences case study where we had to deal with regulated (GxP) and non-regulated software applications as well as medical devices (hardware) and wetware (pharmaceuticals).

Depending on the industry you are working, you will have different ways of categorizing your new product demands.

Setting up the Custom Properties

The next thing to do is to configure all of the different attributes you will need for categorizing and measuring the different new product ideas and requests that are being compared.

In this example we have added four free text custom properties to capture the following key information:

Project Goals - the key goals and objectives of the new system or application being considered
Project Boundaries - the main constraints and restraints on this new application
Time Targets - an overview of the desired schedule and any external deadlines
Business Value - a description of the business value that this new application or system will bring

For these keys of attribute, you will typically want to define them as a rich text field:

In addition to these fields, you may also want to add:

Numeric fields to capture the budget, costing or other financial data
List fields to capture attributes that you pick from a dropdown list:
- Complexity rating - high, medium, low
- Methodology - agile, waterfall, hybrid
- etc.

Configuring the Demand Management Workflows

The last step of configuring the demand management product in SpiraPlan is to customize and configure the workflows for the different types of new product request that you are supporting:

The decision on how many workflows to have depends largely on your organizations review and approval process. If each of the different types of new product request follow the same approval process, then they can all share the same common workflow, but if that approval process differs between types, then you'll need to clone the workflow and customize to match each approach process.

Using SpiraPlan for Demand Management

Now that we have setup the dedicated demand management product, we can now use this to begin tracking the new product requests as they come in. They will be logged directly into the requirements module of SpiraPlan as a new Demand. Using the sortable grid view, we can easily view the different columns (name, priority, status, type, component, business value, goals, boundaries) to be able to filter and sort the new requests.

In addition, we can use the release Gantt chart view to create a major release for each year and phases for each of the quarters in the year. This will allow us to easily track the planned new applications and activities by quarter:

In addition to the grid and Gantt views, you can also easily display an agile board view of the new products being requested:

This provides a visual way to see the requested applications, and drag and drop them between the different components and priorities:

Once you have ranked and prioritized the incoming demands, you can then use the release view of the planning board to assign the applications from the portfolio backlog into the different quarters. This lets you plan the prioritizes for each of the upcoming quarters in the current (and future) investment years.

These views making creating, managing and visualizing the flow of new product requests easy and simple to use. However there are additional features available to further orchestrate your demand management process.

Approvals and Sign-Off

The workflow feature in SpiraPlan lets you easily manage the review and approval of the new application requests. You can simply use the workflow operations dropdown to transition the request from one status to the next:

You may want to attach documents or other information to the new application request. That is done through the Attachments tab of the item. However those documents are centrally managed and versioned within the SpiraPlan document management system for your convenience:

In addition, you can add comments or other information during the review and approval process to capture the feedback and ideas in real-time:

The comments and feedback will be emailed out to anyone configured to receive the notification event or anyone who has explicitly subscribed to the item in question.

Integrating Risks

One other key aspect related to demand management is the need to assess any risks associated with the proposed new initiatives and make sure that we have a place to capture, assess and evaluate the risks, which will inform the demand managers on the relative risk rating of each of the proposed products in a given quarter or year.

In SpiraPlan, you can easily create a risk register and link it to the different new product requests:

Instantiating an Approved Project

Once the new application request has been approved and formally planned, you can now transition this request into a new SpiraPlan product using the Administration > Add Products screen:

You will be able too choose either an existing product template or create a new bespoke one, depending on whether this new product will use an existing development methodology or a new one. In addition, you will be able to group this approved new product under the appropriate SpiraPlan program and portfolio so that it can be managed.

Managing Programs and Portfolios of Projects

Once you have created the new approved product, it will be available in the enterprise, portfolio and program dashboards within SpiraPlan. For example, if you look at the schedule widget on the dashboard:

The new product will appear in the timeline, nested under its appropriate program and portfolio. As the product is defined and refined to have its own release schedule and cadence, those releases will now appear in the timeline along with the % complete shading, let you know the progress of the product. At this point, we are no longer in the demand management phase of this new idea, but instead into program and portfolio management.

Spotlight on Spira 7.0 - New Plugin Architecture With SpiraApps

2022-06-06T04:43:38-04:00

Overview

One of the key attributes of the Inflectra Spira platform is that it is a complete, integrated turnkey solution for companies that need to develop, test and manage their software applications. However there are specific features that are needed by different industries and methodologies that would be better served by a more extensible set of ‘add-on’ features to the core system. For example working in healthcare you have to comply with 21 CFR Part 11, whereas in automotive you need to support ISO 26262. This new plugin architecture will allow Inflectra and its customers and partners to provide increasingly niche features for different industries.

Inside Spira, administrators will be able to browse the list of SpiraApps and enable them at a system level:

Once an App has been enabled in a Spira instance, individual project owners can then enable it for their specific product / project:

In the previous blogs we have described some of the plugins that will be shipped by default with v7.0 - GitLab, GitHub, CircleCI and FMEA, but we have two more plugins that will be part of the initial release:

Standard Tasks and Test Cases for Automating Steps to Doneness
Default Descriptions for new Artifacts

Standard Tasks and Test Cases

The purpose of this plugin is to allow you to create standard tasks and test cases for a requirement or release. A user will have a dropdown menu in the requirement and release details pages that lists different sets of standard tasks and test cases that can be auto-created for the current requirement/release.

This will allow you create a “checklist” for a release or requirement that would be completed.. For example, a release deployment checklist could be a set of tasks. A "steps to doneness" could be a set of standard tasks and test cases (unit, acceptance, UAT) for a requirement.

The product admin will be able to fill in four multi-line plain text boxes:

Requirement - Standard Tasks
Requirement - Standard Test Cases
Release - Standard Tasks
Release - Standard Test Cases

From there, the system will generate the series of tasks and/or test cases when you click on the appropriate menu entry inside Spira:

Default Descriptions

This plugin lets you specify the default rich text Description for a variety of Spira artifacts. It is often requested by clients who want to have a standard “template” for logging a new incident or creating a new requirement.

To use this plugin, once activated by administrators, you can setup the default rich text description for any of the following supported artifacts:

Requirements
Test Cases
Releases
Tasks
Incidents
Risks

Then when a new artifact is created, the description will be pre-populated by the appropriate text template.

Recap: STAREAST in Orlando, Florida

2022-05-02T13:54:52-04:00

Meeting at the National Airport in Washington, DC

Early Tuesday morning on April 26th, #TeamInflectra headed to the DCA airport, swag in tow, ready to take on the STAREAST conference. It just so happened we ended up wearing matching travel outfits, too (completely unplanned!).

Arriving at the Rosen Centre in Orlando

After touching down in Orlando, we made our way to the conference destination: The Rosen Centre. The Rosen Centre is known for its distinct architecture and wide variety of uses, from business, entertainment, to family fun. Inside the hotel were large ballrooms and flexible spaces used for the conference expo, keynote talks, and reception. The space did not disappoint!

Once we settled into our hotel rooms and dropped off our baggage, we had lunch at the restaurant out by the hotel pool. Feeling fueled, we then set up the booth in preparation for the expo taking place the next day. We could feel the conference buzz in the air!

Seeing Familiar Faces

That evening, we joined the attendees and sponsors of the STAREAST conference for a welcome reception out by the pool. We had the opportunity to catch-up with familiar faces and meet new ones. Here, we’re pictured with the Coveros/Techwell team, the masterminds behind the STAREAST conference, as well as a trusted partner of Inflectra.

We also had the chance to visit with Inflectra partner Bob Johnston from Critical Logic.

Inflectra Booth at the Expo Day 1

Rise and shine! On Wednesday April 27th, we woke up early to prepare for the first day of the expo, where people came to explore the latest solutions, technologies, and tools in testing. The expo also provided a place to network with other vendors and attendees and to learn new skills.

We laid out our Inflectra swag, including our “James Bond” pen, bluetooth earphones, customized stickers, “stress” stars, and charging pads. Not a bad array of items! We displayed live Spira and Rapise environments on our iPads, waiting to be demoed.

Finally, the expo doors opened and the attendees flooded in. It was nice to see so many people in-person who were excited to be at the conference. We were grateful to have a busy booth, where we had the opportunity to share our solutions and methodologies.

Running the Risk and a Special Prize Give-Away

That afternoon, our CEO and Founder Adam Sandman gave a presentation on applying a risk-based approach to testing. Presented to both the in-person and virtual audiences, Adam discussed the different types of risk that you should be considering and how you can use the assessment of risk to create a test plan that gives you the greatest risk coverage in the time available. Well done, Adam.

That evening, we participated in the Sponsor Prize Give-Away. We were excited to give one lucky winner a pair of 2nd generation Apple Airpods.

Inflectra Booth at the Expo Day 2

The second and final day of the expo was a bit slower than the first, albeit productive! Given a little more time, we had the chance to talk with other vendors in the ballroom as well as give more in-depth demos to attendees.

Once the expo began wrapping up, we said farewell to the other vendors around us and packed our booth. It was a quick couple of days, but wow was it nice to be back in the conference swing of things.

That’s a wrap!

Until next time, STAREAST. Now, we turn our attention toward InflectraCON 2022 this week May 5th-6th. If you’re in the area or would still like to attend, it’s not too late to purchase tickets!

Backup and Restore Plans - Don't Forget the Restore Part!

2022-04-27T06:44:42-04:00

The Basics

The two most common acronyms you will come across when discussing backup (and restore) strategies are:

The Recovery Point Objective (RPO) – how far back do you maintain backups, and at what points in time can you restore the system back to.
The Recovery Time Objective (RTO) – how long it will take you to get the system back to the specified recovery point.

This sounds pretty simple, but what people often forget to plan for is the need to be able to selectively restore data, or the need to have frequent backup intervals so that the risk of data loss is reduced. For example, if you take backups every day at 9:00am and you have a failure at 8:00am, you have effectively lost 23 hours of data (since the last backup). If you made backups every hour, the most data you could “lose” is only 59 minutes.

Data Tenancy is Key

One other major consideration when deciding of backup and restore strategies is to understand the tenancy of your systems and the data in them:

Multi-Tenant Architecture – you have one single data store that serves all your customers
Single-Tenant Architecture – you have individual separate data stores that are unique per customer

However, even within a single customer instance, you can have a system designed so that each project or workspace has its own data store, or a single instance for that customer for all projects.

The more granular your data tenancy is, the easier it will be to restore a customer’s data without negatively affecting other customers.

For example, imagine we have a fully multi-tenant architecture where all customers use the same database, and backups of the entire database are made every day. If a customer makes an unintended change or deletes some data, they make ask to restore back to the previous day’s data. If that database backup is for all customers, you may have to revert all customers back to the previous day, which is not desirable!! In that situation, you would need to architect the backups so that you can revert just one customer back from the restored data.

If you had the exact same situation, but used a more granular single-tenant architecture, you could simply restore the one customer from the daily backup without negatively impacting other customers

Lessons from the Inflectra Cloud

While there is no single, correct way to manage your backup and restore strategy, here are some recommendations based on how we’ve designed our cloud disaster and recovery plan.

Avoid permanent deletes as much as possible
Maintain customer-specific backups
Frequent snapshots
Geographical dispersion

1. Avoid permanent deletes as much as possible

The need to perform restoration from backups can happen for a variety of reasons including natural disasters or IT disruptions, however one common reason is that a user accidentally deleted something the shouldn’t.

In our Spira platform we have made most deletes “soft”, where we simply mark a requirement, defect, test case or other artifact as deleted rather than actually deleting the item. That allows administrators of the project in Spira to simply ‘undelete’ the item from within the application.

Where there are actions in Spira that result in permanent deletes or changes, we require the user to enter in the name of the project or other item to avoid someone doing it erroneously. This is similar to the approach taken by Amazon Web Services (AWS) where they force you to type in the letters “D-E-L-E-T-E” to permanently delete a resource.

These two design choices generally (but not always) reduce the number of accidental deletes, requiring backup restoration.

2. Maintain customer-specific backups

We designed our Spira cloud infrastructure to mirror in large part our on-premise deployments, this allows us to seamlessly and easily move customers to/from the cloud as their needs (or laws) change. As a result, we maintain daily backups of each SQL Server database separately in a rolling 7-day period. That means we can restore a customer from one of any of the 7 day backups and not negatively impact any other customers with the rollback.

Using the standard Microsoft SQL Server restore tools, the procedure to revert a customer back takes a few minutes vs. days. The longest time is usually the time it takes to coordinate with the customer and inform users – which are of course very important steps.

However, we realized that a daily backup means that you could lose upto 23 hours of data if the event happened just before the next daily backup. For that reason, we have a separate set of AWS volume snapshots that happen every hour.

3. Frequent snapshots

In addition to the SQL Server daily backups, we take hourly snapshots of the web server and database server Elastic Cloud Compute (EC2) instances. In the case of a single-customer database restore, this is useful because it allows us to restore back the data from any hourly snapshot. The means that the most data that will be lost is 59 minutes’ worth (if you deleted something at 3:59pm and the last backup was at 3:00pm).

In the case of a more serious hardware failure, the fact that the EC2 snapshots contain the entire working virtual machine, means that restoring functionality is much faster since you can just restore the EC2 image from the snapshot and the operating system, application stack and all data is restored back at the same time. We can restore back a single EC2 virtual machine (containing over 30 customers) in less than an hour, vs. the multiple hour process it would take using physical hardware.

4. Geographical dispersion

It is important to make sure that you consider the effects of geography and legal restrictions. At Inflectra we have customers that specific data residency requirements. Typically this means that certain customers’ data must stay in the USA, certain data needs to stay in the EU, and other data must remain “in-country”.

What we have done is have a set of legally equivalent “privacy regimes” that we replicate data between. That way we can maximize the geographic spread of our data (to avoid a natural disaster one area affecting both primary and backup regions) and avoid data flowing from privacy regime to another, violating data residency laws such as GDPR or HIPAA.

For example:

Our US customers have their primary data hosted in Northern Virginia and backed up in Ohio
Our EU customers have their primary data hosted in Dublin, Ireland and backed up in Frankfurt, Germany
Our Australian customers have their primary data hosted in Sydney, NSW and backed up to Melbourne, Victoria
Etc.

Conclusion

When looking at disaster recovery strategies, it is important to consider the frequency of backups, the retention period and also the type of backups taken. The latter should be considered in the context of your overall data storage strategy so that you can restore customers’ data back as quickly as possible, with as little data loss as possible, with as little impact to other customers or users as possible.

Recap: Agile Trends in São Paulo, Brazil

2022-04-15T11:45:52-04:00

Preparing the Joint Booth

We’re grateful for our partner OAT Solutions who asked Inflectra to share a joint booth at the conference this year. As we look to expand our footprint in the LATAM region, we were delighted to take up OAT’s offer. The Inflectra Team went straight to planning. Since the conference was in Brazil, we had to figure out the best way to ship some booth materials and of course, some swag, to São Paulo.

Luckily, some members from the OAT team were passing through DC earlier this month. The Partnerships team was able to meet with them for lunch in DC, and pass off some conference supplies!

Meeting at the Frei Caneca Convention Center

Early Monday morning, the Inflectra Team made their way to the Frei Caneca Convention Center. The Frei Caneca Convention Center is considered one of the country’s most renowned venues due to its location, infrastructure, comfort, security, and its wide breadth of services. We could immediately see why it was a top location!

Plus, they had some fun bean bag chairs to lay on when our feet needed a break.

Setting Up the Inflectra Booth

Once we navigated our way to our space at the convention center, it was time to set-up and meet our OAT Solutions partner friends. We were lucky enough to have a spot right next to the large conference hall where thousands gathered to listen to keynote speakers.

When the conference started, the people poured in! We had the opportunity to meet a lot of attendees and talk about our products. We soon discovered that Inflectra was one of the only companies who presented automation and RPA solutions, functionalities required to be Agile. With OAT Solutions, we were able to present our solutions with their services and in-depth knowledge of our tools.

Keynote Speakers and Prizes

Throughout the conference, we had the opportunity to listen to a wide variety of speakers who discussed topics like powering digital transformation with an agile model, agile practices in operational planning, opportunities for lawyers in the world of agility, and more.

We were proud to have our logo projected on the wall next to the main conference stage.

We also participated in a prize give-away for Agile Trends attendees. Two prize winners received a pair of AirPods engraved with the Inflectra name. Who doesn’t love a good prize?

Rockin' n' Rollin' Our Way Through the Conference

On top of the great venue, keynote speakers, and networking opportunities, Agile Trends brought in a local band that rocks the best pubs and bars in São Paulo. This gave us the energy we needed to continue sharing our products and methodologies with the thousands of attendees!

Until next year, Agile Trends!

Bonus: Visiting our Partner Targetware Informatica

While in Brazil, we stopped on by the headquarters of our new partner Targetware Informatica. We were able to give a quick training on Inflectra products and strategize a partnership roadmap. Thanks for meeting with us, Targetware team!

We Look Forward to Seeing You...

... at our annual conference InflectraCON on May 5-6, 2022 in Washington, DC.

Spotlight on Spira 6.16 - Workspace Navigation Enhancements

2022-04-07T14:38:08-04:00

Workspace Filtering

When you have a large number of active workspaces (products, programs and portfolios), expanding and collapsing the hierarchy can be tedious and laborious.

So, in version 6.16 we have introduced a filtering system where you can enter in the partial name of a product, program and portfolio and the system will dynamically filter down the list for you:

Recent Artifacts

In the My Page dashboard you have a special widget Recent Artifacts that shows you the most recently accessed items in the system (requirements, test cases, defects, risks, tasks, etc.). However to access this list you need to first navigate to the My Page from your current location.

To save time, version 6.16 introduces a handy section to the Spira global search dialog box to now display the most recent artifacts directly under the search box.

This means that you can now access the list of recent artifacts from any page directly without first having to navigate back to the My Page. In our testing, this has provided to be a huge time saver, allowing you to quickly go back to an item you were working on.

Spotlight on Spira 6.16 - Custom Reporting Dashboard Enhancements

2022-04-07T14:11:39-04:00

How It Currently Works (In v6.15 and Earlier)

In the current version of Spira, lets say you have two custom graphs defined:

When you want to add them to your reporting dashboard, they all appear as a single widget called Custom Reports:

Then if you add the graph twice, to see both custom graphs at the same time, they have generic names:

You can change the widgets in the dropdown menus, but the widgets will always have the generic Custom Graphs [x] name.

How It Will Work in 6.16 and Later

With the new, updated version of the custom reporting system being introduced in Spira 6.16, you define the two custom graphs in the administration module in exactly the same way:

However, when you go to add the graphs to the reporting dashboard, there is now a separate folder of custom graphs available, with each custom graph listed explicitly by name:

When you add the graphs, they will be added as separate widgets, each with their own name and description (in the tooltip).

This means that each graph will now more clearly communicate what it is meant for, and will make users treat custom graphs and standard graphs the same way.

How Will It Affect Existing Dashboards?

When you upgrade from v6.15 (or earlier) to v6.16, any existing graphs added to your dashboard will still have the old Custom Graph [x] title, but this time without the dropdown list to change the graph. You can use them as-is, or simply deactivate them and re-add the same graph to get the new title.

Spotlight on Spira 6.16 - GitHub, GitLab and CircleCI Webhook Integrations

2022-05-13T16:11:35-04:00

GitLab Pipelines

The new integration with GitLab CI pipelines will initially allow you to execute a GitLab CI pipeline automatically, typically triggered by source code commits or other events from within GitLab itself.

Whenever a GitLab pipeline executes via normal source code commit events, the new GitLab pipeline event will be recorded in Spira as a new build under the release artifact.

The build event in Spira can then be used to trigger other actions, such as auto-scheduling test sets, etc.

GitHub Actions

The new integration with GitHub Actions will initially allow you to execute a GitHub CI pipeline automatically, typically triggered by source code commits or other events from within GitHub itself.

These GitHub pipeline events will show up in Spira as a new Build under the Release artifact:

The build event in Spira can then be used to trigger other actions, such as auto-scheduling test sets, etc.

CircleCI Pipelines

The new integration with CircleCI Pipelines will initially allow you to execute a GitHub CI pipeline automatically, typically triggered by source code commits or other events from within a linked GitHub or BitBucket repository:

The pipeline builds will report back to Spira using the CircleCI webhook functionality and the dedicated Spira endpoint. The build will contain important information that will be reporting back to Spira:

The build event in Spira can then be used to trigger other actions, such as auto-scheduling test sets, etc.

What's Coming Next?

In our next major release, version 7.0, we will be adding the ability to additionally launch these three pipeline types directly from the Spira user interface. This additional functionality will be implemented using the new Spira Plugin & Extensibility Framework that we discussed in a previous blog post.

⚠️ InflectraCON 2022 Early Bird Tickets Expire on March 31, 2022 ⚠️

2025-04-01T21:12:09-04:00

But first a little bit of fun!

If it's been a long winter and even longer two years for you as well, InflectraCON will give you an opportunity to shake off those virtual meeting blues. Adam Sandman, the CEO of Inflectra, just offered you the cure!

Explore the InflectraCON 2022 Program:

As you know

Amazing Keynotes:

Discussions Testers Should No Longer Be Having by Mike Lyles of Mike Lyles Consulting
Tech, Gaming, and Metaverse by Jenn Bonine of the PinkPowered Innovations
Alphabet Soup - What Do DevOps, DevSecOps, DevTestOps, SecDevOps, etc. Really Mean??? by Jeffery Payne of Coveros
Myths About Myths About Automation by Paul Grizzaffi of Cognizant Softvision

Agile Testing Speakers:

Talks about Agile:

Scrumban – Effectively Combining Scrum and Kanban by Bob Payne
How to nudge your way through agile testing by Ard Kramer
I’m a BA Girl in Agile World by Mindy Bohannon
Agile Coaches Can Wear Many Hats. Find the Coach You Need by Steve Moubrey
Spira: Risk Management (FMEA) by Dr. Sriram Rajagopalan

DevOps Speakers:

Dive into DevOps:

Design Thinking (a 2-part workshop)
Explain DevOps To Me Like I’m Five: DevOps for Managers
Automation Framework and the Role it Plays in DevSecOps
The Dos and Don'ts of Accessibility

QA Speakers:

Quality Engineering:

Built-in Quality – How do you build quality in? by Derk-Jan De Grood
Games & Puzzles To Build And Improve Testing Skills! by Bob Crews
Testing Event-Driven Architectures by Nate Custer
Maturing The Enterprise Quality Practice by Sarala Pandey

InflectraCON User Summit Ticket Sales Close On April 10, 2022

Do you need help convincing your boss to send you to InflectraCON 2022?
Here is your Justify Your Trip letter template to get started now!

See you at inflectraCON 2022!

Webinar Recap: The Automation of Requirements

2022-04-01T12:15:00-04:00

On March 29th, Inflectra and partner Orca Intelligence hosted a webinar focused on The Automation of Requirements: Save Time Planning, Creating, and Managing Requirements with Swiftly and SpiraTeam. In this webinar, we covered:

Solicitation Response
- Work in SpiraTeam to build out a scope for solicitation and generate an estimate in Swiftly
Agile Project Planning
- Plan in detail with SpiraTeam and automatically generate details with Swiftly
Agile Delivery Lifecycle Management
- Generate detailed user stories with Swiftly and SpiraTeam
- Manage user stories through SpiraTeam.

If you missed the webinar, we have a full recap below.

Recap: Satellite 2022 in Washington, D.C.

2022-04-15T11:43:22-04:00

Convening at the Convention Center

Early Wednesday morning, the Inflectra Team made their way to the Walter E. Washington Convention Center, not so far away from Inflectra headquarters. The Walter E. Convention Center, located in the heart of downtown DC’s convention and entertainment district, unites locals and visitors from around the world to experience events from international policy conferences to black-tie fundraisers, to industry conventions like this one.

We used the time before the event to grab a coffee and develop a strategy to make the most of our time at the conference. Divide and conquer!

Inflectra at Satellite 2022

Suited in our Inflectra gear, the team was ready and prepared to take on the Exhibit Show Floor full of the latest satellite innovations, technology, and solutions. Although not everyone was prepared for the photo, the team was excited.

After receiving our conference badges and some swag, we made our way to the cavernous Exhibit Floor. But first, we had to stop and take a look at all the conference installations, like this gigantic Satellite board triple our size! We got to thinking…how cool would it be to have something like this at our InflectraCON conference?

Meeting Current Customers

Once we made our way to the Exhibit Floor, we immediately spotted a few Inflectra customers. We stopped to talk and catch-up and even provide some technical support for our SpiraPlan platform.

Learning About the Wonders of the Satellite World

While at Satellite 2022, we got to learn a whole lot more about the Satellite world and its importance in a variety of industries, like media & entertainment, military & government, investment, transportation, and commercial markets. We had the opportunity to engage with industry leaders, young professionals, and entrepreneurs in that space and discuss the evolution of satellites in this broad scope of industries. Plus, we got to check out some pretty awesome booth set-ups on display.

Additionally, we had the chance to share with others how our tools support this evolution—namely the importance of Quality Assurance for the systems responsible for building such crucial technologies. We discussed how our tool platform Spira ensures quality and offers key features, like requirements management and integrated risk management, that help companies better manage the creation of their technologies.

Wrapping Up our Time at Satellite

Once we had made our rounds through the Exhibit Floor, we finished our day off by grabbing a beer near the Convention Center, conference swag in hand. Although our feet may have been tired, we were feeling energized for the many upcoming events this spring and summer. See you next year, Satellite!

We Look Forward to Seeing You...

At our annual conference InflectraCON on May 5-6, 2022 in Washington, DC.

Reviewing the 10 Best API Testing Tools for 2022

2022-03-16T21:06:49-04:00

API testing is a type of software testing that analyzes an application program interface (API) to ensure it meets expectations in terms of functionality, reliability, performance, and security. Since APIs play a major role in our digital lives, API testing ensures that the application is running in an efficient and seamless manner for the end user.

Come for InflectraCON, Stay for History and Fun

2022-03-13T19:03:56-04:00

First comes learning

We are serious about our conference! That’s why we are offering an unbelievable value to all attendees:

Training & Certification: Get trained and caught up with all the latest features of the Spira family of products. Take a final test and walk away with a certificate. Check out our Customer Panel to learn about our Product Roadmaps!
Interactive Learning: join us for interactive 1-on-1 sessions with your favorite Inflectra experts. Bring your questions to us, and we will help you find answers in real-time. Free consulting! YAY!
Advanced Topics: Sit in on the presentations of Advanced topics, covering new integrations, pipelines, and new functionality in Inflectra’s platforms. Ask questions about the product roadmaps, features, and enhancements.
STPcon @ InflectraCON: STPcon is now an integral part of InflectraCON. Meet an excellent lineup of our keynote speakers and practitioners in software development, agile testing, DevOps, cyber, and innovation space. Or sign up to give a lightning talk!
Technology Deep Dive: Hear about the cutting-edge industry trends & emerging technologies from our great technology speakers & Partners!
Want to show off your use case or solution? Schedule a session today!
Networking: Rekindle friendships with your teammates, meet technologists and shake hands with hiring managers from the D.C. area. Need to hire talent? Exhibit with us!
Party: Let loose during the Star Wars-themed party on May 5, 2022. Everyone can join the party (the conference attendance is not required)!

Do you need help convincing your boss to send you to InflectraCON 2022? Here is your Justify Your Trip letter template to get started now!

Then comes fun in DC:

Plan to have a few free days after the conference to enjoy the city with your family! Washington, D.C. has lots to offer a curious mind!

The Washington DC area is full of historical sites, arts, science, history, and culture. Here are the Top 15 things to do in Washington DC:

Bike & Scooter Rentals: First things first! Hop on a bike and enjoy the miles of bike trails and open spaces in and around the monuments and the city.
National Mall: With the Lincoln Memorial at one end and the Nations Capital at the other, the National Mall is a fantastic place. Flanked by museums and other historically significant monuments, memorials, and buildings, it is a sight to behold. You will get your steps in for sure!
National Museum of African American History & Culture: As the most recent museum added to the National Mall, this museum is the only national museum devoted exclusively to the documentation of African American life, history, and culture. It was established by an Act of Congress in 2003, following decades of efforts to promote and highlight the contributions of African Americans. Free!
The National Archives Museum: Home to the Declaration of Independence, Constitution, and Bill of Rights.
The International Spy Museum: A private non-profit museum that documents the tradecraft, history, and contemporary role of espionage, it holds the most extensive collection of international espionage artifacts on public display.
National Zoo: All-time favorite of kids everywhere! Catch a glimpse of roaring lions and enjoy the farm animals at the petting zoo! Red pandas and snow leopards await. Also, it’s free!
Smithsonian Museum of Natural History: Another crowd-pleaser! It also works with your budget, i.e., free!
Udvar Hazy Air and Space Museum: Since the Air and Space Museum on the Mall is undergoing massive renovations, check out Udvar Hazy, a short drive out of town.
National Gallery of Art + Museum of Modern Art: Founded as a gift to the nation, it serves as a center of visual art, education, and culture. A collection of more than 150,000 paintings, sculptures, decorative arts, photographs, prints, and drawings spans the history of Western art and showcases some of the triumphs of human creativity. Free!
The Hirshhorn Museum and Sculpture Garden: An art museum beside the National Mall for all contemporary art lovers. Stroll the gardens enjoy the fountain and coffee on the terrace.
Artechouse DC: Art & technology space with rotating immersive installations, plus a futuristic cocktail bar.
Amazing Nightlife and Dining options in various D.C. neighborhoods like Georgetown, Adams Morgan, Dupont Circle, U Street, Eastern Market, and Capitol Hill.
National Harbor: The Capital Wheel is so much fun!
Arlington National Cemetery: Pay your respects to all who laid their lives in the service of this great nation when you visit the United States military cemetery in Virginia, across the Potomac River from Washington, D.C. The 639 acres of land are home to the dead of the nation’s conflicts, beginning with the Civil War.
Be in the know: Check out DC-ist to get a better sense of what is happening in D.C. this spring!

See you in Washington, DC, on May 5th and 6th!

Team Inflectra

Reviewing the 25 Best DevOps Tools for Agile Projects in 2022

2022-03-13T13:13:38-04:00

Ever since the Belgian consultant project manager and an agile practitioner, Patrick Debois, coined the term “DevOps” to resolve the conflict, “It is not my code; it’s your machines,” increasing the transparency of the integration and interaction between business and technical people, the DevOps framework has played a pivotal role in the end-to-end responsibility. Numerous tools have entered this 8-step framework bringing their unique expertise in specific areas, while others have played within the ecosystem touching more than one segment of this framework as part of the more extensive application lifecycle management.

Webinar Recap: Rapise 7.2: New Functionality: Global Objects

2022-03-04T20:00:30-05:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Rapise 7.2: New Functionality: Global Objects from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy!

See you at our future webinars!

#teamInflectra

InflectraCON 2022: What’s In It for Partners?

2025-04-01T22:19:00-04:00

If you’re an existing or prospective partner, you might think that such a conference is great for users, but what’s in it for partners? Well, you’ve come to the right place.

We’ve been working hard to ensure that all attendees benefit from InflectraCON. In addition to the activities available to all who attend the conference, we have created a partner track focused on providing intensive training, open discussions, and networking opportunities for our partners.

Here are the highlights:

2-hour Partner Summit
2-hour Sales Bootcamp
Exclusive Partner Networking Events
Partner Minute / On-stage Show-and-Tell
Product Roundtable and Roadmaps Discussion
1-on-1 Strategic Meeting with Inflectra Leadership
Spira & Rapise Training and Certification.

Here’s a pamphlet that goes into detail about all the partner perks.

To get even more out of InflectraCON, become a sponsor! With a sponsorship, your organization can:

Gain visibility
Strengthen your brand
Showcase your products & services
Gain access to your target market
Network in an in-person environment
Recruit new talent
Build new business relationships
Save money.

And if you need even more reasons to become a sponsor, we’ve got you covered: here are more sponsorship benefits.

*IMPORTANT:* We are giving a 50% discount to all partners on sponsorship packages.

So, have we convinced you to attend InflectraCON 2022 yet?

Buy Tickets Now!

Not a partner, but want to explore Inflectra's partner and software ecosystems? Join us for InflectraCON 2022 to check us out!

Plugins Aplenty Coming to SpiraTest, SpiraTeam and SpiraPlan

2022-02-22T12:31:57-05:00

Why Are We Adding Support for Plugins?

One of the key tenets and philosophies in our development of Spira is that it should have all the functionality you need to plan, manage and test software engineering projects. As part of our Harmony ideal, we have designed Spira to enable stakeholders in different disciplines to work together to do their job without needing third-party plugins or extensions. For example, business analysts, developers, project managers, software testers and quality assurance professionals can all work in Spira seamlessly. This is in stark contrast to some other platforms where every single feature requires a different plugin or extension. So therefore you may be asking, why have plugins at all? This is a good question as Spira already provides numerous way to configure the system:

Customizable project templates
Customizable types, statuses, priorities and workflows
Custom fields / properties
Customizable reports and graphs

However we found that there were some use cases that were limited by the lack of a plugin framework within Spira:

Integrations with other tools that work best with an in-application user experience (vs. data synchronization or API integration)
Niche features that users will want to be able to enable or disable for specific projects
Customized process workflows and support for business processes that are more sophisticated than can be handled with the current workflows system

So therefore in Spira 7.0, one of the biggest new features is the Spira Extensibility Framework / Plugin Architecture that will make all these things possible!

Managing Plugins

Inside Spira you will be able to see the list of plugins available in your instance:

You can activate any of the available plugins for use in your Spira instance. Once you do that, you will then be able to enable any of the activated plugins for use on selected products:

When you choose a specific product, you will be able to see which ones are enabled for that product:

This allows you to have different plugins in use on different products in the same Spira instance.

Plugin Settings

Depending on the specific plugin, there will be settings available that you will need to configure to enable the plugin to operate successfully. For example, when integrating with GitLab you will need to enter credentials:

and at the product-level you will have settings, such as specifying the GitLab project that the Spira product corresponds to:

Once you have filled in the appropriate settings, the plugin is ready for use.

What Will Plugins Be Able to Do?

Each of the different plugins will be able to take advantage of the different extensibility features available in Spira. In general, plugins will be able to run code on the Spira pages, call external APIs, call Spira API endpoints, listen for key events such as an artifact page load or save event and add UI elements to the Spira user interface. Here are some key examples you can expect:

Menu Entries in Toolbars

The plugins will be able to add menu entries into the various toolbars in the pages in Spira. These toolbar menu entries can have icons and text entries:

When users click on these menu entries it can either open up an external URL or call plugin-specific code on the Spira page. In the example above, clicking on the Run Pipeline button will call an internal Spira API to get the release information and then use that to call the GitLab REST API to start a new pipeline event.

Plugin Dashboard Widgets

Plugins will be able to publish their own custom widgets for use on the various dashboards (My Page, Product Home, Program Home, Portfolio Home, Enterprise Home, Reports Center). In this example, the FMEA risk management plugin is displaying a new grid in the Product Home dashboard that shows the FMEA risk priority number:

These UI widgets will be able to query Spira data using the standard Spira REST API (with an internal library that simplifies the authentication and connection). Rendering of the data into different forms will be done using the following standard JavaScript libraries that Spira already uses:

MustacheJS for rendering tables, grids, treeviews, lists, and other HTML elements
C3 / D3 for rendering graphs and other graphical elements

Custom Grid Columns

In addition to menus and dashboard widgets, the plugin framework will let plugins display their own columns in the various list pages and grids. For example, the WorX plugin displays a set of custom buttons in the test case list grid that will launch the WorX manual testing accelerator plugin for those specific test cases:

Plugins will be able to display a variety of data and other elements in the columns, for example calculated fields, hyperlinks and/or buttons for accessing other systems.

Scripted Event Actions

In addition to the display of UI elements in the various pages, another key aspect is the ability to have customized business processes enabled by a plugin. In this case the plugin will be called whenever an artifact is loaded and saved so that it can perform specific business actions. For example, in the FMEA plugin, whenever you change the probability, detectability or impact of a risk, the Risk Priority Number (RPN) field is auto-calculated:

This kind of event-driven plugin will be useful for many other use cases, including:

Changing which dropdowns are visible based on other dropdown values
Calculating values based on other values (e.g. financials)
Changing the value of a dropdown based on other values. For example, auto-assigning a defect based on the selected Component

What Kind of Plugins are You Planning?

We believe that it will be important to release the first version of the Spira plugin framework with a meaningful set of useful plugins so we have prioritized the following plugins for the initial release of 7.0:

CI / CD plugins for GitLab, GitHub and CircleCI
Risk management plugin that enables FMEA support
Migrated existing support for WorX to a plugin
Integration with other SaaS automation tools
Accelerators for common artifact tasks and workflows

Who Can Write Plugins?

Initially, to ensure a high quality user experience, the plugins will be written by Inflectra to provide integrations or niche functionality that does not make sense to build in the core application. However once the plugin framework is released and any improvements and feedback are incorporated, we anticipate opening up the development of plugins to our technology and solution partners. We will use this to ensure we have robust documentation for third party plugin development and a secure code review and approval process in place. Once that is in place, the final step will be to open up the plugin architecture to customers so that they can create custom plugins that are unique to their own needs.

How Are Plugins Coded?

In order to get ready for writing your own plugins, you will need to have some basic JavaScript and TypeScript coding experience. All of the plugins will use HTML and JavaScript as their coding language:

The core plugin manager in Spira is being implemented in TypeScript and you will need to be knowledgeable in JavaScript, JSON and REST APIs to take full advance of what our plugin framework offers.

Spotlight on SpiraPlan 7.0: FMEA Risk Management Comes To Town

2022-01-26T10:05:04-05:00

What is FMEA Risk Management?

In traditional risk management processes (e.g. PRINCE2), you have two key measures of risk:

Probability - how likely the risk is to happen) on a numeric scale (e.g. 1-5)
Impact - how severe the risk will be if that happens on a numeric scale (e.g. 1-5)

You then calculate the exposure of the risk using this simple formula:

Risk Exposure = Impact X Probability

When looking at safety risks in manufacturing and hardware systems, the traditional risk management framework is extended to handle the additional concept of detectability, since if a risk is harder to detect, it makes it more important to manage.

When using an FMEA approach/methodology, there are actually three key measures:

Probability - how likely the risk is to happen) on a numeric scale (e.g. 1-5)
Impact - how severe the risk will be if that happens on a numeric scale (e.g. 1-5)
Detectability - how easy it is to observe the risk on a numeric scale)

You then calculate the Risk Priority Number (RPN) using this simple formula:

Risk Priority Number (RPN) = Impact X Probability X Detectability

FMEA Risk Management Plugin

In Spira 7.0, you will be able to go to the list of plugins and active for specific products, the new FMEA plugin. This will enable the additional FMEA risk management features in the specific product:

When you enable this feature, the Risk details page in SpiraPlan will show two additional fields - detectability (a dropdown the user can select) and RPN, a calculated integer field. When you change the values of probability, impact, or detectability, the FMEA plugin will automatically calculate the new value of RPN and display it:

In addition, for audit purposes, when you change and save the values, the history tab of the Risk will show the history of the changes in probability, impact, and detectability as well as the change in RPN number:

Finally, the new Spira plugin architecture allows plugins to display custom widgets in the Product dashboards for the first time. If you go to the Product dashboard, you will be able to add a plugin widget to the dashboard, which will show the top product risks, ranked in order of descending RPN value. This is similar to the built-in Risk widget, except that it uses the RPN value (instead of Exposure) and uses a different customizable color-coding.

With this new plugin, we now have built-in support for both traditional (e.g. PRINCE2) risk management and FMEA risk management, all in the same system.

InflectraCON 2022: The Curious Case of Vanishing Tickets

2022-01-25T19:26:33-05:00

Please welcome our newly-minted Early Bird Tickets!

Please treat them with love and care. They are still very young.

Need help navigating the InflectraCON 2022 tickets?

We are here to help.

Are you interested in learning where the Agile Software Testing and DevOps space is headed to?

We recommend you get the STPcon @ InflectraCON Conference Only Pass

Are you only interested in networking and partying at the Star-Wars-themed party?

We recommend you get our Party Pass that comes with 2 drinks tickets and tacos 🌮

Are you an Inflectra customer looking to expand your use of our platforms?

You will love our Full Access Pass that covers 2-day training, all conference talks, a networking party and so much more!

Are you an Inflectra partner looking to understand better the value of your partnership with inflectra and train your sales and technical teams?

Do we have an offer for you! Check out this Partner Pass.

Long live Early Bird Tickets and see you at InflectraCON 2022!

Team Inflectra

How To Convince Your Boss To Send You To InflectraCON 2022 | A Cheat Sheet

2022-01-25T16:59:53-05:00

Email Template

Hello [NAME],

Re: Why I must attend InflectraCon 2022

I’m writing to ask for approval to attend Inflectra’s User Conference of the year, InflectraCON 2022, on May 5-6, 2022, in Washington, DC.

InflectraCon 2022 is two full days of:

live, hands-on user training, including:
- 12 hours of deep dives into product features and administration
- 3 hours of learning about advanced topics and new functionality in Inflectra’s platforms
3 interactive 1-on-1 sessions with the Inflectra Team
A roundtable discussion about the Inflectra product roadmap
Spira, and Rapise Fundamentals' Certifications
a multi-track Agile Testing & DevOps Conference with over 20 industry leaders presenting
3 expert panels on the emerging trends, risks, and opportunities in tech, life sciences, and BFSI sectors
networking with and learning from other users of the Inflectra platforms and techies like you
leveraging the Inflectra's Partners offerings, covering adjacent technologies, managed services, and consulting
a fun and fabulous Star Wars-themed party to rekindle friendships with your teammates, make new friends, and meet your peers from the DC tech scene.

In addition to diving into content-rich sessions led by Team Inflectra experts, I will get to connect with this industry’s top professionals. At a total cost of about $X, it's the most cost-effective way to ensure that we’re getting the most from our Inflectra platform investment and should result in an immediate ROI.

In particular, I’d like to focus on finding solutions or best practices that could benefit these projects and initiatives:

• [add project or initiative]

Onsite I will join fellow Spira and Rapise users, Inflectra technology partners, and industry speakers in 20+ training sessions, 4 keynote talks, 4 Industry panels, and 20+ thought leadership sessions and interact with Team Inflectra in the 1-on-1 couch sessions. The opportunity to meet face-to-face with Inflectra and build our relationship is invaluable, and something that I can leverage across projects I am running next year.

Here’s an approximate breakdown of conference costs:

Airfare/transportation:	$ X
Transportation: (round trip taxi from the airport to hotel)	Roughly $30-$40
Hotel: Kellogg Conference Hotel, Gallaudet University, Washington, DC 3 nights	$189/night + $12 fee + 14.5% tax
Early Bird Registration Fee (expires on Jan 31, 2022)	$399,99 + tax

Total:	$ X

Additionally, InflectraCON offers a robust cancellation policy, with money-back guarantees. The details are listed on the event website. This minimizes the business risk to our company.

I’ll submit a post-conference report that will include an executive summary, major takeaways, tips, and a set of recommendations to maximize our current investments in Inflectra’s platforms (Spira & Rapise). I can also share relevant information with key personnel throughout the company.

Thank you for considering this request. I look forward to your reply. Please let me know if I have to sign -off to attend—the earlier I get tickets the more cost-friendly they will be!

Regards,

Give this approach a try. It will do no harm, but it may further convince your boss that you are committed to excellence in your work.

I hope to see you at InflectraCON 2022!

Do let me know if this email helped - and if you end up attending the conference, seek me out and let's chat!

Thea

Recap: Using Big Data Analysis to Reduce Test Flakiness

2022-01-21T17:35:32-05:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Also, we are happy to share these slides from the webinar presentation.

Webinar Presentation:

Using Big Data Analysis to Reduce Test Flakiness from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

Webinar Recap: SpiraPlan v6 - The Latest and Greatest Features and Enhancements

2022-01-18T17:22:26-05:00

On January 13, Inflectra hosted a webinar called Spira - The Latest and Greatest Features and Enhancements. Adam Sandman, Founder, and Director of Technology covered the following new features and enhancements:

Support for two new (SSO) providers: OneLogin service and a generic OpenID provider
New Upgraded Rich Text Editor
Ability to edit releases and tasks in both the Gantt and Pert chart views
New custom property types: Password (fully encrypted) Release, Automation Host, and Date and Time
Industry-specific Sample Data for new installs and trials
Built-in diagram tools get additional shapes and options, including Swimlanes
Editable Parent requirement types versus previous Epic type and simplified SAFe support for requirement types

If you missed the webinar, we have a full recap below.

Best Practices for Handling Acceptance Criteria

2024-04-24T17:39:06-04:00

Overview

First, imagine you have the following user story that you want to write acceptance criteria for:

As a writer, I want to receive notifications when others add comments so that I am up-to-date.

In Spira you will represent this as a requirement of type user story:

Now you want to add the acceptance criteria to the user story. Here's some different ways you can write the user story:

Given I don't have app open when my phone is locked then I should receive a banner notification.
Given I have the app open when I am writing on the doc then the bell icon should update to show unread notifications with count.
Given a user was mentioned in a comment using @ mention when the mentioned user is reading the comments then a flash message should show up on the same comment thread with a message notifying about the new comment.

1. Custom Rich Text Property

The simplest option is to just add a custom Rich Text property to the User Story requirement artifact:

That will appear underneath the main description:

2. Requirement Type with Steps

Another option would be to use a separate requirement to store the acceptance criteria. You can use a requirement of type Acceptance Criteria and make it a 'Has Steps' type so that you could enter the acceptance checklist as steps.

Then you can enter in the Acceptance Criteria into this requirement as steps:

You can then link to the user story using the Associations feature:

You can also see the relationship in the mind-map view:

3. Gherkin BDD Feature File

Another option is to create a .Feature file in the Documents section and link to the requirement as an Attachment:

That way you get the automated Gherkin BDD syntax highlighting:

You can now link this to the requirement as an attachment:

3. Test Case Type with Steps

Finally, you can use a test case of type Acceptance Criteria and use the test steps to reflect the acceptance criteria:

Then the Test Coverage tab is used to link this test case to the original user story:

Webinar Recap: Parallel Execution of Tests with Rapise and SpiraTest

2021-12-17T18:47:12-05:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Parallel Execution of Tests with Rapise and SpiraTest from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and have a wonderful holiday season!

Let's meet again in the New Year 2022!

#teamInflectra

Webinar Recap: Using SpiraPlan and Tosca to Test Complex Business Applications

2021-12-17T13:03:37-05:00

Webinar Recording:

Webinar Presentation:

Using SpiraPlan and TOSCA to Test Complex Business Applications from Inflectra

If you have any questions, please feel free to reach out.

See you at our next webinar, and in the meantime, stay healthy!

#teaminflectra

Speak Peek on 2022: Teams Come to SpiraTeam and SpiraPlan

2021-12-08T13:00:05-05:00

Overview of Planned Teams Functionality

We are planning on adding a new system-wide way to group users, separate from the current roles and product membership that is already available in the system. This new functionality will be called Teams, and will be managed at the system/global level:

This new way of grouping users will allow you define different types of team, e.g. Developers, Business Analysts, Project Managers, Quality Assurance. That way users will be assigned to a product both with a role (from a security perspective) and also optionally a team:

The exact ways in which you will be able to use teams is still being discussed, but the kinds of uses could include:

Grouping users on the various agile planning boards to make it easier to assign and view work on the boards
Ability to assign artifacts to a group as well as individuals
For SpiraPlan customers, the ability to see all of the work assigned to different roles across the entire enterprise.

Sneak Peek on 2022: GitLab Pipelines comes to Spira

2021-12-08T10:42:44-05:00

Overview of GitLab Integration

SpiraTeam and SpiraPlan provide multiple levels of integration with GitLab, including the following three use cases:

Integrating GitLab CI Pipelines with Releases and Builds in Spira to trigger automation events [planned for early 2022]
Integrating GitLab source code repositories so that you can view changes and have traceability to requirements, tasks, and incidents [available now]
Integrating GitLab issues to that defects raised in Spira will be automatically synchronized with issues in GitLab [available now]

GitLab Pipelines Integration

The new integration with GitLab CI pipelines will allow you to execute a GitLab CI pipeline directly from the Spira user interface. In addition, the GitLab pipelines may be automatically triggered by source code commits or other events from within GitLab itself.

Whenever a GitLab pipeline executes (either from Spira or via normal source code commit events), the new GitLab pipeline event will be recorded in Spira as a new build:

These GitLab pipeline events will show up in Spira as a new Build under the Release artifact:

When you click on the Build in Spira you can see the build details (including the console log) as well as the associated source code commits, incidents and other associated artifacts.

This functionality is similar to what is already available for tools like Jenkins and TeamCity as well as Azure DevOps Pipelines.

GitLab Source Code Integration

Spira includes powerful integration with Git code repositories, including the code repositories hosted in GitLab. From within Spira, you can view the list of folders and files in a branch as well as view the commits in specific branches.

This is the same code repository that is available also inside GitLab:

Spira includes the ability to quickly and easily drill down onto a specific commit and see the files that have changed, with inline code difference viewing. The Associations tab lets you have traceability from every code change made in the application to the relevant requirement, incident, or task that necessitated the change.

GitLab Issue Integration

The third aspect of the GitLab integration is the ability to synchronize the Spira incident tracker with the issue tracking module of GitLab projects:

You can log new incidents, bugs, and defects in Spira, either during testing or just ad-hoc, and have them synchronize seamlessly over to GitLab (and vice-versa):

Within GitLab you can see the incidents and make changes, including assigning developers, adding comments, and making changes to the issue priority, status or description. Those changes are then automatically reflected back in Spira.

Recap: Generating Tests and Scripts for SpiraTest and Rapise using IQM Studio

2021-12-09T10:37:53-05:00

On December 7th, Inflectra and our partner Critical Logic hosted a webinar focused on generating tests and scripts for SpiraTest and Rapise using Critical Logic's IQM Studio.

In this webinar, co-hosts Adam and Evan discussed:

The IQM Studio modeling tool and how it integrates with SpiraTest and Rapise
How IQM Studio can pull Spira requirements, generate automation scripts, and push tests with requirement coverage back into Spira
The benefits and value of an IQM Studio integration

If you missed the webinar, we have a full recap below.

SpiraPlan Azure DevOps Pipelines Support ADO Releases

2021-12-07T21:44:10-05:00

Azure DevOps Pipelines

Inside Microsoft ADO you can see the list of development build pipelines by going to the main Pipelines menu and viewing the list of configured Pipelines. Each of these can be easily integrated with SpiraTeam or SpiraPlan as described in our Azure DevOpe Pipelines Integration Guide.

Basically, you install the SpiraPlan ADO marketplace add-on and then simply add the special Spira task to your pipeline YAML file to configure which Spira product and release the build will be reported against:

Note that the configuration maps the following variables to the build:

Build Number: $(Build.BuildNumber)
Build ID: $(Build.BuildId)

Now, the question from our prospect was whether this integration was also available with Microsoft Azure DevOps release pipelines. Unlike the ones above, these are not for building the code and integrating ready for testing, these are the deployment actions used to deploy the final system into staging or production.

Azure DevOps Release Pipelines

The steps to configure the ADO release pipelines to integrate with Spira is similar to the approach for build pipelines. You can simply click on the Edit button for the release pipeline in ADO:

Then make sure to add the Export data to Spira task from the ADO marketplace add-on. You will need to specify the ID of the SpiraPlan product and release and also adjust the variables being used to send the data to Spira. You will want to change the Build Name and Build ID to use:

Build Name: $(Release.ReleaseName)
Build ID: $(Release.RelaseId)

Once that is done, you can execute the release pipeline as normal. The results of both the build pipeline and the release deployment pipeline will now be recorded in SpiraPlan:

So now you can use SpiraPlan to monitor and track both continuous integration pipeline events and continuous deployment release events.

Webinar Recap: Playing UFT/QTP Scripts Rapise

2021-12-01T18:36:22-05:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Playing UFT/QTP Scripts Rapise from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy!

#teamInflectra

Sneak Peek on 2022: GitHub Actions comes to Spira

2021-12-08T13:36:11-05:00

Microsoft Depreciation of Azure DevOps (ADO)

Our Spira platform has had long-standing support for integrating with Microsoft Team Foundation Server (TFS), Team Services, Visual Studio Online (VSO), and its latest rebrand - Microsoft Azure DevOps (ADO). Our customers can integrate the source code, work item tracking, and Azure DevOps Pipelines features of ADO with SpiraTest, SpiraTeam, and SpiraPlan.

However as is widely known in the industry, Microsoft is advising customers to not migrate to Azure DevOps as it will be a legacy Microsoft platform going forward. Instead, they are recommending that customers plan on adopting their GitHub Enterprise platform instead.

As outlined in the TechTarget article, industry analysts have been recommending its clients plan on migrating from Azure DevOps to GitHub

"the fact that they have a couple plays here in GitHub also shows the continued migration from Azure DevOps to GitHub as their team collaborative DevOps platform,"

Therefore, to ensure that Inflectra customers are ahead of the planned migration effort, we are adding increased integration with GitHub that we are very excited about sharing.

Overview of GitHub Integration

SpiraTeam and SpiraPlan provide multiple levels of integration with GitHub, including the following three use cases:

Integrating GitHub Actions with Releases and Builds in Spira to trigger automation events [planned for early 2022]
Integrating GitHub source code repositories so that you can view changes and have traceability to requirements, tasks, and incidents [available now]
Integrating GitHub issues to that defects raised in Spira will be automatically synchronized with issues in GitHub [available now]

GitHub Actions Integration

The new integration with GitHub actions will allow you to execute a GitHub pipeline directly from the Spira user interface. In addition, the GitHub pipelines may be automatically triggered by source code commits or other events from within GitHub itself.

Whenever a GitHub pipeline executes (either from Spira or via normal source code commit events), the new GitHub pipeline event will be recorded in Spira as a new build:

These GitHub pipeline events will show up in Spira as a new Build under the Release artifact:

When you click on the Build in Spira you can see the build details (including the console log) as well as the associated source code commits, incidents and other associated artifacts.

This functionality is similar to what is already available for tools like Jenkins and TeamCity as well as Azure DevOps Pipelines.

GitHub Source Code Integration

Spira includes powerful integration with Git code repositories, including the code repositories hosted in GitHub. From within Spira, you can view the list of folders and files in a branch as well as view the commits in specific branches.

GitHub Issue Integration

The third aspect of the GitHub integration is the ability to synchronize the Spira incident tracker with the issue tracking module of GitHub projects:

You can log new incidents, bugs, and defects in Spira, either during testing or just ad-hoc, and have them synchronize seamlessly over to GitHub (and vice-versa):

Within GitHub you can see the incidents and make changes, including assigning developers, adding comments, and making changes to the issue priority, status or description. Those changes are then automatically reflected back in Spira.

What Does This Mean for You?

As you begin your planned migration journey from Azure DevOps (ADO) to GitHub Enterprise (or other tools such as GitLab) for continuous integration and continuous deployment, you can use your same SpiraTeam and SpiraPlan instances with the integration to ADO today and then switch over to the new integrations with GitHub as your projects make the switch.

In addition, we have recently enhanced the Microsoft Azure DevOps (ADO) migration tool that lets you migrate requirements, test plans, and defect work items into SpiraTeam or SpiraPlan from ADO.

Spotlight on Spira 6.14 - Single Sign On with OneLogin & OpenID Connect

2021-11-26T11:01:26-05:00

Spira OAuth Support

When we first released the OAuth single signon functionality in Spira 6.4 we provided support for the following providers based on feedback from our customers:

Microsoft Active Directory Federated Services (ADFS)
Microsoft Azure Active Directory (AzureAD)
Google
GitHub
GitLab
OKTA

Based on requests from our customers since v6.4's release, we have added support for OneLogin as well as a generic option for other OpenID Connect compliant providers.

Spira SSO Support for OneLogin

When you enable the new provider for OneLogin, you will see that option available on the login page:

When a user clicks on the button, they will be redirected to the OneLogin login page as configured for your company:

From here they can use the normal OAuth flow and either link their OneLogin account to an existing Spira account, or simply create a new unapproved Spira account "on the fly", and a system administrator can then approve that account.

Inside Spira, you simply use the standard OAuth parameters to configure the provider:

Client ID
Client Secret
Authorization URL
Token URL
Profile URL

Inside OneLogin, you will configure a new "OpenID Connect (OIDC)" application and use that to generate the parameters, secrets and URLs needed by Spira:

Spira Support for OpenID Connect

In addition, we have now added a generic "OpenID Connect" provider option for anyone who needs to use Spira with an OAuth 2.0 / OpenID Connect based single-sign-on solution that is not otherwise listed.

This provider only uses the minimal number of required "OAuth 2.0" claims and therefore should work with any OAuth 2.0 based solution that doesn't deviate from the OpenID Connect standard.

Recap: Agile Testing Days 2021 in Potsdam, Germany

2021-11-22T03:47:59-05:00

Inflectra at Agile Testing Days 2021

Last year, all of the agile and software testing events were cancelled, so we were excited this year to be a sponsor of Agile Testing Days in Potsdam, Germany, and due to the careful 2G safety precautions of the organizers - Trendig - we were able to attend the event in-person this year!

Traveling Safely to Germany

The US Inflectra team consisting of Thea and Adam from our headquarters in Washington, DC flew to Berlin to spend a couple of days adjusting to the timezone and enjoying the sounds and sights of the legendary city. In addition, our European team member Farid made his way from his home office in Marseille, France to Berlin to meet up with the US team.

Setting Up The Inflectra Booth

After a fun (and maybe relaxing?) couple of days in Berlin, the combined US-EU Inflectra team made their way to Potsdam to setup the Inflectra booth, ready to welcome attendees and speakers.

With our Spira requirements and quality management platform running on our iPads and a selection of our legendary SWAG, #TeamInflectra was all systems go!

Meeting Agile Practitioners and Testers

After 18 months of virtual events, it was wonderful to speak with current and future customers face to face, learn about their challenges and discuss how Inflectra's SpiraPlan and Rapise solutions can assist them with their mission critical testing and product development needs.

Making friends at Agile Testing Days, including getting to meet our neighbors at Brightest, we're planning on partnering with them to align the Spira Academy with their certification program. Win Win!

One of the key unique features in our Spira platform is the integrated risk management and risk-based testing functionality. In this photo, Adam is explaining how our enterprise program management platform - SpiraPlan - can help them better manage their projects, reduce risk and create better test plans.

It wasn't all work of course, we had fun meeting the speakers such as Ard Kramer and hearing their perspectives. In this picture you can see Farid from Inflectra sharing a joke about using Excel for test management with Ard.

We also had a chance to leave the booth and listed to inspiring speakers like Vera from The Quality Minds:

The (In)Famous Costume & Dance Party

If you remember previous Agile Testing Days events, then you will know about the famous (or infamous) costume party which is a fixture at Agile Testing Days events. The theme was 1950s Rock & Roll, but the Inflectra Team missed the year part and decided to focus on the Rock aspect, with costumes from 80s metal-heads Guns & Roses and Def Leppard. Here you can see our very own Thea doing a great impression of Axl Rose. Of course, Pepe from Trendig rocked it as Elvis.

After 3 days of fun and comradeship, it was time to bid farewell to Agile Testing Days and Unicornland....

Farid was not ready to leave, but reluctantly we made our way back to Washington, DC and Marseille.... until next year!

Spotlight on Spira 6.14 - Inline Editing on Gantt Charts

2021-11-21T22:58:22-05:00

Inline Editing on the Task Gantt Chart

The Task Gantt chart in the new version of Spira allows you to click on any of the tasks in either the left-hand side hierarchical tree of releases and tasks or on the green task bars displayed in the actual timeline view and display a popup dialog containing the various task fields as well as the option to add a new comment to the task.

Similarly, if you click on any of the blue release bars on the schedule-timeline or the release items in the left-hand hierarchical tree, the system will display a corresponding edit release dialog box that will let you edit any of the release fields or add a comment to the selected release.

You can also select any of the releases (or phases/sprints) in the left-hand side hierarchical tree (so that their background is highlighted in light green) and then choose the option to add a New Task, this will bring up the New Task dialog box that will let you add a new task under the selected release, phase or sprint:

Note that you cannot add a new release of this page, that can only be done on the updated Release Gantt Chart that we will be discussing next...

Inline Editing on the Release Gantt Chart

The new version of Spira has made several changes to the Release Gantt Chart, including the ability to choose the display release on the page (previously it was read-only), and the ability to add and edit releases directly on this page:

If you click on any of the blue release (or sprint/phase) bars on the schedule timeline or the release items in the left-hand hierarchical tree, the system will display a corresponding edit release dialog box that will let you edit any of the release fields or add a comment to the selected release.

To add a new release, phase, or sprint, simply click on the dropdown menu Add Release and choose which type of release you would like to add:

Release (major or minor)
Sprint (formerly known as an Iteration)
Phase

Once you have made the selection, the appropriate release dialog box is displayed:

The dialog box will let you enter any of the release fields as well as add a new comment (if allowed by the workflow).

Inline Editing on the Release Pert Chart

Finally, for completeness, the new version allows adds the same inline release editing capabilities to the release mind map (also known as Pert chart) view of releases:

When you click on the name hyperlink on any of the release, phase, or sprint items, the same edit release dialog box is displayed, with the ability to edit the various fields as well as add a new comment:

With these features now available, all of the Gantt chart views and mind-map views support inline editing. Our future plans for the views will be to add additional interactivity, such as adding dependencies and associations and dragging the Gantt bars to change the dates dynamically in the schedule view.

Recap: Testing OracleForms Applications with Rapise

2021-11-17T08:14:21-05:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Testing OracleForms Applications with Rapise from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy!

#teamInflectra

Spotlight on Spira 6.13 - New Rich Text Editor & Swimlanes in Diagrams

2021-11-03T20:57:42-04:00

New Rich Text Editor

Since version 5.0 of Spira, we have been using the powerful CKEDITOR text editor for all of the rich text editing options within Spira. However we have been using version 4.0 of CKEDITOR for most of the pages in Spira. Eagle-eyed users may have noticed that we were using a newer version in the Requirements Document view. We were beta-testing newer versions of CKEDITOR on that page, and now we can proudly announce that from version 6.13 (and onwards) we will be using the newer version of CKEDITOR throughout the Spira platform:

The new editor provides additional features and enhancements over the old editor, including:

Additional formatting options such as strike-through (as well as bold, underline and italics)
To-do checklists (as well as numbered and unordered lists)
Highlighted text (as well as foreground and background color)
Ability to embed YouTube videos (as well as images)

Finally, the editor also fixes some known annoyances with the old editor:

Hyperlinks included in the rich text descriptions are now clickable
The right-click spellchecker now works without having to CTRL right-click

Diagram Tool Enhancements

In Spira version 6.11 we introduced the new built-in diagram editor that let customers create their own flowcharts, mind-maps, organization charts and other diagrams directly inside Spira.

As part of the upcoming 6.13 release, we have enhanced this diagram editor to include two new features:

Group individual shapes together
Swim lane / Kanban diagrams

Grouping Shapes in Diagrams

The new Group option lets you create expandable / collapsible groups that contain diagram / flowchart shapes:

Swim Lane / Kanban Diagrams

The new swim lane diagram option lets you create horizontal, vertical or mixed row/column boards. For example, a typical horizontal swim lane diagram might look like:

You can create similar diagrams with vertical swim lanes for use in Kanban diagrams, and for ultimate flexibility you can also create a combined row/column diagram layout:

These new diagram layout / grouping options add more power to the content editing features in Spira.

Spotlight on Spira 6.13 - SAFe Support for Requirement Types

2021-11-04T14:10:18-04:00

Requirements Hierarchies in Scaled Agile (SAFe)

When you are implementing Essential SAFe in a project / team environment, you will usually want to structure your requirement items in the following hierarchy:

Where the Feature and User Story requirement items are considered team artifacts and the Epic requirement items are release train (aka Spira Product) artifacts.

Requirements Hierarchies in Waterfall

Conversely when you are working on traditional waterfall (or other non-agile methods such as V-Model), you will usually want a more structured hierarchy based on the type of requirements:

For example, you might have:

Business Requirements
- Module 1
  - Requirement 1.1
  - Requirement 1.2
- Module 2
  - Requirement 2.1
  - Requirement 2.2
- Module 3
System Requirements
- Module 1
  - Requirement 1.1
  - Requirement 1.2
- Module 2
  - Requirement 2.1
  - Requirement 2.2
- Module 3
Use Cases
- Use Case UC1
- Use Case UC2
System Qualities
- Scalability
  - Scalability Requirement 1
  - Scalability Requirement 2
- Usability
  - Usability Requirement 1
  - Usability Requirement 2

Requirements Hierarchies in Agile/Scrum/Kanban

Finally, for classic Agile projects (e.g. Scrum, Extreme Programming, or Kanban) that don't use Scaled Agile concepts, you might have a simple two-level hierarchy of Epic and User Story requirements, with the stories having Tasks underneath the user stories:

Changes to Requirements Type in 6.13

So to make it easier for customers to use Spira for these different types of project, we have made a major change in Spira 6.13.

In previous versions, when you had a requirement that contained children, it would automatically have its type set to either Package (v5.x) or Epic (v6.x). This was regardless of its original type before it became a parent.

Now with version 6.13, we have changed the way requirements work to allow you to make a requirement a "summary" type (with children) and keep its original type. This lets you have a more flexible hierarchy of requirements with different types. In addition, it will make synchronization of requirements with tools such as Atlassian Jira and Microsoft Azure DevOps (ADO) easier because you can now map the specific types.

To simplify the process for new product templates, when you create a new product template in Spira, it will come with an additional requirement type called Epic:

Spotlight on Spira 6.13 - Additional Custom Property Types

2021-11-03T10:17:33-04:00

The Password Custom Property

We have added a new custom property type of Password:

This new custom property type allows users to store important test data such as logins, passwords, and other Personally Identifiable Information (PII) in Spira without it being visible on the screen to the user, and more importantly, the data is encrypted inside the Spira database (in addition to the entire database itself being encrypted at rest).

When you add a password custom property and enter it in text, the data is displayed only when you click on it:

and is blurred out as soon as you click away.

One common use of this custom property is when using Spira with Rapise to manage an external (non-TaraVault) Git test framework repository, where the Git login and password are managed by Spira. For example, when using Spira and Rapise with repositories hosted in such platforms as GitLab, GitHub, or BitBucket.

The Release Custom Property

A common request from customers is the ability to associate artifacts with additional releases. For example, requirements are typically associated with the release that the feature is planned to be introduced in, but it may be useful to know what release the feature was phased-out in as well? Or a defect may need more release fields than just detected, planned, and verified. You can now add additional Release fields as custom properties:

Once you have added the new Release custom property, it will appear in the "Releases" section of the artifact it was added to. For example, we have added "Removed Release" to the Requirement artifact in this example, so the value can now be set on the requirements page just like any other field:

These new custom properties can of course be shown in the list pages, filtered and sorted on as well as controlled by the workflow.

The Automation Host Custom Property

One request we have heard from customers and partners (shout out here to Hugo at Coveros) is the need to associate Test Sets and test results (Test Runs) with the equipment being used to execute the test. Now, Spira already has a built-in Automation Host field that can be used for automated testing, but it would be useful to have different sets of test equipment that could be associated with the test execution. For example, you may use some equipment to run the test, as well as the equipment that the test is being performed on. This is quite common in hardware testing.

You can do this already with List or Multilist custom properties, but the problem is that there is no way to associate meta-data about the equipment with the item, it is just a simple name and ID. However, we have now added in v6.13 the ability to create custom properties that use the Automation Host list as their source. That means you can now add multiple custom properties of type Automation Host:

When you do that to the test set or the test run, you can then have the user pick the appropriate test equipment from the dropdown list:

but unlike a simple List property that has just the name, when you associate the Test Run and/or the Test Set with the Automation Host you can have additional meta-data on the Automation Host itself, including its own custom properties:

This is very useful when you want to categorize the test equipment in different ways and store key information such as serial numbers, version numbers, manufacturers, etc.

New Whitepaper - How To Choose A Risk Management Tool

2021-10-29T12:13:39-04:00

Organizations exist to create value for their customers, shareholders, and stakeholders. Their survival depends on the impact of several known and unknown uncertainties emerging from many types of risks that challenge their ability to deliver value continuously. If you don’t manage risk, risk will manage you. The latter won’t be pleasant for your project.

Inflectra At EuroStar Huddle: Deep Dive Automation Week

2021-10-25T16:46:42-04:00

Inflectra is coming to the Deep Dive Automation Week at #EuroSTAR!

Inflectra is excited to participate in EuroStar’s week-long deep dive into all things automation, with expert talks on test flakiness, Cypress, No Code Automation, and more!

Webinar Recap: Rapise 7.1: OracleForms, Executing UFT/QTP Scripts, Floating Licenses

2021-10-29T15:22:05-04:00

On October 28, Inflectra hosted a webinar called Rapise 7.1: New Functionality and Enhancements. Denis Markovtsev, Principal Software Developer, covered the following topics in the live webinar:

Overview of new big features:
1. Support for OracleForms applications
2. Executing UFT/QTP Scripts
3. Spira managed floating licenses
Demonstration of Spira Dashboard and RapiseLauncher enhancements:
1. Productivity improvements
2. Set input parameters via a test set attachment
3. Parallel execution of Test Cases in RapiseLauncher
4. Option to automatically rerun a test set if failed
Selected new features:
1. Tools > Npm Console to install node modules for a test framework
2. More SoftAssert statements

If you missed the webinar, we have a full recap below.

Why You Should Use SpiraPlan If You Care About Software Quality

2024-05-09T06:59:32-04:00

How does SpiraPlan improve my life as someone in QA?

Inflectra’s agile program management platform - SpiraPlan enables the entire software development team to work together and collaborate easily. Everything you need is in one platform: requirements, source code, documents, test cases, risks, bugs, and so on. With all that, SpiraPlan is still highly intuitive and user-friendly.

From the QA perspective, some of the handiest features of SpiraPlan include:

the ability to create and run tests easily, both manual and automated
the Exploratory testing module, which allows users to create test cases while testing is in progress and to modify the test cases at the same time
the complete end-to-end traceability and a robust audit trail
the ability for every team member to quickly and easily see the current status of the product and to manage their assigned items
the ability for QA managers to easily track the testing process through powerful and customizable executive dashboards and reporting modules.

What misconceptions are there around SpiraPlan?

People think that because SpiraPlan is affordable, it can’t be fabulous! But they are mistaken! The product is fully featured and easy to use and represents excellent value for both small and large enterprises wanting to manage and measure their quality and testing efforts on agile projects of all sizes and complexity.

Some also think that Inflectra’s licensing is as archaic as other tools'. It’s not!

We have concurrent licensing across the Spira family of products, so you only pay for those licenses you need at the peak of your usage by flexing up and down in our Cloud versions. No tying a license to a user with Spira!

Some customers are surprised to hear that SpiraPlan is offered both cloud-hosted and on-premise. The versions are identical, and migrating from one deployment method to another is quick and painless.

What SpiraPlan feature are you most proud of and why?

Across the Spira product range, the best feature, in my opinion, is the testing module. It is so easy to use and does not require much testing knowledge or experience to be productive. Even business testers can use it within a short period of time. Diving deeper, SpiraPlan’s

testing module supports manual and automated testing and with traceability from tests and defects back to requirements.
agile planning boards views highlight Task Progress and Test Case results
baselining feature for versioning makes it incredibly easy to see what changed over the course of a Release or Sprint
defect management functionality lets users log a defect at the time of test execution at the specific test step level making the defect triaging easier
tasks give users the ability to associate tasks with an incident for subsequent follow-up and decision-making
risk heat map widget is great for prioritizing the level of attention to be given to address potential risks.

Last but not least, SpiraPlan is a full-featured stand-alone solution but also strives to meet customers where they are by offering over 55 tool integrations for IDE, Automated Testing, CI pipelines, and Source Code Management.

What is Inflectra's roadmap, and how do you decide what to prioritize?

We are very excited about what the future holds for SpiraPlan. Our roadmap includes a range of compelling new features and improvements, including:

improved people management tools with teams, reporting lines, more robust time tracking, and even resource tracking and expensing
enhanced kanban boards to make teams of all sizes efficiently visualize and manage their backlog and active work across products and programs
dynamic tests that are generated on the fly based on a user's needs
more developer-friendly workflows, building on our already deep integration, such as improved code review tools
reporting at all levels of the organization with different tools and reports so a team can create reports on a sprint, while the CIO can read a report about progress across their entire organization.

How do you involve your customers in the SpiraPlan development process?

Our customers are critical in how we shape SpiraPlan and its future direction. Almost every new feature we release or enhancement we make has come from listening carefully to our users. We receive feedback and suggestions daily in customer support. Our SpiraPlan support team is embedded with the product teams, so the feedback loop between customers and the development process can be as rich and fast as possible. We meet customers regularly (in small and larger groups) to understand how they use SpiraPlan and what they need to be even more productive.

How do you test your own tool - SpiraPlan?

Unsurprisingly, we use SpiraPlan and Rapise to test SpiraPlan. We ARE, in effect, the customer of our own platform. This makes it easy for us to understand what the customer may want out of the tool or what they might not want to happen.

Tactically speaking, we have an extensive suite of automated tests that help us test SpiraPlan. In addition, we do quite a bit of manual and exploratory testing, focussing mainly on new functionality and the user interface. It is customary for all team members, irrespective of their function in the company, to contribute to the testing of new functionality. This keeps the team informed of the changes to the platform.

What is the most underappreciated feature of SpiraPlan?

SpiraPlan’s flexibility of use and integration with other products in the market are two areas largely unknown to our potential users.

SpiraPlan does not impose a prescribed way of configuring, customizing, or using the product, thus making the platform compatible with many industry requirements (including regulated industries like life sciences, finance, defense, aerospace). SpiraPlan's feature responsible for the customization of artifacts and workflows is Templates. This built-in feature makes it easy to manage complex business processes. This gives our customers the greatest level of flexibility to meet their individual organizational needs.

Additionally, not everyone knows that SpiraPlan comes with:

a set of default presets and sample data which makes SpiraPlan incredibly easy to get started with
functionality to manage changes to the software at the source code level. Useful in many software development initiatives, the feature allows technical teams to maintain and visualize the source code in SpiraPlan, ensuring the source code traceability when Spira is integrated with dev tools.
the ability to identify secondary risks and associate them with the primary risks allows QA teams to build contingencies and plan for quality along the way.

The increasing range of FREE integrations is underappreciated too because customers are used to paying for these, as they do with other tools providers.

How do you support your customers when releasing SpiraPlan updates?

Inflectra’s release cadence is quite rigorous with new releases, enhancements, and bug fixes coming out every 1-2 months on average. We support our customers and mitigate the risks of disruption in the following ways:

Our releases fall on a weekend to minimize the disruption in case there is an issue
You may have heard about Inflectra’s legendary customer support! We run a 24-hour tech support operation to answer the questions related to all tech issues, including the new releases
We make sure the platform documentation is updated with new release notes, which we communicate to our customers via email updates, blogs or knowledgebase articles
We usually run release-related webinars to demonstrate the new features and enhancements and answer questions from the audience
With this volume of new releases, there is a large amount of testing that gets done before we release to avoid our customers becoming our testers.

What type of support is given when purchasing SpiraPlan?

Inflectra is quintessentially a company that makes application lifecycle management, QA, and automation platforms that are ready for use out of the box. The easy-to-use and intuitive user interface ensure that users are able to get started quickly after the purchase. However, we do take care of our potential users pre-, during-, and post-purchase. We offer pre-purchase discovery and platform and integration demos to determine if SpiraPlan ( or Rapise - Inflectra’s test automation tool) is a good fit for the user.

In post-purchase, we offer limited live training and additional implementation services for data migration, workflow set-up, and custom reporting.

Additionally, after 16 years in business, Inflectra created a large number of learning resources - both free and paid - that are available on our website and youtube. The VIP management services are also offered through Inflectra’s extensive partner network.

Getting Spira Notifications Using RSS Feeds

2023-05-24T19:53:15-04:00

Step 1 - Setting up the Filter

The first step is to go into Spira and set the filter to find the items that you want to be alerted on. For example, we might set a filter to include all the test cases that have recently failed in the current release:

Once you have the filters set the way you want, simply use the option to Save the filter as a favorite:

This filter will now be available as a subscribable widget on the Spira My Page dashboard:

Now we can use these saved filters and the RSS feed icon to use the notification feature:

Step 2 - Using the RSS Feeds for Notifications

Now that we have created the filter as an RSS feed, we can use it in other applications to get notified. We will look at the examples of Microsoft Outlook and Slack, but any application that you use that supports RSS feeds can also be used to notify you.

Using RSS Feeds in Outlook

Firstly, you need to right-click on the Outlook folders on the left-hand side and choose the Add a New RSS Feed option:

Then paste in the URL from the RSS icon inside Spira:

Finally, click the Add button and the Spira saved filter is now available inside Outlook and will notify you when you have any matching items:

Using RSS Feeds in Slack

The process for adding the Spira newsfeed to notify you in Slack is pretty similar.

Firstly, go to the Slack App Directory and add the RSS app to Slack.

Once that's done you can then choose to Add a Feed and paste in the URL from the RSS icon inside Spira:

You also need to choose the Slack channel that this notification will post into. Once you have done that, click the Subscribe to this feed button to completed the connection.

You should now see notifications like the following:

Recap: QA Financial Forum in New York 2021

2022-12-09T17:57:35-05:00

Travel to New York City

Making a nice change from the usual world of either online conferences using Zoom or in-person events where we have to take a flight from the airport, we were lucky that our trip from our headquarters in Washington, DC to New York allowed us to experience the joys of train travel, in this case, the super-cool Acela from Amtrak. After a short three-hour journey, we made our way from Union Station to....

... The recently renovated Pennsylvania Station in New York. Occupying the Old Post Office building, the new "Moynihan Train Hall" was an unexpected delight after the bad old days of scuttling into New York like rats in a tunnel. Now we could enter through its majestic atrium and be right on 8th Avenue next to Madison Square Garden.

The QA Financial Forum New York 2021

The QA Financial Forum, now in its sixth year, is produced by QA Media, an independent information and research business which is focused on the management of software quality assurance at financial firms. The Forum features expert speakers from leading banks, insurance companies, exchanges, and asset managers discussing key opportunities and challenges.

After an absence of over 18 months, The QA Financial Forum New York returned as a live event on October 19th, 2021 at The Harvard Club on W44th Street.

This year, the Forum key topics included:

Managing enterprise software quality in the DevOps transition
Accelerating continuous integration and delivery with automation
Technologies for automation and AI
App security and DevSecOps
Emerging standards for software risk management and operational resilience

The Inflectra team comprising: Adam, Thea, Teresa, and Sriram were on hand to discuss matters regarding risk management, software development, quality assurance, agile transformation, cybersecurity, and DevOps.

The team were excited to meet QA experts and leaders in financial services in-person for the first time since the pandemic started in 2020. For many of the attendees, the event was also their first in-person experience since 2020.

Demonstrating the ease of use, power and flexibility of the Inflectra SpiraPlan platform, the Inflectra booth features interactive exhibits including high resolution iPads showcasing the live SpiraPlan platform running in the cloud and accessible on any device.

The attendees remarked on the refinement, user-friendliness, and compelling displays of business intelligence that could be accessed with a simple drill down from the main dashboards.

Meeting Key Speakers

In addition to meeting and networking with attendees, Team Inflectra was pleased to be able to invite to New York (and QA Financial) the world-renowned Dr. Oonagh McDonald CBE, who has worked for the London Metal Exchange, International Monetary Fund, and UK Financial Services Authority. In 1998, she was awarded the CBE for services to financial regulation and business. She has been the Chair of the Fairbanking Mark Assessment Panel for the Fairbanking Foundation since November 2013.

In the photograph above, you can see Dr. McDonald along with the Inflectra Team.

The Inflectra team would like to thank the conference organizer - Matthew Crabbe from QA Financial for putting on the event, moderating the sessions, and making sure that everything went according to plan.

We'd also like to give a shout-out to Dr. Sriram Rajagopalan, the resident Agile Evangelist at Inflectra who was able to provide many important insights to the attendees on the subjects of risk management and employing a common-sense approach to agile development.

New frontiers in systems and supervision: Modernization at government agencies, and the response to new compliance standards for software risk management

Adam Sandman, Founder, and CEO of Inflectra was invited to be part of the panel discussing Risk Management and Operational Resilience. The panelists discussed how government agencies and central banks are leveraging DevOps technologies to manage their own digital transformations. At a time when banking supervisors around the world are increasing their scrutiny of operational resilience standards among retail and commercial banks, the panel was looking at how central banks are assessing their own needs for new tools and technologies and how their experience is shaping their views on software risk management and supervisory technologies.

Focus topics included the opportunities for applying machine learning to the automation of supervision and the "pressure points" in the modernization of platforms, notably payments.

The speakers included:
• Dr. Oonagh McDonald, senior advisor, Crito Capital, formerly arbitrator to FINRA and former director of the UK Financial Services Authority
• Jan Guido, business resiliency consultant
• Aaron Bartnick, senior associate, Macro Advisory Partners
• Nita Kohli, head of operational resilience, Freddie Mac
• Adam Sandman, founder and CEO, Inflectra

Heading Out on the Town to Celebrate!

After the conclusion of the day's activities, the #TeamInflectra decided to head out to Times Square to celebrate the return to in-person events and the chance to meet and discuss technical and strategic topics with speakers and attendees in real life!

For those who wonder if New York is Back....

.... Yes, New York is Back and Better than Ever!

Looking Forward to Seeing You

Wherever you live, we hope to see you at InflectraCon 2022 or at an event near you...

How to Use Boards in Spira for Your Agile Ceremonies

2025-11-30T06:06:27-05:00

The Four Agile Ceremonies

The fundamental goal of the four agile ceremonies is that they collectively tell a story! This story is about delivering value to the customer. This value increment is called the Minimally Marketable Feature (MMF) and must be integrated with the benefits for the performing organization. The resulting benefit management sustained through the value stream mapping is part of the Minimum Viable Product (MVP) and must be aligned to the product roadmap delivered in one or more releases.

Consequently, the product roadmap represents the product strategy integrated with the Measurable Organizational Value (MOV) of the business strategy. Therefore, not only the product increments are created, but also valuable lessons are learned. While multiple artifacts are getting created during the delivery of product increment, the story has to emerge through the board that integrates how effectively planning was done and how efficiently increments were delivered. This connection is demonstrated in Figure 1.

Figure 1: Understanding the Context

“Ready State” of a Backlog

One of the prerequisites of a backlog is to be in a “Ready” state. This ready state means the items in the backlog adheres to the DEEP property:

Detailed appropriately
Emergent
Estimable
Prioritized.

It is pivotal that the Product Owner and the team collaborate on creating a healthy product backlog. Based on my personal experience, I recommend that the backlog is filled with items to feed at least two future iterations. Simply put, if we are working on the N^th iteration, a ready state backlog has backlog items conform to the DEEP property for N+2 iterations, as illustrated in Figure 2.

Figure 2: Backlog in a Ready State

While refining the backlog to a ready state, such as from item 4, Spira does not require these items to be associated with any release or iteration. This approach ensures that the delivery team can take part in the release and iteration planning to ensure that they can commit to the work in the upcoming iteration. For instance, a product owner may envision a particular feature to be delivered in a specific release that itself consists of many smaller iterations.

While taking part in the release planning, the delivery team may require some technical experiment to be done. Subsequently, additional backlog items can be added from the delivery team’s perspective, which can serve as an independent evaluation of work conforming to the team’s willingness to take on the feature in any specific iteration.

If any work at this point requires further refinement for absorption into the next iteration, the opportunity is presented for the product owner to work with the appropriate stakeholder to further refine so that this item can be prioritized into the next iteration. When the requirements are finally ready to be delivered in an iteration, they can be associated with the appropriate iteration within the release.

Roadmap to Release Planning

A release is most frequently associated with a major functionality delivered according to the product roadmap. Alternatively, the product owners may also use the roadmap to align with calendar-based releases if an organization uses yearly, half-yearly, quarterly, or monthly releases. Depending upon the organization’s cadence for releasing functionality, a release may consist of two or more iterations. Some organizations may directly go to iterations if the organizational governance and compliance framework allows such an operating cadence.

So, release planning is frequently desired but optionally implemented when agile is adapted. However, iterations are always present. If an organization does not implement releases, then, the iterations still must be mapped to the roadmap.

The relationship between roadmap-release-iteration may be conceptually difficult to understand as many people think releases and iterations are the same or releases are an overhead not required.

Yet, another group of teams incorrectly practicing agile framework without any connection to product strategy may be wondering why a roadmap containing product goals is even required. So, let us illustrate with a realistic example. In light of the global pandemic, where the time required to develop a vaccine is questioned or the efficacy of the vaccine for a specific age population or the booster shot is examined, it is good to review the product roadmap, releases, and iterations with a high-level overview of the drug development lifecycle presented in Figure 3 (Rajagopalan, 2019).

Figure 3: Drug Development Lifecycle and Relationship to Roadmap, Releases, and Iterations

Image created and owned by Dr. Sriram Rajagopalan based on his practitioner experience.

In this diagram, several stages such as the pre-clinical trial, clinical trial on a human population, and drug approval process are identified as the product roadmap milestones concluding approximately at Years 4, 9, and 12. These milestones serve as stage gates before product development can continue as part of the strategy. Even in an IT industry where the product may be a software application, such a milestone is required for getting the appropriate funding and approval for product development to continue.

So, the product strategy perspective lays the foundation for a product roadmap and subsequent planning:

Now, if one focuses on the first milestone of pre-clinical trials, scientists may evaluate areas like the mechanism of action, channeling the drug to use specific pathways, and understanding the resulting pharmacokinetics.
Subsequent to satisfying this need, they may move on to testing the drug with different themes, such as pharmacological and toxicological testing, to ensure that essential organs (such as heart, lungs, liver, etc.) are not getting affected. And, this testing may have to be conducted in various lab animals from mice to monkeys before the results can be compiled for its efficacy to proceed with the testing on the human population, confirming the first human dose.
Each such stage is a release by itself. Each release has its own goal (MMF), serving as a micro-stage gate to continuously progress the drug depending upon the success criteria (MVP).
When the drug does not meet the required criteria, a decision is made to terminate the continuous research or take a different path aligned with the business strategy (MOV).

As one can see, even research & development uses the concepts behind roadmap, release, and iteration.

Therefore, it is imperative that a roadmap exists so that the sequences of releases can be identified and the backlog items are appropriately refined and mapped to the releases and iterations (established in our case, in Spira). This release planning activity precedes iteration planning but serves as a good foundation to ensure that the required stories are in the backlog to deliver on the product roadmap. Figure 4 illustrates this concept in Spira on how five releases are used to deliver on a milestone in the product roadmap.

Collaborating with the team, the product owner may extend the release planning with the continuous backlog refinement activity. This process will help identify any stories from the team’s delivery angle that otherwise would be missed if the release planning is not done. This is shown in Figure 4 below where release 4 is empty requiring work that needs to be done before work in release 5 can start.

Collectively, these releases then unleash the story the product development team must report to the management. For this exact purpose, we have built a number of standard widgets and reports into Spira. Those details are outside the scope of this blog. But if readers want to customize the standard Spira reports, then they should review our blog on the data extraction and reporting in Spira.

Figure 4: Release Planning in Spira

Iteration Planning

Contrary to release planning, iteration planning is focusing on the work committed by the team to be done immediately after planning is completed. It is important to note the keyword – immediately. Generally speaking, iterations are expected to start immediately after the planning is done and the previous iteration ends because the team maintains the operating cadence and also has the context of work already delivered.

Like the roadmap is associated with one or more releases, with each release having a goal towards delivering the MVP for the roadmap, the releases are associated with one or more iterations - with each iteration having a goal to deliver the MMF. This is demonstrated in Figure 5.

Figure 5: Iteration Planning in Spira

Daily Standup

The daily standup is where the team members discuss their progress confirming their commitments to the iteration goals. Please note that the ownership is for the team members to discuss the progress. This daily standup is not a status check meeting where the product owner or other team member acts as a status coordinator. The daily standup is analogous to players visiting the waterhole from the example we previously discussed. The main difference is that the team members are the only members confirming completion, impediment, or feedback.

The completion may be recorded on the individual backlog items that move through the various status. Spira provides a robust requirement workflow to facilitate this movement where the assigned owner can mark the status by executing the appropriate transition operation on the requirement. This is demonstrated in Figure 6. Furthermore, Spira’s comment feature (not shown in Figure 6) can also be used to document observations to preserve the context for any decisions made.

Figure 6: Invoking Workflow Status on the Requirement

If the requirement status has not already been updated, the team can leverage the tracking board under the requirement’s panel in the daily standup. The tracking board allows the team to see all the requirements by various statuses. This can be accomplished by selecting the specific release and the status in the Group By section as illustrated in Figure 7. If readers wonder about the background color on the In Progress lane, this color coding demonstrates Spira’s support for Kanban, where a limit is put on work-in-progress. Readers can follow the Kanban WIP article for more details.

Figure 7: Requirement Status from the Tracking Board

Spira allows options for the tool to be configured to facilitate the automatic status update based on certain events and also do some activities. For instance, as each requirement is “dragged” to an iteration (this is the first part of the iteration planning) in the iteration planning, the status automatically becomes “Planned.” Since teams always break requirements into tasks (this is the second part of the iteration planning after the team commits to a backlog item), Spira can automatically create a default task when the requirement is marked as “In Progress”. Similarly, when tasks or test cases associated with the requirements are updated, the requirement status can automatically move as well. These options can be enabled or disabled in the Planning Options section based on the operating preferences of the delivery team.

Another popular activity that happens in the daily standup is an update on the burn-up, burndown, and velocity charts. Here too Spira comes to the rescue where such details need not be manually tracked. With the requirements moving through the statuses, the charts are automatically updated in the “Requirements Graph” widget for the team to review, inspect, and adapt. This requirement graph is shown in Figure 8 below. In addition, Spira provides numerous widgets to track progress at the project, requirement, task, build, testing, and defect levels.

Figure 8: Requirement Graph Widget

XXXspirateamtrialXXX

Review

The review is where the team demonstrates the product increment on the work completed. While the product owner can review, accept, and even release the work product throughout the iteration, the review presents an opportunity for the team to demonstrate the functionality. These “show-and-tell” review sessions are recommended for the business stakeholders beyond the delivery team. Based on the product increments delivered, new items may be added to the product backlog. However, the accountability rests with the product owner to accept the work completed or reject it based on the definition of done.

As you may have guessed already, the workflow operations at the requirement level can be used for this purpose (as shown in Figure 9). Here, readers can see the “Mark as Completed” transition operation to move the requirement from the “Tested” state to the “Completed” state. This specific section of Spira allows the product owner to also add comments as appropriate, such as tracking an electronic signature to this approval if the regulatory and compliance nature of the product requires it. Spira allows the transition operations to be configurable with many options for what fields must be required, hidden, or disabled, execution options, notification options, and electronic signature. These configurable options are not shown in Figure 9.

Figure 9: Workflow operation for Completing Requirements in the Review Session

Following the similar workflow approach for requirements, it is also important for the product owner to review the iteration workflow and mark the iteration closed. This iteration closure ensures that only active releases are brought when the team works subsequently in future iterations.

XXXspirateamdemoXXX

Retrospective

The goal of the retrospective is not to identify the person observing the improvements and suggesting the recommendations but to capture the improvements and recommendations. To facilitate this goal, many techniques can be utilized. Those techniques are beyond the scope of our blog. However, the product owner or an appointed person can document the observations anonymously (e.g., using a survey) or discuss them in a meeting if members are not concerned about anonymity. So, it is recommended to keep a register for lessons learned in a separate Spira product.

In Figure 10, a new project, “Retrospective” is created where three rich-text-field custom properties are added to the requirement. These properties represent the activities that the team must start doing, stop doing, and keep doing. These activities can be related to a product or process. Subsequently, the backlog in the appropriate Spira product can be populated with requirements related to product and process, brought into the iteration planning immediately, and implemented accordingly.

Figure 10: Handling Retrospective in Spira

Summary

Through these three blogs, we have illustrated how Spira promotes and upholds the basic Agile principles emphasizing transparency, inspection, and adaptation. The Planning Board feature serves as the critical life-saving waterhole in the jungle, and all stakeholders benefit from these Agile principles. At the same time, understanding the role of the backlog items using the DEEP property ensures that the product strategy is aligned with the business strategy.

Agile is not about fierce execution without planning. Agile fundamentally puts a box around the amount of risk that can be controlled by using its timeboxing approach. So, planning for releases to align with the roadmap and then with the iterations, associating backlog items with components and priorities, configuring the requirements through workflows to collect appropriate stakeholder feedback, and tracking commitments through the iteration are facilitated by the planning board and tracking boards.

Spira is a powerful tool and this blog only focuses on the boards it currently has to support Agile approaches to product development and project management.

Many functionalities, such as workflow operations, electronic signature, widgets, and customization are mentioned. Readers are requested to consult Spira Documentation and Inflectra extensive knowledge base articles for more information.

XXXspirateamtrialXXX

References

Rajagopalan, S. (2020). The role of Project Management in Drug Development. Retrieved September 24, 2021 from https://www.youtube.com/watch?v=alxSRZpOJKk

Using Spira Custom Reporting to Your Advantage

2021-09-24T14:19:29-04:00

1) Creating a Graph of Automated vs. Manual Test Execution Duration

Sometimes you will want to get an idea how fast your manual and automated tests are taking. You can use the custom graphing feature to create a custom graph for this:

2) Creating a Report of Requirements Test Coverage Percentages

SpiraTest comes with a built in graph for displaying the requirements' test coverage information. However sometimes you want the raw data and percentages rather than just the graphical form. This KB article shows how you can use the custom reporting functionality to do this.

3) Generating a Report of Artifacts that have Invalid Dates

Sometimes you will load in data into SpiraTeam using Excel, Google Sheets or other methods where you end up with dates that are invalid, for example tasks that have an end date before their start date! This article explains how you can use a custom report to quickly find them.

Recap: JFTL French Testing Day in Paris, France

2021-09-17T16:59:24-04:00

#TeamInflectra Meeting Up

This event was a truly international affair, with our team (François, Jessica and Adam) flying in from Washington, DC to meet up with the latest addition to the Inflectra "family" - Farid - who is based in Marseille and came up by train to Paris.

We used the time before the event for some team building, bonding, discussing the logistics of the event, and of course, since we were in Paris (well technically Montrouge), some fine French food and wine (also beer, which was also excellent).

Setting Up for JFTL

Each year, the JFTL event takes place in the Beffroi de Montrouge, a local cultural center and conference venue that is so named for its belfry that is part of this classic 1930s art-demo masterpiece. In front of the building, there are statues dedicated to famous writers and scientists (such as Molière).

The day before the event, we were able to get access to the building and setup the Inflectra booth:

We were fortunate to have a lot of the booth pre-built for us by the excellent staff from Comité Français des Tests Logiciels (CFTL), so we just needed to setup the displays, iPads, surveys, business cards, brochures and of course ... the SWAG!

Once we were all setup, it was exciting to be back in business after 18 months at home...

After we finished the setup, the team took a well deserved break and explored Paris by night, with lots of stories and anecdotes of conferences past...

Inflectra @ JFTL (French Testing Day)

The team was ready and prepared for the onslaught of the conference attendees. The organizers let us know that they expected about 1,100 people to attend the event, with tickets sold out weeks in advance. We had provided some complimentary tickets to our best French customers, and it was wonderful to meet many of them face to face.

During the day, Francois and Farid took the lead in demonstrating SpiraTest, SpiraTeam, SpiraPlan and Rapise to the delegates, with assistance from Adam as necessary. When there were potential partner discussions, Jessica, our head of partnerships and alliances was on hand.

Just before lunch, Adam took a break from the Inflectra Booth to delivery his talk on "API Testing", which was very well received by the audience.

After the talk, it was back to the booth to hand out swag, answer questions, demonstrate the products and learn about the trends in the software testing industry.

Resting and Celebration

Once we had finished JFTL with our computers full of leads and our heads buzzing with new ideas, it was time to break down the booth and take a rest....

But perhaps not too much of a rest...

After a little break... the team went out one last time for dinner, drinks and some tall stories (including the size of Sardines in Marseille!) before the team prepared for travel back home...

.... till the next time (hopefully).

The Ultimate Conference SWAG :-)

After the conference, we took the Metro into town and visited the month-long wrapping of the Arc de Triomphe in white fabric. This wrappings is a posthumous art project that is an homage to the late artists Christo and Jeanne-Claude, who famously wrapped other buildings such as the German Reichstag in Berlin.

This installation of course, gave us the idea for a little Photoshop fakery:

Inflectra Corporation is pleased to announce our expansion into the French IT market with a gift wrapped present, however it looks like we may have taken #conference #SWAG too literally? #jftl #softwaretesting #agilemethodologies

Understanding the Planning Board for Backlog Refinement

2021-09-13T13:47:21-04:00

As teams work through multiple artifacts, a tool should support both - effectiveness of decision-making and efficiency in tracking the items through the delivery lifecycle. Therefore, it is critical to view the use of the planning board through the lens of the four agile ceremonies of iteration planning, daily standup, review, and retrospective. However, before we proceed with iteration planning, we need to understand the importance of a refined backlog. In this blog, we will review the stages of the backlog before items in the backlog are ready for the Agile Ceremonies.

The Focus of Agile Ceremonies

Too frequently, teams and even organizations embarking on Agile transformation fail to understand the benefit of the four Agile ceremonies. It is true that these ceremonies set an operating cadence. However, by using progressive elaboration and a timeboxing method, the Agile approaches reduce risk- and cost impact on the increment released to the customer for feedback. When the increment is small enough, the time taken to give clear, concise, and comprehensive feedback is also greatly enhanced. As the delivery teams own the commitments, they work to ascertain other stakeholder commitments to ensure that the product increments are sustained in operations to enhance value to the customer. From the perspective of the delivery team, this approach translates into an increased value to the customer and better product quality. Strategically speaking, the time to market and the potential cost of operational ownership is also reduced.

Figure 1: Benefits of Agile Ceremonies

Backlog Refinement

A team will not be able to demonstrate value if there is nothing valuable for them to work on. Therefore, one of the essential prerequisites for an agile team is a good backlog as represented by features from both the internal and external stakeholders but also the project team. Consequently, the backlog may have many items with some large epics and some essential features. As is common with any project, these ideas define the needs, expectations, and wants (Rajagopalan, 2020) of stakeholders while also requiring further refinement of backlog to ensure alignment with the strategic objectives, existing and desired technology stack, and team’s skills, capabilities, and competencies.

Figure 2: Backlog Refinement is an Ongoing Activity

Backlog refinement is initially required to ensure that the product represents a prioritized list of requirements for the minimum viable product (MVP). This refinement is an ongoing activity that happens throughout all four agile ceremonies. The product owner is ultimately accountable for refining this list of backlog items; the agile coach is responsible for ensuring that the refinement process is continuous and consistent. As Garbage-In-Garbage-Out (GIGO) principles illustrate, it is vital to develop reliably value-producing work that factors appropriate stakeholders’ inputs to avoid rework. Equally important is the increased transparency of the work coming to the teams. So, let us (additionally) discuss how a backlog emerges and how it can be viewed.

Initial State of Backlog

In the initial stage, the backlog may have a collection of extremely large items. Represented as the red rectangles, they show how the product backlog initially is a set of items that require more discussions and refinement. Then they will be split into reasonably sized requirement groups for the team to prioritize. Frequently, teams try to categorize these larger requirements immediately into Epic, Theme, or Feature. When teams do not agree on the meaning of these terms, an attempt at the categorization of large requirements creates confusion. What exactly these terms mean and how they can be used to determine the level of required effort in order to generate reasonable product increments to deliver these requirements is a topic of a much larger discussion. So, in the spirit of being agile, let us park that discussion for a future blog.

Furthermore, some teams may assign a subject-matter expert to break down a specific backlog item. For instance, in Figure 3, there is a large requirement called “Demo for Potential First-Time Users” of the library system. Whether this functionality should be a set of documentation with screenshots or a video illustrating the essential functions, or how this documentation or video be made available for non-English speakers or vision-impaired users are more details that require an SME to unpack. To facilitate product backlog, these requirements may be assigned to such a specific user.

Figure 3: Initiate State of Product Backlog

The Emerging State of Backlog

Meanwhile, matured teams or organizations with reasonable experience working in the Agile framework may have definitions to organize the requirement groups into themes, epics, features, use cases, and user stories. If a product owner has further aligned these requirements into product-specific higher-level requirement groups, frequently called Epics, then the product backlog can also be viewed a) by requirements not categorized under specific Epics and b) under requirements categorized into the higher-level product-specific groups.

This emerging state of backlog establishes a connection with both - the strategic direction of the product (with named epics and desired features as minimum expectations for generating value for the customer) and the stakeholder expectations to sustain the customer value by supporting business value, technical value, and process value features. In Spira, you can see this by grouping by Epic after selecting the product backlog as represented by the green rectangles.

The minimum viable product (MVP) emerging from the product backlog is inexorably aligned with the product roadmap, which is further aligned with the business strategy (such as horizontal and vertical product penetration). Consequently, good product owners also align product backlog items with the types of features (theme) that are released. It helps the product owners prioritize these requirements for additional refinement and balance them against the required experiments (spikes) to be carried out. So, Spira supports this good practice by allowing product owners and the teams to have increased transparency of product backlog by components (product features) as demonstrated in Figure 4. The red rectangles here indicate product backlog selection followed by a grouping of defined components that display the requirements grouped by the green rectangles.

Figure 4: Product Backlog by Product Features

**The Ready-State of Backlog**

The definition of ready may differ from one product to another in each organization. Nevertheless, the minimum expectation of a ready-state is that the requirement is scoped out in “just enough” detail and prioritized by the product owner aligned with the product roadmap. Consequently, a ready state is determined by how well the product backlog is risk-adjusted and prioritized. Many Agile practitioners associate the items in the product backlog with the DEEP property that stands for Detailed Appropriately, Emergent, Estimable, and Prioritized. In short, if items adhere to this DEEP property, then they are adequately refined for the team to discuss them in the planning sessions and potentially commit to executing on them.

Figure 5: Backlog Item Characteristics

At a very high level, Spira supports this DEEP property of the backlog item by allowing the prioritization of the features based on product goals aligned with strategic goals. A widespread priority scheme emerging from Dynamic Systems Development Methodology (DSDM) for prioritization is the MoSCoW principles (Todaro, 2019), highlighting what the team must, should, could, and won’t do. These priorities are mapped by categorizing requirements into critical, high, medium, and low. By selecting the product backlog in the planning section and grouping it by priority, the planning gives this ready state view (as illustrated in Figure 6). Please note that these cards are color-coded on the left margin of the card.

Figure 6: Priority Scheme Mapping for Ready State View

Teams can close the gap on what requirements are going through refinement to finally get to the “accepted state” (using the requirement workflow approval process) by exploring the “group by requirement” status. This status demonstrates what requirements are finally ready for iteration planning. Readers are directed to also incorporate the color code on the card’s left margin to also look at how cards can be brought into the iteration planning based on a mix of must, should, and could do to balance team commitments made in planning according to the team’s working agreements. Agile practitioners generally recommend balancing these priority stories committed in any iteration. For instance, having 60-20-20 as a rubric to bring must-should-could stories so that the team can ensure must-should are delivered while recognizing that risks may emerge during a sprint that can impact delivery.

Figure 7: Status & Priority Scheme Mapping for Ready State View

With the transparency enabled by role-based privileges, Spira allows a detailed overview of backlog items demonstrating the DEEP property of these requirements. Stakeholders’ input and approval are recorded, prioritization is confirmed, and enough detail is available for the team to think through the estimation. Such a ready-state nature of the product backlog sets the stage for the first stage of the Agile ceremony of Commitment Planning.

Figure 8: Ready state of items in the Backlog

Summary

Agile approaches promote experimentation so that teams can fail fast by discovering what does not work for the customer or in the technical implementation. However, failing fast is not a prescription to avoid planning. In fact, ‘if we fail to plan, we plan to fail,’ still rings true in Agile. This approach recommends just-enough planning to ensure that backlog item is detailed appropriately with input and feedback from stakeholders. This practice allows for:

continuous improvement of requirements through product increments in an iterative fashion
Estimating the level of work required along with priority alignment to the product strategy.

This DEEP planning sets the stage for Commitment Planning as the first stage of the Agile ceremony. We will discuss the four agile ceremonies and Spira’s support for them in the next blog.

References

Rajagopalan, S. (2020). Organized Common Sense. Parker, Colorado: Outskirts Press.

Todaro, D. (2019). The Epic Guide to Agile. North Hampton, NH: R9 Publishing.

Your Web App <> #TestBowl 2021 - Inflectra's Software Testing Challenge

2021-09-21T16:16:25-04:00

Why Submit Your Software to #TestBowl?

Get real-life testing by a group of experienced testers (up to 2 hours of testing)
Get testing results in the form of a bug report, and/or a test report
Network with expert testers
Get exposure for your app/software among the dynamic and diverse group of professionals from all over the USA and beyond.
Get Inflectra’s test management tool license for a year (SpiraTest / cloud subscription with the test results from the competition preloaded)

Who Is Eligible?

You are welcome to send us your app/software if you can:

Work with #TestBowl organizers to prepare the web app or website for the competition
Demo the app or website at the event to acquaint the participants with its main functionalities
Extra points if you stay during the event to answer additional questions from testers.

What Sorts Of Web Apps/Website Are We Looking To Test?

For the best result, your app/software should be:

in beta testing
if mobile, be available for download from both Apple iOS and Google Play marketplaces
if web, be accessible via a public URL
feature-rich
free to download/use (for participating testers, at least)

Submit your web app information here!

About #TestBowl Organizers

#TestBowl is organized by Inflectra – a DC-based software company that makes SpiraTest. SpiraTest is a QA powerhouse and the official test management tool of #TestBowl.

Webinar Recap: Spira v6.11 - New Features and Enhancements

2021-09-02T16:35:53-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the webinar presentation.

Spira v6.11 is out - New Features and Enhancements from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

When Microsoft Dynamics 365 Updates, Rapise Has You Covered!

2021-08-30T10:57:33-04:00

Microsoft Changes to Dynamics 365

Last month, Microsoft released Microsoft Dynamics 365 2021 Release Wave 2. This major set of updates to Dynamics365 for Sales introduces a lot of new functionality for end users, which is great news. However, it also introduced a lot of breaking changes to the User Interface (UI) which will result in a lot of automated tests no longer working if you are writing your own test scripts using tools such as Selenium.

Rapise Has You Covered

The good news is that Rapise has dedicated libraries for testing Microsoft Dynamics 365 and we have already updated these libraries in v7.1 to handle the changes for you. See our KB Article on the Dynamics365 Library Changes.

Demystifying a Good Agile Product Backlog

2025-11-30T06:15:15-05:00

Nevertheless, I asked why the developers can’t add their technical requirements and specification to the product backlog to promote transparency to the product owner and scrum master. One of the members questioned, “Can we all add access to product backlog? I thought it was product owner’s playground.” Another member reasoned, “We have technical requirements, and the backlog is supposed to be full of user stories!”.

If the team is unclear about the fundamental empirical pillar of transparency to the product backlog and does not understand how value is a function of the entire team’s contribution, are we truly agile to begin with!? We seem to divide the team with roles and confuse ourselves with terms rather than rally the teams around value to customers and business. This is why I claim that “Agile is a Teenager now, but agility is still a toddler!”

In the spirit of being agile, I would like to focus on one important objective? A good product backlog! In this article, let me unpack some of my thoughts on the need for a product backlog!

Product Backlog is like the Waterhole

Most of you have seen the National Geography or other programs talking about various animals in the jungles and forests. Each animal may have its own food preferences or live in various sections of the forests. Some live on the trees; some roam the grasslands, some hunt to survive, and some feed on the leftover. Regardless of the vast differences, they all quench their thirst for water at the waterhole.

Figure 1: Product Backlog is synonymous with Waterhole

When I look at the product backlog, I think of the waterhole. Every stakeholder may have specific responsibilities. Some may be senior members of the management team evaluating which programs to start based on company strategies. Some may be the middle management focusing on aligning these company strategies with the product roadmap, technology stack to sustain mergers and acquisition, regulatory compliance, and ongoing operations. Some may be the core teams focusing on prioritizing the work based on bandwidth towards alignment and delivering on commitments to produce value. Like the waterhole brings all animals together towards the life-source - water, the product backlog brings every stakeholder together towards alignment. Just like the waterhole is open and noticeable, and transparent.

Product Backlog Promotes Stakeholder Alignment

One of the critical aspects of transparency is to align the stakeholders and team members towards the valuable functionality to be delivered. What produces value is not the product owner’s responsibility alone. The product owner is accountable for prioritizing the value stream mapping, aligning the product strategy in the roadmap to the needs and epics in the releases and requirements and stories in the iterations. This value stream mapping should not only be from the customer’s point of view but also from the business to sustain itself in delivering incremental, recurrent, and consolidated value.

The alignment, therefore, integrates the customers, the business objectives, the information architecture underlying the product, and the processes that continually remove overheads, augments efficiency, and promotes effectiveness. Therefore, alignment in the product backlog is analogous to a creative artist’s work. While the ultimate work-product, painting, is the final end value for the customer, the painter also has to be supplied with the tools enabling the painter to sketch and the processes required to give the time and space for the painter to experiment. If you remove these painter’s toolset and the time and space needed for the painter, can the painter deliver the painting?

Figure 2: Product Backlog supports various Stakeholders

But, which paints and canvas are required for the painter? When are they needed? What are the alternatives that can work? The answer to these questions is not always obtained from the manager who manages the initiatives but from the painters themselves? And then the other stakeholders responsible for marketing and promotion, event organizers, and many other stakeholder groups. Their requirements have to be solicited and broken down to needs, expectations and wants to facilitate prioritization.

However, in a rush to deliver value quickly, if the working agreements, necessary tools, and required processes for the team to deliver value are not focused on, a product backlog may have many requests from selected stakeholders making the backlog less valuable. Furthermore, such a backlog cannot facilitate the categorization of functionality for subsequent prioritization of value. This alignment, therefore, requires inspection and adaption, two additional empirical pillars to transparency, from the entire team. As a result, the product owner does not have to write all the requirements, but everyone in the team should contribute to balancing the types of stories.

Characteristics of Good Product Backlog

Now that we have understood who can interface with a product backlog, let us review its characteristics. It is important to reemphasize that a backlog continuously supports transparency, inspection, and adaptation. It is also important to disassociate from incorrect views of the backlog due to the anti-patterns like how a specific company implements agile in their organization by discussing specific roles like the business analyst or technical product owner or having one person function as both product owner as scrum master, or a traveling product owner unavailable for the team, etc.

Accommodate different types of requirements

Once a senior member of an agile team mentioned to me, “Well, we now write user stories. So, I guess that makes us agile!” I am sure agile transformation consultants would disagree. Agile teams frequently get hung up on the terms “user stories” and this is primarily because the work they commit to doing in a sprint leverages user story. However, since different stakeholders may add to a product backlog, their ideas must be categorized into higher-level requirements, disaggregated specific features, and refined as user stories. So, one of the first requirements of a good backlog is that it should allow different requirement types.

Figure 3: Support for Requirement Types in Spira

In the example illustrated above in the high-level requirements for implementing a hospital surveillance system, some uses cases may emerge from various stakeholders. Some of these may be broken down by the stakeholder groups as features and the team by specific user stories. Alternatively, some essential non-negotiables may be identified as large epics that may have design compliance needs, architectural design considerations, or quality considerations, as noted. Each one of these requirements can be refined to come up with granular user stories.

Allows Product and Business Categorization

When multiple stakeholders interact, there will not be a shortage of how categorization might be applied. For example, at one extreme, the business may see value in terms of features delivered to customers that support sales and marketing for product penetration in the customer’s organization and market diversification with new industries. At the other extreme, the team working on the product may view the work in terms of the functionality, such as security, portability, reliability, or user interface improvements, delivered to the product. Any requirement or user story thus developed will have to, therefore, at minimum, support such dual categorization.

Figure 4: Product and Business Categorization

In Figure 4 illustrated, we can see how the various stakeholder requirements on the left of the particular requirement type in the middle are being refined towards the team to potentially work on. Furthermore, the product owner also can balance the requirements around product strategy on what specific areas to focus on. For instance, if the stakeholders agree on Monitoring as the primary value for customers followed by training considerations for security personnel and staff, then such product component categorization allows product functionality prioritization bringing all stakeholders to alignment. As a result, even though policies and procedures related work is important, the stakeholders understand from this categorization that their needs have to be deferred.

Allows Priority Scheme

An important characteristic of the items in the backlog is to enable the product owner to prioritize these items to maximize the value to the customer, simultaneously balancing the team’s expectation of the value-enabling stories (business, technical, and process). Therefore, the backlog must make it very clear what is the most valuable item while also allowing the team members to slice and dice the backlog and filter and query the backlog without altering the priority of the backlog item. The priority scheme itself should be flexible to allow balancing team’s commitment to set them up for success.

Figure 5: Spira’s Support for Importance Schemes

While backlog should give priority schemes, the backlog should also enable the teams to customize the priority schemes based on their domain. For instance, projects related to construction, manufacturing, and digital waste disposal require about 10 levels of prioritization. The easier the backlog promotes these customizations, the more meaningful the backlog becomes for the various stakeholders that benefit from the product features and the teams that deliver these functionalities.

Facilitates the Definition of Ready

One of the critical elements of engaging stakeholders is to constantly lobby them for support. While transparency promotes visibility to work, it does not confirm accountability. As a result, when the team implements a backlog item, it raises questions from stakeholders. Particularly, in regulated industries where the work item has to be evaluated by compliance team, audit personnel, and medical, legal, and regulatory liaison members, facilitating traceable and auditable discussions through the system of record for gathering clarity as part of the “Definition of Ready” before an item is split into appropriate user stories, prioritized and implemented by the development team makes the backlog an inspiring center of excellence.

Figure 6: Confirming Clarity of Stakeholders validating Definition of Ready

As you can see in Figure 6, product owners or technical architects who are accountable for delivering certain features can continue to consult with the appropriate stakeholders seeking validation of requirements. Such traceability of conversation maintains not only validation of definition of ready but also the increased confidence for the team to ensure that appropriate consult is recorded before they begin to implement the work. After all, the last thing a product backlog should promote is a rework because the proper personnel was not consulted before work was performed.

Incorporates activity breakdown

As part of creating the product increment, one of the iteration planning activities is to create tasks that have to be completed so that the related requirement can be completed. When such tasks are created, the traceability to the requirement should not be lost. When tasks are not related to any of the requirements themselves but still have to be completed within the release or iteration, the backlog should still make such enable a seamless way to track these tasks as well.

Figure 7: Breaking Requirements into Tasks for Team’s Granular Progress Tracking

Promote multiple estimation approaches

The traditional approaches to project delivery use higher-level estimates (analogous or parametric estimates) for higher deliverables and detailed hourly estimates at the individual activity level. Similarly, many agile practitioners recommend that the backlog items follow the affinity estimation for requirements in the backlog and hourly estimates at the individual task level. When tasks and requirements coexist in the backlog, the backlog itself should allow multiple estimation schemes to also coexist.

Figure 8: Support for Points at Backlog Item and Hours for Task level

In the above Figure 8 illustrated here, you can see the requirement at the backlog level is estimated at a point level. However, when the task to implement that work item is started as part of the accepted workflow, the task supports hours for both estimation and progress tracking.

Summary

As you can see from the above illustrations listing down the critical characteristics of a product backlog, it brings various types of stakeholders together by promoting transparency, inspection, and adaptation. The customers do not care whether the teams work in agile or waterfall approaches to deliver the value for them or not! But the customers do care about how frequently the teams deliver quality work as committed. As a result, all internal and external stakeholders benefit from transparency, inspection, and adaptation. A good backlog, therefore, facilitates not only backlog refinement at the product backlog level but also progress to work commitments at the iteration backlog level by demonstrating test coverage and task progress as demonstrated in Figure 9 (for a different project to show the color-coded progress)

Just like all the animals come together to quench their thirst at the waterhole, a good product backlog allows such visibility on test coverage and task progress on committed work as well as the stakeholders’ commitment to the product strategy at the product backlog item for the requirement validation for proper prioritization and delivery.

In the next part of this blog, I will discuss the agile ceremonies and outline how to use the planning board.

Coming Soon to Spira - Multi-Factor Authentication (MFA)

2025-09-16T15:30:03-04:00

What is Multi-Factor Authentication?

Multifactor authentication (MFA) is a security technology that requires multiple authentication methods from independent categories of credentials to verify a user's identity for a login or other transaction. Multifactor authentication combines two or more independent credentials: what the user knows, such as a password; what the user has, such as a security token; and what the user is, by using biometric verification methods.

MFA aims to create a layered defense that makes it more difficult for an unauthorized person to access a target, such as a physical location, computing device, network, or database. If one factor is compromised or broken, the attacker still has at least one or more barriers to breach before successfully breaking into the target.

Our Approach to MFA

Our plan at Inflectra is to provide two independent methods for authenticating users; hence, it is also an example of Two Factor Authentication (2FA). The methods we are using are as follows:

Something You Know—A complex, difficult-to-guess password that is not reused across multiple accounts is the authentication we currently use on our website and in our Spira platform.
Something You Have—We are adding support for Google Authenticator-compatible Time-based One-Time Passwords (TOTP). These six-digit randomly changing number codes can be generated by a hardware device or a software application running on a device that you own, such as a cellphone. This is an example of a "software-based security token application."

Many password managers (for example, 1Password) include Google Authenticator TOTP generation tools as part of their platform. We will refer to this as simply the "authenticator application" in the rest of this article.

Multi-Factor Authentication in Spira

We plan on adding MFA to one of the upcoming releases of SpiraTest, SpiraTeam, and SpiraPlan. We are currently targeting our August 2021 release (v6.11), but it is still in testing as I write, so it might end up in v6.12.

For Spira customers, the option to add MFA will be available for all users using either Spira native authentication (login and password) or LDAP/Active Directory authentication. It will not be available for users using OAuth-based Single-Sign-On (SSO) accounts, as those providers should provide the MFA functionality themselves.

To add MFA to your Spira account, you will need to log into Spira as usual and then click on the 'Add 2-Step Authentication' option on the User Profile page:

Once you have clicked on this link, you will be taken to the screen to configure MFA:

You should scan the QR Code with your authenticator application and save the TOTP generator key inside the application.

To verify that the QR Code was successfully scanned, use the authenticator application to generate a sample 6-digit code, enter it in the box, and click Submit.

Once that has been successfully entered, you will see the legend in your user profile change to look like the following:

You can now log out from Spira. When you next try to log in, you will now be asked for:

Your Spira login
Your Spira password
Your one-time password

If you want to change or remove the MFA information, you can use the 2-Step Authentication Settings link on the User Profile page:

This can be useful when you have to replace your mobile device with a new one (for example). That will require you to generate a new TOTP side for this new device.

Multi-Factor Authentication on our Website

Our company website has already been upgraded with the new MFA functionality for all users.

To add MFA to your Inflectra customer account, simply log into your customer account as normal and then click on the 'Add 2-Step Authentication' option in the sidebar:

Once you have clicked on this link, you will be taken to the screen to configure MFA:

You should scan the QR Code with your authenticator application and save the TOTP generator key inside the application.

To ensure that the QR Code was successfully scanned, use the authenticator application to generate a sample 6-digit code, enter it in the box, and click Submit.

Once that has been successfully entered, you will see the sidebar in your customer portal change to look like the following:

You can now log out from the Inflectra website. When you log in, you will now be asked for:

Your Inflectra login
Your Inflectra password
Your one-time password

If you want to change or remove the MFA information, you can use the 2-Step Authentication Settings link on the Customer Area Page:

This can be useful when you have to replace your mobile device with a new one (for example). That will require you to generate a new TOTP side for this new device.

Spotlight on Spira 6.11 - Diagrams, Drawing and Flowcharts

2022-08-30T16:05:01-04:00

What Kind of Diagrams Can I Create?

The new diagram editor is integrated into the Spira document management system. In addition to the ability to create textual content in Markdown, Rich Text, and BDD Gherkin formats, you can now choose to create three different types of diagrams in Spira:

Generic flowchart diagrams using a variety of shapes
Specialized organization charts, also useful for website sitemaps
Mind-map brainstorming diagrams

To create a new diagram, simply use the new option on the "Add Document" dropdown menu on the document management homepage:

Now you can create one of the three different types of diagrams. We shall discuss each one in turn.

Flowchart Diagrams

The flowchart diagram editor lets you view diagrams directly inside the system using the 'View' tab. You can also choose to export the diagrams as either a PNG graphics file or an Adobe Acrobat PDF document.

The built in editor lets you choose a variety of shapes that you can combine with line connectors to create different types of flowchart or diagram. We have included some samples based on the default artifact workflows in Spira to illustrate its power and flexibility:

This type of diagram is especially useful for business and system flowcharts, data flow diagrams, system architectures and network diagrams.

Organization Charts

When you create a diagram of type 'Organization Chart' the system provides special color-coded organizational unit boxes and hierarchical connectors to make it easy to create tree views, sitemaps, or other hierarchical data really easily:

The editor for organizational charts is a simplified version of the main diagram editor. It automatically color-codes the organizational units based on their depth in the hierarchy and has options for displaying the charts either horizontally or vertically, depending on your preference:

This type of diagram is especially useful for creating personnel organization charts, web information architecture sitemaps, high-level requirements hierarchies, and other diagrams that are hierarchical in nature.

Mind-map Diagrams

The third and final type of diagram is the mind-map. Although Spira already has the ability to display actual requirements as a mind-map, sometimes you are not ready to write down actual requirements, you just want to quickly brainstorm ideas and have it be captured in the system. With this diagram type, you can take the main idea and then decompose it into a set of related ideas that come from the initial idea.

Mind maps are a great way to take a new concept and explore all the possible implications and outcomes related to that idea. Sometimes they can then become formal requirements, but sometimes they just remain a brainstorm for future reference.

The mind-map diagram editor lets you quickly add new idea "bubbles" to a mind map (linked to the parent idea) and the system takes care of automatically color-coding them based on their proximity to the initial, central idea. That way you can focus on brainstorming, vs. manually changing the colors or adding lines.

Features of the Diagram Editor

Depending on the type of diagram you are creating, there are various different features available:

The Shapes Pane

The left-hand side of the editor contains a set of shapes that you can drag into the main diagram editor. This is available for flowchart diagrams, but not for mind maps or organization charts since they have standard boxes/bubbles that are auto-styled based on the hierarchy. Once you have dragged the shapes into the main drawing grid, you can add lines or text to the items.

The Properties Pane

The right-hand side contains the properties pane. This displays the properties associated with the currently selected item. This could be the color, size, and orientation of the shape, as well as the text. When you have nothing selected, it lets you adjust the properties of the main drawing grid itself.

Finally, above the drawing grid is the context menu. When you select a shape, depending on the type of diagram, it will let you add new shapes, add connecting lines, and remove existing shapes.

Future Plans

Let us know if you like the new diagram editing functionality. We are considering adding support for additional content editors, potentially including a lightweight spreadsheet editor.

Implementing Waterfall for Execution and Management Teams in SpiraPlan

2021-07-26T05:00:05-04:00

It is essential therefore that tools we use lend themselves to implementing both waterfall and agile approaches because the total cost of ownership for the company to use the same tool across the organization is low.

Spira family of products support the agile framework with its rich set of features, numerous integrations with existing development and testing tool, and customization options. Yet, a question arises if we can use Spira to implement waterfall initiatives. In this whitepaper, we will discuss the approach to implementing the waterfall initiatives in Spira.

Read the Full Whitepaper - Implementing Waterfall in SpiraPlan

Spotlight on KronoDesk 4.0 - LDAP and ActiveDirectory Integration

2021-07-15T13:34:06-04:00

LDAP and ActiveDirectory Support

Many of our customers choose to use KronoDesk for their in-house company IT help desk / service desk. For these environments it makes a lot of sense to be able to integrate KronoDesk with their in-house user directory for internal users. Therefore we have been working in our upcoming KronoDesk 4.0 release to add LDAP and ActiveDirectory support to KronoDesk based on our existing functionality available in Spira.

With this new functionality, you will be able to mix and match different types of user:

Users that login to KronoDesk using a KronoDesk login and password (same as the current version)
Users that login to KronoDesk using their company network login and password (LDAP managed).

Configuring LDAP in KronoDesk

The new LDAP functionality will be available from within the Administration section, on the Users administration menu:

On this page you will be able to enter the information necessary for connecting to the LDAP or ActiveDirectory server. Once that is correctly entered, you will be able to import users directly into KronoDesk from the LDAP directory:

You can then display a list of users to import into KronoDesk:

Once the users have been imported, they can then login to KronoDesk using the current network login and password:

Of course, non-LDAP users will still be able to login using their KronoDesk login and password.

Use Case Mapping with SpiraTeam and SpiraPlan

2021-07-14T22:50:42-04:00

Use Case Example

In this example, consider the following typical use case template that you might create in Microsoft Word or Excel:

ID	UC0001_Approvals
Name or Goal	Submit a Purchase Requisition
Type	User Goal, Black box, Level 4
Scope	Procurement
Actor	Purchaser
Stakeholder(s)	Purchaser Business Approver
Trigger/ event	Desire to submit a new purchase requisition based on identified need. Received an email from the system identifying an action to submit a new purchase requisition
Preconditions	Purchaser is logged into the system Purchaser is authorized to make new purchase requests Business Approver is configured to receive purchase requests from submitter.
Success conditions	Log user's access within the authentication log
Post conditions (Success guarantees)	Log user's access within the authentication log
Main success scenario	1. Purchaser selects option to submit a new purchase requisition 2. Purchaser chooses a vendor from the approved list 3. Purchaser chooses items from the approved supply catalog 4. Purchaser enters the quantity for each item 5. Purchaser enters in the justification for the purchase 6. Purchaser submits the requisition
Alternative flows	A: The vendor is not on the approved list a1. Purchaser chooses the option to request a new vendor a2. Purchaser enters the justification for using a non-approved vendor B: The item being requested is not in the approved supply catalog b1. Purchaser chooses the option to request a new supply item b2. Purchaser enters the justification for using a non-approved item
Exception flows	C: Purchaser logs out End Use Case
Non-functional requirements	NFR001 To comply with applicable regulation in any geography including for example; Regulation (EU) 2016/679 (General Data Protection Regulation) NFR002 To comply with PCI-DSS 4.0 Standards NFR003 To comply with ISO 27001 NFR004 The time to interact should be on average less than 0.5 seconds, 100% of the time NFR005 To apply multi-factor authentication where required
Dependencies & cross references

You can create a customized requirement type in Spira to capture the key fields in this template. The ID, Name, Type, Scope (Component) and Description fields can be modeled using standard fields. For the other fields, you can use requirement custom properties:

Trigger/Event - Rich Text
Preconditions - Rich Text
Success conditions - Rich Text
Post conditions - Rich Text
Stakeholders - Rich Text

The sample use case would then look like the following:

For the Non-functional requirements and Dependencies and cross-references, you can use the requirement associations tab:

However, what are the different ways we can deal with the three kinds of use case flows:

main
alternative
exceptions?

Option 1: Use Primary and Alternate Flow Custom Properties

The simplest option would be to add three more Rich Text custom properties and then you would just use a single requirement that has all the fields populated and the process flows will be just numbered lists inside the field:

When you use the requirement document view in Spira, you will see:

The main advantage of this approach is that it is quick to setup, and you can easily paste in the flows into the text boxes from the original document.

The disadvantages of this approach are that all of the exception flows are buried in the same text field, and its hard to visualize the flows since they are just a list of numbered steps.

Option 2: Use Child Use Case Requirements

Another option would be to create new child requirements for each of the use cases, and indent them under the main requirement:

The child requirements are of type 'use case' and can use the built in Scenario feature of requirements to actually have the steps be discrete items that can be visualized as a diagram automatically by Spira:

When viewed in the requirements document view it will look like:

The advantage of this method is that you can have an easy to visualize hierarchy of requirements, with the use cases nested under each requirement, and the ability to easily display the use case diagrams. The main disadvantages are that it makes all the requirements Epics and limits how the statuses and workflows can be used because the child requirements drive the workflow of the parent. This method is more work to setup than Option 2, but easier than the next and final option...

Option 3: Use Associated Use Case Requirements

The most flexible and extensible option is to use a separate requirements tree for the main use case requirements and additional trees for the different types of use case flow (main, alternate and exception).

In this approach, the main requirement and its associated scenarios are linked together using the Associations tab rather than being parent... child:

This method is the most flexible, allowing you to associate different scenarios with different requirements and use cases (many to many), but is the most complex to setup.

Webinar Recap: The 4th Industrial Revolution: Industry Trends Post COVID-19

2021-07-07T10:23:12-04:00

The 4th Industrial Revolution & COVID-19: The Theoretical Framework

Every failure teaches a lesson. If we have not learned from that failure, we have paid a huge price and not benefited from the lessons to turn failure into success. The COVID-19 pandemic has globally impacted individuals, businesses, societies, and countries in many ways. Yet, it leaves all of us with one powerful lesson that we should all learn from. This powerful lesson has been at the epicenter of the 4th industrial revolution that focused on cyber-physical systems. In many ways, the 4th industrial revolution has greatly influenced several approaches that we have seen in controlling the pandemic by limiting its spread by lockdowns and regulations but also by experimenting through innovation: telecommuting, telehealth, and vaccine development and trial combined with the acceleration of temporary authorization of vaccines.

So, what are these 4th industrial trends? Many of us have been impacted by these trends already, and some organizations have embraced it in many of their products and support successfully. The use of drones for environment control, increasing use of cloud computing beyond the use of just storing documents, predictive data analysis to come up with new solutions and prescriptive client recommendations, the impact of cybersecurity protocols and the threats emanating from the lack of compliance, and the list is endless as a result of the nine pivotal areas where the 4th industrial revolution has an insurmountable role. The border closing and lockdown initiated in many countries phased approaches to reopening and vaccine development & phased distribution seen in the global pandemic is increasingly possible because of some of the advances made before pandemic due to the 4th industrial revolution.

So, has the pandemic changed the goals of the 4th industrial revolution even slightly? What are the foundational principles to this 4th industrial revolution? What important connection runs through both the 4th industrial revolution and the pandemic lessons learned? Please review the webinar, “Influence of COVID-19 on the fourth industrial revolution trends” from Dr. Sriram Rajagopalan, where he unpacks some of the critical elements of the fourth industrial revolution, global megatrends, and lessons learned from COVID-19, along with a tool to incorporate the lesson learned within an organization.

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the presentation.

4th Industrial Revolution Impact on COVID-19 from Sriram Rajagopalan

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy and get vaccinated!

#teamInflectra

Data Extraction and Reporting In Spira: How The Customization Works

2021-06-28T15:04:52-04:00

(by Dr. Sriram Rajagopalan)

First Things First

Spira provides rich, context-sensitive document help. This help system can be accessed by clicking on the “Documentation” under the user’s profile menu in the top navigation bar (Fig 1). Therefore, readers are advised to seek this help if there is any question on the specific areas of the user interface.

Figure 1: Contextual Help Documentation Location

While modifying existing reports, users are advised to ‘clone’ the report (Fig 2) and work on the clone. This is one of the best practices strongly recommended to avoid any challenges in reverting to the original report.

Figure 2: Cloning Reports as part of the Best Practice

Approach 1: Modifying the Standard Reports

One of the first and easiest reporting needs for customers is to modify the existing standard reports. These requests are removing a few existing data, modify the order in which they appear or change the title of the field, or add additional data elements that are also captured. These apply to both long-form reports or tabular reports. The long-form text-based reports capture a lot of information from multiple artifacts over a period of time. These reports are rendered in HTML, Word, or PDF formats. The tabular reports report data frequently from a set of specific artifacts. These tabular reports are rendered in HTML or Excel format.

To modify the existing standard section of the report, you would need to edit the XSLT section of the specific standard section. You can accomplish this by doing the following steps.

Access the Edit Report from the Administration Menu.
Clone the specific report you want to modify.
Click on the Edit button for the new report.
Click on the “Customize” button of the specific standard section (Fig 3) you want to edit as shown below.

Figure 3: Location of the Standard Section Customization

In the pop-up dialog, edit the “template” section with the changes that you want to see in the report. For instance, let us say that you want to get rid of the columns such as the automation engine, component, and duration on the tests. You will have to delete these relevant columns in the XSLT where the columns are defined as part of the table header (Fig 4) as well as in the logic for the data columns (Fig 5). Shown below is the removal of these columns.

Figure 4: Location of Template showing the three columns to be deleted in the table header (TH tag)

Figure 5: Deleting the corresponding Data Columns (TD Tags) shown in Notepad++

You can use this method to add a new standard section and use one of Spira’s prebuilt datasets (Fig 6).
Save the sections and the report.

Figure 7: List of available Standard Sections

Benefits and Challenges of the Standard Section Modification

The benefit of this approach is that the dataset required for reporting is already prebuilt by Inflectra for you to use any of the data. It is easy to add new columns, remove columns, or even use XSLT programming to add your own customization to the dataset. However, the challenge is that one is to the dataset already pre-built and it requires the knowledge of the XSLT programming language. While working on complex reports with nested loops and additional conditional logic, it is possible to make some logical errors requiring you to spend time addressing these errors introduced.

Approach 2: Using Custom Section

This approach addresses the challenge associated with the earlier approach of a pre-built datasets and prior knowledge of XSLT programming. If one has the power to directly access the dataset and can work through what data is required, then, you can address some of these challenges. One powerful data access language is the Structured Query Language (SQL, pronounced Sequel). The Spira family of products supports the Entity SQL (commonly known as E-SQL) that can be used to directly access the data stored.

To include your own data using E-SQL in the custom section, you would need to develop the E-SQL query first and then create the XSLT transformation required to render the report. You can follow the steps below to develop this custom section.

Access the Edit Report from the Administration Menu
Clone the specific report you want to modify
Click on the Edit button for the new report
Delete standard sections you do not want (some prefer to keep project information)
Click on the “Add New Custom Section” (Fig 8)

NOTE: If you already have a custom section that you want to modify, then, click on the “Edit” button next to that section under the operations column)

Figure 8: Adding a Custom Section

Give a name to the custom section (Fig 9). Updated other areas like description, header, and footer as necessary.

Figure 9: Naming the Custom Section

Select one of the datasets available for you to query as shown. Note that every time you select a dataset, a default query is added to the rich text field called “Query”. Make sure only one query is available in the “Query Window”.

Figure 10: Showing available datasets for a Custom Section

For example, when the “Incidents” query is selected from the drop-down, the Query window will appear as follows (Fig 11). You can click on the “Preview Results” to see the name of the attributes (columns) that describe the dataset (entity). This query means selecting all the attributes from the SpiraTestEntities.R_Incidents where the primary key (project_id) is the id of the project selected in the workspace section.

Figure 11: Showing E-SQL Query for the Incident Query

Now, identify specific fields from this entity that are required to be reported. For example, if only the incident_id, project_id, priority_id, incident_status_id are required, the query will look like the following as shown below. Make sure that the query is written in the “Query” window (Fig 12)

select R.INCIDENT_ID, R.PROJECT_ID, R.PRIORITY_ID, R.INCIDENT_STATUS_ID from SpiraTestEntities.R_Incidents as R where R.PROJECT_ID = ${ProjectId}

Figure 12: Modified E-SQL Query showing specific data of Incident artifact

Click on Preview Results to ensure data looks as you expected
Save the section and report

Benefits and Challenges of the Custom Section

The benefit of this second approach is that you have the power over the dataset required for reporting. Using the power of E-SQL, you can join with multiple datasets, compute new data based on the existing system and data attributes, and build robust queries. However, the challenge is that one needs to be somewhat knowledgeable about the E-SQL syntax and spend time on the database schema surrounding the Spira-specific datasets. Those that are familiar with the E-SQL can find this alternative attractive with the limitation that SQL is a set-specific language amenable more to the tabular type of reporting rather than the long-form reporting.

Approach 3: OData Access

While these two approaches solve the majority of the reporting requirements, Inflectra also makes available a third approach to address some of the challenges with the E-SQL knowledge requirements of the custom section approach. This approach requires the use of the higher edition of SpiraPlan and is not available in the SpiraTest and SpiraTeam editions. In this third approach, data is accessed directly through Microsoft Excel using the Open Data Protocol, called OData.

By connecting Microsoft Excel with the OData services exposed by SpiraPlan, data available from Spira can be queried directly from Microsoft Excel using Power Query editor. Inflectra’s blog article on OData access provides a detailed overview of how to establish the connection and perform simple and complicated queries using the OData services. Please review this blog article for more details.

Summary

The request for reporting services is a continuously growing need. While Inflectra recognizes this need and provides numerous customer-friendly out-of-the-box reports, Inflectra also recognizes the need for customizing reports. To support customers to develop these reports themselves, Inflectra makes several options, such as reporting through XSLT modifications, custom E-SQL, and OData services. Inflectra’s support center also provides a lot of articles on these custom reporting needs to extend continuous support.

Webinar Recap: Rapise 7 - What's Covered in the New Release

2021-06-29T14:53:05-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share these slides from the presentation.

Rapise 7.0 Is Here from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

Spotlight on Rapise 7.0 - New Flaky Testing Support

2021-06-25T17:17:00-04:00

Flaky Tests

If you find yourself in a situation that some of your tests pass or fail randomly then you have the curse of the "Flaky Test".

In Rapise 7.0 we have introduce a new feature that allows Rapise and Spira to work together to avoid this curse. In the new Rapise 7.0 Spira Dashboard, there is now a way to mark it as Flaky. Simply find it in Test Cases View and use the Actions menu to set the flag. Flaky test cases are indicated with a special icon (red flag):

When a test case marked as Flaky is executed by RapiseLauncher - its test run is marked as Flaky too.

Note

The Flaky flag makes it easier to distinguish between random and important test run failures.

Automatic Rerun

To instruct RapiseLauncher to rerun a failed test case use the Max rerun attempts test set custom property. If a test case keeps failing it will be additionally executed a specified number of times (by default it is zero). To stop rerunning tests if many of them finally failed use the Do not rerun if N tests failed property. By default this property is zero and it means rerun all the tests in a test set if Max rerun attempts is set.

Test runs that correspond to reruns are also decorated with special icons. The number in the circle designates the rerun attempt:

We hope you enjoy the new Flaky Test / Rerun features in Rapise 7.0, hopefully they should ease the curse of the dreaded flaky test!

#TestBowl 2.0 - It's A Wrap, Folks

2021-06-29T10:38:08-04:00

What went down?

Oh, it was a lot of fun, as Inflectra's TestBowl events usually are!

There were:

over 50 participants - all excellent testers and QA/QC professionals
over a dozen teams
stupendous DJ and funky music
awesome test management tool to report bugs - SpiraTest
fantastic platform to test - RedRex
knowledgeable and fair judges
amazing support teams for SpiraTest and RedRex
lots of fun!

Here are some of the testers hacking away at the app under test.

Here are our fabulous judges:

SpiraTest was awesome with its leaderboard functionality, helping keep contestants apprised of their progress.

The winners were all around, but the top three were: Team Amber - 1st place, Team Gold - 2nd Place, and Team Wine - 3rd Place!

The scores were distributed across all team like so:

After 1.5 hours of testing, 450 bugs were reported by all teams. Not all bugs were unique, of course!

Congratulations to the winning teams!

1st Prize - Team Amber - Madhura Bapat & Neha Chopra

2nd Prize - Team Gold - Egli Isufaj & Ayesha Yussouff

3rd Prize - Team Wine - Vlado Oravec & Strahinja Kokano

The top three teams won, Apple TVs, Apple Airpods, and amazon echos, and all participants will receive certificates.

What we tested?

We all had the privilege to test a fascinating new app that creates virtual buildings/offices (also for teleconferencing and communication) with AI capabilities built into it. The platform is called RedRex!

Why do I see Jennifer Bonine in this screenshot, you ask? Oh, because she is behind RedRex!

Jenn (and her Team at RedRex ) joined TestBolw 2.0 to chat about her new venture, Redrex's features, areas to test, and ambitious and immediate plans for hosting events on social justice on this platform. We wish Jenn and the team the best of luck!

Oh and for the fun part - here are Adam and Thea.... dancing? Maybe.

What comes next?

We are all tired of virtual events, but I would argue that TestBowl is actually best when done virtually! So if you missed our last two competitions, we are pre-announcing our #TestBowl Christmas 2021 Edition for December 2021. The details will need to be worked out, but here is a sign-up link.

We hope to see you there!

Spotlight on Rapise 7.0 - New Spira Dashboard

2021-06-25T16:29:32-04:00

Understanding the New Spira Dashboard

Before we look at the new Spira Dashboard and how it works, first lets take a trip back in time to the original Spira Dashboard:

The original dashboard let you connect Rapise to Spira and display a list of the test cases and test sets in the current project that were either assigned to the current user or were assigned to the automation host that Rapise was running on. However, it was a bit cumbersome to use and had lots of separate boxes and sections. In addition, it used the older Spira SOAP API and was relatively slow to navigate and display content. With those limitations in mind, with the launch of Rapise 7.0 we now have a completely new Spira dashboard:

The new Spira Dashboard has a completely new user interface and style that more closely mirrors the 6.x version of Spira.

The new Spira Dashboard has a fast, easy to use navigation bar that lets you change Spira product as well as access the different parts of the dashboard in one click.

The dashboard contains top level menu to switch between views and a dropdown to switch between products/projects. There is also a button to refresh data and search field to filter data in the current view. Filtering is applied to a column with orange caption (usually Name).

Data Tables

In many cases first column of a data table contains ID of an item in Spira. You may click an ID to open the corresponding item in a browser window.

Each data table has a menu opener (hamburger) located in the top right corner. The menu contains some predefined filters and also allows you to display the filter row and choose which columns to show. Clicking a column caption turns on sorting.

Hierarchical Tables

The Plus icon in a table row means that it can be expanded. Click the icon to reveal the row details. It may contain more data tables.

Tree View

Test cases and test sets may be placed into folders in Spira. The dashboard will load and display the folder hierarchy. To navigate it click on the folder icons.

Actions

Some tables include an Action column. It allows the user to perform certain actions on an item displayed in the row when the Action menu is expanded.

Specific Dashboard Features

Here is the list of tasks you may accomplish with the new Spira Dashboard:

Connect To Spira

If you did not connect Rapise to Spira yet, you will be prompted to enter the connection info.

Assign Automation Host Token

If you did not assign an automation host token to the machine where Rapise is running you may do it in Automation Hosts view. You may even create a new host there.

Dashboard View

Browse Framework Tests

The dashboard view shows tests included in the currently opened test framework (parent test and it's sub-tests).

View Test Runs in Progress

View test runs that are in progress right now.

View Pending Test Runs for This Host

View tests that are scheduled to run on the local host for the next 24 hours.

Setup Custom Properties

Some features of the dashboard require aditional custom properties to exist in Test Cases, Test Sets and Test Runs. Click Create Custom Properties for Rapise button to add the following custom properties in the selected project:

Test Cases
- Flaky (boolean, default is false)
Test Runs
- Flaky (boolean, default is false)
- Run attempt (integer, default is 1)
Test Sets
- Max rerun attempts (integer, default is 0)
- Do not rerun if N tests failed (integer, default is 0)
- Record videos (boolean, default is false)
- Verbose level (integer, default is 1)
- GitUrl, GitUser, GitPassword (string, empty by default)

Clicking the button more than once is safe. If a custom property exists - Rapise won't create a duplicate. To create the custom properties you will need to enter administrator credentials (user name and API Key).

Perform Test Actions

Action menu for a test allows to

Open the test in Rapise
Link the test to a test case in Spira

Pending Test Runs View

This view displays scheduled test runs that must be executed within next 24 hours.

Test Cases View

Browse Test Cases

In the test cases view one may see the tree of test cases for a project, discover when a test case was last executed and status of execution.

View Test Case Details

Expanding a test case reveals last 10 runs of it. The details pane also shows test case parameters and custom properties (editable).

Perform Test Case Actions

Action menu for a test case allows to

Immediately Execute the test case on the local host.
Execute the test case on a selected Automation Host. It will run as soon as RapiseLauncher on that host is ready.
Mark the test case as Flaky or remove the flag.
Add default parameters to the test case. The list of default parameters includes:
- g_verboseLevel = 1
- g_enableVideoRecording = false

Note

For execution of a test case on a selected automation host (#2) - Rapise will use a special test set with the name of the automation host.

Create New Test Case

If you want to create a test case in a specific folder - select corresponding row in the table, otherwise the test case will be created in the root folder. Click the New Test Case button at the bottom of the view and provide necessary details in the opened modal dialog.

Test Sets View

Browse Test Sets

In the test sets view one may see the tree of test sets for a project, discover when a test set was last executed and status of execution.

View Test Set Details

Expanding a test set reveals the list of included test cases. The details pane also shows test set parameters and custom properties (editable).

Add Test Cases

Press Add Test Cases to open the test cases tree, select test cases and append them to the test set.

Reorder Test Cases

Using hamburger icon next to a test case ID one may reorder test cases in a test set.

Perform Test Set Actions

Action menu for a test set allows to

Immediately Execute the test set on the local host.
Execute the test set on a selected Automation Host. It will run as soon as RapiseLauncher on that host is ready.
Rerun just failed test cases on a selected Automation Host.

Note

For execution of a test set on a selected automation host (#2,#3) Rapise will use a special test set with the name of the automation host.

Create New Test Set

If you want to create a test set in a specific folder - select corresponding row in the table, otherwise the test set will be created in the root folder. Click the New Test Set button at the bottom of the view and provide necessary details in the opened modal dialog.

Test Runs View

Browse Test Runs

This view shows most recent test run reports. One may see test run status and execution time and duration. If a test run is failed - Details column displays the first error message.

View Test Run Details

Expanding a test run reveals the report with execution status for every test step. The details pane also contains links to download test run attachments and execution log.

Incidents View

This view displays last 500 incidents and allows to create new ones.

Crowd-Test Your App or Website at #TestBowl 2.0

2021-06-03T15:02:13-04:00

Why Submit Your Software to #TestBowl?

Get real-life testing by a group of experienced testers (up to 2 hours of testing)
Get testing results in the form of a bug report, and/or a test report
Network with expert testers
Get exposure for your app/software among the dynamic and diverse group of professionals from all over the USA and beyond.
Get Inflectra’s test management tool license for a year (SpiraTest / cloud subscription with the test results from the competition preloaded)

Who Is Eligible?

You are welcome to send us your app/software if you can:

Work with #TestBowl organizers to prepare the app/software/website for the competition
Demo the app/software at the event to acquaint the participants with its main functionalities.
Extra points if you stay during the event to answer additional questions from testers.

What Sorts Of Apps/Software/Website Are We Looking To Test?

For the best result, your app/software should be:

in beta testing
if mobile, be available for download from both Apple iOS and Google Play marketplaces
if web, be accessible via a public URL
feature-rich
free to download/use (for participating testers, at least)

Submit your app information here!

About #TestBowl 2.0 Organizers

#TestBowl is organized by Inflectra – a DC-based software company that makes SpiraTest. SpiraTest is a QA powerhouse and the official test management tool of #TestBowl.

The Perils of Agile Estimation (Part 2)

2021-06-07T13:13:18-04:00

Is The Task Complex or Complicated?

Many people conflate complexity with complicated-ness or difficulty. In everyday life, we use the terms complex and complicated interchangeably. However, when we talk about estimation, we need to distinguish between the two. A clear understanding of these two concepts and their implications is crucial for providing ROC-ing estimates.

Understanding Complexity

A complex system is one whose components interact in multiple ways and follow local rules, meaning there is no adequate generic definition of all its possible interactions. In other words, it's a system where, as it expands and more separate parts are added to it, its internal interactions increase exponentially, even to the point where its behavior cannot be modeled or predicted. Any task that requires interaction between different parts of a computer system will have a degree of complexity. A task that simply defines the display of some data on a web page will typically orchestrate interactions between a database, some application-layer component, and the browser, giving it a small but well-defined degree of complexity.

Complexity creates uncertainty. A complex task or system is, by definition, unpredictable to a certain degree. The other parent of uncertainty is ignorance. Sometimes we lack the information to assess the complexity or implications of a task. When we undertake a task that involves uncertainty, we are dealing with risk. Risk occurs when we know all possible outcomes with a certain probability for each but also when we don’t know all the possible outcomes. So complex tasks are inherently risky. Consider the previous example of the task that simply defines the display of some data on a web page. We know that the most likely outcome is that the data will be displayed as intended. We also know that there is a very small chance that a database or browser error will prevent the data from being properly displayed. The small complexity of the task creates a small but present risk.

Identifying and quantifying risk is critical when estimating. We’ll talk more about markers for identifying risk later on in this post series.

Understanding Complicated Tasks

Difficult is an adjective often used as a synonym of 'complicated.' A complicated system may or may not have multiple interacting parts, so it may or may not be complex. A complicated system involves convoluted or intricate steps that are difficult to understand or execute. Once these steps are understood, then the system becomes entirely predictable.

Difficulty implies effort. It takes time and brainpower to untangle the convoluted instructions needed to run a task or to analyze the workings of an intricate problem. But once we do put that effort in, we can minimize uncertainty and have confidence in the expected system behavior.

Consider, for instance, the Smith-Waterman algorithm. It’s a complicated algorithm that takes a lot of effort to understand and implement. However, it is not a complex algorithm. It operates on a single set of data and consists of only 4 steps. There are very few variables in it. But trying to understand the rules on which these variables operate and how the scoring, substitutions, and tracebacks are applied is no simple feat (I’m speaking from experience). There are so many subtle details one has to comprehend and so many decision points in the workflow that it can take many days to get it right. Yet, it’s a relatively simple algorithm. Once the rules and workflow are understood, we can easily and confidently predict the system’s behavior, given some initial conditions. The same cannot be said of a truly complex system.

The following diagram illustrates the implications of complexity and complicatedness

Most tasks we’ll encounter during software development will have a degree of both complexity and difficulty. Complex tasks will comprise many internal interactions, some of which will involve some complicated steps or workflows. To give realistic estimates of such tasks, we need to distinctly identify and assess how complex and how complicated they are. We can do so by estimating in 2D.

2D Estimates

So, now that we understand that complexity and difficulty are not the same, we can start looking at tasks differently when it comes to estimating them. Traditionally we estimate tasks on a linear scale. We give a task a single value, usually a story-point value, based on the task’s perceived difficulty or complexity or effort (there is no consensus or clear guidance on what a story-point represents). Let’s stop doing that. There is no scalar value that can capture the effort and risk associated with a task. As we’ve already discussed in the previous sections, the complexity of a task is associated with risk, while its difficulty or complicated-ness is related to effort. So let’s start estimating on a plane instead of a line. The following diagram illustrates the concept:

Each task we estimate is placed on the estimation plane according to both - its estimated complexity and complicated-ness (difficulty). High-difficulty tasks will be placed more towards the right side of the plane, while high-complexity ones will be placed towards the top side of the plane. We can observe that Task 3, for instance, is more difficult than Task 4 and will require more effort or time. Task 4, on the other hand, is more complex than Task 3 and involves greater risk.

The baseline task at the bottom-left part of the plane is the simplest and easiest task applicable within our domain and application. Baselining is very important in establishing objectivity and consistency in our estimates. Let’s discuss this a bit further.

Baselining

Most of the time, the baseline will be a ‘hello word!’ type of task. The baseline task serves as the sounding line for our estimates. There are three rules about the baseline:

No other task should be estimated at fewer points than the baseline task.
All other tasks must be estimated in relation to the baseline task.
You do not talk about the baseline. (Nah, just kidding!)

Fight-club references aside, a baseline task is like a unit of account, a bit like the US dollar, British pound, or Japanese Yen in the financial world: just like we can value assets in multiples of dollars or pounds, so we can estimate tasks in multiples of our baseline. We could, for example, say that a task is twice as complex and five times as complicated as our baseline. Just like the dollar, the baseline helps establish objectivity. Most people in the world know the value of the dollar and can value things in relation to it; everyone knows what you can or cannot buy with x amount of dollars. Similarly, all people in our team will know what the baseline task represents and will be able to estimate other tasks in relation to it.

Baselining can also help with providing consistency to our estimation. We need to adjust our baseline according to our team’s environmental factors. This is achieved by assessing several environmental factors that affect the team:

Domain experience: is the team experienced with the domain they’re working in? In some domains, like certain finance sectors, for example, a lack of domain knowledge can lead to mistakes and defects. If domain experience is totally lacking in your team, move the baseline task two points up the vertical (risk) axis. If domain experience is partially lacking, move the baseline task one point up the vertical axis.
Technology experience: Have the team members worked with the selected technologies before? If not, then expect a steep learning curve which will affect productivity and cause mistakes and bugs. If there’s a technological knowledge gap in the team, move the baseline one point in both the vertical (risk) and horizontal (effort) axis.
Team spirit: is the team harmonious and cohesive? Do the team members work well together? Are there new members in the team? Has there been any friction or clashes? Cohesive teams are productive teams. Unless the team is fully harmonious and everyone works well together, move the baseline one or two points along the horizontal axis.
Morale: is the team enthusiastic about the project and the technology? Has the company been making redundancies or applying unpopular policies? Low morale almost always correlates to low productivity. Move the baseline one point along the horizontal axis if morale isn’t great.

The following diagram shows an adjusted baseline after considering our team’s environmental factors:

In this diagram, we have assessed our team’s morale, spirit, their domain and technological skills and experience. We agreed that the team is not very experienced in the domain we are working in. This increases risk, so we moved the baseline one-up the vertical axis. We also have some new team members, so we moved the baseline one point on the horizontal axis, as it will require more team effort to onboard the new members and bring them up to speed. Our baseline is now at the (2,2) coordinates. Note how all the other tasks have been moved proportionately. The same environmental factors that affect our baseline will equally affect all other tasks too.

Adjusting the baseline according to environmental factors allows us to estimate collectively by taking into account factors that affect our whole team and not just providing our personal subjective estimate on the task. If we have to re-estimate the task sometime in the future, we will adjust the baseline according to the current environmental factors, thus ensuring our estimates are more consistent and more objective.

TL/DR;

In this post, we discussed the concepts of complexity and complicated-ness or difficulty and their implication for our estimation. We then introduced the 2D estimation method and examined the notion of adjusted baselines and environmental factors to help increase our estimation’s consistency and objectivity.

In the next and final post in our estimation series, we’ll delve more into 2D estimation and discuss how to identify and quantify risk in our tasks, among other things. Stay tuned!

Fred Heath is a software jack of all trades, living in Wales, UK. He is the author of Managing Software Requirements the Agile Way, available for purchase on Amazon.

Spira v.6 Getting Started Videos Are Here!

2021-06-04T16:14:17-04:00

Spira Cross-Cutting Features:

Getting Started With Spira v.6 | Global Navigation

An introduction to system navigation for all tools in the Spira family of products: SpiraTest, SpiraTeam, and SpiraPlan.

Getting Started With Spira v.6 | User Creation

A walk through the steps of creating a new user in the system.

Getting Started With SpiraTest v.6 | Planning Releases

A demonstration of how to plan releases in Spira.

Getting Started With SpiraTest v.6 | User Profile Options

Highlights of the different options for choosing the user profile in Spira.

Getting Started With Spira v.6 | Product Creation

A sequence of steps to create your first project in any of the tools of the Spira family.

Getting Started Getting Started With Spira v.6 | Working With Requirements

A demonstration of how you can create and set up your requirements in Spira.

Getting Started With Spira v.6 | Release Creation

An overview of how you can create and set up your releases in Spira.

Getting Started With Spira v.6 | Working With Test Cases

A walk-through of how you can create and refine test cases and how to add them to requirements and releases.

Getting Started With With Spira v.6 | Test Sets

A series of steps on how you can create test sets, package multiple Test Cases together, and schedule them for execution.

Getting Started With Spira v.6 | Test Execution and Logging Incidents

An overview of test execution and its various options, and Logging incidents during execution, and finding the test run results in the system.

Getting Started With Spira v.6 | Incident triage

A walk-through of the Incident views, options for creating new Incidents, and Incident workflow from New to Closed.

Getting Started With SpiraTest v.6 | Reporting Functionality

A demonstration of how to find real-time product/program data on SpiraTest dashboards, built-in reporting engine for custom reporting, including customizable graphs and detailed, printable reports.

SpiraTeam and SpiraPlan Only Features

Getting Started With Spira v.6 | Managing Tasks

A demonstration of how to assign Tasks, working on the Tasks, logging time, and completing Tasks.

Getting Started with SpiraTeam v.6 | Baselining

A quick demo of the baselining feature in SpiraTeam and SpiraPlan.

Getting Started with Spira v6 | Risk Management
An overview of the risk management module in SpiraPlan.

Getting Started with SpiraTeam v.6 | Advanced Reporting

A more in-depth look into filtering data, dashboard views, reporting widgets per user role, planning views, customizable graphing widgets, and pre-built text reports.

Spira Academy is Coming Soon!

Spira Academy is a training and certification program for users of Inflectra’s software platforms. It aspires, among other things, to help the Spira users develop new skills, advance their professional careers and succeed in delivering high-quality software as Spira experts. More to come, so stay tuned!

Webinar Recap: Mobile Testing in a Device Cloud with Rapise

2021-05-24T15:25:41-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share with you these webinar slides from the presentation.

Mobile Testing in a Device Cloud with Rapise from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

Spotlight on Spira 6.10 - Agile Planning Board Enhancements

2021-05-18T22:23:20-04:00

Inline Editing

In the previous version of the agile planning boards, you could view and add requirement, incident and task cards to the various boards in the system, but when you clicked on an item, it would always navigate you to the page for that item. This meant that editing the name, description or other fields of an item on the board was not as quick and easy as we would like.

With the planned enhancements in v6.10, you will be able to click on a requirement card in the planning board and be able to edit all the fields inline without changing page:

You will be able to edit any of the available fields, with the workflow rules enforced so that the appropriate fields are hidden, disabled or required, depending on the status the item is in:

In addition to editing the various fields, this new version will let you also quickly and easily add comments to the appropriate requirement, incident or task:

The new inline editing functionality is available for the Scrum task board, so that you can edit the tasks inline as well as add comments:

Similarly, for maintenance activities, the incident board will let you edit the various incidents inline, following the appropriate workflow rules and field configurations:

In all of the new agile board views, you still have the option of navigating to the full requirement, incident or task details page, by clicking on the 'edit full screen' item in the title bar:

Enhanced Tooltips & Card Display

In addition to the new inline editing capability, we have also improved the card display to include the initials of the user if an avatar has not been configured, and the tooltips now display additional, useful information such as the type, status, and path information:

Other Enhancements

In addition to these key enhancements, we have also made the following improvements:

The drag and dropping of cards has been made more accurate and consistent
The expanding and collapsing of cards (using the Expand/Collapse All) has been updated to improve performance
You can now print the boards using the standard web browser Print option, which renders the board in an easy to print style
You can now directly create requirements, task and incident cards directly into the different statuses in the Kanban view

Future Plans

This is only the beginning. We are planning several major updates to the planning boards in subsequent releases this year, including:

The ability to have the horizontal and vertical swim lanes available at the same time (e.g. have user stories ranked by epic against status)
More display and filtering options so that you can filter out unnecessary types of requirement, task, and incident
Support for grouping / viewing cards by teams and tracks as well as release, sprint, status and user
The ability to save the current filters, sorts, group by and display mode as a saved, shareable view

Webinar Recap: Spira v6.9 - OData, Baselining and Requirements Management

2021-05-13T09:02:05-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share with you these webinar slides from the presentation.

Spira 6.9 - Requirements Document Views, Odata, Baselining and Custom Properties from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

Financial Systems Are In Fact Mission Critical!

2025-03-23T14:44:06-04:00

What Are Mission Critical Systems?

The textbook definition of a mission critical system is as follows:

A mission critical system is a system that is essential to the survival of a business or organization. When a mission critical system fails or is interrupted, business operations are significantly impacted.

However, in software development, when we talk about mission critical systems, we often think about systems that are either real-time (such as flight-control and process control systems) or are used in industries where failure can mean the difference between life and death (e.g., patient health records, clinical systems, etc.), however, in reality, the definition is much broader in nature. During the past year, we've all been working from home and relying on platforms such as Amazon, DoorDash, so perhaps in the future, we'll consider those to be mission critical as well!

What About Financial Systems?

When the discussion turns to financial systems, the term "business systems" is often used to distinguish such systems from "mission critical systems," the thesis is that if a mission critical system fails, lives are lost, and if a business system fails, it is not as important. This difference in approach is fundamental in how the different systems are built and tested. We tolerate failures and unreliability in business systems that we'd never allow in an air-traffic-control system or hospital system. With many business systems, the assumption is that the failure can be tolerated for a "short time" and that it is cheaper to pay the customer or regulator compensation if an SLA is breached rather than factor in the cost to prevent it in the first place.

Although that approach is very common when people talk about business systems as being somehow less important than real-time systems, I am reminded of the following scene from the movie Too Big to Fail:

In the movie, the characters realize that the failure of certain banks and other interconnected entities in the financial system would have catastrophic effects on the world economy and society as a whole. When banks cannot function, people don't get paid, businesses cannot operate, and society can collapse just as quickly as if a system at an electrical utility were to fail.

Now in most cases, the failure of financial systems will not result in a collapse of society or a worldwide financial panic, but even localized system failures can have catastrophic consequences for those directly involved.

Some Real-World Examples

Migration of TSB Bank Customers to New Platform

The background to this failure was the fact that during the 2008 financial crisis, several large UK banks were hurriedly merged together. Once the crisis has receded, the banks were forced to be de-merged to reduce system risk. However, this resulted in two now separate banks - TSB and Lloyds NatWest - using the same IT platform that was controlled by Lloyds NatWest. When TSB was sold to another bank - Banco Sabadell, the new group decided to migrate the TSB customers to the Proteo platform that was owned by Banco Sabadell. However, the migration was not implemented successfully, and many customers could not access their accounts for days, companies could not pay their staff, and many people lost their life savings when other customers could improperly access their accounts. Beyond just the financial impact (which was severe), people had weddings canceled, lost houses they were trying to purchase.

Knight Capital Group Glitch

Ranking as perhaps the costliest computer “whoops” ever, the massive financial losses spawned by a programming glitch by Knight Capital Group cost the firm $440 million and left it on the brink of bankruptcy.

Knight Group’s computers were supposed to roll out multiple automatic orders over several days. Instead, the computers signaled their programs to make all the changes in one day, resulting in a massive amount of shares being bought and sold immediately. Specifically, 150 stocks listed on the New York Stock Exchange were traded at the speed of sound. The computer error resulted in the company nearly going out of business. As it was, over 5% of their staff were laid off as part of the firm’s subsequent reorganization.

The UK Post Office Horizon Scandal

Horizon was a computer system introduced into the UK Post Office network in 1999. The system was used for tasks such as managing transactions, accounting, and inventory management (effectively a specialized ERP system for post offices). Sub-postmasters complained about bugs in the system after it reported shortfalls, some of which amounted to many thousands of pounds. Some sub-postmasters attempted to plug the gap with their own money, even remortgaging their homes in an (often fruitless) attempt to correct an error. Despite these complaints and reported bugs, the Post Office prosecuted over 700 sub-postmasters - an average of one per week - based on information generated by Horizon, without any external corroboration. Some went to prison following convictions for false accounting and theft, many were financially ruined and have described being shunned by their communities. Some have since died. After 20 years, campaigners won a legal battle to have their cases reconsidered after claiming that the computer system was flawed.

Black Monday of 1987

This devastating date marked the end of the golden eighties decade in America, the stock market plunge has been linked to poor programming planning. In the midst of giant tumbles in market numbers, computers, which had been programmed to protect against compounded losses, went haywire trying to insure their portfolios. Once stocks began to plummet, programs felt the loss and signaled further sale of stocks, resulting in a positive feedback loop. The stocks being sold caused other programs to offset losses and sell into the declining market at high speed. The market crash cost some investors millions of dollars and led to outrage, sometimes culminating in shooting rampages and the death of some stockbrokers who were thought to be responsible for losses, according to stock-market-crash.net.

So we can conclude from these examples that failures in financial IT systems can be every bit as catastrophic as failures in a real-time system. Yet, the processes and oversight used in financial IT programs are, in many cases, not fit for purpose. If we consider the approaches used in high-assurance industries and apply them to projects in the financial sector, maybe we can avoid some of these problems.

Lessons from High-Assurance Industries

When you develop software or systems in the Life Sciences, you don't have the freedom to define the requirements, build the system, test it and release it without any oversight. In such regulated systems, you have to meet the requirements of the 21 CFR Part 11, this means:

Requirements have to be defined and signed by multiple approvers
Tests have to be designed and signed by multiple approvers
All systems being used for development and testing have to be independently tested
Security standards and processes must match the minimums specified in the regulations
Testing needs to be done independently, with the evidence presented and independently reviewed prior to release
External regulators have a say in whether the system can go live or not after reviewing the evidence

In many other high assurance industries such as aerospace or automotive, you have specific quality and safety standards that need to be met (e.g., ISO 26262, DO-178C):

Requirements have to be defined and independently approved prior to development
Traceability needs to be documented between requirements, code changes, tests performed, defects found, and fixes made
Auditability of all project documentation needs to be available with all changes verifiable
Risk assessments and risk management needs to be performed as part of the approach

So we can apply these approaches to developing IT systems in finance, banking, and insurance.

What Does This Mean?

The key is to be able to deliver modern, secure IT systems to customers, partners, and internal users in a way that you get the benefits of an agile approach (early user feedback, deliver increments of functionality on time, ability to quickly adapt to industry changes such as mobile payments, blockchain, etc.) while at the same time being compliant with the various rules (FATCA, SarBox, Patriot Act, GDPR, SDFR) and avoiding catastrophic failure.

Banks, insurance companies, stock exchanges, regulators, and other parties embarking on large, mission critical financial services projects need to design their DevOps toolchain with this in mind. Here are some key take-aways:

Treat financial systems as if they were mission critical / safety critical systems. They really are!
Understand the audit and compliance rules and make sure your agile / DevOps tools can generate that data for you. If not, change your systems before the project!
Document all your quality standards and processes and have an internal SOC 2 audit to ensure your compliance before you start development work.
Use automated testing and validation as much as possible, make sure the results tie back to your requirements, and documented risks.
Integrate functional, load, security, etc. testing tools into your DevOps toolchain
1. Have integrated real-time reporting and traceability back to mandatory requirements
2. Not enough that build failed need to know which requirements were impacted by the failure.
Include risk management and risk techniques into your agile process.

Spotlight on Spira 6.9 - OData Reporting API

2021-04-22T17:23:22-04:00

Introduction

OData is an open protocol that lets you easily query data, over the web. Exclusive to SpiraPlan (6.9+), with OData you can directly query the raw data in your database in a secure and safe way. Whenever you use OData in SpiraPlan you are communicating through a secure intermediary (the application itself) to get data from read-only reporting views. Tools like Excel, PowerBI, Tableau support OData and can therefore communicate with SpiraPlan to access this data with just a few clicks.

With OData you don't need to be a SQL expert to generate rich and dynamic insights into your data. If you can fiddle with a spreadsheet, you can stich tables of data from SpiraPlan ("joins" in database language) to get just the data you need. What sort of insights can you get with OData and SpiraPlan reporting views? Here are some examples:

a pie chart of how many users are members of each of SpiraPlan's products
a list of how long ago each open task was assigned to the current owner
get the most recent test run for each test case against each requirement assigned to a sprint
the top 5 most closed then reopened bugs in a product (or program)

Connecting Excel to SpiraPlan using OData

In this article we will be using Excel to illustrate how you can use OData, but in reality you can use any reporting tool that supports OData, for example Microsoft PowerBI.

Excel comes with a built-in Power Query tool that can connect to OData APIs such as SpiraPlan 6.9:

Once Excel connects to SpiraPln you see a popup "Navigator" where you can see all the different data views you can access ("query"). There is a lot here and a lot to explore. You can access pretty much all the information in your application, across all its products and templates, from these views:

To see all the data you have two options:

Load: this loads the whole view, with all records, into a new Excel sheet in the current workbook
Transform Data: this puts the data into Excel's Power Query so that you can manipulate the data that Spira sends to Excel

If you choose the option to load the data, you will see the following:

With this approach, you can connect Excel and Spira together using OData and view data from Spira live in Excel.

Transforming & Querying Data using OData

In addition to loading entire views, the OData protocol allows dynamic querying of the live data source:

In this example, we might have two different queries that are completely independent from each other. If we want to connect them together, we can use OData's query capabilities. For example, imagine for each incident that we want to get extra information about its status. The main query is Incidents, and the secondary query is IncidentStatuses. With OData we can join these together to get a merged set of data:

In addition to this simple example you can use OData to perform common query needs:

Joining different views/tables of data together
Grouping and aggregating data
Sorting and filtering data

The OData query API allows you to do anything with the data you want. For instance, you can turn the data results into a pivot table to tell you how many open bugs and enhancements there are, in total, in each portfolio. The power of OData and the ease with which you can interrogate your data and draw out insights from it makes the new API a game-changer when it comes to enterprise reporting with SpiraPlan. You can create much more complex data that we have illustrated here, or use more complex reporting tools to create live data dashboards that let you extend SpiraPlan with customized queries that make sense to your organization.

How Do I Access the OData API?

If you like what you have seen here then the next step will be to upgrade to SpiraPlan 6.9 (once it's released in May 2021) and then follow the steps in the detailed OData tutorial that we will be publishing in SpiraDocs.

If you are running SpiraTest or SpiraTeam, then you will need to upgrade to SpiraPlan to access this functionality, since it's only available in the SpiraPlan edition of our Spira platform.

Recap: KronoDesk - On-Premise Help Desk Solution for Regulated Industries

2021-04-22T19:48:52-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share with you these webinar slides from the presentation.

KronoDesk - On-Premise Help Desk Solution for Regulated Industries from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

Recap: Behavior-Driven Testing with Rapise and Cucumber JS

2021-04-20T17:19:38-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share with you these webinar slides from the presentation.

Behavior-Driven Testing with Rapise and Cucumber JS from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

Webinar Recap: Modern Alternatives to Micro Focus Toolset

2021-04-15T09:55:53-04:00

Webinar Recording:

We have recorded the webinar for your viewing convenience.

Webinar Presentation:

Also, we are happy to share with you these webinar slides from the presentation.

Modern Alternatives to Micro Focus Toolset - 2021 Edition from Inflectra

Please feel free to get in touch with our team if you have any questions.

See you at our next webinar, but in the meantime, stay healthy, and get vaccinated!

#teamInflectra

Spotlight on Spira 6.9 - Requirements Management Document View

2021-04-15T10:20:55-04:00

Requirements Document View

When we released Spira v6.2 back in August 2019, we added a new requirements document view. This view was added based on feedback from BA teams that liked using Spira but wanted a view that let them see the requirements' content written out in full, vs. having to view a grid of items and read the descriptions one by one through tooltips. This new view has been very popular since its inception, but it had several limitations:

It was only a read-only view, you had to click on individual items to make changes or edits.
Only the main Description rich text field was displayed, even if you had added other rich text custom properties.
You could not display different fields, e.g., test coverage, task progress, only a fixed set could be viewed.
There was no way to display requirements outline numbering.

Well, the good news is that we've heard your feedback, and Spira v6.9 addresses these issues in its new revamped requirements document view:

Easy Sidebar Navigation

The sidebar navigation has been enhanced to clarify which summary requirement you are viewing, with the ability to quickly view different sections of the requirement document in a high-performance view that blends usability with scalability. As with the previous version, you can display textual requirements as well as the associated use case diagrams.

Configurable Fields Display

The updated view includes a new field selector that lets you choose which fields you would like to display in the requirements document:

When you choose a rich text field such as "Notes," it is displayed as an additional inline text block under the main description. If you choose any of the other fields (e.g., test coverage, task progress, type, priority, status, etc.), it will be displayed in the grey header bar just under the title of the requirement.

Inline Editing of Rich Text Fields

The new document view lets you easily edit any of the rich text fields (including the standard Description field plus any custom fields) inline using our new text editor (an updated version of CKEDITOR). This makes requirements document editing really straightforward, with no need to leave this screen to make real-time changes:

Requirements Outline Numbering

One frequent request by teams used to traditional requirements documents was the need to display an outline number (e.g., 1.1.1, 1.1.2, 1.1.3) with each requirement to make it easier to see the decomposition of business requirements to system requirements, etc. In this new update, we have added a new 'virtual field' called "Outline Number," which is available in the new column selector:

When you choose to display this field, Spira will display the requirements' outline number before each title and requirement ID.

We'd Love Your Feedback?

We hope you like these enhancements to the requirements document view, please let us know if you have any feedback.

The DevOps Dance - Continuous Testing: Shift Left & Shift Right, Get it Right!

2022-05-13T16:12:02-04:00

What is Continuous Testing?

Continuous testing is the process of executing tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.

Originally limited to automated tests in the CI portion

Should include all kinds of testing, throughout the entire CI/CD pipeline

For Continuous testing, the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals, and goes all the way to monitoring the system in production to find problems that need to be corrected.

> Read the Whitepaper: Continuous Testing Shift Left Shift Right

What is the DevOps Dance?

As more organizations move towards continuous integration (CI) and continuous delivery (CD) with DevOps pipelines becoming the norm, where is the right place to do different kinds and levels of testing? In this presentation based on the whitepaper, we provide a blueprint for test managers on how to think about shifting left and shifting right while keeping the overall QA picture and goals in mind.

The DevOps Dance - Shift Left, Shift Right - Get It Right from Inflectra

Inflectra's SpiraTest Is A Tool of Choice To Run Israeli Testing Competition 2021

2021-03-29T10:58:38-04:00

The 2021 testing competition will run in two stages:

The first round will take place online on April 23, 2021, where teams will be asked to test a product in three hours. Currently, there are 70 participants registered at the event. The judging will be done by eight software testing and QA professionals.
The final round will be a part of the Testing & Automation Geekweek 2021 conference on June 21, 2021, at the Daniel Hotel in Herzliya. Here teams will test another product in just two and a half hours.

The award ceremony will be held on June 24th. The winners will walk away with the all-expense-paid trip to Agile Testing Days 2021 in Potsdam, Germany, and will be published in the World of Tests magazine. Just like in the past years, ISTC 2021 will use Inflectra's QA powerhouse - SpiraTest to track and report bugs and issues found in the software under test (SUT) during the competition.

The registration for ISTC 2021 is now closed, but for more information about this annual event, click here!

Check out our recaps from previous years to see all the fun: 2017, 2018!