Please login or join to subscribe to this thread
Fully agree with Sergio and Anton. Understand the agile behaviours, concepts and techniques (practises) and apply what makes sense to the project. You can apply a retrospective event or the concept of user stories also in waterfall (phase) - driven approaches.
Very glad to see your comments here and it really helps and makes me much more confident on the job hunting for an ICT PM in New Zealand.
I think there are two factors that broadly impact the decision
1. Nature of the Project
2. Organization existing practice, culture & willingness to adapt the methodology
For selection of the methodology that we going to apply for the project,
I would like to classify it to Complex, Complicated & Obvious in the Nature. Here let me share what I mean by the each of them
Complex - where project dynamics change very frequently, required lot of time & resources in R&D, very demanding stockholders, customer inter activeness is helpful in terms of achieving project goal, requirements are evolve & change over the period of time. Here incremental deliverable would have great advantage to quickly correct our-self and get the output on track with minimal lose.
Obvious - I would say in the project we can easily set the Standard Operating Procedures, pre-define set of activities are also broadly defined, Out put of the phases in the project is pretty much predictive, most of the activities are also sequential
Complicated - We can't set more than 60% of SOP, can't have more than 50% of pre-define activities, Need to respond on requirement change. Basically this is the area where we can apply the best practices in the industry.
Based on the above classification, I think for the project whose nature is complex should implement the Agile methodology whereas project nature is obvious can be implemented with Waterfall model. We can adapt mix / hybrid approach for the complicated project nature.
Please login or join to reply