Jennifer Garnett

I have identified four “baseline” (Sharp, et al., 1999) stakeholders/stakeholder groups for this system, which include: the users (players, team captains, and attendance committee), the project manager (me), finance (league treasurer) and the “customer” (the league’s Board of Directors). For this iteration of the project, I will focus on satisfying the customer/users. I requested volunteers from the stakeholder groups, and spoke with several of these potential users (via email and in-person interviews) in order to gain an understanding of their background and technical expertise, as well as what they would hope to gain from this system. I have selected six users (representing each of the stakeholder categories on which I will focus), as a starting point for user persona generation and initial testing. I may add a few additional testing participants to account for differences in how each type of user will interact with the system, as needed. This is per the recommendations regarding the most efficient number of users to test during usability testing. (Nielsen, 2000)

 

The tasks the users want to be able to complete with this system include:

• Track skater attendance/participation

• View player status (LoA, Bench, active, etc.)Verify skater eligibility

• View roster and contact information

• Track skater skills & conduct assessments

• Generate, View, and share reports of above

 

They want to be able to do these tasks in real-time, from their mobile phones, while at a practice or event, or when they are without access to a personal computer. They may be sitting or standing. They may be in a loud environment or a quiet one. The data entry needs to be quick and simple as the users want to complete the tasks quickly and efficiently. Users should be able to easily email reports, and view reports on a small screen.

 

For the purposes of this project, I will be focusing on the following tasks:

• Tracking skater attendance/participation

• Verify skater eligibility

• Generate, View, and share reports of above

 

The users need a single comprehensive system that remains consistent for the entire league. It must be clear, simple to use, and easy to find information. Some of the desired features include:

• “Being able to contact the skater through the app and to enter and get current standing in real time.”

• “Organized, easy to use, everyone who needs to access it can access it.”

• “Better ways to track all derby related activities.”

• “Immediate feedback in % of attendance in League and team.”

• “It would be nice to [be able to] do everything in one place.”

 

 

 

References:

 

Nielsen, Jakob. (2000). Why You Only Need to Test with 5 Users. Nielsen Norman Group: Evidence-Based User Experience Research, Training, and Consulting. Retrieved February 3, 2013 from http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/

 

Sharp, H., Finkelstein, A., & Galal, G. (1999). Stakeholder Identification in the Requirements Engineering Process. Database and Expert Systems Applications. Paper presented at 10th International Workshop on Database & Expert Systems Application, Florence, Italy, September (pp. 387–391). Retrieved February 3, 2013 from http://eprints.ucl.ac.uk/744/1/1.7_stake.pdf

 

 

 

For a full discussion of understanding the problem, please download the full M2 text here: