Hot answers tagged

3

I'm going to skip answering the parts of the question that do not make sense or are primarily opinion based. So, which plan should actually contain Risk Management, or it should be completely a separate document? Most software organizations don't do this at all or are not formal about it, so you can probably do whatever you want. If you think it ...


1

I would rate each of these improvements on 2 dimensions: - The impact to quality if it was implemented - The ease/quickness/cost that the improvement can be implemented If you have any high impact, easy to do items - those are your first priorities. Otherwise, you might want to take the highest from each category. (one easy, one high impact) You probably ...


1

Coming to this from the safety critical side of the industry I would say that your Risk Management Plan should start with a Corporate level Risk Management Policy that states how you are going to manage the risk aspects of all of your work, for example how risks are categorized, what documentation, testing policies, etc., must be in place and what type of ...


1

@Eduard Florinescu In my view as a Test Engineer - I have to be more detailed oriented with requirements and clear in understanding of product vision, goal & business values. Psychological - Keeping mind fresh is more important task for tester, I suggest you follow these idea. 1) Think a product in 3D view, you view more dimensions.( 3D can be any new ...



Only top voted, non community-wiki answers of a minimum length are eligible