Power Apps Consultants Canada

Align Sprints with Fiscal Quarters

Streamline Board Reporting for Software Projects: Grouping and Aligning Sprints to Fiscal Quarters

In this article, we will explore grouping agile sprints into four groups that align with the corporate fiscal reporting periods, allowing for easier reporting by Steering Committees to The Board, and having each of the four groups align with your corporate OKR's.

Group your sprints by your fiscal quarters

Scaled agile typically recommends grouping sprints into five program increments. I am advocating for grouping your sprints into four program increments and aligning the timing of those program increments to your fiscal reporting and board reporting needs. My recommendation is to keep your sprint sat two-weeks each, but increase the number of sprints in a program increment to map to your fiscal quarters. The whole company should be on the same sprint schedule, whether it is the Sales department, Accounting department, etc. As an example, if your fiscal year was identical to the calendar year in 2024, you would have the following company-wide sprint calendar:

Now map your OKRs to your program increments

Your corporate OKRs (i.e., objectives and key results) identify your annual goals by focus area, such as brand, culture, revenue, services, etc. Those annual corporate goals at the organizational level flow down to team/department goals. Achieving those goals may require undertaking of software projects. Those software projects should tie directly to those departmental and organizational goals on a quarterly basis. As such, project Steering Committees responsible for those software projects should be reporting to The Board on their quarterly schedule on how they are trying to meet those OKR's with their projects and the status of those projects.

Now tie those OKRs to agile features in quarterly program increments

At the beginning of each quarter, you would undertake your program increment planning event. In that event you would state what software features you will try and accomplish in those seven sprints, tied to the quarter, that align with the OKR's. After you identified the features that you will tackle in your software project for that program increment, you will then align the user stories to the seven sprints as well.

Reporting is now made easier!

What did your department do this fiscal quarter to contribute to the overall organizational OKR's for the year? Well, you should be able to state what software features you released in that program increment, as part of your software project because you gave yourself the quarterly deadline for particular features, and this all aligns to your sprint calendar.

Happy software engineering everyone!

About Purely CRM

For close to a decade our Purely CRM team has been laser-like focused on delivering CRM solutions built solely on Microsoft Dynamics 365 CRM, combined with Power Apps and the Microsoft Power Platform. We’ve expanded our team immensely in the past years to help better serve our clients and partners. Most recently we merged with Endeavour Solutions, a top Microsoft ERP, CRM, and Cloud consulting firm to further expand our talented team of CRM consultants.

Our core focus is on large mid-market and enterprise CRM Design & Development projects, Staff Augmentation, and CRM Support. When needed we can also tap upon our peers at Endeavour for Dynamics 365 Business Central ERP to provide an All-in-One Cloud ERP-CRM.  We provide services to clients Coast to Coast across the United States and Canada. We do not use resources overseas.

Reach out to explore our track record, rates, skills, and approach to discover how we can collaborate and drive YOUR SUCCESS.

Are You Ready To Get Started?

Let's Talk