Add a comment

 

Re: Features vs Behaviour

The sad (?) truth is that features are often prioritised over qualities. This is, in part, a result of not describing qualities in terms of their impact on features and vice versa. In my experience, though, it's usually due to the prioritisation process not having any representation other than end users. Everyone is a stakeholder and it's one of the architect's responsibilities to speak up for the technical qualities.

Jira can help here. By attaching templates to specific types of items you can remind developers and analysts of the non-functional aspects they should consider before starting implementation.


Re: Features vs Behaviour


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).