Let's assume I decide to manage a certain project using Kanban. This happens to be a customer service kind of project where the dev team delivers continuous improvement so Kanban is definitely well suited and scrum would probably be over the top and ultimately unnecessary.
Let's also assume I want to measure the performance of the team. I know someone prescribes to take a, say, two weeks activity and count the number of tasks delivered in that timespan. You can repeat that process every two weeks and so monitor performance. It is advisable to break down stories so that they are kind of comparable and basically become a unit of measure.
I have never used Kanban before but being able to break down stories into similar sized ones sounds like a not very feasible goal to me. In fact the more I think about it the more it seems difficult.
What about adding story points to each task on the board before starting development as we do in Scrum? Would that be a theoretically sound practice?