Scrum can also be used in big projects/companies. But the fact that it has a milestone (at the end of each sprint) only makes sense when something happens at that time.

If a team releases a new version every two weeks, that makes sense. You plan for the work to be released in the end of the sprint. But the world is moving towards CI/CD. Releases happen all the time.

Why would we have that segemtation of work, when Kanban provides a continues flow of development?

Thank you for your reply :)

Software Engineer, fascinated by the impact of technology in our everyday life. Writing about Tech and Personal Development.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store