+ The work and overall progress is being coordinated and tracked on a https://tree.taiga.io/project/modularity-wg/epics[**Modularity WG Kanban Board**].

+ User feedback, such as bugs and feature requests, is being collected in a https://pagure.io/modularity/issues[**Modularity issue tracker**].

+ 1. https://tree.taiga.io/project/modularity-wg/epics[**Goals (epics)**] — A specific definition of a state we want to achieve, ideally a https://en.wikipedia.org/wiki/SMART_criteria[SMART] goal.

+ Setting a direction of the project.

+ 2. https://tree.taiga.io/project/modularity-wg/kanban[**Actions (cards)**] — Tasks that get us closer to a specific goal.

+ Defining actionable work items contributors can complete.

+ We work with an Agile mindset.

+ We have designed our system to transparently communicate our goals and intentions without the need to understand every single piece of work that is being done.

+ It also allows us to present actionable tasks that are clearly defined and prioritized so anyone can help us move forward.

+ Because an Agile process is not "making things up as we go," but rather "iteratively working towards specific goals," the first thing that needs to exist are goal definitions.

+ Goal definitions are ideally SMART — specific, measurable, actionable, relevant, and time-bound.

+ At the absolute minimum, they always must have a clearly defined purpose — so we know why we want to achieve them, and a definition of done — so we know when they achieved.

+ This way we can communicate the direction of the project.

+ Goals (epics) are owned by a single person who acts as a "Feature Driver" or "Epic Owner" (to use the Tiaga term).

+ The owner doesn't necessarily do all the work, but makes sure that actionable tasks that lead towards completion exist at all times, and is responsible for the goal being completed.

+ By de-centralizing leadership, the project can then be scaled across a large community of contributors.

+ Epics are defined in the https://tree.taiga.io/project/modularity-wg/epics[Epics View of our board].

+ This view is used for strategic planning and for monitoring the overall progress of the project.

+ It also allows one to drill down into idividual epics for more specific details about each goal.

+ The details of a specific epic shows the purpose of the goal, the definition of done, and other information such as a delivery deadline.

+ It also lists all the actions (cards) that lead to the completion of this epic.

+ Epic Owners use this view to define and manage individual cards.

+ To work on the project, contributors visit the https://tree.taiga.io/project/modularity-wg/kanban[Kanban View of our board] showing all existing cards sorted into different columns, each representing a specific state.

+ Contributors choose *any* card in the "Next" column they want to work on.

+ To work on a specific card, contributors can simply assign themselves to any card in the "Next" column and move it to the "In Progress" column.

+ This way they indicate to other contributors that this card is already being worked on.

+ While working on a card, updates should be posted to the comment section of the card.

+ Contributors can also mention other people in the comments to ask questions or to notify them about specific information.

+ It is also encouraged to coordinate with others using the xref:community.adoc#_channels[usual communication channels] such as IRC.

+ However, the card should not be treated as "documentation," rather just a communication mechanism about the work.

+ The card has a limited lifespan and will, eventually, be archived.

+ As a result, documentation should land elsewhere, wherever appropriate for the task.

+ When a card is complete, contributors are expected to post an update to the comments, and move the card to the "Done" column in the https://tree.taiga.io/project/modularity-wg/kanban[Kanban View of our board].

+ This step updates the progress of the epic the card belongs to which is useful for tracking progress.

+ If new actions appear as a result of card completion, contributors should coordinate with the Epic Owner about creating new cards for the new actions to ensure there is always a next step in the queue.

+ This communication is also important to make sure the Epic Owner understands the new cards as they are responsible for making sure it happens.

+ Issues such as bugs or feature requests can be created by anyone in the https://pagure.io/modularity/issues[Modularity Issue Tracker].

+ The issue tracker is then processed by the Working Group and new cards or even epics may be created as a result.

+ Separating user feedback from the "work" lowers the pressure on the person who reports the feedback — they don't have to understand the working group's tracking system.