Summary of issues

The sixth chapter Agile process

Question: What are the similarities and differences between agile processes and traditional waterfall patterns?

Features of the waterfall model

(Traditional way of development)

1. Emphasis on documentation

The output from the previous phase is the input to the next stage, and the document is the only information that is linked to the stage. So many developers seem to be developing documents rather than developing software, because the software's "look" can be seen later in the development.

2, no iteration and feedback. The waterfall model does not involve feedback, so it is very difficult to adapt to changing customer needs. The waterfall means there's no turning back.

3, managers like the waterfall model because the document is understood as the speed of development, can easily define the different stages of the milestone.

Features of Agile Development

The idea of extreme programming embodies the rapid change that adapts to customer's needs, inspires the enthusiasm of the developer, and is also an important supporter of the agile development thinking at present.

Agile Software Development is a new management model for developing software, which is used to replace the waterfall development pattern developed by file-driven.

Agile development integrates the common features of the new development model, which highlights:

1. Agility is "fast". Fast to adapt to the current rapid pace of society, it is necessary to play a personal personality thinking more than a number of personality thinking increase.

2. Customer participation. People-oriented, customers are software users, business understanding of the experts, without the participation of customers, developers can hardly understand the real needs of customers.

3. The product that emphasizes software development is software, not documentation. The document is for software development services, not the subject of development.

4. Designed for the quality of the final software, but does not indicate that the design is more important than the implementation.

5. Iteration. The function of the software is the customer's demand, the interface operation is the customer's "feeling". The emphasis on iterations is to shorten the cycle of software releases.

6. Minor version. The rapid function of the display, seemingly simple, but for the complex customer needs of the rational division and the overall unity, it is not easy to do a good job of both.

Chapter Seventh MSF

Question: How does the MSF process pattern be phased in, and completing a function can be said to complete a phase?

The MSF process model consists of four major milestones, each of which is a phase endpoint.

The envisioning and ideation phases reached the endpoint on the "foreground/scope approval" milestone. Once a new product (in an Information infrastructure implementation project, such a product may be a service) attracts everyone's interest and is approved for build approval, the project team begins to focus on defining the product.　　The foreground description document clearly clarifies the ultimate goal of the product or service and provides a clear direction. The design phase reached the end point on the project design approval milestone. The project design includes functional documentation, a plan mix for each role functional group (such as development, testing, user education, system implementation, program management, and product management defined in the MSF teaming model) and time schedule. The functional requirements provide sufficient detail to the project team to determine the resources required and make commitments. On the project design approval milestone, the customer and the project team agree on what to deliver and how to build it.　　This is a very important opportunity to reassess risks, establish priorities, and make final estimates of time progress and resource allocation. The development phase reached the endpoint on the scope complete/first use milestone. Approved functional requirements and related project plans provide a baseline for starting development. The development team has set up a series of internal deliverables milestones, each of which undergoes a complete test/diagnosis/troubleshooting process. At this milestone the customer and project team evaluate the functionality of the product, validate the product transition and support plan.　　Also at this milestone, the development of all new features has been completed, and the deferred development feature is documented as a reference for the next version of the feature. The stabilization phase reached the endpoint on the product release milestone. Test work is accompanied by code development work, in the stability phase because the focus on the search for errors and modify errors, so the test activity becomes the main work. At the product release milestone, the product is formally transferred to the operations and Support group. Typically, the project team either starts the next version of the product development, or splits into other project development groups. Eighth chapter Requirements AnalysisQuestion: When doing a survey, is it a survey to the public or a specific demographic survey? There are different approaches to different surveys: the usual survey methods are universal surveys (one-off surveys of each molecule in each of the respondents), a typical survey (a comprehensive, systematic, well-rounded investigation of the selection of a representative unit or units), a case study (an individual in society, a crowd, or an event , a survey done by a unit).
Commonly used survey methods are questionnaire (rational design of questionnaires, using open, closed or mixed questionnaires to collect information), the literature method (through written materials, statistical data and other literature on the Research object Indirect investigation), access law (through the conversation to obtain information), observation method (on-site observation, with the impression of the perception of data collection). Nineth Chapter Project managerQuestion: How does PM encourage team members to boost their confidence?

Set goals first, and then everyone must bear a point, even if a little better, after the success of the full recognition of each individual's strength, so that they fully understand their value in the team, simply say is to let them understand that they are useful, is conceived and met.

