Adaptation of Agile project methodologies are now being implemented rapidly by different level of organizations for increasing their effectiveness. How do you see role of Agile project methodologies in increasing productivity of an organization in general? On the other hand What benefits organizations working on Agile derive, in terms of customer satisfaction and outputs they produce? Saving Changes...
John TiesoAuthor, Lecturer in Business Management| The Catholic University of America, Busch School of Business & EconomicsArlington, Va, United States
Apr 13, 2017 3:33 PM
Replying to Sergio Luis Conte
...
First: Agile Project Management does not exits.What exists is project management performend into Agile environmentes, where you have to take into account that Agile is not software or IT, Agile is not a method or process, Agile did not estar with the Manifesto. Second, you have to define what productivity mean for your organzation. Thrid, Agile is nothing to do with productivity if you take the definition of productivity that becomes from centuries ago from the economic theory.
I have to respectfully disagree here as well. When you adopt agile-type methods, you are producing working products and services much earlier than more traditional approaches. employees have the ability earlier to learn the new products and/or services and use them when finally delivered at a higher production rate, and with less down-time for training at the end of the project. it seems sound to me to agile some of these methods incorporated in your project plans.
...
4 replies by Aaron Porter, Sergio Luis Conte, and Wade Harshman
Apr 14, 2017 12:27 PM
Aaron Porter
...
You are taking about potential. Actual results may vary. There are no guarantees.
Apr 14, 2017 1:48 PM
Sergio Luis Conte
...
John, you are welcome. Please let me say that you are talking about using a method to do something. in this case an agile development method. That is not agile project management. Is the use of an spekcific method to manage a project. On the other side nothing in Agile is about deliver faster. That is one of the things I have to clarify each time some organization hired me to work with Agile. Agile is about focus on client and quality. Thats all. But all the other like cost, time, scope have to be consider according to the initiative conditions. What Agile address inded is all about risk related to do not create the expected solution.
Apr 14, 2017 2:04 PM
Sergio Luis Conte
...
You are welcome. Nothing in Agile including the use of methods is about deliver faster. Is about focus on client and quality. People think that Agile will help to deliver faster, short costs, etc. All of that is not right. I spend time explaining to people that hiring me to implement Agile that Agile is not all that things they think it is. Becuse the focus on client and quality what Agile address is people will get what they need in the estimated time and the estimated cost.
Apr 14, 2017 2:16 PM
Wade Harshman
...
There are some inherent problems with adopting Agile "methods" without first embracing Agile "culture." If your organization isn't Lean, if it can't establish a high degree of trust in your people and your teams, if your organization has no tolerance for mistakes, and if your organization can't remain narrowly focused on the changing needs of the customer, then any Agile experiments will fail.
I have to respectfully disagree here as well. When you adopt agile-type methods, you are producing working products and services much earlier than more traditional approaches. employees have the ability earlier to learn the new products and/or services and use them when finally delivered at a higher production rate, and with less down-time for training at the end of the project. it seems sound to me to agile some of these methods incorporated in your project plans.
You are taking about potential. Actual results may vary. There are no guarantees.
...
1 reply by John Tieso
Apr 14, 2017 12:41 PM
John Tieso
...
Aaron:
There are no guarantees in anything a PM does. Even the most experienced occasionally show failure, in many cases because they used cookie-cutter approaches with which they were most familiar, instead of trying to create methods, techniques, and tools which might better fit the circumstances. using techniques such as Agile, or LSS at the very least stimulate the mind of the PM to approaches not previously tried and possibly more success-proine.
Saving Changes...
John TiesoAuthor, Lecturer in Business Management| The Catholic University of America, Busch School of Business & EconomicsArlington, Va, United States
Apr 14, 2017 12:27 PM
Replying to Aaron Porter
...
You are taking about potential. Actual results may vary. There are no guarantees.
Aaron:
There are no guarantees in anything a PM does. Even the most experienced occasionally show failure, in many cases because they used cookie-cutter approaches with which they were most familiar, instead of trying to create methods, techniques, and tools which might better fit the circumstances. using techniques such as Agile, or LSS at the very least stimulate the mind of the PM to approaches not previously tried and possibly more success-proine. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Apr 14, 2017 11:10 AM
Replying to John Tieso
...
I have to respectfully disagree here as well. When you adopt agile-type methods, you are producing working products and services much earlier than more traditional approaches. employees have the ability earlier to learn the new products and/or services and use them when finally delivered at a higher production rate, and with less down-time for training at the end of the project. it seems sound to me to agile some of these methods incorporated in your project plans.
John, you are welcome. Please let me say that you are talking about using a method to do something. in this case an agile development method. That is not agile project management. Is the use of an spekcific method to manage a project. On the other side nothing in Agile is about deliver faster. That is one of the things I have to clarify each time some organization hired me to work with Agile. Agile is about focus on client and quality. Thats all. But all the other like cost, time, scope have to be consider according to the initiative conditions. What Agile address inded is all about risk related to do not create the expected solution. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Apr 14, 2017 10:30 AM
Replying to Aaron Porter
...
In the conference session I was in on Monday, Lee gave the current failure rate for agile projects as closer to 40%
Thats the problem with this type of statistics. Each person can read it as their convenience. While I am working with Agile from years nothing demostrate that its use will assure not fail. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Apr 14, 2017 11:10 AM
Replying to John Tieso
...
I have to respectfully disagree here as well. When you adopt agile-type methods, you are producing working products and services much earlier than more traditional approaches. employees have the ability earlier to learn the new products and/or services and use them when finally delivered at a higher production rate, and with less down-time for training at the end of the project. it seems sound to me to agile some of these methods incorporated in your project plans.
You are welcome. Nothing in Agile including the use of methods is about deliver faster. Is about focus on client and quality. People think that Agile will help to deliver faster, short costs, etc. All of that is not right. I spend time explaining to people that hiring me to implement Agile that Agile is not all that things they think it is. Becuse the focus on client and quality what Agile address is people will get what they need in the estimated time and the estimated cost. Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
Apr 14, 2017 11:10 AM
Replying to John Tieso
...
I have to respectfully disagree here as well. When you adopt agile-type methods, you are producing working products and services much earlier than more traditional approaches. employees have the ability earlier to learn the new products and/or services and use them when finally delivered at a higher production rate, and with less down-time for training at the end of the project. it seems sound to me to agile some of these methods incorporated in your project plans.
There are some inherent problems with adopting Agile "methods" without first embracing Agile "culture." If your organization isn't Lean, if it can't establish a high degree of trust in your people and your teams, if your organization has no tolerance for mistakes, and if your organization can't remain narrowly focused on the changing needs of the customer, then any Agile experiments will fail.
...
1 reply by Sergio Luis Conte
Apr 14, 2017 2:41 PM
Sergio Luis Conte
...
Agree with you. Each time the organization introduce new ways to do something thw whole organization is impacted. To put this in ssome practices scope is a matter of business analisys and the business analist must perform the activity fomer named "enterprise analysis". In our Case we use Tom Peter's Seve S model where culture is one of the variables to analyze. If you ask me, in my personam experience, culture is what determines if you can apply Agile practices or not. Bur you ever have to take into account the others.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Apr 14, 2017 2:16 PM
Replying to Wade Harshman
...
There are some inherent problems with adopting Agile "methods" without first embracing Agile "culture." If your organization isn't Lean, if it can't establish a high degree of trust in your people and your teams, if your organization has no tolerance for mistakes, and if your organization can't remain narrowly focused on the changing needs of the customer, then any Agile experiments will fail.
Agree with you. Each time the organization introduce new ways to do something thw whole organization is impacted. To put this in ssome practices scope is a matter of business analisys and the business analist must perform the activity fomer named "enterprise analysis". In our Case we use Tom Peter's Seve S model where culture is one of the variables to analyze. If you ask me, in my personam experience, culture is what determines if you can apply Agile practices or not. Bur you ever have to take into account the others. Saving Changes...
Thank you for your answers and support they were great help in determining either implementing Agile based practices would be helpful or not. Saving Changes...
Community Champion
