Let me make it simple for you: fixed price contracts do not work here and we need time and means contracts.

The reason is obvious: a traditional fixed price/fixed scope contract is based on the upfront definition of the product, and it’s not Agile. How can you give a fixed price when you don’t know exactly what you’re supposed to develop?

Yes, unfortunately many customers do not understand it. They ask you to be Agile (just because it’s cool?), then force you to accept fixed-price contracts or to provide them with documents such as requirements specification and solution architecture. 

There are obviously two solutions:

  • To ignore those customers and look for better ones, which you might not afford to do. 

  • Cop with it! There are some workarounds for fixed-price contracts in Scrum. You can guess: they don’t work perfectly. They all try to convert the contract into time and means without making it obvious. 

OK, we’re almost done! I’m going to introduce some resources for your further studies and talk about available certifications in the next lessons.


- Nader

P.S. if you believe the course can be helpful to your network, you can use the following links for sharing the information and subscription page on the social network. I’d be glad if you do so :)