Changes between Version 1 and Version 2 of PROCESS_R2

Timestamp:

12/03/08 17:14:45 (17 years ago)

Author:

deyan

Comment:

--

PROCESS_R2

@@ -6 +6 @@
 
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
-
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
-
+The PROCESS page should be tuned according to the new rules, expanding the team etc.
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+ * Create a new structure of the document - see implementation idea
+ * Refactor roles
+  * Explain remote implementors
+ * Add a link to an internal process page where you should explain internal rules and other specific information. If possible add read permissions to internal team only
+ * Explain teams (experimental) 
+ * Add nice graphic of the workflow
 
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+[wiki:PROCESS]
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+Tree structure of the PROCESS page:
+{{{
+PROCESS
+|_Overview
+|_Scrum
+|__Explanation
+|__Tunes
+|_Team roles
+|_Teams
+|_Workflow
+|__Diagram
+|__Explanation of States
+|_Task Tips (Maybe these belong to PLATFORM_STANDARDS_GENERAL?!)
+
+}}}
 
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
-
+[wiki:PROCESS_R0] [[BR]]
+[wiki:PROCESS_R1] 
 == How to demo ==
 ^(In this section you must add instructions for the demo of the task.)^