imankulov · October 17, 2014 14:12
diff --git a/the flow™.txt b/the flow™.txt
 * __project notes__
 [[NOTE]]: - We use colors (priorities) to mark the complexity of the task	- It's okay to change the complexity on the task, as you work on it	- We use a flow where tasks "bubble up" from the backlog to done	- Depending on the project, you may have more (or less, without "testing", for instance) stages of the flow	- One may or may not use tags
 ...Trivial. It's barely worth creating a separate item
 ...Easy. No hidden pitfalls, straightforward execution flow, short time to work [[priority 3]]
 ...Hard. Challenging. Pitfalls expected. Or just long and boring [[priority 2]]
 ...Super-hard. But you're not scared. Subtasks required [[priority 1]]
 * !!Done!!
 [[NOTE]]: Move all completed tasks here. They pass the testing phase and are in production, or ready to production. Tasks have to be stricken through
 ...Trivial task @feature
 ...Serious bug [[priority 2]]
 * !!Testing!!
 ...Minor bug @bug [[priority 3]]
 * !!In Progress!!
 [[NOTE]]: Place here all the tasks you are currently working on. Unless it's a single-user project, every task must have its assignee
 ...Small feature @feature [[priority 3]]
 ...Trivial bug @bug
 * !!Scheduled!!
 [[NOTE]]: - These tasks are enqueued for work, and reordered according to their priority. 	- Scheduled tasks are "shovel-ready", there is enough information on what and how should be done here	- Tasks has meaningful names and comments	- Task names are imperatives: "add foo to bar"	- Estimated task complexity for them is defined	- Optionally, there are assignees for tasks 
 * !!Backlog!!
 [[NOTE]]: This is the place where we add tasks initially. They may have arbitrary names and comments. Their complexity and implementation details are up for discussion.
	* __project notes__
	[[NOTE]]: - We use colors (priorities) to mark the complexity of the task - It's okay to change the complexity on the task, as you work on it - We use a flow where tasks "bubble up" from the backlog to done - Depending on the project, you may have more (or less, without "testing", for instance) stages of the flow - One may or may not use tags
	...Trivial. It's barely worth creating a separate item
	...Easy. No hidden pitfalls, straightforward execution flow, short time to work [[priority 3]]
	...Hard. Challenging. Pitfalls expected. Or just long and boring [[priority 2]]
	...Super-hard. But you're not scared. Subtasks required [[priority 1]]
	* !!Done!!
	[[NOTE]]: Move all completed tasks here. They pass the testing phase and are in production, or ready to production. Tasks have to be stricken through
	...Trivial task @feature
	...Serious bug [[priority 2]]
	* !!Testing!!
	...Minor bug @bug [[priority 3]]
	* !!In Progress!!
	[[NOTE]]: Place here all the tasks you are currently working on. Unless it's a single-user project, every task must have its assignee
	...Small feature @feature [[priority 3]]
	...Trivial bug @bug
	* !!Scheduled!!
	[[NOTE]]: - These tasks are enqueued for work, and reordered according to their priority. - Scheduled tasks are "shovel-ready", there is enough information on what and how should be done here - Tasks has meaningful names and comments - Task names are imperatives: "add foo to bar" - Estimated task complexity for them is defined - Optionally, there are assignees for tasks
	* !!Backlog!!
	[[NOTE]]: This is the place where we add tasks initially. They may have arbitrary names and comments. Their complexity and implementation details are up for discussion.