Requirements Planning Version Tracking for Distributed Teams
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional requirements planning methods struggle with managing changing stakeholder inputs and approvals in distributed and expanding stakeholder environments, particularly in software development, where geographic distribution and new stakeholders lacking context hinder effective collaboration and approval processes.
Innovation Solution
A method and system for managing requirements planning in a collaborative computing environment, utilizing version-aware traceability links, annotations, and notifications to track approval status, filter information, and merge changes, allowing stakeholders to annotate and revise requirements in parallel, and notify relevant stakeholders of changes and questions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If stakeholders are gathered into a single physical location for continuous meetings (XP approach), then collaboration and understanding among stakeholders is improved, but the system cannot accommodate distributed stakeholders or large numbers of stakeholders due to geographic distribution and logistical constraints
Solution Approach 1:
The patent creates virtual copies of the physical meeting environment through a computer-based system that replicates stakeholder interactions, document sharing, and approval workflows. This allows distributed stakeholders to participate in requirements planning without physically gathering, thereby maintaining collaboration effectiveness while accommodating geographic distribution.
Solution Approach 2:
The patent introduces a computer-based requirements planning system as an intermediary between stakeholders, facilitating communication and collaboration without requiring direct physical interaction. This intermediary enables distributed stakeholders to engage in meaningful collaboration while the system manages the complexity of coordinating numerous participants across different locations.
2Reliability
If traditional sequential approval processes are used for requirement changes, then stakeholder approvals are ensured, but the process becomes time-consuming and delays software development
Solution Approach 1:
The patent implements dynamic approval workflows where the approval process adapts based on the specific requirement change, stakeholder roles, and pre-configured delegation rules. This dynamic system allows certain approvals to be granted automatically through delegation to representatives, while still maintaining reliability by ensuring all necessary stakeholder groups are ultimately satisfied with the changes.
Solution Approach 2:
The patent establishes pre-configured approval hierarchies, delegation relationships, and stakeholder group definitions before the requirements planning process begins. This preliminary setup enables faster processing during actual requirement changes, as the system can quickly determine approval paths and automatically grant approvals from delegated representatives without ad-hoc negotiations.
3Adaptability or versatility
If new stakeholders are added to the project, then comprehensive requirements coverage is improved, but existing stakeholders lack context of previous discussions and collaboration efficiency decreases
Solution Approach 1:
The patent implements comprehensive feedback mechanisms that automatically notify all relevant stakeholders of new requirement versions, changes, and discussion outcomes. This feedback loop ensures that new stakeholders receive complete context about previous discussions and decisions, while existing stakeholders are kept informed of ongoing developments, thereby maintaining information continuity as the stakeholder group evolves.
Solution Approach 2:
The patent performs preliminary actions by automatically generating and distributing contextual information packages to new stakeholders when they join the project. This includes historical requirement versions, discussion summaries, and stakeholder relationship maps, enabling new participants to quickly understand the context of previous collaborations without requiring extensive onboarding meetings.
4Measurement precision
If multiple versions of requirements are tracked and merged, then requirements evolution is captured accurately, but the complexity of managing and displaying version differences increases
Solution Approach 1:
The patent segments the requirements document into discrete, versioned elements that can be independently tracked and compared. This segmentation allows the system to manage complexity by breaking down large requirement documents into manageable units, each with its own version history and change tracking, while maintaining the ability to merge and display differences across the entire requirements set.
Data Source
AI summary
Embodiments of the present invention provide a method, system and computer program product for managing requirements planning in a collaborative computing environment. In one embodiment of the invention, a requirements planning management method can include identifying each approving stakeholder for a version of a requirement in a requirements plan, creating traceability links between each approving stakeholder and the version of the requirement, and notifying each approving stakeholder having a traceability link to the version of the requirement whenever a new version of the requirement is proposed by a stakeholder. The method also can include merging multiple versions of the requirement into a single document, displaying the single document to a viewing stakeholder, and marking up the single document to reflect differences between the single document and a most recent version of the requirement for the viewing stakeholder.