Agile development with the ancient troops in war

Speaking of project management, you have to Ti Min Jie development, the stuff is newly created term, many people felt quite profound, very mysterious, very modern. But these ancient stuff would not it?

Such as agile development advocate morning meeting, is not ancient battle liter or Zaozhao.

For example, advocates of agile development project billboards, is not ancient sandbox.

Agile development roles such as PO, is not the ancient Great General, PO responsible for the project, too, major general responsible for the outcome of a war.

Agile development team was asked in PO advocate against external interference, too, will be out, military orders.

Let me say in the promotion of agile development requirements document, which in ancient times was not the emperor of the generals assigned combat missions, and agile development in the promotion of the prototype, is the general's battle plan.

As for how to set up the team, who did Product Owner, which is directly sealed to worship and India, and also quite grand, which in ancient times as it is now: "! This project is yours," engage in a little sense of accomplishment did not.

The user story in ancient times is operational objectives. User story is split into the task, the same operational objectives, concrete can be split again.

The final step is to emphasize the role of people, be sure to choose the right people do the right thing.

Like Nokia, Microsoft hired a Trojan horse, and then more and more feeble, and happy kingdom because of my participation, then more and more handsome. This is the same between the two.

 

Agile development knowledge point

Three questions everyone in the morning will be content to answer: A: What you did yesterday? Two: What are you going to do today? Three: What difficulties or rely on it?

User Story Examples: a: as XX, I want XX, XX for two: So, my operation is as follows, first XX, then XX, XX final success.

Six characteristics of the user story: independence, consultative, valuable, can be estimated resistance, short, testability.

Sprint's length: every Sprint should be 2-4 weeks, the shorter the better, first built the team recommended four weeks as the length of Sprint, Sprint length can be adjusted, but the rhythm of the team is important.

 

 Finally, send welfare, we understand.

Reproduced in: https: //www.cnblogs.com/ushou/archive/2013/03/25/2976678.html

Guess you like

Origin blog.csdn.net/weixin_34402090/article/details/93162374