Tags:user story
  • In this sixth and final article, it is analyzed the meaning of T from INVEST mnemonic: Testable. When discussing this aspect, usually it comes down to analyze the acceptance criteria defined. This user story cannot be considered "Done" unless the…

  • In this fifth article, it is analyzed the meaning of S from INVEST mnemonic: Small. High quality user stories are small or sized appropriately. Stories represented up to few days of work (or few story points depending how the estimations is done)…

  • In this third article, it is analyzed the meaning of V from INVEST mnemonic: Valuable. A good user story must define something that is of value to the end user. This could include a feature, performance requirement, or something the user has asked…

  • In this second article, it is analyzed the meaning of N from INVEST mnemonic: Negotiable. According to the guidelines, a good user story should capture the essence of the customers’ requirements. It's not an explicit contract with all the…

  •    INVEST Guidelines are a set of recommendations, put together by Bill Wake (see original article here), to evaluate good quality user stories (or more general, Product Backlog Items). Each of the letter from INVEST mnemonic refers to a…

  • What is a Scrum Master? This role is sometimes quite difficult to understand and implement, especially for organisations with more traditional approaches in organising software development teams. That is because a Scrum Master is NOT a Team Leader…

  • The Product Owner is a key role in Scrum, but many organisations struggle to effectively apply it. As the name suggests, a product owner should “own” the product; he is responsible for ensuring that the product creates value for its customers and…

  • At the end of each iteration, the team adds up effort estimates associated with the user stories that were completed during that iteration. This total is called velocity. Since the effort estimates (story pints, ideal days, etc.) are merely…

  • The Scrum Team is one of the three roles defined within Scrum Framework, together with Scrum Master and Product Owner.All work delivered to the customer is done by The Scrum Team. It consists on a set of individuals (not only developers as you might…

  • Planning Poker is an agile estimating and planning technique widely used by many agile development teams. It is very simple, yet effective and is base on consensus between the estimators.It is very important that the estimations are done all…

  • Story mapping represents a more recent agile practice, one intended to provide a more structural approach to release planning. It consists in ordering user stories along two independent dimensions. The "map" arranges user activities along the…

  • Defining the user stories is important for at least two reasons:·     Gives an overall view on what is expected from the software sytem to be developed;·      Provides just enough information for the developers to provide reasonable estimates in…

  • User Stories are one the main development artifacts in an XP or Scrum project. They are high-level definitions of requirements, containing just enough information so that the developers can produce reasonable estimates of the effort to implement…

  • In the previous article we had a look on the Daily Scrum, a very important Scrum Practice but which can be easily applied in any non-Scrum project. In this article we will on how requirements are managed inside a Scrum project by using the…

  • The Sprint Backlog represents the list of tasks identified by the Scrum Team in order to complete all the work assumed for the current Sprint. The work assumed is represented by those items from the Product Backlog on which the team has agreed,…