Look at the information on the post, consult the material, the following is a definition of agile development. ............... The core role ......... ..........
Product Design: Responsible for product design, translating product requirements into demo and design documentation, delivery development and testing. At the same time, the acceptance of product features.
Development: Turn the design into a real product and deliver it to the test.
Testing: Testing the product, passing the delivery of the test to the product designer. Does not pass the kick back to the development.
Leader: Responsible for the release of the task, another important responsibility is that when the team members appear disagreement, responsible for the decision!
........................................................................
The core of agile development is unity, agile development pursues efficiency, divides a large product function into small, then a piece of iterative development. In this process, we use a mutually understandable way to express product requirements, there may be some special details will not be reflected in the design document (if to achieve very small degree is very time-consuming), in the development and testing process, mutual communication discussion is very much, At this time if the product description is missing or wrong, we will be oral coordination of the treatment method, and then by the product Manager a little to fill in, if the team is not united enough to each other, "you write a document has a problem!" "You understand the ability to be too poor!" "And so on, it will be very difficult to implement. The same is true between development and testing. ............... The core role ......... ..........
Product Design: Responsible for product design, translating product requirements into demo and design documentation, delivery development and testing. At the same time, the acceptance of product features.
Development: Turn the design into a real product and deliver it to the test.
Testing: Testing the product, passing the delivery of the test to the product designer. Does not pass the kick back to the development.
Leader: Responsible for the release of the task, another important responsibility is that when the team members appear disagreement, responsible for the decision!
........................................................................
As we said earlier, the core of agile development is unity, agile development pursues efficiency, divides a large product function into small, then a piece of iterative development. In this process, we use a mutually understandable way to express product requirements, there may be some special details will not be reflected in the design document (if to achieve very small degree is very time-consuming), in the development and testing process, mutual communication discussion is very much, At this time if the product description is missing or wrong, we will be oral coordination of the treatment method, and then by the product Manager a little to fill in, if the team is not united enough to each other, "you write a document has a problem!" "You understand the ability to be too poor!" "And so on, it will be very difficult to implement. The same is true between development and testing.
what is included in agile development
The overall process for agile development is as follows:
1. Demand Planning and Staging
2. Requirements Review
3. Demand explanation
4. Programme review
5. Daily morning Meeting
6. Performance Testing
7. Codereview
8. Demo
9. Test phase
10. Online Bug Modification Process
Tell me what should not be included in the agile development process, if you do not like, and your ideas conflict, you can change the agile development of these four words into any four characters. In short, if you want to solve these problems, this is the best practice I have seen, each node is not an armchair, but after countless attempts and failures summed up.
If you are an IT company manager, if you do not know how to manage their own team, I strongly Ann you according to my said standardized way to do, rest assured that there is a problem I promise not to take a little responsibility.
To be exact, the agile development process I'm talking about is not just about the development team, it hides more ideas behind it.
1. Product and development must be a team, we are only a different division, the role of different, not two opposing teams.
If your company is dividing the product and development into two departments, then congratulations, there must be an infinite amount of disputes between product and development.
In all the teams I've taken, the idea is: there's a problem, don't tell me it's a product design, that's not what the development team can achieve. All I know is that this is the responsibility of all of your development teams, and the consequence is that all people have to bear it. If we carefully distinguish what this is, then just to avoid the next occurrence of the same situation, users will only know that a company has a garbage product, no one cares whether the product or the development of the pot.
This is the premise of agile development. or more than just product and development, the responsibility is shared, and the one team concept is consistent throughout. This is not to say, same big pot, but that, in the face of bad results, all team people must share the burden. The reason for the problem is simply to trace and reproduce the scene at the time to avoid the same situation in the future.
Product and development must be a team also reflected in the requirements of the staging. This will improve when it comes to the process of demand staging. In fact, if the demand stage is not done well, agile development can only be a formality.
Demand staging how to do this is the MVP thing, another topic. To put it simply, every issue has to be predicted in advance, and all of the functions in this period are only to check if their predictions are correct. And according to the results to constantly adjust the development plan.
2. The responsibility is clear, everyone must be responsible for the clear and correct, who should do what things, must be clear in advance.
The recommended role for the development team should be this way.
PM One
UI One
Css/js one or two
Java Four
Android one or two
IOS one or two
QA One
This is a relatively balanced template, such that a 8~10 person's little team can be duplicated. Agile Development supports multiple team parallel development. Theoretically speaking. This way, you can support five to six small team launches simultaneously.
When it comes to the last multi-team collaboration, I'll mention it.
In addition to the role of these project teams, there are also leader of team members. I compare the recommended groups into the following categories:
1. Product Team
2. User Experience team traditional UI teams are upgraded to UE and upgraded to the entire system and even to the company's user experience division.
3. Backend Team Bitter back end
4. Front-end Team Android/ios/js table asked why I put these three together, I just think a front-end engineer should take all the three. You can learn a little more in one client, but it should be no problem to get started on a regular project.
5.QATeam QA requires only functional testing, regression testing, boundary testing, and no performance testing required.
3. Everyone must learn to take the initiative to be responsible for their own affairs
When you have a second, you will soon find out who is in the team who is able to do their job and be more active. 3rd is difficult to do, especially in many companies, do not pay attention to the development of team cohesion, and will not pay attention to the exchange between them, do not know what they want.
So that's what I've been stressing again and again, agile development is not just a development process, it's a way of managing it, he's involved in performance appraisals, corporate benefits, commuting systems, etc. you can't see.
If your team members are not responsible for their own business, then you need to either change the team or try to motivate the team.
A survey of Agile development methods
