pm-review

To assess stakeholder impact from code modifications, run a PMBOK analysis on your local git changes. It evaluates modifications against stakeholder management areas to identify project-level impacts and potential risks, providing a PM's perspective on how the changes affect project scope and involved parties.

Yes, you can review only staged git changes for scope and risk assessment. The PMBOK analysis supports options to review only staged changes, evaluating them against the 7 knowledge areas to identify project-level impacts and risks introduced by those specific modifications.

A PMBOK knowledge area analysis for local git changes evaluates code modifications against the 7 PMBOK knowledge areas: Scope, Risk, Stakeholder, Quality, Integration, Schedule, and Resource management. It identifies project-level impacts and risks, providing a structured product management review before you commit significant features.

Yes, the PMBOK code review generates a structured report detailing project-level impacts and risks, with options to output the report to a file. This structured reporting standardizes the assessment of code modifications across the 7 PMBOK knowledge areas.

You need a project management review of local code changes before committing a significant feature. Running a PMBOK analysis provides a PM's perspective on how the changes affect project scope, introduce new risks, impact stakeholders, or alter the schedule, ensuring alignment and identifying potential issues early.