I came across this excellent resource shared by BaseCamp on how work is structured, https://m.signalvnoise.com/how-we-set-up-our-work-cbce3d3d9cae#.4m7ouefj8.
Apart from just sharing it, I figured that it may provide a way to leverage the community to support the evolution of OpenMRS in addition to supporting project management.
The Next Cycle - is a sprint planning tool, https://public.3.basecamp.com/p/yCe87HJ5EX1Nx48N3R6fhfHX, which can be used quarterly to provide thinking and planning for big ticket items as well as smaller sets of changes. This goes a step above JIRA tickets, since a number of JIRA tickets can be bundled into a feature or a platform change
Pitch (I personally like this one), https://public.3.basecamp.com/p/22KB2DCxpEQLZow8Vc2iJhEq, the description for a feature that is to be done in the next cycle which gets a node to be done.
This is in light of providing some clarity into what is being worked on from cycle to cycle, supporting the project management planning and usage which is being discussed, but starting from a simple, practical and pragmatic process that can be evolved over time.