I agree, Agile and Scrum are not the same. Agile is a framework, Scrum and Kanban are two ways of adapting this framework. On your point about story points: I

I agree, Agile and Scrum are not the same. Agile is a framework, Scrum and Kanban are two ways of adapting this framework. On your point about story points: I am not too fussy with story points, velocity etc, based on Agile guide, we need to have Sprints in Scrum and the team should complete the tasks that it committed for a specific Sprint. So how does the team know which one is too small or too big when adding requirements to the Sprint during Sprint planning meeting? The team needs to have a way to estimate requirements and make sure it wont commit to a long list of tasks without acknowledging their sizes. To achieve that we need to use story points, T-shirt sizing or any other method to estimate requirements, right? Please let me know how was your experience of estimating requirements and adding them to your Sprints? and which approach would you use if you were in our situation?