Tokens instead of Story Points

  As mentioned earlier the notion of story points recognises effort and level of complexity, but it doesn’t recognise the value of the task.   As part of Jiritsu Scrum the focus is on working and delivering higher value and hence doesn't take into account the effort involved. Software delivery is very different from other industries where usually high labour/effort means higher value   As part of Jiritsu Scrum we propose using a token amount to define the value of the task. At the end of each sprint the token value of tasks completed is automatically delivered to the developer's wallet.   A few important points to call out are:  

• The value of a user story is based on the perceived business impact of that userstory.
• The value of the user story is voted by the team during backlog grooming (in most cases using Planning Poker methodologies).
• The value of the user story may not be directly proportional to the effort involved. eg: a 2-3 lines change in a core file, which may take a few hours to complete, but that improves the performance of the application by say 20% will  have a higher token value, even though it might take only a few hours to complete.   The side effect of this process is high value tasks become a priority not only for business but also for the developers as a higher value task will reward them with more tokens.