Align Methodics with the Release Management process - #34
Draft
Jirka3Key wants to merge 3 commits into
Draft
Conversation
Align the Methodics with the Release Management process (PM_Reporting/docs/release-management.md, section 8): the Epic Owner — the Epic's Assignee — now drives the Epic breakdown, distributes work, and owns the Epic's estimates. The PM retains status transitions, Start/End Date, business prioritization, and review of proposed sub-issues. Adds the Epic Owner role to section 10 and updates section 2.2, 2.6, 3.1, and the Quick Start accordingly. Bumps the document version to 1.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Align with the Release Management process: the breakdown review is done by the Tech Lead (technical accuracy) and QA (testing coverage) only. Removes the PM/PO review step from section 2.6 Phase 3 and its flowchart, and the corresponding review bullets from the PM and Product Owner roles in section 10. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Align with the Release Management process: sub-issues are estimated individually — by the Epic Owner, the assigned developer, or QA — and the Epic's Estimate is the sum of those values, with the Epic Owner responsible for it. Updates the Estimate field definition (section 3.1), the estimate suggestion note (section 3.5), and the Epic Owner and Developer roles (section 10). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standing alignment PR
This is the accumulating draft PR for aligning the Methodics with the Release Management process being drafted in
PM_Reporting/docs/release-management.md. Each discrepancy we resolve in favour of the RM document lands here as a separate commit; the PR stays in draft until we decide the batch is complete, then it is marked ready and merged as one review.Commits so far
1. Epic breakdown and estimate ownership → Epic Owner (
8293a35)The RM document introduces the Epic Owner — the Epic's Assignee with an explicit mandate. The Methodics previously assigned the Epic breakdown and the Epic-level Estimate to the PM. Resolution: RM wins, Methodics updated:
/epic-breakdown.2. PM/PO review removed from the Epic breakdown flow (
f95c446)The RM process (chapter 5, step 2) has the breakdown reviewed by the Tech Lead (technical accuracy) and QA (testing coverage) only. Resolution: RM wins, Methodics updated:
3. Epic Estimate = sum of sub-issue estimates (
da4031c)The estimation model per the RM process: sub-issues are estimated individually — by the Epic Owner, the assigned developer, or QA — and the Epic's Estimate is the sum of those values, with the Epic Owner responsible for it (replaces the earlier "not sum of children" top-down model):
🤖 Generated with Claude Code