What do you mean by scrum?
I'll answer
Earn 20 gold coins for an accepted answer.20
Earn 20 gold coins for an accepted answer.
40more
40more
Harper Patel
Studied at the University of Amsterdam, Lives in Amsterdam, Netherlands.
As an expert in Agile methodologies, I can provide a comprehensive understanding of what Scrum means in the context of software development.
Scrum is a framework that supports the development and maintenance of complex products. It is designed to be lean, iterative, and incremental, allowing for flexibility and productivity. The framework is built on five values: commitment, courage, focus, openness, and respect. These values are essential for a Scrum Team to work effectively.
The term Scrum itself is not an acronym but has its origins in the business and management context. It was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 paper titled "The New New Product Development Game." The authors used the term to describe a highly adaptive and cross-functional team that could quickly respond to market changes, much like how the scrum formation in rugby allows for quick and efficient teamwork.
In the context of software development, Scrum is often used to refer to a specific set of practices and roles that facilitate the development process. Here's a breakdown of the key components:
1. Roles: Scrum defines three primary roles:
- Product Owner: Responsible for managing the product backlog, which is a prioritized list of features and requirements needed for the product. The Product Owner ensures that the team is building the right product.
- Scrum Master: Acts as a servant-leader and coach for the team. The Scrum Master ensures that Scrum is understood and implemented correctly. They also protect the team from external interruptions and facilitate the Scrum events.
- Development Team: A cross-functional group responsible for delivering the product. The team is self-organizing, meaning team members decide how to turn the product backlog items into potentially shippable increments of the product.
2. Artifacts: Scrum recognizes three artifacts:
- Product Backlog: A list of all the work to be done on the product, ordered by business value.
- Sprint Backlog: The subset of the product backlog that the team has committed to completing during the upcoming sprint, a time-boxed period (usually two to four weeks).
- Increment: The sum of all the product backlog items completed during a sprint and the work done in all previous sprints. At the end of each sprint, the increment must be in usable condition, regardless of whether the product has been released to the market.
3. Events: Scrum has five time-boxed events:
- Sprint: A time-boxed period of one month or less during which a "Done", usable, and potentially releasable product increment is created.
- Sprint Planning: The work to be done during the sprint is planned at this event.
- Daily Scrum (Daily Stand-up): A short daily event (15 minutes) for the development team to synchronize activities and plan for the next 24 hours.
- Sprint Review: Held at the end of the sprint to inspect the work done and to adapt the product backlog for the next sprint.
- Sprint Retrospective: A meeting after the sprint review and before the next sprint planning to reflect on the past sprint and identify improvements.
4. Rules: Scrum has a defined set of rules that bind a Scrum Team and ensure that Scrum is being implemented correctly.
Scrum is highly adaptable and can be used in various types of projects. It encourages close collaboration, frequent feedback, and continuous improvement, which are essential for delivering high-quality products in a rapidly changing environment.
Now, let's move on to the translation.
Scrum is a framework that supports the development and maintenance of complex products. It is designed to be lean, iterative, and incremental, allowing for flexibility and productivity. The framework is built on five values: commitment, courage, focus, openness, and respect. These values are essential for a Scrum Team to work effectively.
The term Scrum itself is not an acronym but has its origins in the business and management context. It was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 paper titled "The New New Product Development Game." The authors used the term to describe a highly adaptive and cross-functional team that could quickly respond to market changes, much like how the scrum formation in rugby allows for quick and efficient teamwork.
In the context of software development, Scrum is often used to refer to a specific set of practices and roles that facilitate the development process. Here's a breakdown of the key components:
1. Roles: Scrum defines three primary roles:
- Product Owner: Responsible for managing the product backlog, which is a prioritized list of features and requirements needed for the product. The Product Owner ensures that the team is building the right product.
- Scrum Master: Acts as a servant-leader and coach for the team. The Scrum Master ensures that Scrum is understood and implemented correctly. They also protect the team from external interruptions and facilitate the Scrum events.
- Development Team: A cross-functional group responsible for delivering the product. The team is self-organizing, meaning team members decide how to turn the product backlog items into potentially shippable increments of the product.
2. Artifacts: Scrum recognizes three artifacts:
- Product Backlog: A list of all the work to be done on the product, ordered by business value.
- Sprint Backlog: The subset of the product backlog that the team has committed to completing during the upcoming sprint, a time-boxed period (usually two to four weeks).
- Increment: The sum of all the product backlog items completed during a sprint and the work done in all previous sprints. At the end of each sprint, the increment must be in usable condition, regardless of whether the product has been released to the market.
3. Events: Scrum has five time-boxed events:
- Sprint: A time-boxed period of one month or less during which a "Done", usable, and potentially releasable product increment is created.
- Sprint Planning: The work to be done during the sprint is planned at this event.
- Daily Scrum (Daily Stand-up): A short daily event (15 minutes) for the development team to synchronize activities and plan for the next 24 hours.
- Sprint Review: Held at the end of the sprint to inspect the work done and to adapt the product backlog for the next sprint.
- Sprint Retrospective: A meeting after the sprint review and before the next sprint planning to reflect on the past sprint and identify improvements.
4. Rules: Scrum has a defined set of rules that bind a Scrum Team and ensure that Scrum is being implemented correctly.
Scrum is highly adaptable and can be used in various types of projects. It encourages close collaboration, frequent feedback, and continuous improvement, which are essential for delivering high-quality products in a rapidly changing environment.
Now, let's move on to the translation.
2024-05-10 14:07:38
reply(1)
Helpful(1122)
Helpful
Helpful(2)
Studied at the University of Zurich, Lives in Zurich, Switzerland.
Scrum is a framework for Agile software development. Let's have a look at the origins of the term 'Scrum'. And, as a result, understand that it is not an acronym. The term 'Scrum' was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their ground-breaking 1986 paper --The New New Product Development Game--.Jan 9, 2014
2023-06-14 18:02:58
Charlotte Perez
QuesHub.com delivers expert answers and knowledge to you.
Scrum is a framework for Agile software development. Let's have a look at the origins of the term 'Scrum'. And, as a result, understand that it is not an acronym. The term 'Scrum' was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their ground-breaking 1986 paper --The New New Product Development Game--.Jan 9, 2014
