What are the considerations of requirements analysis?

  • To understand the background
  • Question the reasonableness of your requirements
  • Is the demand closed loop? The likes have to be sorted
  • How difficult it is to develop. Small compromise, save time, h5 complex animation, whether can only let app do
  • Whether you need other support, buried in Hangzhou, the public number to come out first
  • Do not rush to schedule, do not give the meeting, unreliable, if there is other things

How to make technical scheme design?

  • Simple, not excessive design, consider the business to consider the development of efficiency of manpower
  • Output documents, delay is not to write half an hour to draw more time, show that the project is complex, do not develop with problems, one or two months later can not remember
  • Identify design focus, component design separation, data structure design, and other students docking
  • Team review, looking for good technology, experienced data security risks, but also learning opportunities, the company’s online tools
  • Communicate with the design back end
  • Issue the conference conclusion, one piece of evidence, done

How to ensure code quality?

  • Schedule the reserved buffer. If it can be completed in 3 days, then 3.5 to 4 days. Keep the parallel work
  • Conform to development documentation, code comments, style
  • Write a development document that someone else might use
  • Timely unit testing, for discussion
  • Mock API
  • Code review, qualification is better, risk is not standard, can not say their own Code is good

How to do the joint investigation?

  • The technology of alignment
  • Design determines the visual effect
  • Let the PM determine product functionality

What about PM plus requirements?

  • To see the real effect, there is a need to increase the demand, not hard
  • Can’t refuse, go through the requirements change process, not just say change
  • If the company has rules, follow them
  • Otherwise, the project team and TL review, re-evaluate the schedule, delay is not their own problem, can not be pushed, or the requirement can not be done
  • Even minor changes should be notified

Don’t say to the test student, my computer is ok!

  • Send email and copy to the project team
  • Test questions should be well documented, Jira
  • If there is a problem, timely communication, and test information asymmetry, and project understanding is different
  • There is no problem with my computer. It is found that there is a problem to discuss and ask QA to provide equipment to reproduce and upload the problem

Project online

  • Notify QA of regression testing
  • Synchronization gives PM and project team extreme mobility issues
  • If there is a problem, timely roll back, stop loss, do not online analysis

The importance of project communication

  • Teamwork, communication is the most important thing
  • A daily communication, something to say, no matter reported peace
  • Identify and report risks in a timely manner