Demand and business model innovation - demand 10- observation and document review

Book10- Observation and document review

The model gives priority to objective information , Then place the part required by the customer .

1. Course extension

1. Internet enterprise antitrust
   1. Google and Facebook face antitrust investigations by the federal and state governments
   2. The State Administration of market supervision is formulating 《 Antitrust guidelines in the field of platform economy 》, Public consultation has been completed
   3. Ali ( INtime )、 Reading passage ( Xinli )、 Fengchao ( China Post Zhidi ) Be punished separately 50 Thousands of yuan ( Less ？ It's like nothing ？)
      1. The maximum fine is 50 Thousands of yuan
2. Hui Wen Wang " retired " And the COVID-19 continues to worsen
3. “ Workers ”-> “ The cook ”
   1. Z The deconstruction of generations of young people 、 Independence and optimism
   2. Look at the domestic demand for capital dialectically " Give preferential treatment "

2. Course review

1. The first half of demand acquisition
   1. Determine the prospect and scope of the project ： Problem analysis - Goal analysis - Business process analysis
   2. Stakeholder analysis ： Stakeholder identification - Stakeholder description - Stakeholder assessment - Stakeholder representatives choose - Participation Strategy
2. The second half of demand acquisition
   1. Based on use cases / Scenario expansion user requirements acquisition
   2. User access means
      1. Interview - Prototype - Observe
      2. Prototype ： Abandonment and evolution , Control the cost , Deal with ambiguity and change
      3. Observe ： Sampling observation and ethnography , Dealing with complex synergies

3. Observe

3.1. summary

1. It is applied when the user cannot complete the active information notification
   1. Sampling observation (Sampling Observation)： Traditional and simple , Observe a specific period of time or a specific event .
   2. Ethnography (Ethnography)： Long term and immersion , The observer goes deep into the user for a long time
   3. Discourse Analysis (Discourse Analysis)： Observe the user's conversation behavior , Observe and analyze interaction patterns or specific discourse analysis
   4. Protocol analysis (Protocol Analysis)： Observation of user tasks , Perform tasks while observing objects
   5. Task analysis (Task Analysis)： Observation of human-computer interaction behavior , Introduce relevant model methods to observe 、 Record and execute the user's interaction with the software system .

3.2. Application of observation methods

Situational ： Some events can only be related to the specific circumstances in which they occur , To be understood

3.2.1. The situational nature of the event (situatedness)

1. Emergence (Emergent)： The event was caused by the collective , Emerge in the interaction , Don't limit yourself to your personal perspective
2. Local (Local)： Specific context , An accurate understanding may not be formed out of context
3. temporary (Contingent)： A moment in the evolution , Events and their interpretation depend on the current situation
4. embodied (Embodied)： We need to understand that the cognition and ability of participants are limited
5. to open up (Open)： Business is uncertain and open , Perfect later
6. Fuzzy (Vague)： The explanation of the event will not be particularly detailed , Based on potential knowledge , Not yet clearly expressed , Requirements engineers are hard to understand .

3.2.2. Problems solved by observation methods

1. Observation focuses the findings on the context of the problem , Called social factors , Including the culture of the organization 、 The structure of the organization 、 User's working environment 、 User's work practice 、 Legal and policy constraints, etc .

1. Understanding complex collaborative Events ( Emergence , More and more complex collaborative problems )： Ethnography
2. Get exception handling at work ( Local , Abnormal flow is easy to be ignored )： Ethnography 、 Sampling observation
3. Acquire practical knowledge that is inconsistent with user cognition ( temporary , There is a gap between cognition and practice , Validation explanation , Make corrections if necessary )： Ethnography 、 Sampling observation
4. Understand the user's perception ( embodied , Be familiar with the habits of the group , Understand the tacit understanding of users )： Ethnography 、 Discourse Analysis ( Talk to understand the user's knowledge base at work )
5. Get the default (tacit) knowledge ( Fuzzy , Part of the work is familiar and natural , The user will not describe )： Ethnography ( Discover default knowledge , High cost )、 Sampling observation ( Get default knowledge , Select a sample to observe , Record constraint information )、 Protocol analysis ( Speak out your thoughts , Make the default knowledge explicit )

3.3. Sampling observation

1. Sampling observation is the simplest method of observation
2. classification
   1. Time sampling ： Observe users at different time intervals , such as 7 individual 8 Randomly assigned during the hour working day 5 individual 10 Observe at minute intervals .
   2. Event sampling ： Select the whole event for observation , Such as " Board of directors " and " User training meeting ", Instead of randomly sampling time periods .

3.4. Ethnography

3.4.1. summary

1. Ethnography was first proposed by anthropologists , To understand the social mechanism of primitive society .
2. Ethnography requires anthropologists to spend a long time living in the society under study and carefully observe the actual activities in the society , Get first-hand observations .
3. A typical example is a complex collaboration problem , These problems often have a certain sociality 、 Sudden situational .
4. advantage
   1. Be able to understand information in depth , You can experience the difficulties personally 、 frustration 、 habit 、 Correlation and risk .
   2. Can make the social factors of the real world visible , Provide an opportunity to show that users are not aware of 、 Some required activities that cannot be described or are unwilling to be described , Especially the social factors in work .
   3. Break some wrong assumptions and misconceptions that people have
5. shortcoming
   1. It takes a lot of time ： Developers using ethnography will generally combine the current practical experience .
   2. It's hard to get the results across to the development process ： The amount of data obtained from ethnography is relatively large , It is necessary to analyze and deal with the abstract description of the problem domain and the real world description of the problem generating part .

3.4.2. The implementation of

1. The successful implementation of ethnography requires researchers to have no pre-existing ideas about the society being studied , There is no list of problems waiting to be solved , Nor will they apply their value judgments to the observed activities .
2. Ethnography in the software will observe the key points and ignore the non key information .

3.4.2.1. Ethnography for complex collaborative problems

1. Focus on three aspects ：
   1. Distributed collaboration of work (Distributed Coordination)
      1. It refers to the method by which people cooperate with tasks in daily work
      2. A personal task is a single step in a complex series of tasks or other steps for others to complete a series of tasks , These steps together constitute a larger task .
      3. Think of the user's activities as part of an organized overall activity .
      4. Pay special attention to those who use notes 、 file 、 The collaboration of objects such as standard forms and the paperwork of creating these objects
      5. Observe the problem
         1. How can the division of work be reflected through individual work and work coordination ？
         2. How to define and distinguish people's responsibilities ？
         3. People's work for others 、 How about the evaluation of tasks and roles ？
         4. What is the work of personal altruism ？
   2. Work plans and procedures (Plans and Procedures)
      1. Data generated in a workplace 、 It is used to record the detailed steps and processes of various tasks , These tasks are integrated to meet the requirements of the whole work .
      2. Focus on how they are used in organizational activities
      3. Find deviations between actual work and documented procedures , because
         1. The document is not updated in time
         2. Different paths to work in the actual work environment
         3. Temporary situational events
      4. The way ： Project plan 、 Project schedule 、 Procedure manual 、 Job description 、 Formal organization icons and workflow diagrams are common examples of plans and procedures .
      5. Observe the problem ：
         1. How plans and procedures work in the workplace ?
         2. Do plans and procedures always work ?
         3. When will plans and procedures fail to apply , How to fail ?
         4. If the application of plans and procedures fails , What are the consequences ?
         5. Under what circumstances can plans and procedures be bypassed , How about bypassing ?
   3. The sense of work (Awareness of Work)
      1. Refers to a certain way of organizing activities , In this way , Activities can be visible or understandable to others who collaborate .
      2. Focus ：
         1. How the workspace is arranged ? How does it affect the work ?
         2. How the personal space in the workplace is arranged ?
         3. What items are at hand to do your daily work better ?
         4. What documents do people at work usually refer to ?
         5. Where are the objects generated by the work located ? By whom ? How often is it used ?
         6. How individuals monitor the work of others ?
         7. How individuals make their work visible to others ?

3.4.2.2. Use the rules of ordinary ethnography

1. Findings should be recorded regularly , Including observations 、 impression 、 Feeling 、 Premonitions and questions , Save your thoughts .
2. Record as soon as possible the interviews that may occur during the observation , And sort it out in time .
3. Review and update your ideas regularly
4. Identify strategies for managing massive amounts of data , Summarize the information 、 Indexing and classification .

4. Application of document review method

1. Document review is a traditional requirement acquisition method , It is dedicated to requirements acquisition activities for documents .
2. The category includes related products ( Original products and competitive products ) Requirements specifications for 、 Hard data and customer requirements documentation ( Specification of commissioned development 、 Tender )

4.1. Requirements reuse

1. When developing new products , You can often find the requirements specifications of related products , We can find similar or even identical problems to be solved , Analyze these parts as requirements acquisition sources
2. Common reusable commonalities between products
   1. Problem domain information ： No transfer due to system introduction , The problems solved are similar or the same
   2. User interface features ：
      1. Specific user groups have specific human-computer interaction requirements , That is, specific user groups have specific user interface characteristics .
      2. The new product has the same user group as the original product 、 New products and competitive products also have great similarities in user groups .
   3. Business needs 、 Organizational strategies, policies and regulations, etc
      1. Business needs are similar
      2. Organizational strategies and policies and regulations are similar to some extent .
3. The main points of ： Once the requirements have been successfully established , And the product itself is successful , Then the requirements do not need to be redeveloped .

4.2. Document analysis

1. Document analysis to examine collected hard data to determine potential requirements , It is to reverse engineer the documents generated or used in the work , Tap new needs .
2. Analyze quantitative hard data , Get problem domain information 、 Organize business workflow 、 Problems in business information .
3. Document analysis can ask questions ( Commonly used in data modeling activities )
   1. What is the purpose of this thing ?
   2. How do you use it? ? Why use ?
   3. The system uses it to do something ?
   4. Which business events use or reference this material ?
   5. Does this thing have a value ? for example , Does it have a number or code or quantity ?
   6. If so , It belongs to a collection of things ?
   7. What is the purpose of this thing ?
   8. Whether the document contains a set of repeated things ?
   9. If so , What is the collection of these things ?
   10. Can you find the connection between things ?
   11. What processes establish the connection between them ?
   12. What are the rules attached to everything ? In other words , Which part of the business strategy involves this thing ?
   13. What process ensures that these rules are followed ?
   14. What documents give users the most questions ?
4. It is important to note that the documentation is not necessarily correct .

4.3. Demand stripping

1. There are user requirements documents , Such as the specification of entrusted development 、 Bidding documents, etc , You can use the requirements stripping technology , Extract a single requirement from the requirements document and enter it into the new requirements document .
2. It can be done by hand , But if there is an electronic format , Usually use a stripping tool , And complete requirements traceability and management tools .
3. After all requirements are stripped , Persuade the customer to give up the original " description ", It's good for developers .

5. Summary of this chapter

1. Among the many methods of requirements acquisition , The role of observation is becoming more and more important , It can help solve situational problems
2. The application method of sampling observation is relatively fixed , But the application of ethnography is very complicated , It needs a lot of practice
3. Document review method is a requirement acquisition method specially used to deal with various hard data

6. Thinking questions

1. It is always difficult to observe users' work . It usually makes you and the user uncomfortable . To ensure that your access does not change the user's behavior , What should you do ？ To make the observation look more natural , What should you do ？
2. " I know you have a lot of material . What is in those materials ？"Betty Kant asked , She is MIS The head of the task force .MIS The task force is your system team liaison Sawder The bridge of furniture company . You dragged a lot of stuff , Just about to leave the building
3. " Oh , Past 6 Some financial accounts for the last month 、 Production report , also Sharon Give me some performance reports , The performance report covers the past 6 Monthly goals and performance ." When you answer , Some paper fell to the ground ,“ Why do you ask this question ？”
4. Betty Pick up the paper for you and put it on the nearest table , He replied ：“ Because you don't need this garbage at all . You're here to do something , Just talk to us users . No useful information can be obtained from these materials .”
   1. Only tell Betty What you find in every document will convince her that every document is important . Explain in a paragraph what help the document provides to the requirements engineer ？
   2. Between you and Betty When talking , Realize that other quantitative documentation is actually required . List what you are missing .