Compare and contrast Agile Usage-Centered Design with eXtreme "planning Game" for

requirement determination.

In agile usage-centered design, the requirement gathering is based on user involvement. All the

parties involved gather together to determine requirements. Everyone will have a chance to

provide their suggestions, feedbacks on the existing system and provide their insights for the new

system. “The requirement gathering focus on user roles, user goals and tasks that are needed to

achieve these goals” (Valacich & George, 2020). In usage-centered design, people think on

behalf of the user who access the system and why they access it and determine the requirements

according to that. Tasks will be decided and divided among everyone depending on the priority.

Then a paper-and-pencil prototype will be created at the end of the meeting.

eXtream “planning Game” also focuses on customer. “Here all the phases of software

development life cycle such as planning, analysis, design and construction are merged into series

of activities” (Valacich & George, 2020). Developer who build the product and customer who

uses the product work together or play together towards the end goal. Customer will provide the

requirements and feedbacks necessary for the system and developers design the system

according to that. Requirements gathered from the customer as called as story cards. The

requirements gathered will be divided into three groups: important features, valued added

features and not important but good to have features. Developers build the product according to

the priority of these features and test it.

We can see there are some similarities in both agile usage-centered design and eXtream planning

game as they both focuses and gather their requirements based on the end user. Tasks will be

gathered and executed according to their priority.

Reference:

Valacich, J. S., & George, J. F. (2020). Modern systems analysis and design (9th ed.). Hoboken,

NJ: Pearson Education.