Comments on: Develop Architectural Needs through Abuse User Stories

By: Chris Sterling

Chris Sterling — Sat, 14 Mar 2009 06:38:22 +0000

Good day rlpmjp,

I have not used QFD in a formal manner and it looks quite interesting from what I just read about it. In the past I have seen a form of this used but the tutorials I see are much more in depth than what I recall. I don’t think that using abuse stories is the only way architecture and infrastructure stories can be prioritized effectively but I have found that it helps business folks understand why they must be addressed. If we put business in charge of priorities then we must help them understand why those requirements must be prioritized for risk and cost of not addressing it in a timely manner.

Thank you for the reference and I will look more into QFD.

By: rlpmjp

rlpmjp — Fri, 13 Mar 2009 22:04:19 +0000

Why not just use a Quality function deployment (QFD) chart, so the most important stories, bubble to the top (as higher ratings)?

Once it is working, it is very effective to deliver what the business-side and customers most want and is a way to push back on unreasonable requests.

By: Chris Sterling’s Blog » User Stories Gone Wild!

Chris Sterling’s Blog » User Stories Gone Wild! — Sat, 03 Jan 2009 21:03:14 +0000

[...] not addressing a system’s quality attribute such as scalability could be. I have written an earlier post on this regarding a term coined by Mike Cohn called “abuse stories”. The idea is to capture the [...]

By: GettingAgile.com » Blog Archive » Qualities, User Stories and sad state of Scrum requirements

Wed, 15 Oct 2008 22:02:10 +0000

[...] insufficient for quality requirements (aka non-functional requirements) and Chris Sterling has this blog entry on how to use an “Abuse User Story” to describe the cost of not addressing quality [...]

By: Chris Sterling’s Blog » Technical Debt Workshop - A Perspective

Chris Sterling’s Blog » Technical Debt Workshop - A Perspective — Thu, 21 Aug 2008 14:26:59 +0000

[...] Abuse Stories – Mike Cohn brought this up during a presentation and they were not in his slide materials. He has since added them and I believe them to be greatly important and easy to implement types of stories to describe the cost of not addressing what are usually technical debt or more likely architectural features. You can follow the link to an old blog entry I posted on this subject. [...]