Parallel activities

[Ypot]

Could there be a way to represent parallel processes?

For example, if in the making of a furniture, a factory could work simultaneously metal and plastic, the sequential order of the kanban board would lose sense:

*  project 1                                                  :proj:doing:
** task in project 1                                            :metal:
** task in project                                               :plastic:

* Table1
#+BEGIN: tagged :columns "doing(DOING)|metal(METAL)|plastic(PLASTIC)|done(DONE)" :match "level>0" :truncation-string "…"
| DOING     | METAL             | PLASTIC         | DONE |
|-----------+-------------------+-----------------+------|
| project 1 |                   |                 |      |
|           | task in project 1 |                 |      |
|           |                   | task in project |      |
#+END:

In that table, it would seem that metal work must be finished, before plastic work can start. But it's wrong, both task could be done simultaneously.

Desired board:

|-----------+-------------------+------|
| DOING     | PLASTIC           | DONE |
|-----------+-------------------+------|
| project 1 |                   |      |
|           | task in project   |      |
|-----------+-------------------+------|
|           | METAL             |      |
|-----------+-------------------+------|
|           |                   |      |
|           | task in project 1 |      |

Maybe we could get to that using "intermediate" boards? Like:
a + b = desired board, where
a:

#+BEGIN: tagged :columns "doing(DOING)|metal(METAL)|done(DONE)" :match "level>0" :truncation-string "…"
| DOING     | METAL             | DONE |
|-----------+-------------------+------|
| project 1 |                   |      |
|           | task in project 1 |      |
#+END:

b:

#+BEGIN: tagged :columns "doing(DOING)|plastic(PLASTIC)|done(DONE)" :match "level>0" :truncation-string "…"
| DOING     | PLASTIC         | DONE |
|-----------+-----------------+------|
| project 1 |                 |      |
|           | task in project |      |
#+END:

[gizmomogwai]

Why not represent it with less tags :) and then use normal org-kanban.

* IN-PROGRESS Project 1
** DOING Metal
** DOING Plastic
** SEARCHING-FOR-CONTRACTOR Wood

[Ypot]

Why not represent it with less tags :) and then use normal org-kanban.

* IN-PROGRESS Project 1
** DOING Metal
** DOING Plastic
** SEARCHING-FOR-CONTRACTOR Wood

Hi!

I suppose it is quite difficult to implement.

But I will try to explain: It's because activity "saturation" (WIP) happens differently on metal than on plastic.
For example, we could have 8 tasks in DOING. But PLASTIC section could be capable of doing 5 tasks while METAL section could only do 3.

If METAL section is already working on 3 tasks, I can't "promote" new tasks to DOING althoug its "WIP" could admit more. METAL section could be saturated, while PLASTIC section iddle.

Not sure if I explained myself more or less.

I like much org-tagged; as said before, I think that org-kanban for a GTD user could be a little incompatible :/

Thanks!

[gizmomogwai]

Mhh .. interesting ... thats the good and bad thing about tags ...
one the one hand you can almost express everything in them, on the other hand it gets hard to collect that information.

i wonder if we need another "view" to show this saturation thing or if it has place in org-tagged... the other thing would simply show columns (ideally full filled, no blank spaces on the top) for the different crafts and perhaps we could add somehow the heading to which a project belongs at the front of the subtasks name.

* Project1
** left side :metal:
** right side :metal:plastic:
* Project2
** top :metal:
** bottom :plastic:

could perhaps yield:

|metal|plastic|
|-------------|
|p1/left side| |
|p1/right side|p1/right side|
|p2/top| p2/bottom |

or perhaps not a table but just a simple report function .. e.g. one that counts the tasks in the different crafts?

[Ypot]

Now I understand that table... not bad!!!

Something like this, I understand you are proposing:

| DOING     | METAL             | PLASTIC         | DONE   |
|-----------|-------------------------------------|-------- |
| project 1 |                                    |        |
|           | task in project 1                  |        |
|           |                                    | task 3 |
|           |                     task in project |        |

vs.

|-----------+-------------------+------|
| DOING     | PLASTIC           | DONE |
|-----------+-------------------+------|
| project 1 |                   |      |
|           | task in project   |      |
|-----------+-------------------+------|
|           | METAL             |      |
|-----------+-------------------+------|
|           |                   |      |
|           | task in project 1 |      |

I think it is too soon for org-tagged to renounce to the board (table) in favor of a report ;D

[gizmomogwai]

or even

| DOING     | METAL             | PLASTIC         | DONE   |
|-----------+-------------------+-----------------+--------|
| project 1 |                   |                 |        |
|           | task in project 1 |                 |        |
|           |                   |                 | task 3 |
|           |                   | task in project |        |

which should already be possible now ... only problem might be the tag inheritance, but you found a way to disable that.