Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I typically only ask for story titles upfront. I try to see if I can triage them to at least within an order of magnitude. I give a very rough estimate based on the number of titles and my estimated velocity/title. I'll usually have the customer break the titles up into (1) need to have now, (2) needed but can wait, and (3) these would be nice.</p> <p>I start by tackling group (1) and coming up with enough information to break them up into a set of releases. At this point I can usually give a better estimate by using the more detailed information to provide per title estimates. I only plan out the group (1) stories. If there are too many group (1) stories to fit in a release, we break it up into multiple, coherent releases/iterations.</p> <p>When we get within about a month of starting on group (2) stories, I sit down again with the customer (in a more focused planning session, usu. talking to them all the time), to start the process over with the group (2) stories.</p> <p>Stories that get added as the project go on get put into the right group and handled as appropriate for that group -- if it's current release, enough detail to work with, if later, just the title as a placeholder.</p> <p>The other thing that I do is make sure the customer understands that it's a cooperative process and we will end up with what they want. They get to choose when to stop -- even if there are stories left on the board. As long as I'm delivering value that they care about, we keep on developing. They need to trust that I'm doing what right for them and working diligently. I need to trust that they will give me the best information they can on what they want as soon as they possibly can.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's a good process for writing story cards?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UStvanfosson
    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. This table or related slice is empty.
    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