Scrum in five minutes-Workshop on lean and agility

After attending an agile Training Course, I sent a document and did not know what I was talking about. I just translated it and saw it. It may be a bit rewarding!

Scrum in five minutes

Scrum is a process model of agile development. It divides agile development into several steps. Here we will introduce this agile development process.

Scrum and agile methods have recently become a hot topic

A simple method for managing complex projects:
The old method is focused on continuous srack, while scrum is always focusing on releasing valuable commercial versions.

The market changes quickly, external factors become more complex, and SCRUM will make it adaptable to changes.

Scrum is directly oriented to project developers rather than technology

In short, scrum is a smart combination of practices and tests.

Question:
1. Do you want to handle demand changes more efficiently? Do you want to promote your design passion and enhance communication between customers and projects?
2. Are you ready to introduce a new leadership culture? That is, change roles and work methods, such as converting some responsibilities from the management personnel to the project team.
3. Will you follow the footsteps of companies like IBM, Microsoft, and Xerox? In addition, you can successfully point out errors in your software development process!

If your answer is yes, you must read it!

Scrum Introduction
Scrum is based on sprint, and sprint is a kind of concentrated effort to achieve a fixed goal (development process) within 30 days ).

A product owner prepares a change plan for all products and gives priority to possible features.

The product owner's work result is the product inventory (product backlog), which is actually a fixed priority and a form of what to do. Before each sprint, the target with the highest priority is converted to the sprint backlog!

Together with the user, the members of an Development Group are fixed between 5-9 people. When discussing with the product owner, the goal of the sprint begins to be determined, and the priority-marked function is then decomposed into specific tasks. The project team is self-managed, and the team members are jointly and severally liable for the results (joint responsibility )!

The SCRUM master trains the development team to eliminate all possible obstacles and fix the workload to ensure that the project team has the most likely environment to achieve the fixed goal of the sprint.

Each sprint needs to increase the market value of the product, add new features, and enhance them so that the product can be released to users!

Role
Scrum Group
A scrum group is a real worker and a problem solver and a special functional designer. According to experience and research, it is usually the best way to work if the members of a group are fixed between 5 and 9.
The team members decide how to arrange the work and how to assign the specified task. There is no project role given here, and each success must be able to switch tasks from another member. Naturally, this will not impede the expertise of some individual members in their fields.

Product owner
The product owner is the person who expresses the voice of the customer. From a business perspective, it measures whether the scrum team is doing the right thing. The product owner manages the inventory of the product (that is, the demand inventory, which is described later), that is, a list of tasks to be completed. The task list is based on the more favorable principles. The document is visible to everyone in the Organization, so that everyone can feel what the product will look like in the future.
The product owner is usually a customer, but it can also be a part of an internal organization. The entire task requires understanding of the engineering, marketing, and commercial processes.

Scrum Mentor (master, who guides scrum Development)
A scrum mentor is a combination of coaches, agents, and supervisors. A scrum mentor is a daily short meeting with the project team. When people outside the project team have important things to discuss with the project, the scrum mentor should ensure that the developer is as little as possible to distract his work.
Scrum instructors always take the current situation to deal with their work, and always focus on providing the best environment for the project team to implement the tasks given in the sprint.
After each sprint, the scrum mentor will initiate an evaluation meeting on the scrum group called the sprint review meeting. In this meeting, we should review the experience and summary. The goal is to improve the knowledge of the project team and enhance the motivation of the project team in the next sprint.

Process
Create a required storage (backlog)
The product owner edits all the requirements and special functions, which are the basis of product changes, such as a new function and bug modification. After the goal is set, each functional entity is broken down into small fragments. Each small clip
It should be in a small way to create business value, and it can be released in the form of a subset in a small part. (It can be released in the form of a patch)
At the same time, a list sorted by priority should be completed. At this point, the product owner makes this decision. What priority should these modifications or releases be given? This result is a decision table about what to do. It is determined by the market requirements and the requirements that users will change over time. When it comes to a new sprint, the product owner "freezes" the most important items in the task list and invites the project team to start a sprint.

Sprint stage
In the 30 days of the sprint, the first thing to do is to help create a sprint demand library. When the tasks and requirements have been determined, the product owner should let the developers do it.
Since then, the scrum group has been working under its own responsibility. If the group has been stabilized, the job is self-organized.

Daily scrum
Every day, at the same time, the scrum mentor and members will have a short meeting. The purpose of this meeting is to eliminate all factors that impede the progress of the project team. Each participant should answer these three questions:
1. What did you do after the last meeting?
2. What are you going to do between the next meeting and the next meeting?
3. Are there any factors that impede your planning?
The previous two questions gave all participants an overall understanding of the project progress. The third problem provides a foundation for difficult solutions-from correcting the computer's mouse to improving company management.
Anyone can attend the meeting, but only the scrum master and project team members can speak.

Demonstration and evaluation
There is a demo at the end of each sprint. This demonstration is to check whether the software functions can run before a large function group is merged, including the product owner, and the users and Representatives manage the software in collaboration. This is the basis for evaluating meetings in turn and the start of the next sprint.

A burndown chart is used to identify the saved work in days. This chart clearly shows the work done by a sprint on an hourly basis.

Agile development methods
What is agile development is divided by scrum, which focuses on some work methods and work boxes:
* Improve the ability to respond to market demands and needs
* Reduce waste and wait
* Reduce the workload of employees and increase output

