Implementing Scrum Within Waterfall Methodology

How would tested and integrated increments of genuine release quality be delivered each Sprint? How would a team inspect and adapt an emergent product and a collaborative way of working? Where would the transparency come from, and how would value and progress be evidenced?

Regarding your first question...  I'm not sure if this is what you're referring to but I've worked with customers that like the idea of Scrum but they still are set on establishing a contract that defines specific requirements up front as to what they will get and how much it will cost them.  In these cases it's difficult to fully implement scrum.  You can still implement increments of working software every sprint but the product backlog just doesn't evolve like it would on a more scrum project.  Anyways, not sure if this is what you were referring to when you asked about implementing scrum on a traditional waterfall project.  If I were you I would lean towards scrum whenever possible.  It may take time to fully establish the scrum methodology fully.

Regarding your second question...  Yes Scrum will work if there are dependencies among work items.  Scrum has a product backlog which the Product Owner and others keep prioritized.  Things like dependencies are things they consider when they prioritize that backlog.

This has an easy answer: no. Don't even start it, as it will bring more chaos than anything else. Either you implement Scrum as the framework of choice, or you don't. 

The only way I could see waterfall and scrum in one sentence, is if you determine whether you use scrum or waterfall for each project/product separately. 

If you have really simple projects where everything is known, then waterfall is definitely a valid way. If more is unknown then known, then you enter the complex field (of the Stacey matrix), and then Scrum is the way to go.



Can't stress it enough: don't try to mix the two. It's dirty and a recipe for disaster.

If you implement Scrum properly, it should be possible to see whether it is helpful to combine it with other approaches. This includes waterfall.

As the benefits of Scrum are subsequently inhibited by a waterfall approach, there could be a strong case for abandoning waterfall.

However, I suspect in many cases where waterfall is being used, there is very little appetite for reaping the benefits of Scrum.