MISY430 Lecture Notes - Lecture 6: Executive Sponsor, Scope Creep, User Story

• School: University of Delaware
• Department: Management Information Systems
• Course: MISY430
• Professor: Clinton White

Document Summary

Include all stakeholders at all levels of the organization: understand the client, the business, and typical pain-points and opportunities, help the stakeholders uncover requirements, they tend to jump to conclusions, be organized/structured, disciplined, and thorough. Inadequate initial problem statement: getting access to the right people can be difficult, users jump to conclusions. Inappropriate project sponsor should be at a high enough level within the organization: usually means you didn"t get to the root cause of the problems. Functional requirements: something the system must do to meet needs, ex: query database, provide interactive input, access external data, etc. Nonfunctional requirements: characteristics of a system, ex: operational, performance, security, etc, need to meet usability requirements. User stories: use functional and nonfunctional requirements, lightweight substitute for requirements specification, each user story identifies something that the system needs to do for a user (functional and nonfunctional)