Dear Juanjo, I have any problem with the definition of AGILE terms and consequently with the deliverables to be provided for tomorrow. Product Backog: The Scrum Alliance provides this definition: "The product backlog (or "backlog") is the requirements for a system, expressed as a prioritized list of product backlog Items. These included both functional and non-functional customer requirements, as well as technical team-generated requirements" EPICs Epics are large user stories, typically ones which are too big to implement in a single iteration and therefore they need to be disaggregated into smaller user stories at some point. (User stories are one of the primary development artifacts for Scrum and Extreme Programming (XP) project teams. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. For you: * Product backlog: It's about keeping track of "work to be done", and keep it described in a way that makes sense to both users and development teams * User Stories are simply description of "work to be done" that is detailed enough as to be addressable by a development team along the duration of a sprint. * EPICs relate to "work to be done" you have to further split before being addressed in the next sprint" I am not familiar with the Agile but I feel that the definitions are very different. Also I have trouble understanding what I need to deliver about it tomorrow. Could you enlighten me with a very specific example. Best regards Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20110929/2f29dd01/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy