Ubuntu work-flow is a push system

[Alberto Salvia Novella]

***************
 THE PROBLEM
***************

According to Lean Management theory, the Ubuntu work- flow is a push system. That is, one which processes (or roles, or people) push their work to the next process regardless of the actual capacity of the next one to cope with more work.

We're creating a bunch of written work (bug reports, studies, surveys...). Usually having this pile of resources is understood to be good for production. But reality is very different:

- It is workforce saved in a can, unused for real project movement.
- Since its storage tends to increase progressively , it is like a black-hole.
- Most this workforce rots before being translated into an improvement for the product (Ubuntu).

And metrics aren't designed at this time to stop this scenario.

***************
 THE SOLUTION
***************

By redesigning metrics about how workforce is distributed along individual processes can boost the productivity, according to Lean experience, between a 400% and a 1700%. This is because it will allow individuals to easily evaluate themselves where the overload in production is, and dynamically reallocate their workforce wherever it is more needed.

This will transform work-flow into a pull system, where production in individual processes are made on demand of the next one. So capability of coping with work is always warranted, and already done work is in constant flow.

******************
 MORE RESOURCES
******************

Please, have a look at these resources; so you can actually understand this report:

DIAGRAMS
- Concept: <http://tinyurl.com/potbs7o>
- Comparative: <http://tinyurl.com/oavbe8z>
- Implementation: <http://tinyurl.com/p5jra3r>
- Example: <http://tinyurl.com/njrj2h9>

PAPERS
- Concept: <http://tinyurl.com/oslzuxr>
- In deep (if you're interested in details): <http://tinyurl.com/o6b6yme>

[Alberto Salvia Novella (es20490446e)]

Priority set to "high", because the bug renders essential features or functionality of the application or dependencies broken or ineffective.

[Alberto Salvia Novella (es20490446e)]

Status changed to "opinion" for One Hundred Papercuts, because this is the status for the main project (work-items-tracker).

[Alberto Salvia Novella (es20490446e)]

Please, can you explain your choices?

[Chris Johnston (cjohnston)]

You provide what you believe to be a problem with no actionable things to
work on. From what I can tell, what you are wanting to do should be
discussed on a mailing list or a UDS session (or both) and then, if an
agreement is reached turned into a BP.

Also, at this point, the work item tracker is maintenance only with no new
work planned on it.

[Alberto Salvia Novella (es20490446e)]

Okay: thank you 🍃