Agile principle states, “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”This is why Scrum recommends co-located teams. But with the changing business realities and globalization, co-located teams are becoming more and more difficult and are slowly being replaced with distributed teams. You might ask, what…
Managing risk must be done proactively, and it is an iterative process that should begin at project inception and continue throughout the life of the project. The process of managing risk should follow some standardized steps to ensure that risks are identified, evaluated, and a proper course of action is determined and acted upon accordingly.…
Stakeholder(s) is a collective term that includes customers, users, and sponsors, who frequently interface with the Product Owner, Scrum Master, and Scrum Team to provide them with inputs and facilitate creation of the project’s product, service, or other result. Stakeholder(s) influence the project throughout the project’s development. Thus it is important to understand the risk…
In part 1 of this series, we discussed some of the common pitfalls that a Scrum team can fall into. Scrum is a highly viable software development methodology used by organizations looking for methods to advance their complex development practices. As a concept, Scrum is easy to understand and simple. However, when it comes to…
Agile methodology is a dynamic project management approach to software development and implementation. Within a few years of its inception, Agile methodology has become popular because it is both developer and customer friendly. This is because—unlike the traditional Waterfall approach—Agile methodology is an adaptive approach that permits changes and modifications to be incorporated into the…
Story point estimates are a way of estimating Agile projects. Story points are calculated using known tasks as a frame of reference to estimate other tasks. For example, if a task such as creating an input screen, for which we already know the amount of effort required to complete, has been assigned 3 points, we…
It is widely known in the software development industry that Agile values “working software” over “extensive documentation.” This leads to the common misconception that Agile does not believe in documentation. It is true that documentation in Agile does not always mean typing code descriptions or lengthy time consuming information that may come in handy sometime…
Scrum is the most widely used Agile framework for developing and managing complex software and product applications. In its simplest terms, Scrum is characterized by its core values of Plan Ahead and Inspect & Adapt. Therefore, Scrum successfully manages projects in which there is marked uncertainty and ambiguity at the early stages of the project. With Scrum, an…
Well, a User Story is basically what the user is required to perform as a part of his job responsibilities. It gets the data of who, what and why pertaining to a prerequisite in a simple and conscience way on a notecard made of paper. User Stories are written by or for the business user…
We are aware of the fact that the Scrum Master plays the role of a servant- leader who serves the needs of the Scrum Team. A Scrum Master doesn’t get involved with the development of project deliverables and lets the Scrum Team function on its own. A Scrum Master prepares the organization and the team…
