Llewellynfalco.blogspot.com Website Review

BUGS HAPPEN. WHILE YOU COULD SIMPLY FIX THEM, YOU COULD INSTEAD TAKE AN EXTRA STEP TO PREVENT SIMILAR MISTAKES FROM OCCURRING AGAIN. THIS. We will go in to the philosophies and reasons to do this in other articles. Do safeguarding right after you’ve fixed a bug. The same day or next is good. This is when it’s fresh in your mind and when The key roles that need to be in the room are the people who: 2. Root Cause An*lysis (RCA) We are going to gather impartial observations about what happened. Create a Google Doc that everyone can access, with with the following tree: Everybody is going to start adding nodes under these three headings. They will also add questions in response to the nodes. All of this is done at the same time by all attendees without any talking. We will do a version of dot voting. Everyone will vote on as many items as they want but no more than once per item. Voting is done by After voting, copy the top 3-4 items into a section labeled: REMEDATIONS Before we come up with solutions, start by asking: was the total impact of this bug small, medium, or large? Have everyone hold up 1, 2, or 3 fingers. Pick the most common answer. Then propose an initial time box: Since we execute solutions immediately, this is the point where we need the approval of the project manager. Because we intend to do 3 solutions, each solution can only be ¼ of the total budget (to allow some slack). This means that each item will This section is timeboxed to 2 MINUTES. 5. Identify Remediations Next we are going to brainstorm improvements to our system to reduce the chances of this issue happening again. Going back to the Google Doc, everyone will silently add ideas to the second section that we copied from the top brainstorming section. Solutions that require extra discipline are bad solutions. We are looking for ways to make success easier. Remember to keep in mind these are timeboxed solutions meant to improve our system and environment as opposed to solve everything.