Embed Size (px)
Citation preview
The Good, The Bad, and The Ugly of
User Involvement in Software Development
Dr Muneera Bano
User Involvement/User Participation
System SuccessLeads to
User Involvement/User Participation
System SuccessLeads to
Muneera Bano, Didar Zowghi, A systematic review on the relationship between user involvement and system success, Information and Software Technology, Volume 58, 2015, Pages 148-169, ISSN 0950-5849, https://doi.org/10.1016/j.infsof.2014.06.011.
Case Study 1
Case Study 1
Case Study 1
Case Study 1
• Based on our analysis we posit that there is a mutually constituted relationship between user satisfaction with their involvement process and their satisfaction with the delivered system.
• Our results suggest that two important factors played crucial roles in increasing the benefits of user involvement in achieving user satisfaction: • Dynamic management strategies introduced in the Portal project, and
• Effectiveness of the user representation (SME) throughout the project
Bano, M., Zowghi, D. & da Rimini, F. Empir Software Eng (2017) 22: 2339.
https://doi.org/10.1007/s10664-016-9465-1
Case Study 2
Case Study 2
M. Bano, D. Zowghi, F. da Rimini. 2018. Power and Politics of
User Involvement in Software Development. In Proceedings of
Evaluation and Assessment in Software Engineering,
Christchurch, New Zealand June 2018 (EASE).
https://doi.org/10.1145/3210459.3210477
Case Study 1
User Dissatisfaction with their involvement (Process)
Inter-Organisation Politics Ineffective role of PM and SME
User – Developer communication
Case Study 2
User Involvement in Software Development
• The Good• Democratic process and neo-humanist systems aiming to improve the work
process
• Successful implementation and usage of system
• User satisfaction
• The Bad• Challenging to involve users (time, resources, strategy)
• The Ugly• Tussle of power and inter-organisational politics between users and
development team
Effective Management of User Involvement
• Objectives and benefits from psychological, managerial, methodological, cultural or political perspectives
Why to involve?
• Stages of Software Development Life Cycle
When to involve?
• Effective user representation
Who to involve?
• Neo-humanism (PD) or functionalism (JAD)
How to involve?
• The degree and level of involvement i.e. Informative, Consultative, Participative
How much to involve?
References• Bano, M. and D. Zowghi. User involvement in software development and system success: a
systematic literature review. in Proceedings of the 17th EASE 2013. ACM.
• Bano, M. and D. Zowghi, A systematic review on the relationship between user involvement and system success. Information and Software Technology, 2015. 58: p. 148-169.
• Zowghi, D., F. da Rimini, and M. Bano. Problems and challenges of user involvement in software development: an empirical study. in Proceedings of the 19th EASE 2015. ACM.
• Bano, M., D. Zowghi, and F. da Rimini, User satisfaction and system success: an empirical exploration of user involvement in software development. Empirical Software Engineering, 2017. 22(5): p. 2339-2372.
• Buchan, J., et al. Alignment of Stakeholder Expectations about User Involvement in Agile Software Development. in Proceedings of the 21st EASE 2017. ACM.
• Bano, M. , D. Zowghi, F. da Rimini. 2018. Power and Politics of User Involvement in Software Development. In Proceedings of Evaluation and Assessment in Software Engineering, Christchurch, New Zealand June 2018 (EASE).
Q&AThank you for listening!
