SCRUM!

Cold Open

According to scrum.org, Scrum is a framework where people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. It implements a dynamic way of development by breaking down the problems for the developers into small problems that can be done in a sprint. While some thinks that the idea is risky, this way is actually well-thought out. This idea can be summarized into some points called “The Agile Manifesto” there 12 points.

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity–the art of maximizing the amount of work not done–is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

These points can be inferred into 4 main points which are Individuals and interactions over processes and tools, working software over comprehensive documentation, Customer collaboration over contract negotiation, and Responding to change over following a plan.

Scrum Roles

• Product owner, which responsible for the product backlog and the requirements of the product.
• Scrum Master, which responsible in maintaining and coaching the scrum team.
• Development Team, which responsible for developing and implementing the product.

Scrum Events

• Sprint Planning, will be held by first breaking up the product backlog into smaller problems. Then the product backlog will be assigned a weight as the difficulty, after all that then each of the development team can choose which backlog they want to do.
• Daily Scrum, which consists of a meeting that last for about 30 minutes where each of the member of the development team will tell their progress.
• Sprint, is where the development team does the implementation to the product.
• Sprint Review, is the big presentation of what the sprint team has achieved for this particular sprint. During the Sprint Review the stakeholders be present.
• Sprint Retrospective, is the reflection of how the Scrum went the scrum team can talk about what went right and what went wrong to improve the team dynamic for the next sprint.

source: https://guntherverheyen.com/the-scrum-values/

That’s all for Scrum, hopefully this article give you more insight about Scrum and everything to do with it.

See you next article!