In the first post of the article, I wrote about how senior executives need to see the list of features before approving the product development (the list of features is reviewed in terms of competitor analysis, projections of the direction where the product should be heading towards, and also whether these are features that customers [...]
|
||||||
|
In the previous post, I took a real life example of a team (Daily Scrum and ScrumMaster) where Scrum was getting implemented, and yet soon after the actual work started, we were finding that things were not going on schedule, and that there were a lot of issues about commitment from the team, analysis revealed [...] The previous article (Scrum stories being too generic) was about providing the required right level of detail in Scrum User Stories, in order to make it represent the User Workflow. In this article, we focus on what a User Story should not be, and though these may seem obvious when we think about these deeply, [...] |
||||||
|
Copyright © 2012 Learn Software Development - All Rights Reserved |
||||||
Recent Comments