Business analysis: what have we done? What else can we do? (Finishing)

After four years of business analysis and four years of fatigue, business analysis is always poor, R & D is exhausted, and customers are in a hurry. What did we do.
Let's look at the tips
1. Customers cannot freely access the ocean of data
Customer: I need such a report.
Vendor: We have generated the file. Please find it in the YYY directory under the xxx directory
 
Problem: The report layout is unreasonable. It may be due to a level disorder, a level that is too deep, or a inconsistency between the business understanding and the actual report.
Solution: first, it is clear that reports must be organized. unorganized reports are a nightmare for both parties.
Whether the report is organized by business logic or data type is a matter of opinion and wisdom. Generally, the departments involved in the telecommunications business analysis system (end users of the system) may come from different departments, and their data concerns are different. In this case, we recommend that you use business division. Users will always be lazy and users will always be right. Therefore, the job of locating a report can only be done by the system.
For reports organized by data, for example, the user analysis directory contains all the users, user development, and user analysis. This analysis has a certain effect and needs to be verified.
You may also need to provide some auxiliary methods for report organization, such as report description, REPORT query, and report Association wizard.
I did not agree with some people's idea of "putting all datasets together and organizing reports by users themselves". I have made business analysis over these years, we haven't seen any business department people collecting data into a report by themselves, but we have seen more and more people coming up with a ready-made table sample. This question will be discussed later.

2. Ice Age of Data Trust
Customer: This indicatorAlgorithmWhat is it? How can I check with other systems?
Vendor: we need to check that our algorithms are all algorithms defined by the headquarters.
 
Problem: too many system indicators overlap, making verification difficult. The system fails to establish a complete indicator library, and there is no online indicator description.
Solution: Create an indicator library and describe reports and KPIs online. Improve metadata and check various metrics from metadata. It is best to establish a verification alarm mechanism.

3. chicken ribs, tasteless food, abandon a pity
Customer (LEAD): can this system give me a clear way to present data, and I can see it at a glance?
Manufacturer: you are talking about ....
Customer: You can see that this system is good!
Vendor: But there are only a few indicators in that system. We have hundreds of indicators in our system. It is impossible to design a display style for each indicator @@

Problem: the leader's entry point is different from the observation point. The leader's requirements on the Data scope are basically determined, but how to display them is not realized.
Solution: Abstract The leadership view and customize templates for leaders.

4. Leap of a thousand miles
Customer: You can't use this system. Many of my requirements have not been met.
Vendor: What are the requirements?
Customer: for example ........
Vendor: we have already implemented these products long ago.

Problem: poor communication. The current business analysis mainly meets the requirements of the carrier's National Headquarters and provincial subsidiaries, and basically does not meet the needs of cities and counties. The evaluation of the management and operation layers of local cities affects the promotion of the system to a certain extent. If the customer uses third-party similar products to meet their own needs, have you seen the evening?
Lack of promotion efforts. More often we have implemented features but users do not know.
Solution: Proactive promotion and communication. Gain an in-depth understanding of data requirements at the operation layer and level 2 management layer.

5. Technology, a sweet lie
Manufacturer: Our system adopts the world's leading XXX product and can implement the ##### function. The test result is #####
Customer :...
Vendor: front-end presentation, which can be used from provincial drilling to county or even business sites, or even a single end user. You can also migrate data from the end user to the province.
Customer :...

Problem: the customer is full of head terms, but vague about the system functions, so it is often the vendor to write documents for the customer, let the customer report.
The customer's focus is on meeting the daily work needs, and then improving the work ability and quality.
I seldom see customers who drill and roll with the mouse so seriously. I think there were very few in the past and there were very few in the future.
Solution: technology is an auxiliary means after all and cannot be a highlight of the system. The real highlight is how to better meet the customer's needs (although there is no high technical level ). In this way, the customer's requirements are clearly defined from the previous question. Do you know what data the marketing department needs every day? Do you know which departments are concerned about the launch of a package? If you do not know, the road is still long.

6. Acceptance, project pain forever
Vendor: Can the system be accepted after such a long period of operation?
Customer: I still have some requirements...
Vendor: TMD.
 
Problem: requirement definition and requirement management are not standardized
Solution: What else can I do? The requirement management should be regarded as a dead-end provision! The rule is dead, and the person is living? How can we build a square without rules? -- Hand-painted, reliable, and talented.
// Todo: What's the problem ???

 

What should we do? How can we make breakthroughs?
// Todo: 1. requirement definition

// Todo: 2. Communication Mechanism

// Todo: 3. Promotion Mechanism

// Todo: 4. Technical Implementation

// Todo: 5. Customer Training

Summary
Life is painful, and business analysis is elder care. If there is no mutual understanding or improvement between customers and manufacturers during the painful elder care process, then there will be no fun-this is what makes it clear.