Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>(1) Tasks are the steps towards the goal of a user story, similar to steps in a recipe. In both cases there are dependencies what to do when and in what order. <strong>The key is that the team talks about how to split things to work most efficient</strong>. This is not one person's job, but the Scrum team's. This happens initially during sprint planning when user stories are tasked out (by the whole team), but also daily as work is being done (daily standup etc.).</p> <p>The skill is not really about finding tasks with no inter-dependencies as much as it is to <strong>minimize the dependencies and to organize things in an optimally for team efficiency</strong>. This is the team's responsibility. A Scrum Master's job is to mentor them in this direction.</p> <p>(2) <strong>In Scrum</strong> (agile) <strong>you don't do architecture up front</strong>. That doesn't mean there is no architecture work in agile. On the contrary, <strong>architecture is done continuously throughout the whole project</strong>. From the start there are loose concepts and containers of ideas how to do things, and later on in the project this shell is filled with concrete architecture, bit by bit as needed by the user stories being worked on.</p> <p>With regards to learning, this is true in any case, agile or not. <strong>In agile you learn the whole time</strong>. Not upfront. In the first few sprints there might be much less user stories picked as the team needs to learn new technology and other things, but <strong>the essential thing is that something shippable needs to be taken on every sprint</strong>. This has several benefits because the team can try both architectural ideas as well as their skills harnessing a new technology. Over time, this alters and the team will have a pretty good idea what the overall architecture looks like and how the technology works to pick more user stories.</p> <p>My last advice is to not take over any constraints from waterfall like Q1, milestones etc. that say architecture is done by then and then. This is counter-productive and will fail. Stay agile (or not)!</p>
    singulars
    1. This table or related slice is empty.
    1. POScrum: task dependency and task for architecture design
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmurrekatt
    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. CORegarding the point (2): we can always divide the task, but merging the code is the problem. The architecture design is for setting the direction on how to merging the code later, like providing suitable interface, or using certain framework. or perhaps on how to passing the event/message from one programmer to another.
      singulars
      1. PO
      1. USjanetsmith
    2. COI don't quite understand. What is the problem in practical terms? Speaking loosely, if you know how two things fit together (interface so other), add this first and each part should be possible to add independently. It needs to be made in such a way that it doesn't break existing things (build/tests), but provides new things to be added which increments the feature towards completion.
      singulars
      1. PO
      1. USmurrekatt
    3. CO"add this first" shows dependency task dependency. Someone must created an interface before it can be shared, whereas others need to wait for this interface before they can use it, right?
      singulars
      1. PO
      1. USjanetsmith
 

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