Across
- 3. One-on-one conversations used to extract detailed information from stakeholders.
- 4. Physical devices or infrastructure the system must run on or be compatible with.
- 5. The maximum amount of money available for the project.
- 8. Rules or limitations that restrict how a system must operate within a business workflow.
- 9. A guided discussion with selected participants to gather opinions on a topic.
- 10. The structure or layout in which data must be stored, processed, or exchanged.
- 11. The requirement for the system to work with existing software or platforms.
- 13. Specific programs or platforms the solution must support or be built with.
- 14. Following a user closely to see how they perform tasks in real time.
Down
- 1. A set of written questions used to collect data from many people quickly.
- 2. Scheduled gatherings where team members discuss project progress or issues.
- 6. Watching users in their environment to understand how they interact with systems.
- 7. System qualities like performance, reliability, and usability that don’t describe specific behaviours.
- 12. The deadline or schedule the project must adhere to.