Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Estimation process is the hardest thing in SCRUM. Sometime it may take up to 1 day to sit in conference room with a team and discussing what efforts need to be applied in order to complete every particular story. Don't even hope to get an accurate estimate in few first sprints. You should just accept this as the fact and go forward. Depending on how much details in your stories and how long team work together this process will be getting better from sprint to sprint and estimate will be more accurate. So far you can just calculate velocity or take 0.5 as the current velocity of you team. After you end up with first sprint you will get a more accurate velocity which then can be used to build a scope for next sprint.</p> <p>My team had a huge problems with giving an accurate estimate at the very beginning of a project. There was nothing in a project we could rely on, there was no architecture and the system is so large and complicated so everybody was scared to give any estimate at all because nobody knew what exactly should be built. We've solved this problem by introducing System Analyst(SA) to our company who is analyzing all incoming requests and doesn't pass them to development until everything from business point of view will be clear. The main purpose of SA is to understand new feature, see how it can be implemented and propose the solution on high level taking in account dependencies on already implemented functionality and keeping in mind the functionality we plan to implement in upcoming sprints. After initial analyzing has been done SA creates stories and add them to backlog. Then these stories go to designers. They design screens and attaches them to stories. After that story goes to product owner for approval and setting business value. </p> <p>All of these steps above has significantly reduced a time spent by whole team on estimation meetings. Now when meeting starts we have almost everything we need. Every story is explained in details, developers see how it affects existing functionality and see design so it's easy now to focus on technical questions only. So just as an conclusion in process we built SA and Designers are working on features which are planned for next sprints while developers and QA are focused on the active one. This allows us by the end of active sprint to get all stories analyzed and with design for the next one.</p>
    singulars
    1. This table or related slice is empty.
    1. POSCRUM estimation accuracy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlexey Andrushkevich
    1. USAlexey Andrushkevich
    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. 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