The Need for Agile
As I start exploring different blogs, books and courses (which I probably recommend on future posts) I go back to my good old Agile Methodologies.
By definition Agile methodology is "a type of project management process, mainly used for software development, where demands and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customers". Now, if we look closer we can see how a Product Manager fits in the middle of all this, a PM has the mission to be at the center of this whole process, but not as the source but more of a balance core who handles multiple tasks and wears different hats.
Agile brings a perfect balance between Planning all the way to Deployment/Review, this balance is not only kept by the PM but by the different inputs from clients and developers who at the same time value each of the tasks and the effects of spending time on a specific product.
In previous jobs I have applied Agile as a way to track and measure code deployment but never experienced it in a place where code or software was more like a product that needed to be deliver. Currently, I'm starting to realize that Agile is more beneficial not as a stand alone piece of process but it makes more sense when it is integrated with other processes as well, so when a PM takes into account multiple factors which might affect the delivery of a product, we can have a better chance of delivering a product within schedule, budget and with most specifications.
By definition Agile methodology is "a type of project management process, mainly used for software development, where demands and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customers". Now, if we look closer we can see how a Product Manager fits in the middle of all this, a PM has the mission to be at the center of this whole process, but not as the source but more of a balance core who handles multiple tasks and wears different hats.
Agile brings a perfect balance between Planning all the way to Deployment/Review, this balance is not only kept by the PM but by the different inputs from clients and developers who at the same time value each of the tasks and the effects of spending time on a specific product.
In previous jobs I have applied Agile as a way to track and measure code deployment but never experienced it in a place where code or software was more like a product that needed to be deliver. Currently, I'm starting to realize that Agile is more beneficial not as a stand alone piece of process but it makes more sense when it is integrated with other processes as well, so when a PM takes into account multiple factors which might affect the delivery of a product, we can have a better chance of delivering a product within schedule, budget and with most specifications.
Comments
Post a Comment