Language constructs for managing change in process-centered environments
SDE 4 Proceedings of the fourth ACM SIGSOFT symposium on Software development environments
Software project management
Introduction to the team software process
Introduction to the team software process
Proposed NIST standard for role-based access control
ACM Transactions on Information and System Security (TISSEC)
Agile software development ecosystems
Agile software development ecosystems
Designing Complex Organizations
Designing Complex Organizations
Object-Process Methodology: A Holistic Systems Paradigm
Object-Process Methodology: A Holistic Systems Paradigm
Deriving executable process descriptions from UML
Proceedings of the 24th International Conference on Software Engineering
Business artifacts: An approach to operational specification
IBM Systems Journal
Using a role scheme to derive software project metrics
Journal of Systems Architecture: the EUROMICRO Journal - Special issue: AGILE methodologies for software production
Enacting responsibility assignment in software development environments
Proceedings of the 1st international workshop on Software development governance
Towards governance schemes for distributed software development projects
Proceedings of the 1st international workshop on Software development governance
Artifact-centered operational modeling: lessons from customer engagements
IBM Systems Journal
Agile Software Engineering
Defining an integrated agile governance for large agile software development environments
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Supporting Software Development With Roles
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
Hi-index | 0.00 |
Teams differ in the way they define roles and responsibilities and in the level of formalism by which they establish and communicate these definitions. Responsibilities are not always clearly defined, and there is often confusion or mismatch between the individual's perspectives of a role and the expectations of that role by other team members. This lack of shared understanding can lead to issues in performance and lack of accountability. We review the notion of role specification as part of software development governance and present an approach for specifying responsibilities in terms of decisions to be made during the life cycle of software development artifacts. We present evaluation data from software teams as they redefine their roles and shape their responsibilities. We further present a tool for governance specification based on this approach, which can ensure that these specifications are adhered to in the software development platform. We conclude by describing a methodology for how the tool and approach can be implemented to help software development teams understand and evolve the appropriate governance for their needs.