In situations where changes are inserted at a high frequency

Resulting in repeated and large amounts of ineffective communication

Product, development, and testing waste a lot of time on requirements N times of lookup and N times of interrupt rewriting of the code

Reduce repeated and ineffective communication on product, development, and testing

1) Company resources are limited at any time 2) Use limited resources to meet the highest value needs

The reason for the product is that the business is not planned

Method: Review once a week

Way: Reviewed on Monday, delivered online next Tuesday; Reviewed on Tuesday, delivered online next Thursday; Cycle in turn

Method: One version every two weeks or three weeks

Urgent needs can also be raised at any time

Large demands can also be scheduled across versions

The project starts to be implemented according to the iteration priority plan

result

Products are the downstream of business, and business demands should be planned in a unified manner

Technology is the downstream of products, providing reasonable suggestions for product demand planning and uniformly improving research and testing efficiency.

Each function has its own responsibilities and needs to think of ways and strategies

Department leaders reached agreement

OKR collaboration

Keep doing the right thing

Will face product and business pressure

Requires leadership authorization and support