Software Estimation Educational Games
COSMIC Chaire philanthropique ETS
← Back to Game B Questionnaire • Early sizing

Early Sizing of Requirements Questionnaire

Early sizing of the requirements of software projects & issues - Game B

Game narrative
Welcome to this educational game that consists of performing an early sizing of a software.

This game considers:

  • The profile of the measurer
  • The measurer experience
  • The number of requirements that must be measured
  • The number of functional user requirements is 10 or 50.
  • The budget is $2,500 or $10,000 depending on the number of functional user requirements to measure.
  • If you choose to buy a tool, the speed to complete the measurement will be faster.

To move forward in the game you click "Next" after choosing all your options.

Measurer profiles

Nine (9) employees are available, and you must choose only two (2) measurers to carry out this early software sizing. The measurers can have one of the following three profiles:

Profile Description
Perfectionist Analyzes each requirement carefully and takes all steps to ensure the right interpretation before deciding on the size to allocate. Measurement accuracy is what matters most; measurement speed is less important.
Expeditious Aims to determine the size of each requirement as quickly as possible. Accuracy is less important. Completing the early sizing quickly and finishing on time is the priority.
Balanced A 50-50 mix of perfectionist and expeditious: aims for a balance between measurement speed and measurement accuracy.

Documentation quality

Other factors contribute to speeding up or decreasing the effort and duration of the early sizing. Documentation quality is the most important factor.

Documentation level Description
Detailed All functional user requirements are fully documented with all the details required for COSMIC measurement purposes (functional users, functional processes, data movements, and data groups are clearly identified).
Not detailed Many elements for functional size measurement are ambiguous or missing. Information on functional users, functional processes, data movements, and data groups is incomplete or unclear.