<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: SpiraPlan Best Practices</title><description>Discussions of best practices for using SpiraPlan with specific agile methodologies and lifecycles (e.g. Scrum, Kanban, XP, AUP). Please do not pose general issues in this forum.</description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums</a10:id><ttl>120</ttl><link>/Support/Forum/spiraplan/best-practices/List.aspx</link><item><guid isPermaLink="false">threadId=2796</guid><author>Tasmania DoH (spiraplanadmin@health.tas.gov.au)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">test case</category><category domain="http://www.inflectra.com/kronodesk/thread/tag"> obsolete</category><title>Manage old test cases</title><description> What is the best way to manage old test cases and to avoid that they are used in new test sets?  You can set the status to obsolete but that doesnt block them to be still used.  Is there a way to block future usage?  Thanks </description><pubDate>Wed, 24 May 2023 09:08:16 -0400</pubDate><a10:updated>2024-11-12T19:03:43-05:00</a10:updated><link>/Support/Forum/spiraplan/best-practices/2796.aspx</link></item><item><guid isPermaLink="false">threadId=2691</guid><author>Federico Merritt (fwsmgqehkwwisqljci@nespf.com)</author><title>Product with multiple software packages and variants</title><description> I have a single product that consists of multiple pieces of software all maintained by my team.  There are also variants of this product that inherit a majority of the requirements from the base product but then might have a few additional requirements.  A particular release of the base product might contain several releases of support software.  Are components the correct this to use in this situation? i.e.   Base Product  Product Variant 1  Product Variant 2  Software Package A  Software Package B     We also have various optional software products that may be installed into the Base Product.  Sometimes this might require changes to the Base Product and sometimes not.  Would these be considered separate products?  Can I connect requirements between products? </description><pubDate>Thu, 13 Oct 2022 14:46:09 -0400</pubDate><a10:updated>2025-09-08T03:26:15-04:00</a10:updated><link>/Support/Forum/spiraplan/best-practices/2691.aspx</link></item><item><guid isPermaLink="false">threadId=2692</guid><author>David J (adam.sandman+support@inflectra.com)</author><title>Product vs Project</title><description> Does spiraplan have a way to manage projects vs products?  In my case a project might involve multiple products and I would like to track the overall project progress which might involve requirements and tasks in multiple products. </description><pubDate>Thu, 13 Oct 2022 16:02:19 -0400</pubDate><a10:updated>2025-02-14T13:28:43-05:00</a10:updated><link>/Support/Forum/spiraplan/best-practices/2692.aspx</link></item><item><guid isPermaLink="false">threadId=3183</guid><author>David J (adam.sandman+support@inflectra.com)</author><title>Best Practices for Using SpiraPlan with Agile Methodologies (Scr</title><description> Im looking to start a focused discussion on how teams are effectively using SpiraPlan in combination with specific agile methodologies such as Scrum, Kanban, Extreme Programming (XP), and Agile Unified Process (AUP). </description><pubDate>Tue, 31 Mar 2026 06:45:17 -0400</pubDate><a10:updated>2026-03-31T13:02:57-04:00</a10:updated><link>/Support/Forum/spiraplan/best-practices/3183.aspx</link></item></channel></rss>