Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
titleDRAFT

These guidelines help the community to understand the refinement process. Without a clear refinement process, it could be challenging to know how to make changes. These are guidelines, it is possible for maintainers to adjust to the needs.

Needs for refinements

Refinements are needed when your plans affect multiple people. Refinements can help with:

  • Improve the quality (more eyes/idea's can help to improve the idea and/or decide to stop)
  • Let the community know that changes are coming

Community refinements

If your issue/architect is ready for refinement you can follow the next steps:

This page describes the process of establishing clear goals and agreeing, as a community, on the steps and the way we collaborate to achieve the goals.


1. Make sure we have clear goals and everyone in the community knows what we are working on.

  • last week of each quarter the refinement sessions are used to inspect what was achieved in the quarter that is ending and to discuss the goals for the quarter that is about to start
  • goals need to be clear & measurable (clear acceptance criteria)
  • goals will be tracked using the Roadmap: Planned Features · Roadmap (github.com)
  • each goal will be discussed by the community members, and broken down into high level steps
  • availability of the community members will be shared, and an agreement will be made on how the members will collaborate to acheieve the goals

2. Refine the tasks needed to acheive the goals

  • during each refinement session the community members look at the goals and align on the next tasks to be worked on
  • technical solution is discussed
  • in case of disagreements regarding the techincal approach, a discussion will be created

3. Discussions & decisions

  • discussions can take place in the github tickets, or a separate discussion can be created, if needed, and linked to the ticket that triggered it
  • questions, remarks, risks can be shared by anyone
  • maintainers will make a decision, considering all the input, and the decision will be communicated under the task/discussion
  • when the maintainers cannot come to an agreement, the possible approaches will be shared in the TSC, where a decision will be made

...