From: Exploring reprioritization through systematic literature surveys and case studies
S. no. | Organization | Reprioritization techniques | ||
---|---|---|---|---|
Software engineers employed | Interviewed engineers | Engineers’ characteristics | ||
1. | A | 10,000+ | 07 | Experience of working for the development of many projects at current and some other organizations performing roles and responsibilities. Higher level engineers were also involved |
2. | B | 10,000+ | 04 | Experience of working for the development of many projects at current and some other organizations performing roles and responsibilities. Higher level engineers were also involved |
3. | C | 10,000+ | 03 | Experience of working for the development of many projects at current and some other organizations performing roles and responsibilities. Higher level engineers were also involved |
4. | D | 6000+ | 02 | Experience of working for the development of many projects at current and some other organizations performing roles and responsibilities. Higher level engineers were also involved |
5. | E | 400–600 | 02 | Experience of working for the development of many projects at current and some other organizations performing roles and responsibilities. Higher level engineers were also involved |
6. | F | 400–600 | 01 | Experience of working on many consultancy based projects; typically those which require small team sizes |
7. | G | 200–400 | 02 | Intermediate experience with software development projects |
8. | H | 500–1000 | 01 | Experience of working on many consultancy based projects; typically those which require small team sizes |