The daily Stand-up or Scrum meeting is a daily meeting which provides status update to all the team members. Every member focuses on answering three statements: Task Completed Task to be done Road Blocks It’s very powerful tool and it keeps the project moving in the planned direction. If team does not follow the Rule…
Leadership styles vary depending on the organization, the situation, and even the specific individuals and objectives of the Scrum project. Some common leadership styles described in the SBOK are as follows: Servant Leadership—Servant leaders employ listening, empathy, commitment, and insight while sharing power and authority with team members. Servant leaders are stewards who achieve results…
Scrum developers, also referred to as the development team or Scrum team, are responsible for developing the product and they possess all the essential skills required to carry out the work of the project. They have a high level of collaboration to maximize productivity, so that minimal coordination is required to get things done. To…
A Product Owner’s role is one of three core roles in Scrum. Together with a Scrum Master and the development team, a Product Owner can be considered one of three legs that make a tripod. A good Product Owner is crucial to the success of a Scrum project. The Product Owner plays a crucial role by…
The objective of the Scrum Team members, the Scrum Master should be to minimize the risk involved in attaining the project objectives if not to remove it completely. Therefore, the Scrum Teams and the Scrum Master should spend their time to attempt to identify the potential risks that impact the project. This can be achieved…
Time-boxing is a technique to limit the time spent to accomplish a task. A fixed amount of time is allocated to complete each process and activity in a scrum project. After the allocated time is over the task or goal is either accomplished or incomplete, but the time cannot be extended. Why Time-boxing? Time-boxing ensures…
Risk Prioritization Scrum allows for quick identification and assessment of risks. Identified Risks are taken into account when creating a Prioritized Product Backlog during the Create Prioritized Product Backlog process, or when we update the Prioritized Product Backlog during the Groom Prioritized Product Backlog process—so a Prioritized Product Backlog could also be referred to as…
Quality control refers to the execution of the planned quality activities by the Scrum Team in the process of creating deliverables that are potentially shippable. It also includes learning from each set of completed activities in order to achieve continuous improvement. Within the cross-functional team, it is important to have the skills necessary to perform…
Any Scrum Master worth his Scrum Master certification believes that all humans are enthusiastic and seek to receive greater duty. So, they deliver much greater value when self-organized. This self-organization is what created us from single celled beings. A Scrum Master brings working deliverables sooner and makes available more precise predictions of timetable and budget compared…
Sprint Retrospective is a meeting convened by the Scrum Master in which the team talks about the previous sprint and decided on how to make the next sprint productive. This meeting differs from a Sprint Review meeting. In Sprint review meeting the team looks into what the team is currently working on whereas the Retrospective…
