Planning - Revision history

TiberiusB at 19:28, 19 April 2026

2026-04-19T19:28:30Z

TiberiusB: /* See also */

2024-02-24T19:40:22Z

TiberiusB: /* Planning in ventures and projects */

2024-02-24T19:39:57Z

Planning in ventures and projects

TiberiusB: /* See also */

2024-02-24T19:39:16Z

at 22:34, 24 November 2021

2021-11-24T22:34:09Z

at 22:33, 24 November 2021

2021-11-24T22:33:27Z

at 22:26, 24 November 2021

2021-11-24T22:26:42Z

at 20:28, 10 November 2021

2021-11-10T20:28:56Z

at 20:27, 10 November 2021

2021-11-10T20:27:56Z

at 05:34, 20 October 2021

2021-10-20T05:34:34Z

@@ Line 1: / Line 1: @@
 Planning is an activity related to model future activities, based on knowledge about how things may play out. Planning is operating between what is predictable and what can happen unexpectedly.
-It is about scheduling [[resource]] allocation based on a predefined process (model of future activities) that will play out into the future.
+It is about scheduling [[resource]] [[allocation]] based on a predefined process (model of future activities) that will play out into the future.
 It is the preferred mode for addressing future activities of an organization, in a command and control paradigm.
@@ Line 35: / Line 35: @@
 ==Plan small tasks==
-'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, induces [[stigmergy]], helps the talent allocation process, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
+'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, induces [[stigmergy]], helps the talent / skills [[allocation]] process, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
 The minimal planning is done using the [[NRP-CAS]], employing a methodology that has been formalized using Workflow recipes. See more on the [[Recipe]] page.

@@ Line 62: / Line 62: @@
 * [[Project management - past and current practices within SENSORICA]]
 * [[Stigmergy]]
-* [[strategy]]
+* [[Strategy]]
 * [[Mapping]]

← Older revision		Revision as of 19:39, 24 February 2024
Line 7:		Line 7:


−	==Planning in ventures and projects==	+	==Planning in open ventures and projects==

	See distinction between [[venture]] and [[project]].		See distinction between [[venture]] and [[project]].

@@ Line 61: / Line 61: @@
 * [[Project and task management]]
 * [[Project management - past and current practices within SENSORICA]]
+* [[Stigmergy]]
 -----------------
 [[Category:Planning]]
 [[Category:Project management]]

@@ Line 1: / Line 1: @@
 Planning is an activity related to model future activities, based on knowledge about how things may play out. Planning is operating between what is predictable and what can happen unexpectedly.
-It is about scheduling resource allocation based on a predefined process (model of future activities) that will play out into the future.
+It is about scheduling [[resource]] allocation based on a predefined process (model of future activities) that will play out into the future.
 It is the preferred mode for addressing future activities of an organization, in a command and control paradigm.
 Planning is more suitable in a predictable environment, such as manufacturing, where a process can be scripted.It is less suitable in a creative environment, which is highly unpredictable.
-Self organization, or real-time situational adaptation to deal with an issue, is adapted for chaotic situations. Stigmergy is one mechanism that works well in these conditions.
+Planning is more suitable in a predictable environment, such as manufacturing, where a process can be scripted.It is less suitable in a creative environment, which is highly unpredictable. Self organization, or real-time situational adaptation to deal with an issue, is adapted for chaotic situations. [[Stigmergy]] is one mechanism that works well in these conditions.

← Older revision		Revision as of 22:33, 24 November 2021
Line 1:		Line 1:
−	~~Different~~ activities can be ~~planned:~~	+	Planning is an activity related to model future activities, based on knowledge about how things may play out. Planning is operating between what is predictable and what can happen unexpectedly.
		+	It is about scheduling resource allocation based on a predefined process (model of future activities) that will play out into the future.
		+	It is the preferred mode for addressing future activities of an organization, in a command and control paradigm.
		+	Planning is more suitable in a predictable environment, such as manufacturing, where a process can be scripted.It is less suitable in a creative environment, which is highly unpredictable.
		+	Self organization, or real-time situational adaptation to deal with an issue, is adapted for chaotic situations. Stigmergy is one mechanism that works well in these conditions.
		+

	==Planning in ventures and projects==		==Planning in ventures and projects==

@@ Line 1: / Line 1: @@
 Different activities can be planned:
