![stay focused app bugs stay focused app bugs](https://cdn.nerdschalk.com/wp-content/uploads/2021/06/focus-not-working-fixes-3-b.png)
At the very least, this will minimize the impact of the bug on new users.ĭoing this requires having a production deployment system setup that supports clean rollbacks. If a bug in production is the result of a previous sprint’s work, and it’s having a negative effect on users, the simplest thing to do whenever possible is to roll back the production server to the state that it was in before it was updated after the last sprint. Choosing the one that works best for your team is dependent on how your company is structured, how critical the bug is, and what matters most to your product owner and your customer. There are many different approaches to dealing with bugs in production that come up during a sprint. How’s your agile team supposed to respond to that?
Stay focused app bugs code#
Maybe some aspect of the code that wasn’t fully tested comes to the surface, and starts causing problems for users. Your team has finished deploying, all the tests passed, and everything has been pushed out to production so customers can start using it.īut maybe an edge case that wasn’t considered comes up. One of the problems that comes up frequently for teams is the discovery of a new bug in production right in the middle of a sprint. It’s about adapting to reality, and iterating to improve your processes and your flexibility so that when problems arise you’re able to deal with them. Agile isn’t about pretending that your world is perfect. That’s one of the reasons why we have agile in the first place. Of course, we don’t live in a perfect world. There would never be any bugs, and there would never be any issues that forced us to roll back code that has already been deployed. In a perfect world, every time we rolled out code at the end of a sprint, it would work perfectly in production.