Scrum Overview
The SCRUM overview is nothing more than agile declaration, agile principles, scrum frameworks and values. Before that, let's take a look at some professional scrum introductions.
Scrum is a development framework for developing products or projects in an iterative and incremental manner across functional teams. It makes the development group known as the sprint work cycle. Each of these iterations does not last more than four weeks (the most common is two weeks), and is continuously performed without intervals. The Sprint is limited by the time box. whether the work is completed or not, it will end on a specific date and never extend. Generally, the scrum team selects the duration of a sprint and uses this duration for all of their sprints until the team's capabilities are improved and can use a short cycle. At the beginning of each sprint, cross-functional teams (about 7 members) select items (customer requirements) from the list of priority levels ). Teams should agree on which sets of goals they believe they can deliver at the end of the sprint, which should be tangible and truly "completed. New items cannot be added during the sprint. Scrum accepts changes only during the next sprint. In the current short sprint cycle, only short, clear, and relatively fixed goals are concerned. The team conducts brief meetings every day to test the work process and adjust subsequent steps to ensure that the remaining work is completed. At the end of the sprint, the team and stakeholders will review the sprint and demonstrate the Products built. The team members can obtain feedback that can be combined with the feedback in the next sprint. Scrum emphasizes the creation of work products that are truly completed at the end of the sprint. In the software field, it refers to an integrated, fully tested, and potentially deliverable system that has generated documents for end users. Let's take a look at the scrum framework.
Agile declaration of agile development
Agile Software Development Declaration
We have been exploring better software development methods in practice,
While helping others. Therefore, we have established the following values:
Individuals and interactions are higher than processes and tools
Working software is higher than detailed documentation
Customer cooperation is higher than contract negotiation
Response changes are higher than follow-up plans
That is to say, although the right item has its value,
We pay more attention to the value of the Left item.
12 agile principles of agile development
1. Our most important goal is to satisfy our customers through continuous and early delivery of valuable software.
2. We are happy to face changes in requirements, even after development. Master the changes in the agile process for the customer's competitive advantage.
3. often deliver software that can work, several weeks or one or two months apart, tends to adopt a short cycle.
4. Business and development personnel must cooperate with each other, and every day of the Project is no exception.
5. inspire individual morale and build projects with them as the core. Provide the required environment and support, coupled with trust, to achieve the goal.
6. whether inside or outside the team, the best and most efficient way to deliver information is face-to-face communication.
7. Workable software is the primary measurement of progress.
8. The agile process advocates sustainable development. The responsible person, developers and users should be able to maintain a stable and continuous pace together.
9. persistently pursuing technical excellence and good design, and increasing agility.
10. being concise, it is an art to reduce unnecessary work.
11. The best architecture, requirements, and design come from a self-organizing team.
12. The Team regularly reflects on how to deliver results and adjust their behavior in sequence.