Agile
Agile
A product owner is a person responsible for maximizing the value of the products created by a scrum
development team. Here the value stands for the business value of the product.
SCRUM MASTER
The scrum master is the one responsible for ensuring that the team follows agile values, principles, processes and
practices. He is also the one who facilitates meetings and is the medium between the product manager and the
development team.
DEVELOPMENT TEAM
It is the development team that takes the feedback from the scrum master and the product owner so that the
product does not steer away from the business value and is delivered on the agreed time frame.
Agile Scrum is a project management methodology which focuses on enhancing the collaboration and communication of the
team which helps to address complex issues in a simpler way
It creates a positive impact which enables team members to work towards efficient and quicker completion of the project.
SCRUM ARTEFACTS
Transparency plays a key role in the scrum. The artefacts were created to ensure that the transparency is
maximized, and everyone has the same understanding of the artefact at any point in time.
SPRINT BACKLOG
A sprint is set period during which specific work must be completed and should be ready for review.
The goal of the sprint backlog is to discuss and prioritize the user stories which are to be pushed to the sprint.
The scrum master should make sure that there is active participation by every member of the team.
Neither the scrum master nor the product owner should try to intimidate or coerce team members towards the
desired opinion, which destroys the whole point of using agile methodology.
PRODUCT INCREMENT
The product increment is a sum of all the completed product backlog items plus the value of all the previous
increments.
The product increment provides a transparent and accurate state of the product at each sprint.
SCRUM CEREMONIES
Ceremonies in a scrum are also known as meetings. The use of such a traditional word should give you an insight to the
importance given to meetings
There are four ceremonies in a scrum.
SPRINT PLANNING MEETING
Sprint planning is a collective effort of the scrum master who facilitates the meeting, product owner who clarifies the details of
the product backlog items with respect to acceptance criteria and the entire development team which develops the product.
This is a timed session which may last roughly 1 hour and is conducted before every sprint backlog.
In sprint planning the entire team agrees to complete a set of product backlog items.
This agreement defines the sprint backlog and it is based on the team’s tempo or capacity and length of the sprint.
Here every team member provides an update on the work assigned to him in the previous scrum.
They are also supposed to inform about the impediments which may become problematic in the future and whether they
require help from other team members if the task is too complex.
The scrum master and the product owner must take steps to ensure that all the deadlocks are taken care of and have a
contingency plan in case of any new obstructions.
SPRINT REVIEW MEETING
As we already know that the purpose of a sprint is to deliver a potentially shippable product.
The scrum team is supposed to demonstrate their accomplishments during the sprint review, hence this is also known as
the sprint demo meeting.
This meeting needs to be informal otherwise the team members will end up wasting precious time for creating
presentations instead of just showcasing their product.
It is done to take note of the things which went wrong and the impediments which delayed the process.
Bottom line: The sprint retrospective meeting is done to analyze the mistakes done in the just concluded sprint so that the
mistakes can be avoided in the next sprint
The Agile Scrum methodology is one of the most popular methodologies in the world and it is because of its advantages or
benefits which other methods fail to deliver. Here are the major benefits of Agile Scrum methodology
•Scrum needs to be exercised only by the experienced people otherwise it will end up becoming the kryptonite of
the organization.
•If the tasks are defined poorly, the project often becomes a victim of inaccuracy
•As it is a new technology it will take time for any organization to get accustomed to it
https://www.digitalmarketplace.service.gov.uk/g-cloud/services/720500939254377