User Story - Database design -
i need build product have database on end store , retrieve data.
i started gathering user stories stakeholders , stuck...
if have project leader has 1 user story like: "as project leader, want able see , modify scope of project make sure project date"
this user story require had created database , have table before having data in table.
should collect user stories , add database component on acceptance criteria?
should create user stories end , front end?
i'm not sure how separate or make them work together.
the idea behind scrum architecture / design emerge develop. in mind still need product backlog reflect product be. somewhere in backlog there should user story like... "as user, want application can use manage projects". story rather large (epic) level. has broken out smaller stories (like "... application must have ability x"). if indeed user story, sub epic (still large needs breaking out) story be... "as application developer (notice context change here), need database store project application data". story gets broken out person making db scripts (assuming creating application database first, applications code first , orm generates database schema). main point here start large , break down until full backlog small stories. know have full backlog (groomed backlog) , ready start planning sprints.
Comments
Post a Comment