Scrum Fundamental

4 min readMar 25, 2021

1. What is Agile?

Agile Software Development help deliver the customer’s value early and involves the customer tightly in the development process.
Agile provides definitions that the practitioners must adhere to.
There are 12 principles:

In short, there are 4 main points that need to remember about the AGILE
1. Satisfy the customer through early continuous and valuable software. Deliver frequently shippable product increment of functionality, from a couple of weeks or a couple of months, with a preference to the shorter timescale.
2. Always welcome the customer to change the requirement throughout the processing.
3. Stakeholders work tightly together.
4. Create a pleasing environment not only for the team to communicate easily but also to motivate, trust, and empower them to make their own decision and to get the job done.
The Agile characteristic:
1. Iterative/Sprint: every sprint is usually from 1–4 weeks. The development team performs all necessary tasks such as planning, requirement analysis, design, implementation, and testing (to varying degrees) to produce small parts of the product.
2. Incremental and Evolutionary: by the end of every iterative/sprint, there is a usable small functionality would be delivered to the customer. All of them would be accumulated and grow up to satisfy the customer’s requirement.
3. Adaptive: because every iterative/sprint lasts in a short time, it could be adjusted easily.
4. Cross-functionality and self-organization: no hierarchy, the whole team can share the role and take their own decision.
5. value-based development: only focus on valuable functionalities. So, there is no redundant work.

There are 3 characteristics:
1. Transparency: all members would know the information such as the vision of the product, customer requirements, work progress, problems, and barriers.
2. Inspection: keep detecting the issue throughout the developing period and find the solution for it. It makes the product more sustainable.
3. Adaptation: because of the short timespan of iterative/sprint, it’s not much waste time to adjust the requirement or previous functionalities.

Product Owner: is the key leading to the success of the product. The person defines the requirement, tests, and evaluates the result at the end.
Scrum Master: the person that has knowledge about Scrum and makes sure every member can work efficiently.
Development Team: self-control, transform the requirement to the functionality of the product.

Sprint Planning: hold at the beginning/ending of a sprint, the development team agrees to complete a set of product backlog items. It roughly around 1 hour. The longer the sprint is the longer this takes.
Daily Scrum Meeting: an early meeting takes around 15 minutes every day to report the task’s progress and also share the difficulties with the team to get the solution.
Sprint Review: would be held at the end of the Sprint around 2–4 hours. The whole team will review all the features that have been built in the Sprint.
Sprint Retrospective: Take place right after Sprint Review. With the help of the Scrum Master, the development team will review the working process and optimize it better.
Backlog Refinement Meeting (optional): around 1 hour between Product Owner and team when the Sprint ends. The purpose of the Backlog Refinement Meeting is to decompose the highest priority items in the product backlog into user stories that are suitable for inclusion in the next sprint.

Product Backlog: The features are defined and prioritized by the Product Owner
Sprint Backlog: The features from the Product Backlog would be discussed and picked by the team. Sometimes, the big feature would be breakdown into smaller features.
Burndown Chart: is used to keep track of the progress of the Sprint.