Project governance in MIS: during the development of a Management Information System, how frequently should progress reporting meetings be held to maintain control and transparency?

Introduction / Context:
Effective MIS projects rely on cadence-based communication. Different horizons (day-to-day tasks, weekly sprints, monthly steering) serve distinct governance purposes—task tracking, risk removal, and strategic alignment. The right answer reflects that multiple cadences typically coexist within mature project management practices.

Given Data / Assumptions:

• Teams often use daily stand-ups for tactical coordination.
• Weekly reviews address sprint goals, blockers, and cross-team dependencies.
• Monthly checkpoints align stakeholders, budgets, and scope.

Concept / Approach:
No single meeting frequency covers all needs. Daily stand-ups enhance visibility and quick adjustment; weekly progress meetings consolidate status, metrics, and risk mitigation; monthly steering meetings enable executive oversight and scope/budget decisions. Together they form a layered control system that keeps an MIS initiative on track, especially when requirements evolve or integration complexity is high.

Step-by-Step Solution:

Verification / Alternative check:
Agile and hybrid methodologies prescribe daily stand-ups and regular reviews; PMOs typically require monthly steering committees for significant projects.

Why Other Options Are Wrong:
Limiting to a single frequency creates blind spots and delays escalations.

Common Pitfalls:
Meeting overload without clear agendas; skipping monthly governance, leading to late surprises in cost or scope.

Final Answer:
all of the above