{"title":"Distributed Project Governance Assessment (DPGA): Contextual, hands-on analysis for project governance across sovereign boundaries","authors":"W. Anderson, D. Carney","doi":"10.1109/SDG.2009.5071333","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071333","url":null,"abstract":"Managers of technology-intensive projects know that external dependencies beyond their direct control can pose significant risks to their performance. Unfortunately for them, there is a trend toward collaborative systems of systems with combined or threaded capabilities that generate many external dependencies. Today's world of networked, interoperating applications calls for a management perspective that seeks governance across sovereign boundaries.1 The Carnegie Mellon® Software Engineering Institute (SEI) proposes a Distributed Project Governance Assessment (DPGA) process, a work in progress, which helps organizations understand the number and characteristics of external dependencies. We seek to describe the proposed process and solicit community feedback on feasibility, shortcomings, or improvements.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122334336","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Controlling and monitoring agile software development in three dutch product software companies","authors":"T. Cheng, S. Jansen, M. Remmers","doi":"10.1109/SDG.2009.5071334","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071334","url":null,"abstract":"Agile software development governance depends on successful monitoring and control mechanisms. Software development managers generally are unaware of the complete set of monitoring and control mechanisms that are available to them, leading to uninformed decisions with unsuccessful outcomes. This paper presents a list of key process indicators and a list of interventions that software development managers require for successful governance of agile development processes. The list is based on three case studies of product software companies that have successfully developed and sold software for several decades.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133525211","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Scaling agile software development through lean governance","authors":"S. Ambler","doi":"10.1109/SDG.2009.5071328","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071328","url":null,"abstract":"Agile project teams are potentially easy to govern than traditional project teams due to the greater visibility and opportunities to steer provided to stakeholders. Unfortunately, traditional IT governance strategies prove to be at odds to agile's collaborative, value-focused strategies. As a result a lean approach based on enablement, collaboration, and motivation is required to effectively govern agile teams.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131446978","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Software development governance: A meta-management perspective","authors":"Paul L. Bannerman","doi":"10.1109/SDG.2009.5071329","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071329","url":null,"abstract":"Software development governance is a nascent field of research. Establishing how it is framed early, can significantly affect the progress of contributions. This position paper considers the nature and role of governance in organizations and in the software development domain in particular. In contrast to the dominant functional and structural perspectives, an integrated view of governance is proposed as managing the management of a particular domain (that is, a meta-management perspective). Principles are developed and applied to software development governance and illustrated by a case study.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"53 85 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132722007","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"End-to-end features as meta-entities for enabling coordination in geographically distributed software development","authors":"M. Cataldo, J. Herbsleb","doi":"10.1109/SDG.2009.5071332","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071332","url":null,"abstract":"The nature of the software development work activities and their inter-relationships makes supporting geographically distributed software development projects a challenging endeavor. In this paper, we discussed the limitations of the traditional organizational design views in terms of coordination in the context of geographically distributed software development projects. We propose the well-established concept of a product feature as a framework to improve support distributed product development projects through collaborative tools that enhance the coordination capabilities of the development organization. Finally, we present a conceptual idea on how such improvement could be realized using product features as the center pieces for communication and coordination in distributed software development.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"147 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122051215","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Governance of an agile software project","authors":"D. Talby, Y. Dubinsky","doi":"10.1109/SDG.2009.5071336","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071336","url":null,"abstract":"Effective governance of agile software teams is challenging but required to enable wide adoption of agile methodologies, in particular for large-scale projects. In this paper we apply a full lifecycle governance model to agile projects, focused on the iteration level. The concept is demonstrated via a case study of a large-scale, enterprise-critical software project that implemented agile practices. We analyze three governance events, including the metrics that triggered the event, the decisions taken and the followup to ensure resolution. We conclude that governance iterations can be naturally unified with agile development iterations, resulting in a lean governance mechanism that identifies and resolves issues in an effective and timely manner.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"299 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116592203","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Roles, rights, and responsibilities: Better governance through decision rights automation","authors":"Alex Kofman, Avi Yaeli, Tim Klinger, P. Tarr","doi":"10.1109/SDG.2009.5071330","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071330","url":null,"abstract":"At its essence software development governance is about guiding the development organization so that it produces value that aligns with the needs of the business. As software development platforms mature they provide increasingly sophisticated capabilities for process measurement and guidance. These new capabilities in turn offer an excellent opportunity for governance tools to help guide the development. In this paper we discuss a model of the development organization that includes: roles, responsibilities, decisions, rights, artifacts and their lifecycles. We show how this model can be elicited and deployed as part of a governance solution to guide the development organization and provide a description of a prototype we have built to automate this process. We conclude with a discussion and important directions for future work in the area.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"105 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123170967","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Software development governance challenges of a middle-sized company in agile transition","authors":"Ilkka Lehto, K. Rautiainen","doi":"10.1109/SDG.2009.5071335","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071335","url":null,"abstract":"We studied how a middle-sized Finnish company employing agile methods governs its software product development. Through observations and interviews we followed the trace from strategic plans in the form of roadmaps to various backlogs and all the way to daily work. The governance roles, responsibilities and deliverables seemed to be in place on different organizational levels. However, closer inspection revealed challenges in the practical implementation. There were too many roles and hierarchy levels with information consistency problems in between. Prioritization of the high-level goals was unclear and made it difficult to plan and organize development work based on business value. The trace from high-level goals to more detailed plans was easily corrupted due to poor planning practices. Progress monitoring of daily work was poorly done and not linked to high-level plans. Consequently, the required feedback loops were inadequate, making it impossible for management to take corrective actions in time.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134300394","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Software development under bounded rationality and opportunism","authors":"Cengiz Erbas, B. Erbas","doi":"10.1109/SDG.2009.5071331","DOIUrl":"https://doi.org/10.1109/SDG.2009.5071331","url":null,"abstract":"Due to the wicked nature of software development, it is imperative to take into consideration bounded rationality and opportunism of the agents involved in, when managing software development projects. These two concepts, which are at the foundations of transaction cost economics, have not yet been studied in relation to software engineering. In this paper, we develop transaction cost economics approach to software engineering, specifically as it relates to governance. This approach enables us better understand the strengths and weaknesses of top-down and bottom-up processes, and outlines a method to be used in choosing amongst alternative governance structures given relevant project characteristics.","PeriodicalId":191853,"journal":{"name":"2009 ICSE Workshop on Software Development Governance","volume":"38 4","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114051788","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}