How do you make Scrum under Waterfall?

scrum-under-waterfall
Very often the Scrum under Waterfall exist in organisations. It might not exist formally, but it can be required by contract or by law. The Scrum can be part of the Agile experiment.
The Scrum under Waterfall be because it’s practically for the organisation.

What will be the same/different using Scrum under Waterfall?

Same

Focus on ‘Definition of Done’
Daily Scrum
Sprint Planning
Sprint Review
Sprint Retrospective

Different

Backlog = Project Plan
Less time on Backlog refinement
Less time on Sprint planning
Less negotiation during Sprint

But be aware, during Waterfall delivery: 

Waterfall has poor communication / misunderstandings
Lack of transparency
Detachment from reality
Slow feedback / No feedback
Nothing is Done

So you need to do following things:

1: Work in Sprints

The Waterfall can be scheduled for example 12 months. If one Sprint last 30 days, you will have 12 Sprints.

2: Avoid ‘Earned Value’

The task can’t be done for 85.6 or 98%. The task is done or not done!

3: Focus on Done

Create a Definition of Done (DoD), work with DoD

4: Testing, testing, testing

Test throughout Sprints, start to design your tests at the beginning of project. Test until the end

5: Get Frequent Feedback

Gather feedback early. Show the increment before it’s actually due

Related Post

Integration Team in Multi-team Scrum If one team in Scrum not enough, it's advisable use Multi Team. But here you get one more problem - how to manage more than one team. And the answer: use the Integration team. With Multi Team your Scrum will look a little bit different. Multi-team...
User Story Scenarios Each User Story needs to be testable, need to demonstrate, that requirement has been met. Here is effective formula, which demonstrate, that specific user story has been met: Given , When Then
Understanding Product Owner Role Responsibility Must have a Shared Vision Developing Winning product Product Owner controls the development effort in order to create a product Other Features A) Create Product Vision B) Maintaining the product backlog C) Release pla...
3 Levels of requirements in Agile development In Software Development Requirements have 3 levels: - expanded description of customers business - business point of view requirements - functionalities which should be made in our application Example: “We need a tool for selecting big data...