It would be nice to be able to report against themes and Qualities for a given spring, on which quality was the effort spent...) as well as to be able to filter ping and product backlog by theme or quality.
Statement from Kunagi Team
Backlog filtering ist covered by sto166.
The rest does not make too much sense (see comments).
Issue is closed.
Wed, Feb 2, 2011, 10:07 by Witek (SM,T)
Could you please explain a little more, what requirements you have for the sprint reports? I don't realy understand what the goal is. Tasks have no direct connection to Qualities. Only Stories do. So how could we create a report, which shows effort spent on a Quality? We would have to connect Tasks to Qualities. Is this what you have in mind?
Wed, Feb 2, 2011, 11:37 by artjom (PO,T)
Just a quick note on Qualities in Kunagi: A Quality is a non-functional or a Cross-Story-Requirement. You don't exactly spent effort on it. Qualities are linked to Stories and Stories have a (abstract and relative) Story Point Estimation.
What takes effort, on the other hand, is completing Tasks. This has no direct connection with Qualities or Story estimation.
Mon, Feb 7, 2011, 23:33 by P
Mon, Feb 7, 2011, 23:33 by P
My understanding is that usually, a task is attached to a story which can be associated to quality. Like "implement a new button to do X" is a task that belongs to "implement feature Y" which could be associated to quality "User interface improvement" or "reporting" for instance.
My request would be to see, out of all the tasks completed on a given sprint, how many can be linked to each quality (through stories). I understand that some might not be linked to any story (or to a story with no quality) but it would be nice to be able to tell the stakeholders on which qualities they will be able to see improvement at the end of the sprint. Not sure if I'm clear. Sorry.
Tue, Feb 8, 2011, 00:27 by Witek (SM,T)
I still don't see how you could answer the question: How much time was spent on Quality X? We could count, how much time was spent on Story Y, which links to Quality X. But who says, this has a relation to Quality X. Perhaps the team completed the Story, but didn't even look at Quality X. Or, they have spent 99% of the time on Quality Z, which is linked to our story Y too.
Perhaps you have a different interpretation of Qualities, then we have. We understand Qualities as non functional requirements, which need consideration in some Stories. A Quality can never be completed, and there is no measure of completeness, like 42% would be. Its just an attribute to a story. Examples would be: Response time less then 500ms or Buttons, which change data are red. Your example Supports reporting would be good too. The other one User interface improvement would be not so good, because it is so abstract, that the PO can not verify it.
User interface improvement would be better suited as a Theme. So the PO can define concrete Stories, which belong to that theme. Counting spent time on Themes would be a legitimate requirement for Kunagi.
Please keep arguing, if you think, we still do not understand each other. ;-)
Tue, Feb 8, 2011, 12:45 by artjom (PO,T)
Regarding the information for Stakeholders, it should be sufficient to provide a list of Stories that are expected to be completed. Some Stories are affected by Qualities in which case the requirements of the Quality naturally will hold.
As far as Scrum goes, there is actually no (theoretical) need to see how many Tasks were created or how many hours were spent, because it actually very much depends on the circumstances. A person that is less experienced in some field, might need 5 hours for a task, for which an expert would require a few minutes. What completion of Stories is concerned, however, both results have equal value.
Wed, Feb 9, 2011, 23:46 by P
I was not aware of sto166. I tink it should be good enough as a starting point.