Strategic Release Planning and Evaluation of Operational Feasibility
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Strategic planning (or road-mapping) of software releases addresses the assignment of requirements to releases on a strategic level. Effort, finance and risk constraints are considered to determine strategic release plans. The goal is to find an optimal balance between competing stakeholder priorities and bottleneck resources. However, strategic planning has to be supplemented by more fine-grained operational planning as typically performed in project management. The paper describes mechanisms by which to reduce the complexity of strategic and operational planning to a series of data and formulae that objectively represent input from all stakeholders and can easily reported, analyzed and manipulated. The capability provides improved planning and re-planning in a dynamic business environment, including the ability to validate strategic plans against operational limitations and revise as necessary. For performing strategic planning, we present the research prototype ReleasePlanner™. Real-world experience in performing strategic planning using ReleasePlanner is reported from a case study at Trema Laboratories Inc.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it