Cruel Preeminence - severity and priority in software development

One of the most important aspects of the defect life cycle on the most basic level is a defect tracking.  You probably think that it is mostly software testers job, right? Wrong. Tracking tasks and issues is bread and butter in software development, it is something that drives work forward, no matter if you are a tester, developer or project manager. But how do you know which of the tasks need to be dealt with first? How do you recognize if something needs more attention and immediate action? This is when what I call “Cruel Preeminence” meaning defect prioritization and severity, comes to play. What do they stand for? What is the difference between them and why can’t we use both terms interchangeably?

see what we can create for you

We use cookies on this site to improve performance. By browsing this site you are agreeing to this. For more information see our Privacy policy I understand