Typical users and scenarios
Question: What if the user's needs are not realized?
Another way to achieve, really can not be with the user to understand, to speak clearly. We are the new products on the road when the product personnel in the product, it must be clear before the hands of their own ideas, understand what we need to do is what kind of products, users exactly what is needed, this we must be clear, not clear to ask, to think, is so-called AX.

The 11th chapter Software design and realization

Problem: Software design needs to constantly communicate with customers, if the customer's daily requirements are different, how to manage design changes?

First of all, see if this requirement change is reasonable. If it's reasonable, then it's definitely going to change. Second, if the same place he repeatedly changes the demand, then it is necessary to think that the customer is not exactly what they want at all.  This is the time to slowly, and so customers want to be clear and then set.  Again, it is also a place where he repeatedly changes the demand, it may be that you come up with something that is not what he wants, at this time to try to guide customers to describe the requirements clearly, and then in understanding the customer wants to express the meaning of the case, the abstract results, and then confirm. Finally, if the customer's demand is unreasonable, should try to explain with the customer where unreasonable, reasonable circumstances should be how.　Let the customer understand why it is unreasonable. If the realization of his unreasonable demand, and so on after the customer understand, will also ask for change

12th Chapter User Experience

Question: Is the product basically complete at this stage of user experience? Just need to make a few changes, OK?

This phase is basically complete and there are some bug issues.

The 13th Chapter Software test

Question: Can software testing get all the bugs out, and the new bugs are the software updates that appear?

Software testing is necessary, otherwise it is not updated. In fact, updates are also updated

    We do not know how to bug, for example: 360 accounted for 100% of memory, next time to set the software is not so big

    Software is dead, people are alive, all software basically have bugs.

14th Chapter Quality Assurance
Question: What are the aspects of software quality assurance?
Software Quality Assurance (Sqa-software Quality assurance) is the establishment of a planned, systematic approach to ensuring that the standards, procedures, practices and methodologies developed by the management are correctly applied to all projects. The purpose of software quality assurance is to make the software process visible to managers. It verifies that software is compliant by reviewing and auditing software products and activities. The Software Quality Assurance team participates in the establishment of plans, standards, and processes at the beginning of the project. These will enable the software project to meet the requirements of the institutional approach.

Chapter 15th stability and release phase
Question: How do you maintain the lifecycle of the software after the release order, which is more of a bug at this stage than the test?
Constantly test and update software to develop more features.

16th. Innovation in IT Industry

Question: Many people have tried innovation, but not many people can succeed, so it industry innovation is not accepted, how?

Who doesn't like innovation? However, to think carefully, innovation is to do things that are not the same as before, not all people like "different." When you put forward an innovative idea, you may not get the approval of others.
In our familiar computer and it fields, all the "cool" things we see are generations, and several teams wave upon wave the results of continuous innovation. Like puzzles, a lot of smart people can see the final image, all in a piece of stitching together, often to spell the last piece of the students to get the greatest honor. But no previous accumulation, no own solid ability, no "last piece" waiting for the students to spell.

17th. People, Performance and professional ethics

Question: The team constantly has new replacements, then the team is to continue to experience the running-in period?

The so-called running-in period is the phase of mutual adaptation. For example, to new jobs, to adapt to new jobs, new leadership, new colleagues, new environment and so on. The same leaders, colleagues should be familiar with and understand you. This period is called the running-in period. The running-in period may produce some contradictions. When familiar with each other, understand, and adapt to each other, you can work well together. The running-in period has passed. Every time you change a job, what you lose is experience and familiarity, need to start all over again, there will certainly be a period of running-in. Every time you change your job, you get new opportunities, new learning, and a new stage. All that you get will make up for all that you've lost.

So, do not worry and impetuous. Give yourself enough time to be familiar with the environment, in addition to work, it is necessary to establish a good interpersonal network, more know some people, ask them to give you a "induction proposal", encounter problems best can have a few "think tank" to help you out ideas. Have a good relationship with your boss and make sure that his expectations are consistent with what you can do.

Just enter a company, if you make a mistake, everyone will forgive, if you ask silly questions, people will not blame you. Therefore, must grasp this time, the mistake all committed, the silly question all asked. I can see that you are a person who wants to do things and is also a person in charge. I'm sure you'll do well.

In the work of the running-in period there will be a lot of things to pay attention to, to learn to correct their own mind to calm their mood, through the various levels can smoothly into the social integration work, so that in the work to achieve their life ideals.

Summary of issues