Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is a real tension between Scrum and other agile dev methodologies and spec writing. I think there are two big points of tension:</p> <ol> <li><p>Because agile says everything should be on an index card, that means you have to have stuff planned out enough to <em>fit</em> on an index card. (E.g. you have to know how it's all going to work.)</p></li> <li><p>Some things don't make sense in isolation (what's the use of an upload file page without a manage uploaded files page, for instance.)</p></li> </ol> <p>You don't have to design the whole app all at once, but you have to have a vision of the whole app. Then, especially if you have a separation of designers and programmers, you do functional design for a sprint-sized chunk at a time. Those designs then have to be broken down to story-sized chunks. </p> <p>This is a lot of up front functional design, and I think that's overlooked in a lot of the talk about agile methodologies. Perhaps some shops have the devs do more of the design. Also, I think it's a lot easier to use scrum/agile for making changes/bug fixes to existing apps rather than building new ones.</p> <p>The thing I've found most helpful is to fight back on story size. A lot of organizations have gone crazy, saying stories need to be only a few hours. The original scrum book says 16 hours, I think, which is often large enough to fit an entire screen of a web app. So "implement manage my account" could be a story (as opposed to the hundreds-of-tiny-stories approach of "implement username", "implement password" etc.) Then reference your design doc for "Manage My Account" and make sure to have word-perfect screenshots/prototype/mockup so the dev can look at them and copy/paste the text directly into the code they're writing, and they know for sure which fields need to be there (or which links, or which pictures, or whatever).</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. USAdam J.R. Erickson
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COI think you got a lot of the things behind agile in general and scrum wrong. Please consider further learning on what is scrum about and how things proposed to be done. -- I don't have enough space to comment in detail. But, "Implement X, Y, Z" will never be a user story. Have a look: http://en.wikipedia.org/wiki/User_story -- It's ok to write down epic stories at first, you only have to break them down, when it comes near implementation. -- Your designers and programmers shouldn't be separated. Teams are supposed to be x-functional. -- No characters left, but still much to comment ;-)
      singulars
      1. PO
      1. USPeter Wippermann
    2. CO1) Designers and programmers are almost always separated in practice, if not physically or organizationally, then de facto. 2) The user stories that you point to on wikipedia are exactly the kind of "hundreds of tiny stories" things that cause the process to grind to a halt. 3) You're hanging onto my misuse of the word "implement" which, you're right, should have been written in user-centric language. But you're disregarding my larger point that breaking down a vision into hundreds of teeny stories takes up front design and makes it hard to keep them organized.
      singulars
      1. PO
      1. USAdam J.R. Erickson
    3. COHi Adam, I have to agree with Peter here, you seem to be mssing some of the core ideas behind Scrum and Agile. Scrum emphasizes cross functional teams, meaning having a divide between designers and programmers is an impediment to forming a highly productive team. Hand offs produce bottlenecks and waste. You want your designers to be working with the developers on the same team so that you can avoid having to do large amounts of up-front design and handing off detailed design documents.
      singulars
      1. PO
      1. USTodd Charron
 

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