From 76dec6873d8ed1f094659ecb29246e81379def8e Mon Sep 17 00:00:00 2001
From: Adam Samalik <asamalik@redhat.com>
Date: Oct 05 2018 08:17:51 +0000
Subject: [PATCH 1/2] add project tracking page


---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 78d7739..9fb8fd7 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -17,5 +17,6 @@
 * xref:using-modules.adoc[Using Modules]
 * xref:community.adoc[Community]
 ** xref:community/teams.adoc[Teams and Working Groups]
+** xref:community/project-tracking.adoc[Project tracking]
 * xref:faq.adoc[FAQ]
 * xref:references.adoc[References]
\ No newline at end of file
diff --git a/modules/ROOT/pages/community/project-tracking.adoc b/modules/ROOT/pages/community/project-tracking.adoc
new file mode 100644
index 0000000..9dd7714
--- /dev/null
+++ b/modules/ROOT/pages/community/project-tracking.adoc
@@ -0,0 +1,43 @@
+= Project Tracking
+
+The work and an 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**].
+
+== What is being tracked
+
+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.
+3. https://pagure.io/modularity/issues[**Feedback (issues)**] — User feedback such as bugs, ideas, questions. Influencing the project from outside.
+
+== How do we operate
+
+We work with an Agile mindset. We have designed our system to be transparently communicating our goals and intentions without the need of understanding every single piece of work that is being done. It also allows us to display actionable tasks that are clearly defined prioritized so anyone can help us with moving forward.
+
+Because Agile 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.
+
+=== Setting and tracking the goals
+
+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 do we want to achieve them, and a definition of done — so we know when exactly are 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. The owner doesn't necessarily do all the work, but makes sure that actionable tasks that lead towards a completion exist at all times, and is is responsible for the goal being completed. This way the project can 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 to drill down into idividual epics for more specific details about each goal.
+
+The specific epic detail 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 a completion of this epic. Epic owners use this view to define and manage individual cards.
+
+=== Making progress
+
+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 can 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 can 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 other using the xref:community.adoc#_channels[usual communication channels] such as IRC.
+
+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 a card completion, contributors should coordinate with the Epic owner about creating new cards for the new actions to ensure there is always next step in the queue.
+
+=== Reporting issues
+
+Issues such as bugs or feature requests can be created by anyone in the https://pagure.io/modularity/issues[Modularity issue tracker]. This issue tracker is then processed by the team 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 our tracking system.
\ No newline at end of file

From dd71c72fa27ba2269fdf9bac282683a8e2211175 Mon Sep 17 00:00:00 2001
From: Adam Samalik <asamalik@redhat.com>
Date: Oct 05 2018 08:39:05 +0000
Subject: [PATCH 2/2] fix grammar and typos


---

diff --git a/modules/ROOT/pages/community/project-tracking.adoc b/modules/ROOT/pages/community/project-tracking.adoc
index 9dd7714..85d7a2c 100644
--- a/modules/ROOT/pages/community/project-tracking.adoc
+++ b/modules/ROOT/pages/community/project-tracking.adoc
@@ -10,9 +10,9 @@ User feedback such as bugs and feature requests is being collected in a https://
 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.
 3. https://pagure.io/modularity/issues[**Feedback (issues)**] — User feedback such as bugs, ideas, questions. Influencing the project from outside.
 
-== How do we operate
+== How we operate
 
-We work with an Agile mindset. We have designed our system to be transparently communicating our goals and intentions without the need of understanding every single piece of work that is being done. It also allows us to display actionable tasks that are clearly defined prioritized so anyone can help us with moving forward.
+We work with an Agile mindset. We have designed our system to be transparently communicating our goals and intentions without the need of understanding every single piece of work that is being done. It also allows us to display actionable tasks that are clearly defined and prioritized so anyone can help us move forward.
 
 Because Agile 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.
 
@@ -20,7 +20,7 @@ Because Agile is not making things up as we go, but rather iteratively working t
 
 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 do we want to achieve them, and a definition of done — so we know when exactly are 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. The owner doesn't necessarily do all the work, but makes sure that actionable tasks that lead towards a completion exist at all times, and is is responsible for the goal being completed. This way the project can be scaled across a large community of contributors.
+Goals (epics) are owned by a single person who acts as a feature driver. The owner doesn't necessarily do all the work, but makes sure that actionable tasks that lead towards a completion exist at all times, and is responsible for the goal being completed. This way the project can 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 to drill down into idividual epics for more specific details about each goal.
 

