Perry RamenIT Service Manager Coordinator| LinkbynetVacoas, Mauritius
I come from a software development background and have 20 years of experience in IT, today I’m working as IT Project Manager and Service Delivery Co-ordinator.
Agile is a word that has been attributed to a way of doing things. Several years before the word Agile was attributed to the Agile techniques we were already working in a similar way as and when required. Where incremental delivery was possible, incremental delivery was being done. Where iterative development was possible, iterative development was being done. Agile called techniques are not new in themselves.
I'm sure that most Project Managers will agree with me that we have always known how to approach solutions delivery before some people have put a name to it and called it Agile.
Hybrid Project Management is not new. Before Agile, Hybrid existed.
Please share your thoughts if you agree and disagree. Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
There is a big mistake outside there. Agile is not a way of doing things. Agile is a way of behave and thinking with focus on client, value and quality. This is the definition created on the place where Agile was formaly defined in 1990. You can apply Agile with any type of life cycle, for example waterfall. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I somehow agree with you Perry. Hybrid was always there and now it has a name Agile-Watergfall Hybrid. One more thing, Agile is more of a mindset than it is a way of doing things. Saving Changes...
Lenka PincotChief of Staff to the CEO| Project Management InstituteParis, France
I believe that people use common senses and apply various principles to situations to improve their outcome. So from this perspective methods and frameworks sometimes become blended or hybrids are created. But that is different from selecting and applying a method for an organization. It is different when you manage a project and decide to deliver increments on a particular delivery or when you join organization that declared a method to be used to improve results across processes and functions. For these situations it is useful to have guidelines because it is about educating larger amount of people and transitioning them to a specific way of working. So to your question, I think that these various approaches existed and were indeed applied, but what is happening now is a lot of codification and formalization to support wide adoption. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
On the other side I firmly believe that the worst thing we can do is name things like something project manager. Here an example of my actual work place. We have five different life cycles which address different approaches. The same person is assigned at the same time to lead more than one project where some of them are running on Agile based environments (including the use of Agile based method) while other are running on non-Agile. So, how could we name that person?. somethingproject management or somethingproject manger does not exist. What exist is project management performed inside different environments. Saving Changes...
Community Champion
