=Paper=
{{Paper
|id=Vol-1519/paper9
|storemode=property
|title=People Management Issues in Scrum from COBIT Perspective
|pdfUrl=https://ceur-ws.org/Vol-1519/paper9.pdf
|volume=Vol-1519
|dblpUrl=https://dblp.org/rec/conf/apsec/Ozkan15
}}
==People Management Issues in Scrum from COBIT Perspective==
https://ceur-ws.org/Vol-1519/paper9.pdf
People Management Issues in Scrum from COBIT
Perspective
Necmettin Ozkan
IT Governance Division
Turkiye Finans Participation Bank
Istanbul, Turkey
necmettin.ozkan@turkiyefinans.com.tr
While Scrum aims to maximize the business value of that it may take enormous effort, time, and patience to build a
information technology (IT), COBIT (Control Objectives for culture of trust and respect among the employees [4].
Information and Related Technology) is to assure the business Documentation as useful artifacts for the backup of
value of IT throughout the international set of generally information is discouraged in Scrum [5]. Thus, much of the
accepted IT control objectives [1]. However, from the point of knowledge in agile development resides in the heads of the
people management, Scrum and COBIT present different development team members [4].
approaches in their essence: Using an agile approach entails formidable responsibility
While COBIT is to standardize people to the processes, on the client’s part [8]. The success of agile development relies
SCRUM relies on people and their creativity rather on finding customers who are expected to be collaborative,
than processes [7]. representative, authorized, committed, and knowledgeable [3].
Great Scrum also needs great product owners [11].
Instead of a command and control style of management Consequently, Scrum brings the advantages of flexibility
in COBIT, Scrum encourages teams with the resources and human initiative, yet opens gates to the diversity and
they need and then trust them to do their jobs well [6].
unpredictability of people which at the end may inhibit to
Albeit Scrum teams have a freedom inside the team, they achieve a level of assurance and control [2], [6]. Thus,
one way or another still have an interaction with the remaining organizations within COBIT environments need to strike a
parts of organizations which have authorities over the same balance between the two conflicting interests: agility and
subject which is maximizing the value. Scrum should gain control.
recognition throughout the organization, and be applied
appropriately. Otherwise, conserving and protecting the natural References
structure and mechanism of the teams becomes a challenge. [1] ISACA, "Cobit 4.1", Rolling Meadows, ISACA, 2007.
The focus migrates from people centric management to [2] Z. Zhiying, 'CMM in uncertain environments', Commun. ACM, vol. 46,
product centric management by Scrum methods and the no. 8, pp. 115-119, 2003.
structure of Scrum shapes around the product concept. Line [3] B. Boehm and R. Turner, Balancing agility and discipline. Boston:
managers, who have primary responsibilities over people, Addison-Wesley, 2004
disappear. However, still someone should watch over people [4] S. Nerur, R. Mahapatra and G. Mangalaraj, 'Challenges of migrating to
agile methodologies', Commun. ACM, vol. 48, no. 5, pp. 72-78, 2005.
who are prone to be forgotten somewhere in the product lines,
[5] K. Beck et al., "Agile manifesto" http://agilemanifesto.org/, 2001
aggressively designed for continuous and unremitting delivery.
[6] A. I. Khan, M. R. J. Qureshi, and U. A. Khan, “A Comprehensive Study
Accountabilities and responsibilities of people management of Commonly Practiced Heavy & Light Weight Software
functions of teams should be addressed in Scrum. As a part of Methodologies,” International Journal of Computer Science and Issues,
it, responsibilities of workload and resource capacity vol. 8, no. 4, pp. 441-450, June 2011
management among and inside the Scrum teams should be [7] A. Cockburn and J. Highsmith "Agile Software Development, The
defined. Performance measurement and reward systems must People Factor", Computer, vol. 34, no. 11, pp. 131 -133, 2001
be suitably designed [4] team based, where collective goals [8] V. Vinekar, C. Slinkman and S. Nerur, 'Can Agile and Traditional
Systems Development Approaches Coexist? An Ambidextrous View',
supersede individual accomplishments [8]. Moreover, career Information Systems Management, vol. 23, no. 3, pp. 31-42, 2006.
path development is a field to study for Scrum which provides [9] K. Judy, ‘Great Scrums Need Great Product Owners: Unbounded
a flat structure of organization rather than a hierarchy including Collaboration and Collective Product Ownership ', in the 41st Hawaii
steps to managerial positions. International Conference on system sciences, 2008.
For the teams that are expected to trust each other, the
concept of codes of ethics plays a critical role for the success of
agile methodologies. And, organizations should be aware of
Workshop on Alternate Workforces for Software Engineering (WAWSE 2015) 54