It is clearly a hypothetical question and answer differ based on scenarios here:ĭefect Spotted: Severity 2 (vulnerability defect in a password field by performing SQL injection)ĭays before release: found 3 Days before release in 50 days cycle so that even if you miss or incorrectly categorize a bug you will still know about the effects from the data about your users. Measure engagement, web site visits, customer/order conversions etc. Release early and often and you will be forced to constantly improve to quickly fix problems. Practice dealing with release bugs ahead of time with play acting so you know the procedures. Use an agreed list of people to notify, steps to take, severity levels and what to do for each of them, etc. Use or establish procedures for release bugs. ![]() Not so much 'the slider doesn't work' but more 'all IE users will be unable to place orders (averaging $12,000 per hour.) Use knowledge of the product, domain, users and business to help determine potential severity so that you can. The error comes when you don't communicate about them or help assess their severity. ![]() Suggest a post mortem and develop any procedures or checklists that you believe are needed. may be better than long emails chains Going forwardĭetermine that, going forward, you wish to change things and not be in this situation again, as far as is possible: Using a good communication form - slack, teams, etc. Err on the side of over-communicating and most of all don't let fear stop you from being honest. Early and often For this releaseĪssess the situation as best you can but be sure to pull in the rest of the team and get their input, advice and opinions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |