Review Processes for Agile, Waterfall, and Hybrid Development Styles

Published Date: October 26, 2025
Validated: Yes
Audience: Everyone
Products and Versions Covered:

• Jama Connect® (all supported versions)
• Cloud / CVC
• Self-hosted

Summary

This article explains how to align review processes in Jama Connect® with the agile, waterfall, and hybrid development methodologies.

Each development style requires a different approach to managing reviews. Agile teams benefit from continuous, item-level reviews to enable rapid feedback and early QA involvement. Waterfall teams typically review complete sets of requirements at defined milestones to ensure alignment before progressing. Hybrid teams combine both approaches, managing stable (“foundational”) requirements with structured reviews while continuously iterating on evolving requirements.

By tailoring filters, fields, and workflows, teams can ensure reviews are timely, traceable, and aligned with the maturity and role of each requirement in the development lifecycle.

Resolution

Agile / Iterative Development

Use continuous, filter-driven reviews to validate requirements as they are ready.

1. Create a Filter to display requirements with a status such as Ready for Review
2. From the Filters tab, right-click the filter and select Send for Review
3. Follow the Review Wizard to:
   • Name the review
   • Add participants
   • Include all items currently meeting the filter criteria
4. As requirements are approved, update their status to Approved (or your preferred state)
5. Continue moving additional requirements to Ready for Review as they mature
6. Periodically publish a new revision of the review:
   • Approved items are automatically removed
   • Newly qualified items are added
7. Repeat until all requirements are reviewed and approved

Note:
E-signatures may not persist across review revisions. If signatures are required for all approved requirements, create a baseline of approved items at completion and collect signatures on the baseline.

Waterfall / Milestone-Based Development

Use milestone-driven reviews to validate complete sets of requirements.

1. Add a Release or Milestone field to your requirement item type:
   • Use Jama’s predefined Release field for project-specific milestones
   • Or create a single-select picklist for standardized milestones
2. Use the Status field to track requirement maturity (e.g., Draft, In Review, Approved)
3. Create a filter combining Release/Milestone and Status, or initiate reviews from the Releases tab
4. Conduct reviews at defined milestones
5. After approval:
   • Update the milestone value (e.g., Milestone 1 → Milestone 2)
   • Adjust status as needed
6. Enable QA teams to begin test development once requirements reach Approved

Hybrid Development

Combine structured and continuous review strategies.

1. Add a Foundational field (Yes/No or picklist) to distinguish:
   • Stable (foundational) requirements
   • Iterative (evolving) requirements
2. Create filters using Foundational + Status (and/or Release)
3. Configure visibility:
   • Ensure the Foundational field is visible in the Review Center (via Org Admin)
4. Initiate reviews using one of two approaches:
   • Separate reviews (foundational vs. evolving)
   • Combined reviews with clear visual distinction
5. Manage each group using the appropriate process:
   • Foundational → milestone-based (waterfall-style)
   • Evolving → continuous (agile-style)

This approach ensures consistency, visibility, and traceability across both development streams.

Additional References

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.