Program Roadmaps - ARCHIVED

Deprecated content

This content might be obsolete as the page was archived following deprecation of the concept of FINOS Programs in early 2020. For the latest on FINOS Corporate Governance please refer to the FINOS website while for the Community Governance check the FINOS Community Github Repository.

All programs are expected to have 12 month roadmaps. Ideally these roadmaps are kept updated - "evergreen" and it's good practice for programs to update them at least once a quarter. At a minimum, programs are expected to update their roadmap once a year, as part of reviewing the past year's progress and planning the year to come.

Programs are afforded discretion and independence in choosing the format of the roadmap that works best for their programs as well as the component projects and working groups within the program. FINOS recognizes that some programs have tight interdependencies between some or all of its projects and working groups, while in other programs projects and working groups work largely autonomously from each other.

What should be in a roadmap? We recommend that the roadmap include the following:

A summary of the product / release roadmap of each of the respective programs and work groups. What's on the "to do" list for the next year? What does the team in each project and working group want to take on? What are some of the bigger features in the backlog that the project team intends to build (and when) in the coming 12 months?
Across projects and working groups what are the major releases of code, standards, etc. for public consumption and production system use? Releases may also include things like best practices libraries, process models, pro forma legal and governance policies, HR/talent development "cook books", or white papers.
- What sort of support will the program require in terms of product marketing from the foundation team?
Where are their emerging product and technology opportunities that might warrant starting a new project or working group? What might warrant soliciting new contributions and contributors?

Roadmap Example 1: Confluence Template

The Confluence "Roadmap Planner" macro provides a ready made way within the wiki itself to build a basic roadmap in a Gantt chart format. This macro could be used to document and map out different initiatives across program projects and working groups

Serverless Backend Project

API Project

Standards WG

Cross-Project / PMC

Dev Sprints (4 x 2wk)

Integrated Testing & UAT

Dev Sprints (2 x 2wk)

Integrated Testing & UAT

Build SDK

User Story Development

Write Test Cases

UAT

Develop Microsite

Roadmap Example 2: Quarterly Grid

		Q1	Q2	Q3	Q4
Project 1	Activities & Focus (E.g., major features being developed, analysis being performed)	Building (features) ... Investigating ... Testing ...	Building (features) ... Investigating ... Testing ...	Building (features) ... Investigating ... Testing ...	Building (features) ... Investigating ... Testing ...
	Releases (if any)
	Additional FINOS support requested (above and beyond steady state)
Project 2	Activities & Focus (E.g., major features being developed, analysis being performed)
	Releases (if any)
	Additional FINOS support requested (above and beyond steady state)
Working Group 1	Activities & Focus (E.g., major features being developed, analysis being performed)
	Releases (if any)
	Additional FINOS support requested (above and beyond steady state)
Program Overall	Common / Cross project releases and milestones