Scrum Agile development?

What is scrum? To be blunt is to bring in some rules, team members plan projects according to scrum rules, execute projects, and complete projects. Enables teams to work more efficiently

There are many other things like Kanban,xp,rup (too many rules) in addition to scrum:

Scrum :

• Split the organization into small, cross-functional self-organizing teams
• Split the work into a series of small and specific deliverables. Sort by priority to estimate the relative amount of work for each task.
• Split the time into a fixed-size short iteration (usually 1-4 weeks), at the end of each iteration, to the basic
• Demonstrate with the delivered code. Review the release objectives with the customer at the end of each iteration and optimize the release plan accordingly, updating the task priority.
• Review and process optimization after each iteration.

Scrum three roles are defined: Product owner (depicting product vision, defining priority), team (implementing product), Scrum Master (removing barriers, leading process operations).

Scrum can be divided into three phases, and there are three scrum scenarios that each team can use as appropriate:

• • At the beginning of the iteration: Taking into account the priorities defined by the product owner and their own productivity, the team selects a certain number of entries from the product backlog to create an iterative plan.
• • Iterative: The team is fully committed to the task. The iteration range is fixed.
• End of iteration: The team demonstrates to the relevant stakeholders the code that they can work with, ideally, the code can be published (tested and delivered). The team then reviews and discusses how to improve the process.
• 　　

The following is an introduction to the following scrum Kanban, the simplest of which can be listed in three columns to Do;ongoing;done, where ongoing is the WIP (work in progress) that needs to be set to a maximum of productivity

Incidentally introduce the following kanban:

Visualize the process

1. Split the work into small pieces, a card to write a task, and then put the card on the wall.
2. Each column has a name that shows where each task is located in the process.
3. Limit WIP (in-product, work-in progress)-explicitly limit the number of simultaneous tasks on each state in the process.
4. Measure the production cycle (the average time to complete a task, also known as the cycle cycle), to tune the process to minimize the production cycle and make it predictable.

Kanban does not specify any roles.

Scrum Agile development?