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...
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.
...
2 replies by Mohan Kulkarni
May 11, 2020 9:44 AM
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
May 11, 2020 10:54 AM
Mohan Kulkarni
...
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
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.
...
2 replies by Mohan Kulkarni
May 11, 2020 10:23 AM
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
May 12, 2020 1:29 AM
Mohan Kulkarni
...
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
I do not agree with your first statement but let me say that reading your whole post it is because people mix things (not you). Here I go: 1-Waterfall is a life cycle. Agile is an approach. Both are not matter of comparison. 2-Project management can be used with any approach/life cycle without problems. To give an example, in my actual work place, the same person is assigned to lead projects simultaneously where one of them are non-agile based and the other is agile based and is using a framework like Scrum as the mean to use agile approach. Agile was not born in software field But not matter that, if people take the Manifesto for Agile Software Development, read and understand it, and mainly read carefully this https://agilemanifesto.org/history.html, things will be more easy mainly for people like me that are working with agile from the genesis of agile.
...
1 reply by Mohan Kulkarni
May 11, 2020 10:47 AM
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
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Mohan,
I agree with your first sentence, as it implies that project management was agile all along.
In my 30+ years as project manager I always had to be looking out for changes and adapt my strategy to them. Changes came not only from the outside, but also as we got deeper into the projects, we gained insights and knowledge we did not have before. So the plans and requirements were 'progressively elaborated', which is a term from PMBoK Guide since ages.
We project managers have to deal with future and make our customers and team secure in the way they see a way forward. We provide security. Sometimes we can show them the vision and idea of the output of the project, be it a building, an application, a medical treatment or a filled bank account. Then we may show them a sequence of steps how to get there, and if the type of project has been done before, we can build on that experience. If not, we provide them with an initially trial and error approach, timeboxing and iterating steps (that was what the PDCA cycle was and Barry Boehm's cyclic model for SW, in 1988). Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
Dear Thomas
Thanks for your response
My point was those who work on software projects are considered as knowledge workers and said to be assets and not expense to the project --this sends a descriminative message to other workers on industrial projects or infrastructural projects----The root of this thinking is in software projects the uncertainty is of a higher order and many time customer himself is not clear about the requirements--but this is equally true for industrial or infrastructural projects.---the uncertainty ,risks, initially unknown requirements keep evolving and many times the degree of uncertainty ,ambiguity, complexity or risks are terriably high in case of industrial or infrastructural or many other projects that projects get stalled for the solutions---and still these projects are said to be waterfall projects with a descriminative tone to it.
I find that this is not in tune with the basic value of Respect that we preach in Project management. ---If you see the 12 values of agile manifesto it clearly states the software industry personnel are knowledge workers and hence are assets while workers on other projects are considered as expense.--Hence the concern
I would request you to throw your understanding and thoughts on this aspect.
Thanks once again and look forward to have regular interactions
Warm Regards
Mohan
...
1 reply by Thomas Walenta
May 11, 2020 3:18 AM
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.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
May 11, 2020 2:49 AM
Replying to Mohan Kulkarni
...
Dear Thomas
Thanks for your response
My point was those who work on software projects are considered as knowledge workers and said to be assets and not expense to the project --this sends a descriminative message to other workers on industrial projects or infrastructural projects----The root of this thinking is in software projects the uncertainty is of a higher order and many time customer himself is not clear about the requirements--but this is equally true for industrial or infrastructural projects.---the uncertainty ,risks, initially unknown requirements keep evolving and many times the degree of uncertainty ,ambiguity, complexity or risks are terriably high in case of industrial or infrastructural or many other projects that projects get stalled for the solutions---and still these projects are said to be waterfall projects with a descriminative tone to it.
I find that this is not in tune with the basic value of Respect that we preach in Project management. ---If you see the 12 values of agile manifesto it clearly states the software industry personnel are knowledge workers and hence are assets while workers on other projects are considered as expense.--Hence the concern
I would request you to throw your understanding and thoughts on this aspect.
Thanks once again and look forward to have regular interactions
Warm Regards
Mohan
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.
...
1 reply by Mohan Kulkarni
May 11, 2020 11:27 AM
Mohan Kulkarni
...
Dear Thomas
I agree with you totally
Warm Regards
Mohan
Saving Changes...
Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
Thank you so much for the clarifying clear reply
regards
Mohan 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
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
...
1 reply by Thomas Walenta
May 11, 2020 11:03 AM
Thomas Walenta
...
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 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 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
...
1 reply by Sergio Luis Conte
May 11, 2020 1:31 PM
Sergio Luis Conte
...
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 10, 2020 7:58 AM
Replying to Sergio Luis Conte
...
I do not agree with your first statement but let me say that reading your whole post it is because people mix things (not you). Here I go: 1-Waterfall is a life cycle. Agile is an approach. Both are not matter of comparison. 2-Project management can be used with any approach/life cycle without problems. To give an example, in my actual work place, the same person is assigned to lead projects simultaneously where one of them are non-agile based and the other is agile based and is using a framework like Scrum as the mean to use agile approach. Agile was not born in software field But not matter that, if people take the Manifesto for Agile Software Development, read and understand it, and mainly read carefully this https://agilemanifesto.org/history.html, things will be more easy mainly for people like me that are working with agile from the genesis of agile.
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
...
1 reply by Mohan Kulkarni
May 12, 2020 12:43 AM
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