Mario CoquillatProject, Program and Portfolio consultant, mentor and trainer| CoquillatPMSan Pedro Del Pinatar, Murcia, Spain
In an agile conference a speaker explained his view about what is coming after "agile"....and he said "Resilience, as a strategy to absorb disruptive changes in the industry"
Changes are going to be so fast than even with an adaptative approach you´re not going to be able to react to them.
Your insights would be much appreciated. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Dec 18, 2018 4:13 PM
Replying to Stelian ROMAN
...
It's pretty obvious: Lean. DevOps, Kanban... although initially Agile was a replacement for Lean. It didn't work :)
@Mario, Lean is about eliminating waste by standardisation. Agile is promoting change, about prototyping and adaptation. The two concepts are fundamentally opposed although both are seeking the delivery of better products. Lean by cutting costs and ensuring quality and Agile by responding fast to changes in requirements.
Agile can't be a subset of Lean.
...
1 reply by Mario Coquillat
Dec 21, 2018 1:48 AM
Mario Coquillat
...
@Stelian. This is not from me. This is from "Agile Pratice Guide".
"Figure 2-4 also shows Agile and the Kanban Method as subsets of lean. This is because they are named instances of lean thinking that share lean concepts as "focus on value", "small batch sizes" and "elimination of waste".
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Dec 20, 2018 1:28 PM
Replying to Mario Coquillat
...
You´re right. First step is about integration & automation.
Streamlining and automating tasks through integration and process automation.
Integration and automation are not new, they are the essence of Lean SIx SIgma and are done in manufacturing for more than 100 years. Automation doesn't mean computers. For the younger generation it is good to know that the first media to store data (punch cards) was not invented for computers but for manufacturing, to automate the weaving.
It is interested that most of 'post Agile' proposals are a sort of back to the future...
'Those who do not learn history are doomed to repeat it.' Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
I agree 100% with Sergio about the buzzword phenomena. It always amazes when the 'young ones' talk about these things like they are new. Like he said, these things existed for many, many years and then somebody came along and commercialized it by giving it a new fancy name. This new fancy name is usually so fancy that more energy is spend on arguing what is means and actually doing something. What comes next? Whatever new buzzword somebody thinks up and gets traction. Will it be new? Most probably not, just the wrapper will be but the guy who was born in the year 1995 will consider it the best thing since sliced bread. And the all job titles will change to include this new adjective like we have now - Agile this, Agile that.
BTW I do and always will disagree with the statement that agile has nothing to do with predictive and adaptive. Putting any terminology and definitions aside it is logical that the more adaptive you are the more agile you are and vice versa. While you could probably apply agility to a predictive environment you ability to adapt i.e. be agile, diminishes to the point where it just does not add any value.
My annoyance this is tendency is so great that I wrote an article about it recently :)
3 replies by Keith Novak, Sergio Luis Conte, and Stelian ROMAN
Dec 21, 2018 1:09 AM
Keith Novak
...
Many people want a cookbook that explains how to arrive at a solution rather than understand the theory that will allow them to find their own solutions.
I recently had a coworker who attended a 3 day seminar on one of the latest agile buzzwords, and came back convinced that if everything was not done exactly like the instructors taught them, all would be lost.
I am by no means an expert in agile, but reasonably well read and my immediate impression was that if unwavering dogma is required to be flexible, I think you missed the point in those 3 days of lectures.
Dec 21, 2018 4:29 AM
Sergio Luis Conte
...
I like the article very much. Mainly when you wrote "what a hell is an agile BA?". In some forums I made jokes on that saying "a BA that has the ability to run faster than stakeholders when things go wrong". English is not my first language then I could not understand the sence but calling things something BA/PM/Project Mangement etc contributes to general confusion and jeopardize the intentions of some people that are tying to find a new job. Just let me a comment about adaptative or predictive. I use sometimes some statement like you wrote perhaps because I have not a good english. What I tried to say when I wrote that is some people think that Agile is tied to the life cycle model. That is not right. As Lean, Agile is not tied to the life cycle model. Indeed, I fully agree with you about adaptive model helps a lot to implement Agile.
Dec 21, 2018 5:19 AM
Stelian ROMAN
...
Nice article. Indeed what the hell are Agile XXXX? will an "Agile PM' manage only Agile projects?
And on the topic: if Agile is replaced by something else what the Agile XXXX will do? Get another certification to change their prefix?
I agree 100% with Sergio about the buzzword phenomena. It always amazes when the 'young ones' talk about these things like they are new. Like he said, these things existed for many, many years and then somebody came along and commercialized it by giving it a new fancy name. This new fancy name is usually so fancy that more energy is spend on arguing what is means and actually doing something. What comes next? Whatever new buzzword somebody thinks up and gets traction. Will it be new? Most probably not, just the wrapper will be but the guy who was born in the year 1995 will consider it the best thing since sliced bread. And the all job titles will change to include this new adjective like we have now - Agile this, Agile that.
BTW I do and always will disagree with the statement that agile has nothing to do with predictive and adaptive. Putting any terminology and definitions aside it is logical that the more adaptive you are the more agile you are and vice versa. While you could probably apply agility to a predictive environment you ability to adapt i.e. be agile, diminishes to the point where it just does not add any value.
My annoyance this is tendency is so great that I wrote an article about it recently :)
Many people want a cookbook that explains how to arrive at a solution rather than understand the theory that will allow them to find their own solutions.
I recently had a coworker who attended a 3 day seminar on one of the latest agile buzzwords, and came back convinced that if everything was not done exactly like the instructors taught them, all would be lost.
I am by no means an expert in agile, but reasonably well read and my immediate impression was that if unwavering dogma is required to be flexible, I think you missed the point in those 3 days of lectures. Saving Changes...
Mario CoquillatProject, Program and Portfolio consultant, mentor and trainer| CoquillatPMSan Pedro Del Pinatar, Murcia, Spain
Dec 20, 2018 3:34 PM
Replying to Stelian ROMAN
...
@Mario, Lean is about eliminating waste by standardisation. Agile is promoting change, about prototyping and adaptation. The two concepts are fundamentally opposed although both are seeking the delivery of better products. Lean by cutting costs and ensuring quality and Agile by responding fast to changes in requirements.
Agile can't be a subset of Lean.
@Stelian. This is not from me. This is from "Agile Pratice Guide".
"Figure 2-4 also shows Agile and the Kanban Method as subsets of lean. This is because they are named instances of lean thinking that share lean concepts as "focus on value", "small batch sizes" and "elimination of waste".
...
1 reply by Sergio Luis Conte
Dec 21, 2018 10:29 AM
Sergio Luis Conte
...
The worst thing you can do is pay attention to the Agile Practice Guide. I was part of the group of authors and reviewers of PMBOK and the agile guide was never reviewed nor delivered for public review so you can find "collisions" between both. And not matter one of the examples on the Agile Practice Guide was provided for me. I am really sad on the result. At least, the name must be "Practice Guide for Agile Software Delivery".
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 21, 2018 12:28 AM
Replying to Anton Oosthuizen
...
I agree 100% with Sergio about the buzzword phenomena. It always amazes when the 'young ones' talk about these things like they are new. Like he said, these things existed for many, many years and then somebody came along and commercialized it by giving it a new fancy name. This new fancy name is usually so fancy that more energy is spend on arguing what is means and actually doing something. What comes next? Whatever new buzzword somebody thinks up and gets traction. Will it be new? Most probably not, just the wrapper will be but the guy who was born in the year 1995 will consider it the best thing since sliced bread. And the all job titles will change to include this new adjective like we have now - Agile this, Agile that.
BTW I do and always will disagree with the statement that agile has nothing to do with predictive and adaptive. Putting any terminology and definitions aside it is logical that the more adaptive you are the more agile you are and vice versa. While you could probably apply agility to a predictive environment you ability to adapt i.e. be agile, diminishes to the point where it just does not add any value.
My annoyance this is tendency is so great that I wrote an article about it recently :)
I like the article very much. Mainly when you wrote "what a hell is an agile BA?". In some forums I made jokes on that saying "a BA that has the ability to run faster than stakeholders when things go wrong". English is not my first language then I could not understand the sence but calling things something BA/PM/Project Mangement etc contributes to general confusion and jeopardize the intentions of some people that are tying to find a new job. Just let me a comment about adaptative or predictive. I use sometimes some statement like you wrote perhaps because I have not a good english. What I tried to say when I wrote that is some people think that Agile is tied to the life cycle model. That is not right. As Lean, Agile is not tied to the life cycle model. Indeed, I fully agree with you about adaptive model helps a lot to implement Agile. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Dec 21, 2018 12:28 AM
Replying to Anton Oosthuizen
...
I agree 100% with Sergio about the buzzword phenomena. It always amazes when the 'young ones' talk about these things like they are new. Like he said, these things existed for many, many years and then somebody came along and commercialized it by giving it a new fancy name. This new fancy name is usually so fancy that more energy is spend on arguing what is means and actually doing something. What comes next? Whatever new buzzword somebody thinks up and gets traction. Will it be new? Most probably not, just the wrapper will be but the guy who was born in the year 1995 will consider it the best thing since sliced bread. And the all job titles will change to include this new adjective like we have now - Agile this, Agile that.
BTW I do and always will disagree with the statement that agile has nothing to do with predictive and adaptive. Putting any terminology and definitions aside it is logical that the more adaptive you are the more agile you are and vice versa. While you could probably apply agility to a predictive environment you ability to adapt i.e. be agile, diminishes to the point where it just does not add any value.
My annoyance this is tendency is so great that I wrote an article about it recently :)
Nice article. Indeed what the hell are Agile XXXX? will an "Agile PM' manage only Agile projects?
And on the topic: if Agile is replaced by something else what the Agile XXXX will do? Get another certification to change their prefix? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Dec 21, 2018 1:48 AM
Replying to Mario Coquillat
...
@Stelian. This is not from me. This is from "Agile Pratice Guide".
"Figure 2-4 also shows Agile and the Kanban Method as subsets of lean. This is because they are named instances of lean thinking that share lean concepts as "focus on value", "small batch sizes" and "elimination of waste".
The worst thing you can do is pay attention to the Agile Practice Guide. I was part of the group of authors and reviewers of PMBOK and the agile guide was never reviewed nor delivered for public review so you can find "collisions" between both. And not matter one of the examples on the Agile Practice Guide was provided for me. I am really sad on the result. At least, the name must be "Practice Guide for Agile Software Delivery". Saving Changes...
Mario CoquillatProject, Program and Portfolio consultant, mentor and trainer| CoquillatPMSan Pedro Del Pinatar, Murcia, Spain
@Sergio. Thanks for your information. I´m nearly new to agile and I used this guide as a first reference because it has a hybrid approach which is my current situation.
Any recommendation to read about it?
Thanks!
...
1 reply by Sergio Luis Conte
Dec 26, 2018 10:14 AM
Sergio Luis Conte
...
No problem. In fact, in my actual work place, I am in charge to define process and methods and we have defined our own hybrid method too.
The important thing is the definition of Agile. With that on hand, my recommendation is take a closer look to your organization actual situation analyzing the whole enterprise architecture. With a simple piece of paper is enough,
Then, if you have found what you need inside the PMI´s Agile Practice Guide then go ahead.
If you are creating software products then the "bible" is the Manifesto.
I should said that Agile could be divided into two different worlds: Agile as it was born (enterprise wide) and Agile as it was best implemented or researched (software domain). About Agile as it was born search for Rick Dove´s book "Response Ability". About application of project management in Agile environments here comes my recommendation (I worked with the authors of the books then I lived what they wrote, including using it for non-software products):
-Agile Project Management, Jim Highsmith
-Agile Estimating and Planning, Mike Cohn
-Organizational Patterns for Agile Software Development, Jim Coplien
-Essential Scrum, Kenny Rubin, mainly if you will use Scrum
Saving Changes...
Kevin ColemanSubject Matter Expert, Author, Speaker and Strategic Advisor| - InsightsPa, United States
