[core-workflow] workflow types: agile (gameplay) vs rigid (process)

[anatoly techtonik]

On Tue, Apr 29, 2014 at 7:27 PM, francis <francismb at email.de> wrote:
> On 04/29/2014 01:33 PM, anatoly techtonik wrote:
>>
>> Agile models [...]
>>
>> adopt it, because it makes projects personalized,
>> requires them to be open.While being open
>> harms profits, the biggest problem is loss of control.
>
> Could you please elaborate on why projects (A) get personalized,
> (B) need to be open and (C) there is a loss of control?

(A) project get personalized, because the driving force
behind achievements is personal and even emotional,
highly dependent on people involved in the process, how
these people feel outside and inside of their working space,
and if they are able to effectively communicate

(B) openness is required to earn trust, in human systems
trust is the main asset for healthy environment. you can not
demand trust (or empathy), and being closed needs a very
good arguments to be trusted. openness is important, because
people want to act independently, and if people are not
aware of the processes that happen in other parts of the
company, they won't have confidence in what are they doing
and won't be able to optimize and seek advice when their
competence is not sufficient. closed systems often lead to
situation where people need to receive permissions too often,
and will lose the gumption soon

(C) loss of control means that stakeholders become dependent
on people.  patents, NDAs, contract obligation and CLAs -
these things exist to protect business from conflicts and
human factor. they create environment that is independent of
humans. this is the opposite of trusting people. loss of control
means that there is no central authority (person or a
committee) who is giving green light - the decision and
responsibility is taken by people who make the solution. these
makes it much more easier to do things. it is only important to
keep team to be cross-disciplinary and practicing (no pure
theorists).

> PS: I'm just asking because from my experience cannot extrapolate
> that points (it may be that my experience here is too small :-))

This is my experience of working with cross-disciplinary teams.
There is a high probability that it is highly dependent on age,
social status, region and mentality, but this is why agile workflows
were born.