Bug Vs Feature Development



  • Not sure if this has already been discussed, if yes please point me out appropriately.

    I am a Product manager in at a software firm. We are developing a mobile application. We are developing 2 features. Now, the client has pointed out a bug. As a Product Manager/Product Owner, how do I handle this situation. We have a team working remotely and another team working in the same location I am working.

    Please let me know how to handle this step wise and also if you can give me examples of what you have done. It will be helpful. Any perspective from tech/IT would be super useful.



  • When you receive a bug report, it needs to be triaged. The workflows that I use tend to look something like this:

    1. Review the bug report and confirm that it truly is a bug. Some people who report issues may not be aware of the intended behaviors of the system. The issue reported could be acting as designed.
    2. Assuming that the issue is a bug, check the quality of the report. Is the bug consistently reproducible? If it is, does the bug report have steps to reproduce? If not, is there any indication of how frequent it happens? What is the impact of the bug on end users? What is the difference between actual and expected behavior of the system?
    3. Once the report has sufficient details, it needs to be prioritized. Not all bugs are created equal. For example, a bug that results in data loss is different than one that highlights a spelling mistake, taking two rather extreme cases. A bug that happens consistently and repeatedly is different than one that is intermittent. A bug with a known workaround is different than one with no known workarounds, and the level of effort to execute the workaround also matters. In an ideal world, all bugs would be prioritized over new features, but this isn't always achievable.
    4. Once a bug has been prioritized, it will eventually come up with a development team. They can make sure that it's understood, clear, and that they have any information that they need to investigate, implement, and fix. As the development team learns more, there may be various options and ways to either fix the bug or mitigate problems. This can possibly spawn new work and it's up to the development team and product manager to understand the risk and impact of various options.

    As the product manager, you should be communicating with stakeholders - customers, end users, technical support staff - to make sure that the right people have the right visibility into the status of the issue. This can also help you understand the stakeholder impact of not addressing the issue - priorities can change over time based on how the manifestation of the bug is also changing.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2