Databases
StackOverflow2013
Postsdbo
POArchitectural principles as "non-functional" user stories
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POArchitectural principles as "non-functional" user stories
    primarykey
    data
    text
    <p>I am about to start a pilot project in our company to introduce agile practices, including the use of user stories. After reading two books by Mike Cohn, Agile Estimating and Planning in particular and User Stories Applied, I now have a clearer idea of how to proceed. I have confidence in refining our techniques along with practice.</p> <p>However there is one thing that does not convince me. <a href="http://blog.mountaingoatsoftware.com/non-functional-requirements-as-user-stories" rel="noreferrer">In this blog post</a> Mike Cohn defines a specific type of user stories, which he called constraints, which can be used to define the so-called non-functional requirements. Personally I do not like the word <em>constraint</em> and even the use of the classic template "As a ..., I want ..., so that ...".</p> <p>Rather I will try make the customer to write, always on the cards, perhaps with the above template, those that Nick Rozanski and Eoin Woods called, in their fantastic book <a href="http://www.viewpoints-and-perspectives.info/index.php?page=home" rel="noreferrer">Software Systems Architecture</a>, <em>architectural principles</em>:</p> <blockquote> <p>"An architectural Principle is a statement of belief, approach, or intent that guides the definition of an architecture."</p> </blockquote> <p>(they also divide these principles into <em>business principles</em> and <em>technology principles</em>, a differentiation I think we should not care of.)</p> <p>What I would like to do with these <em>principles</em> cards is to put them next to our backlog cards board in order to have them always present during the user stories definition and the planning activities. I would also encourage customers and developers to pick them up and put them next to the iteration board each time they think a card could be useful as a reminder for the team.</p> <p>Have you ever tried any similar approach? Do you discourage it for any reason? Have you any suggestion on this matter?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMarco Ciambrone
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POArchitectural principles as "non-functional" user stories
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POArchitectural principles as "non-functional" user stories
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POArchitectural principles as "non-functional" user stories
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload