Tags:scrum
  • What is a backlog? Backlog is that list of characteristics that helps particular teams in maintaining their management projects. It is considered essential and adequate for a project towards its completion. In simpler terms we can say that Backlog…

  • 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…

  • One of the fundamental concepts of Scrum is the team must deliver a potentially shippable increment of code each sprint. This increment must include complete slices of product features, and it must be "Done." Additionally, the increment…

  • The Burn Down Chart is a very simple tool use to monitor and show the progress of the current sprint. Is exposed in a public location so that any stakeholder can get the information on how the sprint is progressing against the initial plan. The…

  • Agile methods or Agile procedures for the most part advance a restrained project management process  that energizes visit examination and adjustment, an authority that supports collaboration, self-association and responsibility, an arrangement of…

  • Looking at Scrum methodology, one can see that there is no Project Manager role in it. No one assumes a position from where it can directly command and control project execution. So, it might say that there is no Project Manager role in Scrum…

  • SPIKEs are not unusual and come up naturally during other SCRUM activities. This is happening for example, when something is blocking the progress of a sprint: the developer might face an issue that requires a more holistic approach on the design of…

  • It is essential for the Scrum process that the Scrum team has authority over the work they take on, and is allowed to focus on how that work is accomplished during the sprint. This enables the team to become self-organizing with no set leader. Over…

  • The Scrum development process is a series of sprints that are linked to each other, in a linear way. At the end of each sprint the product increment grows larger. Each sprint is built on top of the outcome from the previous sprint.Sprint duration is…

  • Being an Agile framework, Scrum reflects the values expressed in the Agile Manifesto (http://agilemanifesto.org/). On top on these values, Scrum adds its own five (common-sense) values, but critical for the success of a Scrum implementation. These…

  • Any project starts when stakeholders agree to allocate resources to achieve something that has been evaluated to have a satisfactory return on investment. This means the project must be well defined from the beginning, otherwise the stakeholders…

  • 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…

  • One of the most important practice in Scrum is the Daily Scrum. This 10-15 minutes meeting, kept at the beginning of the day, has the main objectives to capture the current project status (What have you done yesterday?), the immediate planning (What…

  • 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…

  • Scrum and eXtreme Programming (XP) are both Agile approaches on software development, and for that reason, are very much aligned. They share the concepts of iterative development, working software, release and iteration planning, daily meetings,…

  • 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,…

  • Scrum is an agile methodology applicable in principle to nearly any type of project, but with a high rate of adoption in software development. It is suited for projects where requirements cannot be known in advance to their full extent, are…