Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Ask the team!</strong></p> <p>Fair, my answer is short so let me explain. The team has better context of your technology, issues, cultures and product than anyone else here; thus they are the best to answer it. This is a typical topic you should bring up in a retrospective and in the spirit of continual improvement - Inspect and Adapt. Keep adapting and trying things until things start getting better. </p> <p>So in your next retro, bring it up and inspect the problem and admit it is unproductive. Look at opportunities to adapt and do it.</p> <p>Some Tips (but not as a Scrum Master)</p> <ul> <li>Scrum recommends 10% of your capacity spent on grooming</li> <li>There is no rule that everyone should do it in a meeting</li> <li>Have meetings to manage exceptions or areas where more formal discussion is required</li> <li>Try some pair grooming </li> <li>Remember a Story is a placeholder for communication, not a contract</li> <li>Get the core acceptance criteria, build the rest in planning sessions and in sprint</li> </ul> <blockquote> <p>How many stories do you typically end up with after a Grooming Session?</p> </blockquote> <p>Just enough for the next two sprints with a Just-In-Time attitude</p> <blockquote> <p>Do you create the Acceptance Criteria as part of the Grooming Session, or outside?</p> </blockquote> <p>Both, the critical business acceptance criteria in a formal session with the PO and the functional ones outside of the session as they are identified. Acceptance Criteria should be added the whole time, even in sprint planning and within the sprint. Avoid treating them as a contract.</p> <blockquote> <p>How do you create User Stories and what process works for you?</p> </blockquote> <p>I normally start with the business focus story that delivers on a business need. In grooming we break it down to functional stories by using an action/verb or use case model. These can be written as stories. In a typical 1 hour session, you can easily brainstorm over 50 requirements at a high level. As the implementation sprint gets closer, you can break them down into INVEST stories; but report at the functional level.</p>
    singulars
    1. This table or related slice is empty.
    1. POMore productive Grooming Sessions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBrett Maytom PST
    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. VTUpMod
    2. 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