Quarterly planning

Structured collection of numerical data for analysis and research.
Post Reply
mstakh.i.mom.i
Posts: 173
Joined: Mon Dec 23, 2024 6:54 am

Quarterly planning

Post by mstakh.i.mom.i »

The first step is for the board to set goals. Board goals are often seen as vague. For example, we want to improve the quality of service or we want to be faster. I think that's OK and boards should not communicate more. It is up to the employees to set the goals in a meaningful way.

My recommendation is therefore to collect 3-5 goals per quarter from the board in the first step. There is now a full-time FTE who creates very large program epics (P-Epics) together with the board members. This is a translation of the goals into software such as Jira (Plugin Portfolio). The process step takes 8-16 hours per quarter. Examples are: improving service management or introducing an ITSM tool as a P-Epic.

Agile Program Management 1
Agile Program Management Part 1
Step 2: Designing epics and involving employees
Now it's time for the second step. Together with the program team (1 FTE), the small business email list department heads must name concrete measures in the form of epics that "contribute" to the respective goal. For example, to improve product quality, we take measures 1, 2, 3,... I recommend that each department head names 3 concrete projects that they would like to implement and prioritizes them according to 1, 2, 3.

Together with the program team and the department heads, these 3 measures per goal are presented to the board and approved. This happens within the first 14 days of the quarter. This means that with 3 department heads, 9 major measures per quarter can be guaranteed to implement the strategy. The department heads coordinate the measures with the respective employees. This also ensures involvement and the opportunity to shape things. Now it's time for implementation.
Post Reply