What is Scrum? Project organization process according to Scrum

Currently, the Scrum model is widely applied in enterprise project management activities. So what is Scrum ? How does the project organization process according to Scrum take place? In the article below, 1C Vietnam will provide detailed basic information about this project management model.

1. What is Scrum?

Scrum is an agile project management framework used for product development, especially software. In Scrum, work is done by a small, self-managed team, called the Scrum team. The Scrum team will do work in short iterations, called Sprints. Each Sprint has a fixed duration, usually lasting from 1-4 weeks.

The Scrum model is an agile project management framework used for product development

2. Who is the Scrum model intended for?

Scrum was initially mainly used for software development projects, but in fact this model can be used for many different businesses and project development teams. Regardless of whether projects or products are complex and the results are difficult to predict, the scrum model can be applied.

Today, Scrum is used by many large organizations, including Facebook, Google, Microsoft, the US and UK governments, Spotify, Daily Mail, The Times & Sunday Times, Sky, the European Space Agency, Twitter and universities.

Scrum is mainly used for software development projects

3. 3 main pillars of Scrum

Scrum is a practical process built on three pillars, including transparency, inspection, and adaptation.

3.1. Transparency

Transparency is understood as providing complete, accurate and timely information to all Scrum members. This helps each member clearly understand the goals, progress, and results of the project, thereby being able to coordinate and adapt effectively.

In Scrum, transparency is demonstrated through meeting events such as Sprint Planning, Sprint Review, Sprint Retrospective and Daily Scrum:

• Sprint Planning helps clearly understand the goals of the Sprint and the work that needs to be done.
• Sprint Review helps evaluate Sprint results and identify areas for improvement.
• Sprint Retrospective allows finding ways to improve workflow.
• Daily Scrum helps update progress and adjust plans if necessary.

Transparency is a prerequisite for inspection and adaptation. Lack of transparency will make implementation of the remaining two pillars difficult or even impossible. For example, if developers do not know the product requirements clearly, it will be difficult for them to implement features that meet user needs.

Transparency helps members clearly understand project goals, progress and results

3.2. Inspection

To ensure product quality and avoid errors compared to initial requirements, businesses need to conduct regular and periodic inspections. Inspection is carried out at a certain time and should not interfere with the production process.

Inspection to ensure product quality, avoid errors compared to requirements

3.3. Adaptation

Products and processes need to be designed and developed flexibly to adapt to changes from many factors, such as:

• Deviation from Product Roadmap
• Market needs change
• Customer's request
• The development of technology

For example:

• The development team needs to adapt their product at the end of each Sprint, to match the product development roadmap, with the requirements of customers and stakeholders.
• In case market demand changes, the development team needs to quickly adjust the product to meet new needs.
• Teams also need to consider applying new technology (if necessary) to improve work efficiency.

Products and processes need flexible design to adapt to change

4. Scrum values

A complete Scrum model includes the following 5 core values:

• Focus: Everyone focuses on the team's sprint goals. This means they have to eliminate extraneous tasks and focus on the most important things.
• Courageous: Scrum encourages everyone to voice their thoughts and opinions, even if they are opposing opinions. This requires courage to face negative feedback or rejection.
• Commitment: Scrum is based on everyone's commitment to common goals and plans and a willingness to change plans if necessary. However, they also have to work hard to achieve their set goals.
• Openness: Scrum requires transparency and openness in communication. This means that all members must be willing to share their information and ideas with each other.
• Respect: Scrum is based on mutual respect between team members, even when disagreeing with individual opinions.

The Scrum model includes 5 core values

5. Tools of the Scrum model

The tools of the Scrum model are important factors that help businesses manage projects effectively and quickly achieve their goals. Here are the 4 main tools in Scrum:

5.1. Product backlog

Product Backlog is a list of tasks that need to be completed to develop a product, managed by the Product Owner. This list includes features, requirements, upgrades, or bugs.

The Product Backlog is arranged in order of priority, usually the most important tasks will be at the top of the list. The Product Owner needs to regularly monitor the Product Backlog to ensure it accurately reflects customer and market needs.

Product Backlog is a list of work that needs to be completed

5.2. Sprint backlog

Sprint backlog is a list of tasks the development team chooses to perform during a Sprint. Before each Sprint, the development team will meet Sprint Planning to select tasks from the Product backlog. The Sprint backlog can change during the Sprint, but the Sprint goal cannot change.

The Sprint backlog is a list of tasks the development team chooses to perform

5.3. Increment (Sprint Goal)

