Agility is not a prerogative of only software project management
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
i am of the view that without agility, project management is only operations management. The so called tag of waterfall management is said to attract the non agility as character. I feel it is perception and not reality. Without agility and consideration of importance of all human involved as value adding elements project mangement cant exist. It is insulting to those workers and also the insult of process of project management when the workers realising the infrastructure or other industrial projects are tagged as liabilities and not assets to the business or project. Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
May 10, 2020 4:47 AM
Replying to Peter Ambrosy
...
Agility ist about high responsiveness, speed, adaptiveness, cultural change and especially about values, behaviors and mindset. Agility cannot be planned and has no end-state. There is no silver-bullet or blueprint for agility. Agility deals with complexity, regardless of industry and project life-cycle.
Dear Peter
Further to my reply i would like to say the following :
My point was the every project or day to day living needs agility for enhancing the possibility of generating successful outcome.. In case of projects the systems cant be set and that closely defined as the entire path of project goes through continuous dynamic environment requiring decisions to be made.,let it be any kind of project or Industry... In case of operation management the systems or steps of operations are optimised based on study ,considering the sustainable degree of agility/swiftness in operation --but there also, in abnormal --other than set and well defined situations agility needs to be exhibited as a deligent operation. ( what I mean to state in my first statement is -- to that extent agility is not part of operations management) So agility shall be integral part of life.
My point was that agile manifesto considers software project worker as an asset and not a cost to the project while the contributing workers of projects other than software projects as Expense to the project.
I differ here and of the view that all the projects whether softtware or infrastructure or construction or any other industrial project are equally complex ,ambiguous ,uncertain demanding terrific deligence and agility to respond to changing demands and hence all those contribute to such projects are equally an asset and not just expence. In fact many large projects undergo tremendous turmoil and terrific nerve breaking uncertaities as the gestation period of such projects run in couple of years and the degree of agility required for making right decisions is very critical for success of the project (not necessarily only speed, at times as an agile act speed of execution is needed to be lowered)
I would like you to throw your thought process on this important issue of recognising all the contributing workers should as assets and not an expense for the project vis a vis what is stated in the agile manifesto.
Look forward to your reply
Thanks once again
Warm Regards
Mohan
...
1 reply by David Portas
May 11, 2020 1:24 PM
David Portas
...
Hi Mohan, you seem to be mistaken about the Agile Manifesto (agilemanifesto.org) In the English version it doesn't mention the words "asset" or "expense". It does mention individuals and people of course but it doesn't say anything about workers or about industries other than software development. Are you referring to something said elsewhere?
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
May 11, 2020 9:44 AM
Replying to Mohan Kulkarni
...
Dear Peter
Very aptly put that Agility deals with complexity ireespective of any industry and Project life cycle.
Yes it is a state of mind and all about quick adaptability to the changing demands or situations.
Thanks for excellent summary
Warm Regards
Mohan
I would argue than humanity was responsive, adaptive, quick if required, changing and dealing with different values and mindsets long before the label of 'agile' was invented. We also always dealt with complexity (which is a individual perspective anyhow).
I do not even see a benefit in bringing these components together under one umbrella. Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
May 11, 2020 3:18 AM
Replying to Thomas Walenta
...
Mohan
yes, I also feel a lack of respect on the side of the agile proponents.
The agile movement in my view was founded as a potential solution to problems caused by uncertainty in SW development. Still there are uncertainties, but some causes and risks have been shifted to business. POs are expected to handle this, what traditionally a project manager would do.
As to the lack of respect, the manifesto stipulated a belief system that needs to distinguish itself from other belief systems. It does this by devaluation of features of the other system, and also by hijacking features that are considered useful.
As for people, anyone is cost factor and an asset at the same time. And food if you walk thru the jungle.
Again, setting up comparisons that heighten your side vs others is a technique to sell your belief system, not a fact based argument.
Dear Thomas
I agree with you totally
Warm Regards
Mohan Saving Changes...
Dear Peter
Further to my reply i would like to say the following :
My point was the every project or day to day living needs agility for enhancing the possibility of generating successful outcome.. In case of projects the systems cant be set and that closely defined as the entire path of project goes through continuous dynamic environment requiring decisions to be made.,let it be any kind of project or Industry... In case of operation management the systems or steps of operations are optimised based on study ,considering the sustainable degree of agility/swiftness in operation --but there also, in abnormal --other than set and well defined situations agility needs to be exhibited as a deligent operation. ( what I mean to state in my first statement is -- to that extent agility is not part of operations management) So agility shall be integral part of life.
My point was that agile manifesto considers software project worker as an asset and not a cost to the project while the contributing workers of projects other than software projects as Expense to the project.
I differ here and of the view that all the projects whether softtware or infrastructure or construction or any other industrial project are equally complex ,ambiguous ,uncertain demanding terrific deligence and agility to respond to changing demands and hence all those contribute to such projects are equally an asset and not just expence. In fact many large projects undergo tremendous turmoil and terrific nerve breaking uncertaities as the gestation period of such projects run in couple of years and the degree of agility required for making right decisions is very critical for success of the project (not necessarily only speed, at times as an agile act speed of execution is needed to be lowered)
I would like you to throw your thought process on this important issue of recognising all the contributing workers should as assets and not an expense for the project vis a vis what is stated in the agile manifesto.
Look forward to your reply
Thanks once again
Warm Regards
Mohan
Hi Mohan, you seem to be mistaken about the Agile Manifesto (agilemanifesto.org) In the English version it doesn't mention the words "asset" or "expense". It does mention individuals and people of course but it doesn't say anything about workers or about industries other than software development. Are you referring to something said elsewhere? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 11, 2020 10:23 AM
Replying to Mohan Kulkarni
...
Dear David
Thanks for the confirmation that agility is not confined to Software. My point was the every project or day to day living needs agility for enhancing the possibility of generating successful outcome.. In case of projects the systems cant be set and that closely defined as the entire path of project goes through continuous dynamic environment requiring decisions to be made.,let it be any kind of project or Industry... In case of operation management the systems or steps of operations are optimised based on study ,considering the sustainable degree of agility/swiftness in operation --but there also, in abnormal --other than set and well defined situations agility needs to be exhibited as a deligent operation. So agility shall be integral part of life.
My point was that agile manifesto considers software project worker as an asset and not a cost to the project while the contributing workers of projects other than software projects as Expense to the project.
I differ here and of the view that all the projects whether softtware or infrastructure or construction or any other industrial project are equally complex ,ambiguous ,uncertain demanding terrific deligence and agility to respond to changing demands and hence all those contribute to such projects are equally an asset and not just expence. In fact many large projects undergo tremendous turmoil and terrific nerve breaking uncertaities as the gestation period of such projects run in couple of years and the degree of agility required for making right decisions is very critical for success of the project (not necessarily only speed, at times as an agile act speed of execution is needed to be lowered)
I would like you to throw your thought process on this important issue of recognising all the contributing workers should be recognised as assets and not an expense for the project vis a vis what is stated in the agile manifesto.
Look forward to your reply
Thanks once again
Warm regards
Mohan
Hi Mohan Agile and Lean are totally different things. The problem is some people think that are the same. In fact, Agile was born when a group was created in USA at DoD/NSF in 1990 level for searching a new way to deal with a predicted future world .I do not agree with you about your interpretation on how the Manifiesto consider workers. It say nothing about that. And here is a debate on other field. For me, what I am sustain and debating into each place I had the pleasure to work, workers are "assets" to call them in some way. No matter they are working to create software products or not. Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
May 11, 2020 10:47 AM
Replying to Mohan Kulkarni
...
Dear Sergio
Thanks for your response.
I agree with you Waterfall is a kind of project life cycle while agile is an approach and projects can have any of the project life cycle and run accordingly.Agile has roots in Lean princiiple established by Toyota.
My point was the every project or day to day living needs agility for enhancing the possibility of generating successful outcome.. In case of projects the systems cant be set and that closely defined as the entire path of project goes through continuous dynamic environment requiring decisions to be made.,let it be any kind of project or Industry... In case of operation management the systems or steps of operations are optimised based on study ,considering the sustainable degree of agility/swiftness in operation --but there also, in abnormal --other than set and well defined situations agility needs to be exhibited as a deligent operation. ( what I mean to state in my first statement is -- to that extent agility is not part of operations management) So agility shall be integral part of life.
My point was that agile manifesto considers software project worker as an asset and not a cost to the project while the contributing workers of projects other than software projects as Expense to the project.
I differ here and of the view that all the projects whether softtware or infrastructure or construction or any other industrial project are equally complex ,ambiguous ,uncertain demanding terrific deligence and agility to respond to changing demands and hence all those contribute to such projects are equally an asset and not just expence. In fact many large projects undergo tremendous turmoil and terrific nerve breaking uncertaities as the gestation period of such projects run in couple of years and the degree of agility required for making right decisions is very critical for success of the project (not necessarily only speed, at times as an agile act speed of execution is needed to be lowered)
I would like you to throw your thought process on this important issue of recognising all the contributing workers should as assets and not an expense for the project vis a vis what is stated in the agile manifesto.
Look forward to your reply
Thanks once again
Warm Regards
Mohan
Dear Sergio
Thanks for your response
I agreev with you agility and lean are not the same things .What i say is agile thinking is having some roots in lean thinking.
The software projects are considered and said to be knowledge projects and full of uncertainties and Agile is said to deal with knowledge Power and those uncertainties. Thus the people working on software projects are termed as knowledge workers.On this background it is said that Industrial projects are such that the upfront planning can be done as there are not those many uncertainties and hence predictive life cycle works good.
Here i expressed my opinion stating that not only software but all projects including industrial projects cant be really accomplished successfully without knowledge and agility mind set.
Thanks for clarifying that all workers who work on any kind of project including software and industrial projects are assets to the project and not just expense.
Warm regards
Mohan
...
1 reply by Sergio Luis Conte
May 12, 2020 7:56 AM
Sergio Luis Conte
...
Now I understood. What you stated about considering software workers like knowledge workers was (as far as I know) a paper publised in 2005 by Thomas Davenport. But it was not taken into account to much mainly because it was fully debatible and not to much to sustain because: they say software creation is about to create and distribute knowledge. Just to comment, because my Ph.D degree, I am a researcher on the field working with some Universities on the world. I am making this comment just because I have the opportunity to debate it in extense. But it does not say nothing beyond the fact I have the opportunity to interact with others regarding this line of thinking.
Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
May 10, 2020 5:21 AM
Replying to David Portas
...
Agility is certainly not confined to software. The distinction you are making between project and operations management is an interesting one. A logical conclusion of organisational agility seems to be that the distinction between projects and business-as-usual all but disappears. The argument goes that if you are agile in what you do every day then you don't need anything called a "project" to become more agile - you just need to focus on delivering valuable products and services.
Dear Davis
I agree with you that in Agile Manifesto neither expense nor asset word appears.
My point was software projects are considered as knowledge projects and people working for those as knowledge workers.ans as uncertainities are high agile is said to be the approach to amnage tose. All this is fine with me. Where I differ and do not agree is that the understanding created about other industrial projects can be managed by upfront planning with waterfall--predictive life cycle approach and hence uncertainties are taken care off and hence need not be treated as value driven but task driven,as running things and not changing things,as command and control and not autonomy driven,as standard things and not innovative things,waorkers as cost and not assets, not complex and simple-straight forward.
I am of the opinion that all projects require agility and ready mindset to take on changes as they come and also some upfront planning --without this approach projects can't be successfully accomplished.
I -as aproject manager believe in application of holistic wisdom more than just grammer of management
Trust you appreciate my thought process.
Thanks once again for such a wonderful interaction.
Look forward to many more interactions and exchanges.
Warm regards
Mohan Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 12, 2020 12:43 AM
Replying to Mohan Kulkarni
...
Dear Sergio
Thanks for your response
I agreev with you agility and lean are not the same things .What i say is agile thinking is having some roots in lean thinking.
The software projects are considered and said to be knowledge projects and full of uncertainties and Agile is said to deal with knowledge Power and those uncertainties. Thus the people working on software projects are termed as knowledge workers.On this background it is said that Industrial projects are such that the upfront planning can be done as there are not those many uncertainties and hence predictive life cycle works good.
Here i expressed my opinion stating that not only software but all projects including industrial projects cant be really accomplished successfully without knowledge and agility mind set.
Thanks for clarifying that all workers who work on any kind of project including software and industrial projects are assets to the project and not just expense.
Warm regards
Mohan
Now I understood. What you stated about considering software workers like knowledge workers was (as far as I know) a paper publised in 2005 by Thomas Davenport. But it was not taken into account to much mainly because it was fully debatible and not to much to sustain because: they say software creation is about to create and distribute knowledge. Just to comment, because my Ph.D degree, I am a researcher on the field working with some Universities on the world. I am making this comment just because I have the opportunity to debate it in extense. But it does not say nothing beyond the fact I have the opportunity to interact with others regarding this line of thinking. Saving Changes...