Since it is a note, I only mark what I think is useful to me at this stage. Not a summary of all the contents of the book.
The first chapter, the product demand mining ....... Slightly, basically similar
Chapter II, product definition The first step, write the press release:
- Name
- Estimated time of release
- Target Customer
- What problems have been solved;
- How to solve (core function point).
The second step is to create and constantly update the FAQ document:
- svn★★★★★
- dropbox★★★★
- windows Live sync★★★★★
- These are some of the tools recommended online? Many people recommend using wikis, but I don't know what a wiki is, not Wikipedia? How is it a synchronous document?
with the continuous refinement of the product plan, there will be more problems, pointing out the lack of products, FAQ documents can be divided into internal FAQs and external FAQ (Customer view), this documentyou can save time by maximizing the amount of time it takes to answer repetitive questions. Step three, Flowchart/prototype (wireframes)I personally think that we need to draw the flowchart first and then draw the prototype (wireframe), because the drawing prototype will sometimes fall into the details, interaction and other design. Please abandon this habit. And if there is a process diagram, the prototype is caught in detail and can be quickly back on track. Basic principles of Flowchart:
- Create prototypes of the relevant parts of the user interface only.
- Always use the finished, properly edited text: for example, a large paragraph of text = "There is a phrase here", but for any form, button, dialog box, or other meaningful control you must use accurate, high-quality copywriting.
- Control the time spent on visual design.
- Use grayscale instead of other colors: color increases the difficulty of development and takes away attention.
- Beware of visual tricks: unconsciously striving for recognition, such as corner gardening or transparency, can make things more aesthetically pleasing.
Fourth step: Make a Product single page/10min ppt
- Name
- Estimated time of release
- Target customer+ number of customers
- what issues are resolved + the value of this issue to the target customer
- How to solve (core function point) + Competitive Product analysis
- Time node (major milestone)
Fifth step: Write the function Specification document
- Introduction: Why to do this product and what to do; the necessary terminology key Words Unified analysis
- Target and non-target: refine target, prioritize
- Use cases and User scenarios: Use cases refer to a brief statement describing what the user must do, and the user scenario describes how the user experienced the product by describing the incident.
Example:use case: Users can share a screenOr: When the user view shares the screen, if other users are sharing, the user is prompted by the system to confirm that they are replacing the other screens that are currently being shared. The better use case description model is: User type + user behavior example: as one of the video chat participants, I want to be able to "share my screen to other video chat participants". Re-describe it in a user scenario: Jody wants to share her screen. She clicks on the "Share Screen" button. System pop-up prompts him to select the window he wants to share or to share the entire desktop, eachWindows have window previews and label descriptions, and the preview is real-time, like a small video. When Jody clicked on one of the options, his screen was successfully displayed in the videoIn group chat The But if someone is showing the screen in a group chat, the system pops up with a hint: "Rick is sharing his screen, do you want to replace it with your screen?" "If Jody DotHit "Yes", Rico. Grams's video interface will be cut back to his camera, Jody's screen will be displayed in group chat, if Jody clicks "No", she goes back to the original state.Priority should have a common standard sort, for example: P0: There is no way to demonstrate P1: No such feature can not be published P2: Icing on the cake, the next version of the candidate P3: hehe
- Prototypes and Flowcharts
- Non-functional requirements: API, various interface specifications,
- Load Planning
Have a strategy to deal with sudden spikes in Access Chapter III I have been incorporated into the above ... Slightly
Notes-the first to third chapter on how Google and Amazon do products
