User Involvement

1. Better and quicker understand users’ needs

2. Users as productive resource in software lifecycles

3. Give users a voice and avoid frustration

• “main users” of product

• their satisfaction closely aligned with achieving products business objective

• users who are “not supposed to use” product for legal, security or safety reasons

  • e.g. user who might stolen a bank info

• 
  

• “wont use your application”

• access data or services through

  • other applications or reports

• e.g. product installer or integration into website

• is a person who takes an inordinate interest in seeing that process or product is fully developed and marketed

• each Product Champion represents one user class

• have clear view of new system

• effective communicators

• e.g. major customers, beta testers, community leads, product owners…

• Planning

  • Refine the scope and limitations of the product

• Requirements

  • Input on requirements from other users

  • Develop usage scenarios, use cases, and user stories

• Validation and verification

  • Review requirements and provide real test data

  • Conduct beta or user acceptance testing

• User aids

  • Contribute to training materials and system demonstrations

  • Evaluate and prioritize defect corrections and enhancements

• Change management

  • Evaluate impact of changes on users and processes

• is a placeholder for “fictional representative“ of user class

• include

  • social and demographic characteristics

  • behavioral patterns

  • peferences

  • annoyances

  • stories

• sonsidering the goals, desires and limitation of user class

• used when representative is “not abailable“

• 
  

1. Revolutionize the role of users in software lifecycles

2. Dissolve the boundaries to software engineers

3. Make software processes and systems social

• Scalability issues

  • Manual analysis infeasible with more users; informal data hard to process.

  • Need tools to filter, analyze, and aggregate feedback.

• Contribution quality

  • Unpredictable information quality without professional support.

  • Misunderstandings and inconsistent user terminology.