-'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, induces [[stigmergy]], helps the talent allocation process, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
+==Planning in ventures and projects==
 '''Manufacturing''', or production is a more scripted activity, which can be better planned. The planning includes work that needs to be done and resources that need to be consumed or used. The plan becomes a script, which is designed to optimize parameters such as efficiency, environmental impact, social aspects of work, etc.
 NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience (ex. [https://trello.com/ Trello]). If planning and logging are done in two different places, we create an overhead, the task of transferring data from the planning environment to the logging environment, work that no one likes to do. Even if this transfer can be automated using an API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.
@@ Line 12: / Line 28: @@
 =In relation to NRP-CAS=
 ==Plan small tasks==
-Individuals can plan their daily activities using the ToDo tool in the [[NRP-CAS]].
+'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, induces [[stigmergy]], helps the talent allocation process, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
+The minimal planning is done using the [[NRP-CAS]], employing a methodology that has been formalized using Workflow recipes. See more on the [[Recipe]] page.
 A [[Resource type list]] can also be used to plan tasks and even projects. The difference between a Workflow [[recipe]] and a [[Resource Type list]] is that the first one has one deliverable or output and the second one can have many outputs. There is a way to create other deliverables in Workflow recipes.
@@ Line 28: / Line 40: @@
 To plan a [[venture]] just go to the [http://nrp.sensorica.co/accounting/plan-from-recipe/ Plan Work Order Using Recipe]. You can get there from the [http://nrp.sensorica.co/accounting/demand/ Demand] page.

← Older revision		Revision as of 20:28, 10 November 2021
Line 8:		Line 8:


−	NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience (ex. [https://trello.com/ Trello]). If planning and logging are done in two different places, we create an overhead, the task of transferring data from the planning environment to the logging environment, work that no one ;likes to do. Even if this transfer can be automated using an API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.	+	NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience (ex. [https://trello.com/ Trello]). If planning and logging are done in two different places, we create an overhead, the task of transferring data from the planning environment to the logging environment, work that no one likes to do. Even if this transfer can be automated using an API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.

	=In relation to NRP-CAS=		=In relation to NRP-CAS=

@@ Line 1: / Line 1: @@
 Different activities can be planned:
-'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, helps with the delegation of tasks, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
+'''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, induces [[stigmergy]], helps the talent allocation process, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
-'''Projects''' are planned up to a certain point. We need to remain compatible with the open way of development, which is agile. There we need to strike the right balance between planning and emergence. Experience within [[Sensorica]] shows that plans in projects always change, since the environment is very dynamic.
+'''[[Projects]]''' or [[ventures]] are planned up to a certain point. [[Sensorica]] leans a lot on the stigmergic way of structuring collaborative work, although some planning is also done by the [[core group]]. The process is  very agile, a balance between planning and emergence.
-'''Manufacturing''', or production is a more scripted activity, which can be better planned. The planning includes work that needs to be done, materials that need to be consumed or used, spaces, etc.
+'''Manufacturing''', or production is a more scripted activity, which can be better planned. The planning includes work that needs to be done and resources that need to be consumed or used. The plan becomes a script, which is designed to optimize parameters such as efficiency, environmental impact, social aspects of work, etc.
-NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience. If planning and logging are done in two different places, we create the task of transferring data from the planning environment to the logging environment, which represents extra work that no one wants to do in an open environment. Even if this transfer can be done automatically using some API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.
+NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience (ex. [https://trello.com/ Trello]). If planning and logging are done in two different places, we create an overhead, the task of transferring data from the planning environment to the logging environment, work that no one ;likes to do. Even if this transfer can be automated using an API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.
 =In relation to NRP-CAS=

@@ Line 3: / Line 3: @@
 '''Tasks''' pup up every day within an OVN. In most cases, [[affiliates]] just do stuff as the need arises, without creating tasks in a planning and management tool, such as the [[NRP-CAS]]. Creating tasks makes activity more transparent, helps with the delegation of tasks, and makes logging of activities more accountable, etc. There is a balance to strike between bothering to create a task for everything and being efficient doing what's necessary.
-'''Projects''' are planned up to a certain point. We need to remain compatible with the open way of development, which is agile. There we need to strike the right balance between planning and emergence. Experience within [[SENSORICA]] shows that plans in projects always change, since the environment is very dynamic.
+'''Projects''' are planned up to a certain point. We need to remain compatible with the open way of development, which is agile. There we need to strike the right balance between planning and emergence. Experience within [[Sensorica]] shows that plans in projects always change, since the environment is very dynamic.
 '''Manufacturing''', or production is a more scripted activity, which can be better planned. The planning includes work that needs to be done, materials that need to be consumed or used, spaces, etc.
-NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[SENSORICA]] uses the [[NRP-CAS]] to do both. In the past, some [[SENSORICA]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience. If planning and logging are done in two different places, we create the task of transferring data from the planning environment to the logging environment, which represents extra work that no one wants to do in an open environment. Even if this transfer can be done automatically using some API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.
+NOTE: It is highly advised that planning and [[logging]] are done in the same place. [[Sensorica]] uses the [[NRP-CAS]] to do both. In the past, some [[Sensorica]] affiliates have proposed to use other planning tools made by third parties that have better user interface and experience. If planning and logging are done in two different places, we create the task of transferring data from the planning environment to the logging environment, which represents extra work that no one wants to do in an open environment. Even if this transfer can be done automatically using some API, we we still create extra work that requires more specialized and rare skills, which is to maintain the API, so that the two services continue to talk to each others as they both evolve.
-=In relation to NRP-VAS=
+=In relation to NRP-CAS=
 ==Plan small tasks==
 You can schedule and plan small tasks using the [[NRP-CAS]] by employing [[processes]]. Process are created in context, i.e. for [[projects]]. The creation of a process needs to specify a project.
-Individuals can plan their daily activities using the ToDo tool in the [[NRP-VAS]].
+Individuals can plan their daily activities using the ToDo tool in the [[NRP-CAS]].
@@ Line 27: / Line 27: @@
 Some methodologies have been designed by [[Tibi]], [[Fernando]] and [[Lynn]], with the help of [[Bob]]. All methodologies are templates that anyone can fork and improve.
-To plan a project just go to the [http://nrp.sensorica.co/accounting/plan-from-recipe/ Plan Work Order Using Recipe]. You can get there from the [http://nrp.sensorica.co/accounting/demand/ Demand] page.
+To plan a [[venture]] just go to the [http://nrp.sensorica.co/accounting/plan-from-recipe/ Plan Work Order Using Recipe]. You can get there from the [http://nrp.sensorica.co/accounting/demand/ Demand] page.