All of these will be noticed as long as they can walk along with agility at work. It is no exaggeration to say that the entire IT industry is facing an agile trend. The following table has been summarized in Philosophy:

Important more important
Unique process and tool Interaction
Detailed documentation of workable Software
Contract and negotiation work with customers
Adapt to changes as planned

In theory, agility is good for the process, but it is not always the case in practice. Therefore, agile methods are also described as experience-based completely based on actual experience and proven working methods.
An explicit concept of agile methods is to adapt to changes in external factors. When the old methods predict and try to predict future needs, Agile Methods actively and quickly adapt to new needs, along with the motto of "Embracing Change. The only way to measure success is a workable product.
Another important principle is simplicity and lean thinking. According to the concept of agility, large-scale projects cannot be described by themselves. Instead, it is more likely to maximize the workload, which is actually not needed. These include taking the time to write useless documents,

Other Agile Methods
Together with scrum, eXtreme Programming is a well-known agile method. Extreme Programming (XP) is very difficult to implement. It is more than a method, a method that should be done in the project. In 12 fixed basic practices, queuing programming and output test cases are two good examples before coding.
Another agile method is lean development, which is derived from the just-in-time of the manufacturing industry and the concept of lean products. Lean development processes the company's development activities at the management level.
These agile methods can be considered complementary:
* Lean development processes principles to be understood throughout the Development Organization
* How should scrum process project organization and planning,
* How should XP Process Code?

FAQs about lean Agility:
Will scrum go wild because everyone does something different from their design? Is there such an important risk?
From a large amount of project experience, this will not happen. The reason is that these principles are easy to understand, and the project team releases an available version every 30 days. They work together for allCodeTaking responsibility also makes scrum developers more passionate about setting routines and rules.

Can scrum be used only for small projects?
No, these methods can be combined into a large-scale project by putting several small project teams together. A scrum called scrum can contain hundreds of developers to organize and manage several dozen scrum groups.

How should I start?
One common method is to learn from one or more people and become a scrum mentor. Many companies now offer such courses. Another option is to start a pilot project that allows several developers with scrum experience to assume the role of a mentor in the group, such as a scrum mentor or scrum master.

What if the job cannot be completed?
Scrum is not allowed to change the release date! If you lag behind, you can delete your functions from the product library of the scrum group. If you are ahead of schedule, you can ask the product owner for more functions.

Must a scrum be 30 days?
It is not necessary, but each scrum time should be the same throughout the project development process. In addition, experience tells us that 30 days (about 1000 working hours in a group) is a good compromise between a comfortable working environment and adaptability.

What should the project manager do?
Scrum does not have this role. A product manager is more inclined to be an administrator, usually as a product owner. Those most suitable for coaching are likely to be better suited to become scrum mentors.

How is scrum mixed with CMM?
A good CMM method is required in a scrum project, but it usually does not have a specific CMM role. The running CMM process is a group of self-management and evolution. Continuous integration and automated testing should be used as much as possible for a small CMM process.

Is the scrum Method Applicable only to software development?
No. These methods can adapt to all different types of projects, such as newspaper production or medical development.

Where did scrum come from?
The word scrum comes from rugby, which describes a closely shoulder-to-shoulder rugby formation used by all players to move the ball forward together. This term was first used by Takeuchi and nonoka in a famousArticleThese articles are used to describe the most successful product development projects in Japan in Harvard Business Review.

Vocabulary
Adaptive Adaptation: here, the project's goals or plans should adapt to changes in external factors.

Burn-down char a piece of software used to monitor a piece of data in a sprint is not implemented much.

Daily scrum is short, meeting every day (about 15 minutes), recruiting between the scrum mentor and the scrum members. It aims to keep the workflow going smoothly and clear all obstacles.

Empirical, based on experience.

Agile development is a software development theory. It focuses on, adaptability, ideas and short paths of implementation, and simplified cooperation. An example of agile development methods includes XP and scrum.

Sprint explain spective the review meeting after each sprint is completed (about 3 hours ). Scrum mentors and scrm masters review what is done well and what will be added in the next sprint.

Predictive prospective, here, refers to the external factors identified before the project's goal and plan based on prognosis.

The product backlog is the list of tasks to be performed. It includes the purpose and priority of the project. Managed by the product owner.

The product owner, the product owner, is responsible for the product's backlog, and must ensure that the project is oriented to the goal of maximizing business interests.

Release backlog is the same as product backlog, but it indicates that it has been completed.

The SCRUM Master Scrum mentor can be considered as the leader of the scrum group.

Here, the scrum team is a new force in the work. In the scrum project, it is the software designer who manages his own work and does not need formal Group administrators (team leaders ).

A commitment iteration of the sprint scrum Development Team, usually 30 days, is used to concentrate on achieving the goals set in the sprint backlog of the project.

Srpint backlog a task list for a sprint. It sets the highest priority for the target set by the product owner. The final form is given at the beginning of a sprint meeting, this meeting was attended by the product owner and the project team.

Sprint review an Informal Meeting (about 4 hours) after each srping. The development team is required to participate. If possible, it will show the functions to managers, customers, and product owners, indicating that the tasks have been completed in this sprint.

Timebox is a time period. In this time period, something should be developed. A sprint is the result of thinking about the time period. The deadline should not be exceeded -- otherwise, a given task will be deleted.