Structure - any tips for a managing mix of Kanban and Scrum projects?

Stuart Lipinski

Hi

We're starting to use Structure to help give some visibility to a cross team program of work. One issue that I've come across is that the teams that are working on this are using a mix of Kanban and Scrum, so some projects have tickets with story points, and others, well, don't. 

I'd love to be able to look at progress using story points, but can't do that with there being a load of tickets sans points. At the moment this means that we can only show progress in Structure using something like the status of the ticket, but then that doesn't take into account the different sizes of different stories.

Has anyone come up with any creative ways to solve this? Did you somehow get story points assigned to relevant tickets that sit in kanban teams, or something else?

Thanks in advance for any suggestions!

Stepan Kholodov

Hello @Stuart Lipinski 

The progress can be calculated using the Formula column with a custom logic applied to it. And once it's all set, the Formula can create progress value for the whole structure how you need it.

Here is some ideas of how you can manage issues that currently have no Story Points:

1. If the Story Points field isn't available for all Kanban projects,  you can create a custom numeric field in Jira and assign Story Points through it just the same as you would in the Story Points field. The Formula can take into consideration both fields; for example, if there is Story Points value in an issue then the Formula can use it and if the field is empty - the Formula can take values from another defined field.

And for assigning values in the field - you can just add the field's column to the structure, double-click inside of the column for each issue with no value and set values for each issue like this. But please make sure that the field is added to the right screen to allow the inline editing through Structure.

2. You can define alternative values for issues with no Story Points in the formula itself. For example, such issues can be considered to have an average Story Points value per structure or you can define values for issues of a specific scope(issues of a particular project, issue type etc).

If you would be interested, we can take a closer look at your setup and recommend something more specific. Please reach out to us directly in that case.

Best regards,
Stepan Kholodov
Tempo