This year, the company rolled out the scrum development process. From the beginning of the year to the present, it was a massive training: Ask internal teams that have implemented scrum; ask us colleagues who have attended training by Mike Cohn; invite external professional training institutions ~~~ There are many, but it seems that there is a lack of system arrangement, which is quite messy.
Last week, I attended a uperform training session entitled <user stories, agile estimating and planning> for two days. I want to say that I have improved my understanding of scrum. After all, we have been running scrum for a month or two, and I know almost everything about it. But there are also some interesting things that you may wish to record.
-
- About Lecturers
The training lecturer is Vernon, an American, but a Chinese name is Shi wenlin. I like his explanation very much. It is lively and lively, and he often makes some American exaggerated expressions. He has an interesting conversation with his Chinese assistant: He speaks English and the other party speaks Chinese. Both parties can understand it ~~~ Er, his assistant is Li guobiao. The introduction on the website is quite cool, but it seems a bit exaggerated for the performance and the reason.
-
- Cause of software project failure
At the beginning, let each of us analyze the cause of the failure of the software project we encountered. The arrows all point to "requirement". It seems that many people have realized that this is the biggest problem in software development, no wonder that so many methods have been invented to solve this problem, such as the user story and scrum that we are applying. Other listed causes include quality of design/code, communication, aggressive schedule, and risk management.
- What is Kanban?
Learn a new term in production management: Kanban. It is a management method to pull production based on the target. If it is like eating steamed buns, we can say that the store's steamed buns are packed in two cages. If a person finishes eating them in one cage, they will return the cages to the boss, the boss installs two more for you.
Eat, and take the cage back to the boss, the boss will know that it is time to give you two more, the boss did not receive the cage to give you steamed buns, it means you still have to eat, you don't need to send the cage back to the old
Board, lest the Boss send it again before you finish eating it.
Obviously, software development is not a production, creation, but rather a matter of great uncertainty. It is not suitable to use this method for management.
-
- A pig with lipstick
Someone asked if the first sprint of each project should be used to collect the user story and make the initial architecture. The answer is that this is the scrum-fall development method, that is, the combination of scrum and waterfall. In essence, it is still waterfall, just like a pig with lipstick or a pig, not a girl, the waterfall model, coupled with the form of scrum, is essentially a waterfall model. Scrum is brave, dare to get start without certainty, and keep learning and refining requirements during the development process.
-
- Innovation is not necessarily Addition
When talking about Apple's innovation, Li guobiao raised this point. I agree that, in many cases, simple search is beautiful. For example, Yahoo has been doing search for so many years, but its search box is always drowned in countless contents. Google is born and gives you a simple search box, success: subtraction innovation.
-
- Scrum difficulties: courage, TDD, clients
I raised a question and asked them what the greatest resistance they encountered when they were helping other companies implement scrum. In summary, it is courage: clients is not used to this new process of close participation; development is not used to TDD development models (they adopt TDD), and it is useless to accept this change.
- TDD first
The next afternoon, another lecturer appeared to be more senior than other students in history. They all strongly recommended TDD, just as I was convinced when I recommended "Avatar" to others: if you haven't started using TDD, you will fall in love with it immediately! In this case, although the current project does not need TDD, I must try this method myself ~
-
- Use story point to estimate the benefits of a task
We generally get used to using story point to estimate the user story, while using "Hour" to estimate each task. However, they proposed to use story point to estimate the task, which is also quite convincing: first, you can check whether your user story estimation is correct, while hour and story point are not comparable. Second, the time for each person to complete a task is different, cannot accurately reflect the "workload" of a task ". Even so, I will continue to use hour to estimate the task: We are used to this, and we use the system Jira to support this. Apart from the abstract story point, we need an intuitive view of our work.
-
- Don't push a sprint
If one finds that the story selected in the sprint cannot be completed, do not "Catch up" the construction period, which will inevitably lead to a decline in software quality. The correct method is to discover and adjust in advance-as long as our sprint goal is acceptable.
-
- Use the fucking wall !!!
Someone asked what is the best tool for implementing scrum: Of course it's a wall. It's transparent, convenient, and intuitive to display all your backlogs and burn down charts on the wall. However, I suspect that our walls will not be enough unless we rebuild them. Therefore, we will also use Jira: first, to facilitate the cooperation of distributed team, but to facilitate the inspection by the management team :)
- Metaphor: scrum and cycling
This is a good metaphor for scrum: If you plan to ride a bicycle from to, how did you do it? First, you must be sure to know where your direction is, B. Second, you must constantly adjust your direction in the course of your journey, in order to achieve your final goal and reach point B. Isn't that true for scrum development projects.
-
- People! = Resource
Shi wenlin is very disgusted with calling people a resource. This should be the general name of foreign companies. To be honest, I also quite dislike this saying, as Shi said: What is resource, just like toilet paper, if you use it, you have to discard it. you can replace it with resource.
