Project Manager feelings 2: Requirements

Umlchina Pan Jiayu said: "project requirements must understand the vision of the customer's boss ". From the previous project experiences, it is concise.

(1) In some project demands, the customer's staff deliberately distort the meaning of the boss.

(2) In the project demand process, too many non-boss strong willingness to consider, resulting in a shift in the focus of the work. The customer's boss's vision cannot be achieved with enough resources and is given a discount.

 

Taking the previous project as an example, the project originally centered on data analysis was evolved into an office OA system when the data warehouse was built. As a result, developers have been working overtime for more than two months in the OA field they are not good at. As a result, the development is exhausted, and the customer staff are awkward. The customer leadership is not satisfied. If you can understand the meaning of the customer's boss earlier: relevant reports are required, and the Data Warehouse creation process can be pushed from top to bottom from the customer's organization. Even if the customer's employees use awkwardly and do not get used to it, the project is successful after the function is completed and the customer's boss is satisfied.

 

Software developers need to correctly understand the vision of the customer's boss, and draw a blueprint from the vision of the customer's boss as the starting point of all project activities. In the process of demand, the customer will come up with specific implementation of the vision, such as "I want a button" and "I want an image, these requirements can easily compete with the project goal to seize resources, or even directly conflict with the customer's vision. If the requirement personnel simply follow the specific requirements of the customer without considering the customer's vision and objectives, the project will fail in.

Recall an old thing. Once a customer leader proposed to integrate the C/S system interface into the same interface of the existing B/S system. His opinion is: "The current usage status leads to frequent switching in the C/S and B/S windows at work. If they are integrated, it will be very convenient ". It took us a lot of time to understand the customer's intention. Later I explained that it is feasible but not necessary. I wrote several lines of HTML text, and put two boxes on the page to show it to the customer, saying, "If this is the case, in your work, you need to move the mouse up or down, which is more difficult than switching at + TAB on the keyboard ". The customer later accepted the request. Fortunately, we were so bold at that time that we would have to be exhausted by activx.