Everything starts with "The client has requested a change..." or "This is not what the client had in mind..." and then we see our developers working extra hours, weekends. I have seen and lived this several times!. We need to avoid scope creep at all cost. How do we do that? Let's find out...

In this session we will cover the following topics:

1. What is scope creep?
2. What are the casues?
2.1 Agile: How can it lead to scope creep if it is not well "implemented"
2.2 Drupal: It can go against you if not properly managed
3. How can we prevent scope creep while allowing change requests?
4. What tools can we use and how can we provide better estimates.
5. Conclusions