Developer Productivity Framework Systematic Literature Project Plan

Role: Head of Developer Experience (DevEx) Research and Staff Socio-Technical Systems Analyst.

Context

• Research Topic: {{productivity_framework_topic}}
• Empirical Methods Scope: {{empirical_study_methodologies}}
• Non-Academic Sources: {{gray_literature_sources}}
• Target Developer Cohort: {{developer_cohort_profile}}
• Evaluation Rubric: {{quality_assessment_rubric}}
• Program Milestones: {{strategic_rollout_milestones}}

Task

Formulate a rigorous mixed-methods literature review and evidence synthesis project plan that aggregates academic software engineering literature and practitioner gray literature to construct an actionable developer productivity model for {{developer_cohort_profile}}.

Method

1. Define primary research questions investigating cognitive load, feedback loops, engineering velocity, and satisfaction metrics.
2. Design a multi-vocal search strategy integrating academic engines (ACM/IEEE/Springer) and practitioner sources defined in {{gray_literature_sources}}.
3. Establish source-specific qualification criteria separating rigorous practitioner whitepapers from non-reproducible promotional content.
4. Apply {{quality_assessment_rubric}} across identified empirical software engineering studies to weight evidence credibility.
5. Construct a qualitative coding framework (using inductive and deductive coding) to extract themes around friction points and interventions.
6. Formulate a synthesis model harmonizing quantitative telemetry metrics with subjective perceptual surveys.
7. Map synthesized findings directly against the socio-technical constraints of {{developer_cohort_profile}}.
8. Establish governance and milestone execution gates aligning with {{strategic_rollout_milestones}}.

Constraints

• MUST utilize a dual-track appraisal protocol that separately scores peer-reviewed empirical papers and industry gray literature.
• MUST NOT recommend interventions that lack empirical triangulation across at least two independent studies.
• All qualitative extraction codes must be cross-referenced against validated constructs within {{productivity_framework_topic}}.
• Synthesis outputs must separate correlation from verified causal relationships in surveyed interventions.

Output format

Provide the complete review project plan organized into five markdown sections:

1. Literature Review Charter & Research Objectives (clarifying questions, scope, and target outcomes)
2. Dual-Track Search & Retrieval Protocol (academic Boolean queries and practitioner screening heuristics)
3. Methodological Quality Appraisal Framework (evaluation scoring cards based on {{quality_assessment_rubric}})
4. Qualitative & Quantitative Synthesis Schema (thematic coding structure and metric triangulation matrix)
5. Execution Roadmap & Leadership Milestone Schedule (phased activities mapped to {{strategic_rollout_milestones}})

Self-review

• Verify that the plan explicitly differentiates data extraction protocols for academic papers versus {{gray_literature_sources}}.
• Ensure the synthesis schema directly addresses the unique operational context of {{developer_cohort_profile}}.
• Check that the quality appraisal section specifies transparent threshold scores for study inclusion.