The boss wants to make a collection function, make it quick (Party A’s word demand) this need must be done the day after tomorrow (product reverse time) This experience is not good, quickly change (UI, interaction frequent adjustment is not time, work is a bug) time is not enough interface has not been written, you first adjust part of the background box, You are to blame for the delay in debugging. Front end: they’re all daddies, I’m just the one taking the blame, I’m too hard, whoo-hoo ~~~

Note: The following methodology is not applicableCut cornersIs only used when subjected to multiple PUACounter PUA, remember!!

How does the front end battle party?

Party A is the father

  • Dig deep into party A’s claims,Figure out real needs and hidden needsTo prevent frequent rework
    • Party A says I want a horse (demand), but actually I want a faster means of transportation (demand)
  • Sort out the primary needs and the secondary needs, see if you canStart with the main requirements, and then arrange the schedule of secondary demand
    • Party A needs 100, all important
  • Impossible to achievePatience,Explain the reasons and give an alternative plan to prevent party A from being whimsical again
    • Party A wants the phone case to change color according to the mood
  • The need to rise to the challenge,Escape your comfort zoneEasy access to technological breakthroughs
    • Party A wants to synchronize changes on the PC while operating on the mobile
  • Rio is incompetentReport toOr ask the big guy
    • Holding on leads to problems, and the consequences are serious
  • It will be answered, answered in time,The service is supreme
    • Party A is not a killjoy, he is the bread and butter
    • Party A does not understand technology, so he should speak reason in a language he understands

One word demand

  • Patient inquiry, dig into the real needs and primary and secondary needs and hidden needs
  • First out solution, ask for party A’s consent
  • Schedule and give detailed time estimates (prevent battle and compression)
  • Party A repeatedly modify, first try to persuade him to give up; If not, give detailed time evaluation table. If time is acceptable, do it. If not, cut demand
  • In a word:Take trouble to avoid trouble! Front trouble to solve trouble!

How does the front end battle products?

Product reverse time

  • givenDetailed time assessment sheetIt is impossible to prove the fact (it is better to confirm the working time with the leader first to prevent challenge)
  • Let the product go: 1.delay 2.Cut secondary requirements 3.Negotiating human resources

The product frequently modifies requirements

  • Assess whether the current demand is adjusted, the new demand is down a period orReassess time
  • Assess whether the improvement is reasonable, unreasonable rejection, reasonable also to reassess the change of hours
  • Increase the evaluation hours and notify the product for each change,Scheduling postponePlease see “Product Reverse time”.

What about scheduling conflicts

  • Coordinate PM of both sides to arrange battle schedule in person, or coordinate resources upward.
  • Put two PMS and the front endContradiction between transferA contradiction between two PMS!

How does the front end battle?

Why you can’t do what others can do

  • If it does improve the user experience, make it as satisfying as possible!
  • If there is no significant improvement and it takes time, tell them that there is not enough time to do it

Changing the design frequently

  • If it does improve the user experience, make it as satisfying as possible!
  • Do not modify a little bit at a timeLet the design work out the modification documentAnd assess the working hours according to the documents
  • Communicate with product to increase design optimization time, not bug fix

How does the front end battle the background?

You develop part of the interface document before it is finished

  • No development!
  • How to mock without an interface document? Inform PM interface document to give time delay, which may cause project delay
  • Can develop first, but does not guarantee time limit
  • Improve yourself: ask 1-2 days in advance whether the project can be delivered on time, and ask questions in advance to ensure that the project schedule is controllable

I’m not done with the interface. I need you to tune some of it

  • No!
  • If the project is urgent to notify the product, the background interface document gives a time delay, which may lead to project delay
  • Can be adjusted first, but do not guarantee the time limit
  • Improve yourself: ask 1-2 days in advance whether the project can be delivered on time, and ask questions in advance to ensure that the project schedule is controllable

Interface data not cleaned or assembled

  • Refuse assembly cleaning!
  • Failure to clean may result in data leakage fromData securityThe Angle made it necessary for him to clean
  • Background non-assembly leads to more requests and more interface data.Affect page seconds open rate, waste traffic
  • Try to communicateAdding BFF layer, do data cleaning assembly,Expand the front-end business scope and technology breadth

The fake data does not mock itself

  • The development phase interface documentation is complete and can be mocked
  • The data must be falsified during the joint investigation, otherwise the joint investigation will be refused

How does the front end battle test?

  • Let herLook at the prototype firstConfirm whether the design is defective, and how to change it after confirming the product
  • Teach him to see the networkDon’t always look for the front end first
  • More important than anything else is testing good habits

How does the front end battle lead?

The detailed time assessment was questioned by the leader

  • Go through each one in turn, giving reasons where you question it
    1. There are preconditions
    2. There are technical difficulties
    3. Multi-department collaboration
    4. The new code is not familiar with the business and code
    5. Uncertainty
  • Total hours of work multiplied by a buffer factor of 1.2 to 1.5 is the final hours
    1. Leave possible
    2. There could be an emergency
    3. There may be boring meetings
    4. Requirements may be modified
    5. To prevent the delay
    6. Code optimization
    7. Write unit tests and smoke tests

Performance falls short of psychological expectations

  • Pull business side to prove business value achievement
  • Pull the time and task list, task amount to support the workload
  • Hold a sharing meeting to share the difficult solutions in the project,Extend industry solutionsTo expand business results
  • Reflect on whetherPoor communicationThe PPT is not good enough
  • Ring by group memberAre they all too good
  • Is it too easy to work on your own
  • Neither. Then you get PUA and run

How does the front-end battle subordinate (PUA)?

  • Workers why difficult workers
  • Thirty years east thirty years west mo bullying young poor
  • Please be human

Tore the sky tore the air, tore the wound,

  • Take trouble to avoid trouble! Front trouble to solve trouble!
  • The detailed time evaluation sheet proves that the fact is impossible, and the time is consistent with the leader in advance to prevent challenge
  • Think of achievable alternatives before you say no
  • Working hard won't earn you praise. Don't be a code machine that doesn't think
  • 36 plan to go for the plan, here do not leave my own leave my place

Deep thinking

  • The front-end needs to communicate with everyone in the project team, and the workload of communication is far greater than the amount of code.The benefits of good communication are obvious!
  • The current situation is: Party A is the father, the product is bigger than the day, the design leads the user experience, the background leads the business logic, the test guarantees the product quality, the front end has no voice, passively accepts and executes the instructions of anyone in the project team
  • How does the front end grasp the right to speak?Time management! The front end controls the initiative and voice of the whole project through time node management.
    • For Party A: When will the node requirements be sorted out?
    • For the product: when will the final prototype be produced?
    • For design: when is the UI draft and interactive draft delivered?
    • Against the background: when does the node deliver the interface document? When is the interface background self test? When can the time node interface be connected?
    • For testing: When does the node deliver the smoke test case? When will nodes be tested?

Day does not give birth to my little pig, time management is like night! Sword!!

(Battle)