Open sophie2-wbs.py and:
 * decompose the tasks further in work breakdown structure (read the rules in the beginning of the document)
 * look up for tasks with too small or too big effort and correct them
 * add missing tasks and comments
 * verify and finalize the document

[[BackLinksMenu]]

= Analysis =
== Overview ==
The goal of this task is to decompose the tasks to subtasks with less effort.
== Task requirements ==
( Taken from /manage/sched/sophie2-wbs.py Rules section)
= Task rules =
 * It should be clear what a given task is!	

 * Sub-tasks should not overlap!

 * Sub-tasks should cover 100% of the parent task.

 * Each task should have either:
	
  * Several revisions.
	
  * >=2, <=7 sub tasks

 * Super tasks which contains sub-tasks (not a revisions) should not need work for themselves. 
	
  * If it looks like it needs, define a child-task that covers this.

 * Try to keep to entity/feature driven spec.

 * No end task (with revisions only) should have more than 10 effort.

 * No task should have less than 1 effort.

 * No revision should have less than 0.5 effort.

 * Names are global! It should be clear 0.5 effort.

 * Names are global! It should be clear what the task is, without its context.	

== Task result ==
Schedule meeting listed requirements.
== Implementation idea ==
Open /manage/sched/sophie2-wbs.py and look for:

 * Tasks with less than 1 effort

 * Revisions with less than 0.5 effort

 * Tasks with same names.

 * Unclear task names.

 * Subtasks do cover < 100% of the parent task.

 * Subtasks do overlap each other.
 
 * Child tasks (final) with effort more than 7

 * Child tasks (final) with effort less than 2

Note that in some cases effort <=2 and >=7 is permissible.


== Related ==
[wiki:SCHEDULE_WBS_TIME_ALLOC_R0]
[wiki:SCHEDULE_WBS_DEPENDENCIES_R0]
[wiki:SCHEDULE_WBS_EXPORTS_R0]

== How to demo ==
^(In this section you must add instructions for the demo of the task.)^

= Design =
Open sophie2-wbs.py and:
 * look Implementation Idea section
 * decompose the tasks further in work breakdown structure (read the rules in the beginning of the document)
 * look up for tasks with too small or too big effort and correct them
 * add missing tasks and comments
 * verify and finalize the document

= Implementation =
The following tasks do have effort >7
PRO_LIB_CORE_COMMONS effort=8
PRO_LIB_CORE_TUTORIAL effort=8
PRO_LIB_MODEL_PRO_OBJECTS effort=8
PRO_LIB_MODEL_PRO_LISTS effort=8
PRO_LIB_MODEL_EXTRA_STRUCTURES effort=8
PRO_LIB_REMOTE_OBJECTS effort=8
PRO_LIB_CONNECTION_INTERFACES effort=8
PRO_LIB_LOCAL_CHANGE_SERVER effort=8
PRO_LIB_EXTENSIBILITY_SAMPLES effort=8
CORE_MVC_BASE effort=8
CORE_ADDITIONS effort=20
PLATFORM_STRUCTURE effort=10
PLUGIN_DECOMPOSITION effort=24
PLUGIN_MODULE_STRUCTURE effort=9
SCENE_COMMONS effort=10
BASE_RESOURCE_COMMONS effort=9
BASE_RESOURCE_LOCATOR effort=8
BASE_SKINS_COMMONS effort=8





= Testing =

= Log =
^(Link the log of the task here)^