Posts

Showing posts with the label Scrum Project

Product Owner Responsibilities in a Scrum Project

Image
  The key Business stakeholder of Scrum Projects is the Product Owner. So, one integral responsibility of the Product Owner is to convey the importance and significance of the Scrum Project to the Scrum Team. This is the key to the success of any Agile Project through the use of Product Backlog. Now let us look at some of the major responsibilities of a  Product Owner : Creation and Maintenance of the Product Backlog:  Scrum framework  is mostly used in the software environment and new product development field. This is an on-going job and full-time responsibility of the Product Owner. He has to constantly keep refining it especially before any sprint planning meetings. Prioritizing of Backlog according to the Business ROI: Product Owner also needs to prioritize and sequence the backlog according to the needs of the business and situations. He also elaborates the epics, themes, and features into user stories which are feasible enough to be achieved in a single s...

Managing Internal and External Stakeholders in a Scrum Project

Image
  Scrum is one of the most popular Agile methodologies. It is an adaptive, iterative, fast, flexible, and effective framework designed to deliver significant value quickly and throughout a project. A key strength of Scrum lies in its use of cross-functional, self-organized, and empowered teams who divide their work into short, concentrated work cycles called Sprints. The Scrum cycle begins with a Business  Stakeholder Meeting , during which the Project Vision is created. The Product Owner then develops a Prioritized Product Backlog which contains a prioritized list of business and project requirements written in the form of User Stories. Each Sprint begins with a Sprint Planning Meeting during which high priority User Stories are considered for inclusion in the Sprint, during which the user stories are developed into deliverables or outputs. As we have seen that Scrum is not your regular waterfall technique but an agile framework which changes traditional roles. The Organ...

Managing Multiple teams in a Scrum Project

Image
  A project is a collaborative enterprise to either create new products or services or to deliver results as defined in the Project Vision Statement. Projects are usually impacted by constraints of time, cost, scope, quality, people and organizational capabilities. The objective of the project team is to create Deliverables as defined in Prioritized Product Backlog. The logical approach of the guidelines and principles in Scrum framework can be used to manage projects of any size, spanning geographies and organizations. Large projects may have multiple Scrum Teams working in parallel making it necessary to synchronize and facilitate the flow of information and enhance communication. Since Scrum favors small teams, one may think that this method can only be used on small projects, but this is not the case. Scrum can also be used effectively on large-scale projects. When more than ten people are required to carry out the work, multiple Scrum Teams may be formed. The project team cons...

Prioritized Product Backlog – the Backbone of a Scrum Project

Image
  The Prioritized Product Backlog is the basis on which the direction of the project proceeds. If the project is a film, the Prioritized Product Backlog is like the Script. So what does the Prioritized Product Backlog contain and how is it made? The Product Owner develops a Prioritized Product Backlog after developing Epic(s) and Personas. The Prioritized Product Backlog contains a prioritized list of business and project requirements written in the form of Epic(s), which are high level User Stories. The Prioritized Product Backlog is based on three primary factors: value, risk or uncertainty, and dependencies. It is also referred to as the  Risk Adjusted Product Backlog  since it includes identified and assessed risks related to the project. It also encompasses all Approved Changes that can be appropriately prioritized in the Prioritized Product Backlog. It is the Product Owner’s responsibility to ensure delivery of those requirements that provide the highest level of bu...

Managing multiple teams in a Scrum Project

Image
  A project is a collaborative enterprise to either create new products or services or to deliver results as defined in the Project Vision Statement. Projects are usually impacted by constraints of time, cost, scope, quality, people and organizational capabilities. The objective of the project team is to create Deliverables as defined in Prioritized Product Backlog. The logical approach of the guidelines and principles in Scrum framework can be used to manage projects of any size, spanning geographies and organizations. Large projects may have multiple Scrum Teams working in parallel making it necessary to synchronize and facilitate the flow of information and enhance communication. Since Scrum favors small teams, one may think that this method can only be used on small projects, but this is not the case. Scrum can also be used effectively on large-scale projects. When more than ten people are required to carry out the work, multiple Scrum Teams may be formed. The project team cons...

What makes a good User Story?

Image
  Good user stories are vital for a Scrum project as user requirements are primarily captured in this form. Good user stories alone are not enough to ensure that the product is of high quality. However, good user stories are important to communicate user requirements to the Scrum team to develop products of high quality. The INVEST acronym, given by Bill Wake, suggests characteristics of good user stories. The acronym stands for  I ndependent , N egotiable , V aluable , E stimative , S mall, and  T estable. Let us examine each characteristic in detail. Independent User Stories are often inherently dependent on each other. In such situations, it is not clear which story should be given the higher estimate. One of the solutions is to combine these stories into one, big independent story. If some of the needed functionality has already been created or implemented, then the estimate should be revised to reflect this change. Also, it is important to define a non...