Understanding the use of an electronic process guide

Scott, Louise; Carvalho, Lucila; Jeffery, D. Ross; D’Ambra, John; Becker-Kornstaedt, Ulrike

doi:10.1016/s0950-5849(02)00080-0

Cited by 46 publications

(29 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An electronic process guide [18,25,38] may be viewed as an online, structured, workfloworiented [21], reference document for a particular process that exists to support participants in carrying out the intended process. An electronic process guide may include the following basic elements:…”

Section: Electronic Process Guidesmentioning

confidence: 99%

“…Scott et al [38] report the results of an eight-month study of the usage of the electronic process guide at Alette: what it is used for, how it is used, and the effects of usage. A first study reports a declining use over the period studied, and the electronic process guide was used principally to support process improvement, mainly through providing templates and task lists for projects and by providing a discussion forum on templates.…”

Section: Electronic Process Guide Usagementioning

confidence: 99%

See 1 more Smart Citation

The Impact of Employee Participation on the Use of an Electronic Process Guide: A Longitudinal Case Study

Dingsøyr

Moe

2008

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Many software companies disseminate process knowledge through electronic process guides. A common problem with such guides is that they are not used. Through a case study we investigated how participation in creating an electronic process guide, through process workshops, influenced the use of the guide. We studied developer and project manager usage with respect to three factors: frequency of use, used functionality, and reported advantages and disadvantages. We collected data from three rounds of interviews and 19 months of usage logs in a longitudinal study in a medium-size software company. Employees who participated in process workshops showed a higher degree of usage, used a larger number of functions, and expressed more advantages and disadvantages than those not involved. Our study suggests that employee participation has a long-term positive effect on electronic process guide usage.

show abstract

Section: Electronic Process Guidesmentioning

confidence: 99%

Section: Electronic Process Guide Usagementioning

confidence: 99%

The Impact of Employee Participation on the Use of an Electronic Process Guide: A Longitudinal Case Study

Dingsøyr

Moe

2008

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…For process guides to be useful, increasingly more software companies not only tailor their process guides to the specific needs of the company, but also make them available on the company's intranet. This way the traditional process handbook shifts from a bulky pile of paper to a flexible on-line structure allowing easy access to all relevant information by means of an electronic process guide (Scott et al, 2002). A process guide can be seen as a structured, workflow-oriented, reference document for a particular process, and exists to support participants in carrying out the intended process (Kellner et al, 1998).…”

Section: Electronic Process Guidesmentioning

confidence: 99%

A Workshop-Oriented Approach for Defining Electronic Process Guides – A Case Study

2006

Software Process Improvement

View full text Add to dashboard Cite

Abstract:We introduce electronic process guides, and discuss their role in software engineering projects. We then present existing methods for constructing electronic process guides by defining a set of common processes for a company. Different approaches from the software engineering and management science are presented. We then go on to propose a new way of dealing with process description in software engineering: using process workshops as a tool to reach consensus on work practice. The main reason for this is to get realistic descriptions with accurate detail as well as company commitment in an efficient manner. We describe our workshop-oriented method to define processes, which we have used in small software companies, and show examples of results.

show abstract

“…These problems of paper-based process guides can be mitigated by an EPG which provides a process guide using the web technology [5,8]. However, simply providing a process guide in forms such as PDF, Microsoft Word, or other electronic formats or converting the contents of a process guide into HTML is not treated as an EPG.…”

Section: Epg and Ermentioning

confidence: 99%

“…A paper process guide generally has problems in its usability and maintenance because it is very inconvenient for developers to search and navigate process information and difficult to add process-related information or to modify existing information [8]. To solve these problems caused by a paper process guide, an EPG using the web technology is proposed allowing easy access to all process-related information [5,8]. To allow easy navigation of the PSP process information and to enable storing additional information, it is necessary to develop an EPG which enhances the contents and usability of the paper-based PSP guide.…”

Section: Introductionmentioning

confidence: 99%

Jasmine: A PSP Supporting Tool

Shin¹,

Choi²,

Baik³

Software Process Dynamics and Agility

View full text Add to dashboard Cite

Abstract. The PSP (Personal Software Process) was developed to help developers make high-quality products through improving their personal software development processes. With consistent measurement and analysis activities that the PSP suggests, developers can identify process deficiencies and make a reliable estimate on effort and quality. However, due to the high-overhead and context-switching problem of manual data recording, developers have difficulties to collect reliable data, which can lead to wrong analysis results. Also, it is very inconvenient to use the paper-based process guide of the PSP in navigating its process information and difficult to attach additional process-related information to the process guide. In this paper, we describe a PSP supporting tool that we have developed to deal with these problems. The tool provides automated data collection and analysis to help acquire reliable data and identify process deficiencies. It also provides an EPG (Electronic Process Guide) in order to provide easy access and navigation of the PSP process information, which is integrated with an ER (Experience Repository) to allow developers to store development experiences.

show abstract

Understanding the use of an electronic process guide

Cited by 46 publications

References 4 publications

The Impact of Employee Participation on the Use of an Electronic Process Guide: A Longitudinal Case Study

The Impact of Employee Participation on the Use of an Electronic Process Guide: A Longitudinal Case Study

A Workshop-Oriented Approach for Defining Electronic Process Guides – A Case Study

Jasmine: A PSP Supporting Tool

Contact Info

Product

Resources

About