A Sprint goal is a specific, measurable and achievable goal within a Sprint. Sprint goals are set during the Sprint Planning Meeting. The function of the Sprint goal is to guide implementation and allow the Scrum team to evaluate the success of the Sprint.

Sprint goals are managed by the Development Team and Product Owner. The Development Team is responsible for implementing the Sprint goal, the Product Owner is responsible for confirming the Sprint goal has been achieved.

Sprint goals need to be specific and measurable

5.4. Burndown chart

Burndown chart is a chart that tracks the amount of work remaining in the Sprint backlog over time. Burndown chart is updated daily in Daily Standup Meeting. The function of the burndown chart includes tracking development progress during the Sprint and allowing the Scrum team to detect problems early.

Burndown charts are used by the Development Team to track development progress during the Sprint. If the burndown chart is not going according to plan, the Development Team needs to take actions to resolve the problem.

Burndown chart - Chart that tracks the amount of work remaining in the Sprint backlog over time

6. How does the Scrum process work?

Scrum is one of the popular methods used by businesses when managing projects. So what is the Scrum process and how is it specifically applied step by step? Here are 6 steps to use the Scrum model effectively for businesses:

6.1. Organize backlogs

The Product Owner (PO) is the person responsible for organizing the backlog. The PO needs to have a clear vision of the product, and be sensitive to the market and customer needs to promptly adjust plans when necessary.

Besides, PO is also a bridge between users, customers and development teams. PO will receive feedback from both sides to build a list of tasks that need to be implemented in the next time.

6.2. Sprint planning meeting

During the meeting, the development team will determine the goals of the Sprint and plan the work that needs to be done.

Sprint goals are determined based on each specific product. User stories will be added to the Sprint backlog from the Product backlog and need to be approved by team members for implementation.

At the end of the Sprint Planning meeting, the development team needs to clarify with each other what needs to be delivered during the Sprint and what the delivered product increments will look like.

Sprint planning meeting identifies goals and plans work to be done

6.3. Developments during the Sprint

Sprint is a certain period of time, lasting from 1 to 4 weeks, in which the development team coordinates with each other to complete a portion of product growth (increment). The Sprint scope of work can be renegotiated between the Product Owner and the development team, if necessary. All Scrum events take place within a Sprint.

6.4. Create daily meetings

Daily Scrum is a short meeting that takes place every day at a fixed time. The purpose of the Daily Scrum is to check progress toward the Sprint goal, adjust the Sprint Backlog if necessary, and plan work for the next 24 hours.

Meetings should only last 15-30 minutes. During this meeting, members will answer 3 questions:

• What did you do yesterday?
• What will you do today?
• What difficulties are you facing?

Daily Scrum helps check progress, adjust the Sprint Backlog and plan the next work

6.5. Sprint review meeting

Sprint Review is the final meeting of a Sprint, where the development team will present its achievements to the Product Owner and other stakeholders.

During this meeting, the development team will demo the increment - the product growth they completed in the last Sprint. They will also share details about how they implemented Increment as well as the challenges and difficulties they encountered.

The Product Owner will listen to the opinions of the development team and make a decision on whether to release an increment or not. In addition, the Product Owner will also use this meeting to update the Product Backlog for the next Sprint.

6.6. Sprint retrospective meeting

Retrospective is a Sprint summary meeting, where development team members sit together to evaluate what was achieved and what was not good in the past Sprint. The purpose of Retrospective is to help the development team look back at the past process to gain experience and find areas for improvement to improve efficiency in the next Sprint.

Sprint improvement meeting to reflect and learn from experience

7. Manage Scrum effectively with Office software 1C:Document Management

Currently, through modern technology platforms, project management according to the Scrum model becomes easier with the support of software. In particular, 1C:Document Management solution is a digital office tool capable of effective Scrum management, contributing to helping businesses achieve their goals and plans.

Office Software 1C:Document Management is a solution to automate document management, processes and work administration. Developed on a modern technology platform, the software provides the ability to support centralized storage of structured and unstructured information on a single system, helping individuals and organizations manage their work. anytime, anywhere, even on mobile devices.

In addition to modules related to document management, process management, and digital office management, the software can also manage the entire life cycle of a project. With the support of powerful features in the project management module of 1C:Document Management, businesses can manage Scrum simply, quickly and effectively.

Office software No. 1C:Document Management helps manage Scrum simply and effectively
Thus, the content of the article above has specifically presented the concept of Scrum and how the project organization process follows the Scrum model. In addition, businesses can apply supporting software such as Office software 1C:Document Management to help manage projects automatically, simply and effectively anytime, anywhere. Contact 1C Vietnam immediately for consulting support on project management solutions suitable to the specific characteristics of your business.