Business justification demonstrates the reasons for undertaking a project. It answers the question “Why is this project needed?” Business justification drives all decision making related to a project. So, it is important to assess the viability and achievability of a project not only before committing to significant expenditures or investment at initial stages of the…
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…
“We are uncovering better ways of developing software by doing it and helping others do it.” This is how the Agile Manifesto starts. In simple words, the way people have learned better ways of implementing Agile is by doing it and trying out things. As such, practitioners have tried out multiple things and some of…
One of the Agile principles is, “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.” This is taken by most practitioners as the rationale for collocated teams. There have been several debates around the possibility of teams which are distributed and how that would work in…
Scrum supports the practice of using cross-functional, self-managed teams in which individuals help each other in completing tasks to deliver value. The SBOK™ Guide says that employees “deliver much greater value when self-organized.” Self-Organization encourages team members into taking ownership, being entrepreneurial, and contributing the best that they genuinely can. So Scrum discourages appraisal methods like Stacked…
Every project is uncertain. To deliver projects successfully using Scrum, one needs to avoid the pitfalls in implementation of the Scrum framework. One of the more important ceremonies in Scrum is “Sprint Planning Meeting”. Not giving due importance to this ceremony can be detrimental not just to the concerned Sprint but also to the entire…
The key stakeholder of Scrum Projects is the Product Owner 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…
We know that 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 members to adopt the Scrum…
