A routine question before starting a project is “Why is this needed?” Such a question might be posed by primary school students who are assigned to create a diorama about the water cycle. But the question is just as likely to be raised when dealing with large projects in the corporate world. The answer to…
The answer to this question is No. Release planning is a very important part of the Scrum process. In this process, the Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule, which is essentially a phased deployment schedule that can be shared with the project stakeholders.…
An integral part of the Scrum process is the Daily Scrum meeting which is a regular ritual practiced every morning. The team comes together on each working day about the same time to discuss the status of the project. The synonyms to the Daily Scrum meeting include “Daily Stand up”, “Daily Scrum”, and “Scrum Meeting”…
Personas are highly detailed fictional characters, representative of the majority of users and of other stakeholders who may not directly use the end product. Personas are created to identify the needs of the target user base. Creating specific Personas can help the team better understand users and their requirements and goals. Based on a Persona,…
In a Scrum project, it is the Scrum Team members who are responsible for delivering the desired product or service and not the Scrum. Hence, we should be careful in forming the Scrum Teams. The Scrum Team is sometimes referred to as Development Team since they are responsible for developing the product, service or other…
A typical Prioritized Product Backlog will contain all User Stories, their time estimates (including any revised estimates), and the status of higher priority requirements. Any new or revised User Stories resulting from changes to business requirements, customer requests, external market conditions, and/or lessons learned from previous Sprints are also incorporated. Product Backlog Review Meeting Also…
The role of a Chief Scrum Master is necessary to ensure proper collaboration among the Scrum Teams. Coordination across various Scrum Teams working on a project is typically done through the Scrum of Scrums (SoS) Meeting. There is no hierarchy between the Scrum Masters: they are all peers. The Chief Scrum Master just works on…
Agile and Waterfall are two different methods used in managing a project. Both the methods have their own pros and cons and choosing one model is based on many project-centric factors. Waterfall Method The Waterfall model is a progressive design process which in the software development industry goes through stages such as Conception, Initiation, Analysis,…
Selecting appropriate Scrum Master(s) and identifying relevant Stakeholder(s) is crucial to the success of any project. In some projects, there may have been pre-conditions stipulating certain team members and their roles. When there is flexibility in choosing the Scrum Master(s), the following are important Selection Criteria: Problem-solving skills—This is one of the primary criteria to…
Release Planning Sessions are conducted to develop a Release Plan. The plan defines when various sets of usable functionality or products will be delivered to the customer. In Scrum, the major objective of a Release Planning Meeting is to enable the Scrum Team to have an overview of the releases and delivery schedule for the…
