Julian Bass is researching how communities adapt and use digital technologies. He has published findings in ICT for International Development, agile software development methodologies and socio-technical systems engineering (See Citation List).
Dr Bass is a lecturer at University of Salford, Co-Chair of the IFIP Working Group Conference on the Social Implications of Computers in Developing Countries, Yogyakarta, Indonesia, 2017 and a Senior Editor of the Electronic Journal of Information Systems in Developing Countries (EJISDC).
- Improving writing processes using lean and Kanban
- Artefacts and agile method tailoring in large-scale offshore software development programmes
- Large-Scale Offshore Agile Tailoring: Exploring Product and Service Organisations
- Scrum Master Activities: Process Tailoring in Large Enterprise Projects
- How product owner teams scale agile methods to large distributed enterprises
Julian was formerly secretary of the IFIP Working Group on the Social Implications of Computers in Developing Countries.
Previously Dr Bass was the Higher Education IT Advisor at the Higher Education Strategy Centre (an agency of the Ministry of Education) in Ethiopia.
He co-authored and edited the national Computing Guidance Notes and Benchmark document now in use in the country.
Agile Method Tailoring in Distributed Enterprises: Product Owner Teams
This paper explores practitioner descriptions of agile method tailoring in large-scale offshore or outsourced enterprise projects. Specifically, tailoring of the product owner role is discussed. The product owner identifies and prioritizes customer requirements. But in globalized projects, the product owner must reconcile large numbers competing business interests and generate prioritized requirements for many development teams. The study comprises 8 international companies in London, Bangalore and Delhi. Interviews with 46 practitioners were conducted between February 2010 and May 2012. A grounded theory approach was used to identify that product owner teams comprise nine roles: Groom, Prioritizer, Release Master, Technical Architect, Governor, Communicator, Traveler, Intermediary and Risk Assessor. These product owner roles arbitrate between conflicting customer requirements, approve release schedules, make architectural design decisions, provide technical governance and disseminate information across teams. Understanding these roles will help agile coaches guide large scale agile teams
The full paper is avialable here