From dd71c72fa27ba2269fdf9bac282683a8e2211175 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Oct 05 2018 08:39:05 +0000 Subject: 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.