Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The short answer is, you don't.</p> <p>The important question to ask yourself when writing these specs, is why do we do them? What is the value in the spec?</p> <p>The value in the spec usually comes in communicating the ideas of the business with the development team. Scrum is designed to bring the business (in the form of the Product Owner) to the development team. By interacting with the team frequently (remember, individuals and interactions over processes and tools), and by seeing working software frequently, the business can work hand in hand with developers to produce software that solves business problems better than by trying to spec out the whole thing before you get to try it out.</p> <p>This is how Agile projects do a better job of delivering the product the business wants instead of the product they requested.</p> <p>That said, there are certain base criteria that need to be met. We can test for this, and as with any good tests, we can automate it.</p> <p>Have a look at BDD and <a href="http://cukes.info/" rel="nofollow noreferrer">Cucumber</a>. In addition to your User Story, it's good to have a basic set of conditions of satisfaction, preferably in the "Give/When/Then" format. These conditions are the <strong>minimum</strong> set of criteria for the story to be accepted as complete.</p> <p>For example, "Given I am logged in, when I log out, then I am taken back to the home page".</p> <p>If you're going to have acceptance criteria, you're going to want to automate it. The worst part of most specifications is they often end up out of date and collecting dust when the project is complete.</p> <p>Also, you shouldn't be assigning tasks to the team. Scrum teams are self organizing and anyone should be able to grab any task they feel they can work on while respecting the priority of the stories. Swarming is a big part of the performance benefits of Scrum. </p> <p>You may want to consider bringing in an outside coach to assist with your transition.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I manage specs in Scrum?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTodd Charron
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I manage specs in Scrum?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      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