Can we combine both the Agile and Waterfall development strategies?

I have been able to combine Waterfall and Agile models successfully in my project execution. The overall project plan can be linear with clear cut phases. Once requirements are finalized, the design, construction and Testing phases can have iterations with Agile principles followed. Each iteration is planned with design, coding, unit testing and system testing components and delivered to the customer. This results in the early visibility of the product to the customer which reduces the risk of non compliance to requirements. The customer involvement will be high as we get the continuous feedback from the customer which can be discussed, prioritized and incorporated in the subsequent phases leading to an acceptable product during the UAT and final acceptance.

Yes both Agile and waterfall methodologies can be clubbed for the best results. Both methodologies stand alone has thier own drawbacks and by clubbing we can leavrage for best results in project execution. Agile ensures better productivity along with testable features running at the earliest along with waterfall model ensuring that minimum required project structure is adhered to along with critical project artifacts in place for the future references. Clubbing both ensures quicker adption of requirement changes along with involvement of customer/product owner thereby not compromising on rqeuirement change management..

Waterfall approach provides structure, control, progression and finite project cycles.

Agile is different in that additional leaway is given for teams to iterate through a single deliverable numerous times until a level of satisfaction is achieved.

It's difficult to implement this approach when working with shared resources, or when time to market and budget cannot be shifted.

Ultimately,Waterfall development Disciplines with agile principles for superior results.

Yes you can always combine agile with waterfall and may call it as modified agile methodology. I am currently working in distributed agile methodology, where we follow a modified version of agile. One of our teams which is stationed in offshore works on a relational part of the project which follows waterfall where as in the client side we follow agile. But often this balance may go wrong as agile is a highly aggressive way of getting things done. But if the vision of the project is there from the very begnning and the goals are fixed we can combine methodology after all this also means being agile.

According to me, the waterfall approach has proper structure, control, progress and very finite project cycles. This works when one has access to limited resources and when specific hours are assigned to granular stages of a project phase. But whereas Agile is different in that additional time is given for teams to iterate through a single deliverable for number of times until a proper level of satisfaction is achieved. It's difficult to implement this approach when you are working with shared resources, or when time to market and budget cannot be shifted.  So combining best features of both i guess one can get very good results...