Click here to Skip to main content
15,904,652 members
Home / Discussions / Design and Architecture
   

Design and Architecture

 
QuestionWhy MVC Pin
KK Kod16-Jun-13 21:51
KK Kod16-Jun-13 21:51 
AnswerRe: Why MVC Pin
Richard MacCutchan16-Jun-13 23:21
mveRichard MacCutchan16-Jun-13 23:21 
AnswerRe: Why MVC Pin
Keith Barrow17-Jun-13 0:04
professionalKeith Barrow17-Jun-13 0:04 
GeneralRe: Why MVC Pin
KK Kod17-Jun-13 0:54
KK Kod17-Jun-13 0:54 
GeneralRe: Why MVC Pin
Keith Barrow17-Jun-13 1:27
professionalKeith Barrow17-Jun-13 1:27 
QuestionI seek help defining a SCRUM structure for an application I am working on. Pin
Brady Kelly16-Jun-13 21:41
Brady Kelly16-Jun-13 21:41 
AnswerRe: I seek help defining a SCRUM structure for an application I am working on. Pin
Jonathan Davies17-Jun-13 23:09
Jonathan Davies17-Jun-13 23:09 
AnswerRe: I seek help defining a SCRUM structure for an application I am working on. Pin
Keld Ølykke27-Jun-13 5:48
Keld Ølykke27-Jun-13 5:48 
I agree with Jonathan that you as a developer should not really be the Product Owner.
However, if you are both the Product Owner and the Team then you are the one to write the User Stories.


A User Story tells something of value to a user - that is why we can put a Business Value on it.

Here is an example from one of your bullet points: "Parking access control".
Ask Who and What and Why?
The answers are your user stories e.g.
"A Customer should be able to see how many free parking lots that are left when getting near a Parking Basement Entrance".
The why's do not need to be elaborated in the title, but you need them to determine a business value and the priority of the User Story (priority partially hinted by should[^])

You break this story into a number of tasks needed to fulfill the user story. Tasks are of whatever you need to do e.g. talk, purchase, seek, read, write, code, assemble, install, upgrade, etc.
The estimates of the tasks is the estimated cost of the user story. The business value and estimated cost gives you an estimated velocity; a number quite useful when you select user stories to put into a sprint.
When you complete a task, you log how much time you used on it. When all tasks for a user story are complete the business value with the total used time gets you the actual velocity.


The quality of your user stories dictate the quality of your estimated and actual velocity. A good user story has an obvious business value and is easy to break down into small set of simple tasks. A small set of simple tasks are easy to estimate and can be completed within a sprint. Hence, both estimated and actual velocity benefit from a good user story.


Kind Regards,

Keld Ølykke
QuestionMVVM architecture for a Hardware based application Pin
Praveen Raghuvanshi13-Jun-13 4:47
professionalPraveen Raghuvanshi13-Jun-13 4:47 
AnswerRe: MVVM architecture for a Hardware based application Pin
jschell13-Jun-13 8:53
jschell13-Jun-13 8:53 
AnswerRe: MVVM architecture for a Hardware based application Pin
dusty_dex13-Jun-13 8:55
dusty_dex13-Jun-13 8:55 
AnswerRe: MVVM architecture for a Hardware based application Pin
Jonathan Davies14-Jun-13 3:00
Jonathan Davies14-Jun-13 3:00 
GeneralRe: MVVM architecture for a Hardware based application Pin
Praveen Raghuvanshi17-Jun-13 1:28
professionalPraveen Raghuvanshi17-Jun-13 1:28 
QuestionSoftware Design Books Pin
msr_codeproject13-Jun-13 2:43
msr_codeproject13-Jun-13 2:43 
AnswerRe: Software Design Books Pin
Amarnath S13-Jun-13 17:38
professionalAmarnath S13-Jun-13 17:38 
GeneralRe: Software Design Books Pin
msr_codeproject13-Jun-13 23:47
msr_codeproject13-Jun-13 23:47 
QuestionQUERY FOR ALL vs QUERY FOR EACH Pin
Paulo S X Soares5-Jun-13 4:13
Paulo S X Soares5-Jun-13 4:13 
AnswerRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Bernhard Hiller5-Jun-13 21:16
Bernhard Hiller5-Jun-13 21:16 
GeneralRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Paulo S X Soares6-Jun-13 2:50
Paulo S X Soares6-Jun-13 2:50 
GeneralRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Eddy Vluggen6-Jun-13 2:54
professionalEddy Vluggen6-Jun-13 2:54 
GeneralRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Paulo S X Soares6-Jun-13 3:06
Paulo S X Soares6-Jun-13 3:06 
AnswerRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Abhinav S5-Jun-13 22:17
Abhinav S5-Jun-13 22:17 
GeneralRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Paulo S X Soares6-Jun-13 2:58
Paulo S X Soares6-Jun-13 2:58 
AnswerRe: QUERY FOR ALL vs QUERY FOR EACH Pin
jschell6-Jun-13 10:15
jschell6-Jun-13 10:15 
GeneralRe: QUERY FOR ALL vs QUERY FOR EACH Pin
Paulo S X Soares7-Jun-13 5:22
Paulo S X Soares7-Jun-13 5:22 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.