Get to know about Agile Scrum in 10 minutes
There are many standardized software development methods, and one of them is the method following the Agile-Scrum model which has reached immense popularity across the globe. for companies operating in the field of software production/ outsourcing, technology start-ups, etc. So why Agile Scrum?
The main motivation to use agile scrum with business is to achieve the greatest value in project teams, by deploying continuous quality software features, at less risk and with improved team engagement.
In this article, we would like to describe and share the basic concepts of the Agile philosophy as well as the theory of Scrum for you to understand whether you may personally or as an organisation benefit from this way of working.
The 5 outcomes of agile scrum and values to follow:
1) Software Quality Improvement: Scrum's Framework helps the Scrum development team to receive frequent feedback and enables the team to swiftly adjust their work to ensure the highest software quality while responding to the ever-changing market needs.
2) Shorten software release time: The Scrum model works with the main principle of breaking the software to be produced into small parts for the development called a Sprint. Each Sprint usually takes 2 to 4 weeks to complete.
3) Improve team spirit: The Scrum model applies a self-managing & self-organizing approach, with the aim that Scrum team members can work together happily, provoking creativity and proactive in surname. There is no leader but only the Scrum Master who helps the team overcome obstacles and shields the team from internal or external influences.
4) Increase customer satisfaction: The Scrum team is committed to producing products or services that can satisfy customers. The Product Owner needs to understand the project requirements and customer needs; to deliver highest value features to the clients at a faster product delivery time.
5) Good project control and minimize risk: All members of the Scrum project team have ample opportunity to test and tailor products throughout the project and ultimately make the best product. Scrum works in Sprints, so the project team can do it step by step, then learn from experience or continue to promote the advantages of the previous Sprint to improve the product in the next Sprint to avoid losses.
Scrum Team
Within an agile scrum team, there are three main roles, each with their own specific responsibilities and desired behaviours and characteristics.
Scrum Master (SM)
Product Owner / Product Owner (PO)
Development Team / Development Team (Cross Function Specialists)
Some of these roles are very technical, while others are more business or facilitator type roles. This reinforces that the tech industry can be for anyone, you just need to identify the right role for you.
1. Scrum Master (SM)
Encourage face-to-face communication, the formation of team organizations, and accountability.
Solve problems in the team, no matter who broke it or who should fix it.
Make sure the Scrum team is functional and efficient.
Conduct Scrum audits, create rules, and practice across the organization.
Provides guidance and support to the Scrum team.
Provide regular feedback to the team, and help each member of the team drive change
2. Product Owner (PO)
Provide a vision for the team, and clearly communicate this to the entire team.
Optimize and increase the value of the product.
Create and maintain the Product Backlog.
Set the acceptance criteria for each user story.
Choose what to execute and when to release.
Represent stakeholders and customers with the development team.
3. Development Team
Operate the Sprints.
Organize your own work to do.
Create an increase in products.
Work with PO and optimize value.
Usually consists of 6 (+/- 3) members.
The development team must do cross functions (backend developer, frontend developer, architect, tester, mobile developer ...)
Complete development, testing, and other engineering tasks to achieve each sprint's goal.
Attend all meetings, and report status after each day.
Artifacts
Product Backlog
List of preferred features that the product owner wants to be delivered. Product Backlog is a unit of a deliverable product with clear criteria that refers to other artifacts such as mock-ups, models, and specifications.
Sprint backlog
A list of tasks identified and prioritized by the Scrum Team will be completed during the Sprint.
During the Sprint Planning Meeting, a list of Product Backlog (PBIs) items will be selected to form the Sprint Backlog.
Scrum Events
Sprint Planning
The team develops what will be done in each sprint. This is a collaborative effort involving the Scrum Master, who facilitates the meeting and the product owner describes the details of PBIs and their acceptance criteria, helping the team determine the work and efforts to fulfill commitments in each sprint.
Inputs
Positive and motivated attendees who are mentally available, enthusiastic, and excited in attending this immensely interactive meeting.
Product backlog is refined and on top there lies the item that Product Owner (or Business) wants to implement first followed by more in priority sequence.
Team capacity for the sprint is known i.e. number of effective hours available from each team member and sum thereof. This information should be handy with Scrum Master.
Process and the activities during the meeting:
Product Owner (PO) states the Goal of the Sprint and introduces the list of priority items (stories) that the PO wants implemented by the end of the Sprint.
Development Team reviews top item (story) from the list and clarifies and defines: Requirements, Acceptance, or Done criteria of the story, All tasks to be done to complete the story, Estimation of each task.
At the completion of each item's discussion the team's capacity should be checked, and if there is more room available to fit in additional items then Step 2 need to be repeated otherwise the committed items become Sprint backlog with all the tasks defined, assigned to individuals.
The team should avoid any item with an existing impediment or dependency which is unlikely to get resolved within the certain acceptable duration and which might otherwise cause delay to complete the story within Sprint.
Outputs
Sprint Backlog i.e. stories committed for the Sprint.
Each item defined with actual tasks, assignee identified estimates, and done criteria.
The stories committed in the Sprint should be able to be completed, demoed, and deployed (released) at the end of the Sprint.
Daily Scrum
Meetings are usually held at the same place and time in front of the Scrum Board each day in the morning.
The team evaluates progress for the sprint, plans for the next 24 hours, synchronizes activities, identifies obstacles and actions.
Take place over a period of 15 minutes.
Sprint Review
The Scrum Team presents and demonstrates an increase in products.
Scrum Team and stakeholders join the meeting.
Scrum Team receives feedback from stakeholders.
The responses are noted and they will serve as a guide for the next step.
Sprint Retrospective
The three core elements that form an experimental process management model are: transparency, inspection and adaptation.
Inspect and adapt is one of the most important things in Agile Scrum and this meeting is to inspect and provide an opportunity to adapt to the Scrum team. Inspect to see how sprint passed, decide what and how to adapt to the improvement process.
Refinement Meetings
Reassessment of existing PBIs. PBR is not for current sprints, it sets PBIs for next sprints. This should be fine for refinement in the next two sprints. Therefore, sprint planning meetings will be more efficient and quick because PO and SM start planning with a clear list of user stories. If it is not completed, sprint planning will become completely erroneous.
