Overview: End to end OFN Product Development Process


In December 2017 the OFN global team came together in Australia and defined an end to end product development process that democratises the way we make decisions and build the platform.

Inherent in this process is:

  • We make priority decisions that are best for the global platform; it is about the collective good, not separate (and often conflicting) local priorities that are or are not realised dependent upon whether that local instance has funding.

  • There is a single development pipe, within which bugs, small improvements, and bigger feature (or tech debt) items are designed, developed, and released. There are no longer development pipelines for each local instance with dev/test people onboard. “One pipe to rule them all” :grin:

The proposed process

Part 1. Choosing what to develop

This process covers the path we take to determine what the global development team should work on. It includes both new/improved features (and tech debt) and any bugs that are identified as we use the platform.

Read more about each of the steps in the process:

  1. Generating Ideas within the community.
  2. Curating these ideas into an Icebox of possible things/items we should focus on.
  3. Votes for the ideas that are most important for each instance.
  4. Prioritising the most important items and adding them to the Product Development Backlog (link takes you to Milanote, log in details required for access).
  5. Brainstorming these ideas (where the solution is not obvious) to determine Feature Candidates to add to the Product Feature Backlog (link takes you to GitHub).
  6. Scoping the selected Feature Candidate using an Inception process.
  7. Adding the stories for the Feature to the Delivery Backlog.

and also

  1. Identifying Bugs and triaging them based on severity level (link takes you to GitHub)
  2. Adding all severity 1 and 2 bugs to the Delivery Backlog

Part 2. The delivery train (toot! toot!)

< coming after the july global gathering >