This step is to tell the business
Support them by hard-coding the development side code and iterate in subsequent versions. , configure it as a page. Step: Output the product planning document and reach an agreement with the business party The next step is to output our product plan into a document and explain it to the business side in a meeting. While we are synchronizing the conclusions, we must also explain the logic behind the thinking.This step is to tell the business side so that they can judge whether there are aspects Indonesia Phone Number that are inconsistent with the business reality based on our logical deduction, and let the business side act as our "strategist" Further error correction. In addition, the time planning of each version also needs to be clearly explained to the business side. After a consensus is reached at the meeting, written evidence is formed to provide a basis for discussion in the event of subsequent backlash.
https://lh7-us.googleusercontent.com/3ytQw3KMpwd47qL-y2lumzoBhxp0begNYpNgc-2QUAyBT9uYsAs1sLgZ1otgkQ22ojqNv4r6_nOeJyH9QgA338wGnbpBLkWdRYb23Ly06egCWPS0J3poPgMkR9_IR9QC2hGbGZAUxdVfK7sH
Step: Based on the version staging results, deliver products sequentially Finally, the product is delivered according to the version staging results. So far, we have split the construction of a system into various more detailed requirements. The product manager can iterate the product according to the complete process from acceptance to delivery of daily needs. Here No longer. It should be noted that during daily iterations, we will inevitably find unreasonable aspects of the original system architecture.
頁:
[1]