How I was taught to work. Second day
The first day
On the second day, we had a seminar on the SCRUM and Agile project. It told the practical application of the Agile project in software development.
')
Apparently, the lecturer's favorite story, because the slide met with her in presentation 7 times :)
And so, met the pig and rooster. Rooster offered to open his restaurant and call it "Pork and Eggs." To which the pig refused: "You will only participate, and I will give myself entirely."
In terms of SCRUM pigs are developers, the rooster is a project manager. The essence of the story: the pig is more important than the rooster. The essence of SCRUM: developers are more important than a manager, you can not ignore the opinions of the first.
The leaders of large software companies decided to develop a common style of work, which was later called Agile.
The main document, one might say, the code of commandments, is the manifesto "Manifesto for Agile Software Development".
It reads:
People and relationships above processes and tools
A working product is better than detailed documentation.
Customer relationship is more important than signed contracts.
Readiness for change is more important than following plans.
In English
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
At the forefront is a person, because it is he who produces the product. If the process causes irritation, it should be changed. If the tool is inconvenient, it should be discarded.
The customer pays for the working draft, and not for its description.
It is also important to be ready for changes in the project. The team must be flexible in terms of opportunities.
The main principles are:
I will explain a little. Agile is customizable. But this does not mean that any whim should be performed without primitive. It is necessary to ensure a dialogue between business people, customer and programmer.
The product should be released quite often - it's like a blog - the more often you write useful posts, the more people read you and are not removed from friends. The customer does not need a product that is updated every half year and increases the functionality for a couple of features. There is still need to remember about competition.
Well, a satisfied and motivated programmer will write the code better than if he were sitting in a damp basement and was undernourished.
There are two more points. They are technical.
1. Each new version of the product should do more than the previous one.
2. You need to initially write the code well, so as not to rewrite it later, and preserve its quality. If you need to refactor.
The example of Tayota is indicative: she bought the unprofitable production of a single American company (sorry, I forgot the name) along with the workers and equipment, and brought this production into a plus. The key to success was Lean Production.
Its principles are:
Why put off the decision and how to deliver the product at the same time? It's simple: the decision should be thoughtful and consistent, it will help avoid problems in production and speed up the time of product release.
Perhaps the key is getting rid of all the excess.
Any extra process or procedure adds value to the product. Each area has its own list of superfluous. For software development it is:
It is part of the Agile & Lean software project development. As I wrote, it is part of tactical planning.
SCRUM cycle consists of:
1. Actually software development. The process in 1-4 weeks with daily rallies.
2. The end of the sprint. Again, the rally at which the developers show everyone what they have done.
3. Retrospective meeting - analysis of mistakes and problems, successes and improvements.
PS: this week ended all training meetings. From Monday to the battle. In general, we are ready. Fight will show :)
On the second day, we had a seminar on the SCRUM and Agile project. It told the practical application of the Agile project in software development.
')
Pig and rooster
Apparently, the lecturer's favorite story, because the slide met with her in presentation 7 times :)
And so, met the pig and rooster. Rooster offered to open his restaurant and call it "Pork and Eggs." To which the pig refused: "You will only participate, and I will give myself entirely."
In terms of SCRUM pigs are developers, the rooster is a project manager. The essence of the story: the pig is more important than the rooster. The essence of SCRUM: developers are more important than a manager, you can not ignore the opinions of the first.
How it all started
The leaders of large software companies decided to develop a common style of work, which was later called Agile.
The main document, one might say, the code of commandments, is the manifesto "Manifesto for Agile Software Development".
It reads:
People and relationships above processes and tools
A working product is better than detailed documentation.
Customer relationship is more important than signed contracts.
Readiness for change is more important than following plans.
In English
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
At the forefront is a person, because it is he who produces the product. If the process causes irritation, it should be changed. If the tool is inconvenient, it should be discarded.
The customer pays for the working draft, and not for its description.
It is also important to be ready for changes in the project. The team must be flexible in terms of opportunities.
Agile Development Principles
The main principles are:
- Deliveries of new product versions should be regular and made as early as possible.
- If the customer wants to change something in the product, you need to do it at any stage of development (if this is of course possible)
- It is important to release a working product as often as possible. Desirable period from 2 weeks to 2 months
- Developers and businessmen (those who are responsible for working with the customer) should work together.
- Good working conditions. Developer should be comfortable working
- More personal meetings
I will explain a little. Agile is customizable. But this does not mean that any whim should be performed without primitive. It is necessary to ensure a dialogue between business people, customer and programmer.
The product should be released quite often - it's like a blog - the more often you write useful posts, the more people read you and are not removed from friends. The customer does not need a product that is updated every half year and increases the functionality for a couple of features. There is still need to remember about competition.
Well, a satisfied and motivated programmer will write the code better than if he were sitting in a damp basement and was undernourished.
There are two more points. They are technical.
1. Each new version of the product should do more than the previous one.
2. You need to initially write the code well, so as not to rewrite it later, and preserve its quality. If you need to refactor.
Success Tayot's or Lean thinking
The example of Tayota is indicative: she bought the unprofitable production of a single American company (sorry, I forgot the name) along with the workers and equipment, and brought this production into a plus. The key to success was Lean Production.
Its principles are:
- Get rid of all the excess
- Monitor quality
- Respect people
- Increase experience
- Postpone the decision to the last moment
- Deliver product quickly
- Optimize the process
Why put off the decision and how to deliver the product at the same time? It's simple: the decision should be thoughtful and consistent, it will help avoid problems in production and speed up the time of product release.
Perhaps the key is getting rid of all the excess.
Any extra process or procedure adds value to the product. Each area has its own list of superfluous. For software development it is:
- Unfinished work. Remember that nobody needs an unfinished feature. You need to try to bring everything to the end
- Extra processes. These are the ones that are made "for show".
- Additional features. If the customer asks only the opportunity to open the text, do not make it possible to edit it.
- Switch between tasks. The programmer should not rush between two projects.
- Transfer product. Because it takes extra resources.
- Expectation. If the project needs something, he should not wait and sit idle.
- Defects. It's bad everywhere :)
A little bit about SCRUM
It is part of the Agile & Lean software project development. As I wrote, it is part of tactical planning.
SCRUM cycle consists of:
1. Actually software development. The process in 1-4 weeks with daily rallies.
2. The end of the sprint. Again, the rally at which the developers show everyone what they have done.
3. Retrospective meeting - analysis of mistakes and problems, successes and improvements.
PS: this week ended all training meetings. From Monday to the battle. In general, we are ready. Fight will show :)
Source: https://habr.com/ru/post/50678/
All Articles