By Topic

7-13 Aug. 2011

Filter Results

Displaying Results 1 - 25 of 54
  • Agile 2011 Conference [Cover art]

    Publication Year: 2011, Page(s): C1
    Request permission for commercial reuse | PDF file iconPDF (155 KB)
    Freely Available from IEEE
  • [Title page i]

    Publication Year: 2011, Page(s): i
    Request permission for commercial reuse | PDF file iconPDF (80 KB)
    Freely Available from IEEE
  • [Title page iii]

    Publication Year: 2011, Page(s): iii
    Request permission for commercial reuse | PDF file iconPDF (151 KB)
    Freely Available from IEEE
  • Copyright (c) 2011 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. [Copyright notice]

    Publication Year: 2011, Page(s): iv
    Request permission for commercial reuse | PDF file iconPDF (109 KB)
    Freely Available from IEEE
  • 2011 Agile Conference: AGILE 2011 - Table of Contents

    Publication Year: 2011, Page(s):v - viii
    Request permission for commercial reuse | PDF file iconPDF (263 KB)
    Freely Available from IEEE
  • Message from the Conference Chairs

    Publication Year: 2011, Page(s): ix
    Request permission for commercial reuse | PDF file iconPDF (84 KB) | HTML iconHTML
    Freely Available from IEEE
  • Committee Lists

    Publication Year: 2011, Page(s):x - xi
    Request permission for commercial reuse | PDF file iconPDF (93 KB)
    Freely Available from IEEE
  • The Combination of Agile and Lean in Software Development: An Experience Report Analysis

    Publication Year: 2011, Page(s):1 - 9
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (233 KB) | HTML iconHTML

    There has been a noticeable focus shift from agile methods such as extreme Programming (XP) and Scrum to lean software development in the last several years, which is indicated as "from agile to lean". However, the reality may not be as simple or linear as the term implies. To provide a better understanding of the combined use of agile and lean approaches in software development, a set of experien... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • There's Something about Lean: A Case Study

    Publication Year: 2011, Page(s):10 - 19
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (215 KB) | HTML iconHTML

    One of the ideas gaining significant interest at the moment is "how can we apply Lean manufacturing principles to software development?" There is however, limited information on how Lean is being used by industry practitioners and if the principles and practices are as effective as current interest levels suggest it might be. We have used a case study to explore the practicalities of how one high-... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Why Scrum Works: A Case Study from an Agile Distributed Project in Denmark and India

    Publication Year: 2011, Page(s):20 - 28
    Cited by:  Papers (8)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (176 KB) | HTML iconHTML

    Scrum seems to work extremely well as an agile project management approach. An obvious question is why. To answer that question, we carried out a longitudinal case study of a distributed project using Scrum across Denmark and India. In our analysis of case study data we used three selected theoretical frameworks. We conclude that Scrum works so well because it provides communication, social integr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Survey of Agile Tool Usage and Needs

    Publication Year: 2011, Page(s):29 - 38
    Cited by:  Papers (16)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (385 KB) | HTML iconHTML

    Today, little is known about what tools software companies are using to support their Agile methods and whether they are satisfied or dissatisfied with them. This is due to lack of objective surveys on the subject. The surveys that have been conducted so far are of a subjective nature and have mostly been performed by tool vendors. They are very limited in number and focus mainly on company struct... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Decision Making in Agile Development: A Focus Group Study of Decisions and Obstacles

    Publication Year: 2011, Page(s):39 - 47
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (297 KB) | HTML iconHTML

    The process and effectiveness of decision making in agile development is critical yet poorly understood. This research examines decisions made across the four stages of the sprint cycle: Sprint Planning, Sprint Execution, Sprint Review and Sprint Retrospective. A focus group was conducted with 43 agile developers and managers to determine what decisions were made at different points of the sprint ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Reconciling Perspectives: How People Manage the Process of Software Development

    Publication Year: 2011, Page(s):48 - 56
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (235 KB) | HTML iconHTML

    Social factors are the significant cost drivers for software development and in this field study we develop a grounded theory of how people manage the process of software development. We discovered the main concern of those involved in the process of software development is getting the job done and to get the job done, people engage in a constant process of Reconciling Perspectives. Reconciling Pe... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Agile Team Perceptions of Productivity Factors

    Publication Year: 2011, Page(s):57 - 66
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (202 KB) | HTML iconHTML

    In this paper, we investigate agile team perceptions of factors impacting their productivity. Within this overall goal, we also investigate which productivity concept was adopted by the agile teams studied. We here conducted two case studies in the industry and analyzed data from two projects that we followed for six months. From the perspective of agile team members, the three most perceived fact... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Enacted Routines in Agile and Waterfall Processes

    Publication Year: 2011, Page(s):67 - 76
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (375 KB) | HTML iconHTML

    Agile methods form an alternative to waterfall methodologies. Little is known about activity composition, the proportion of varying activities in agile processes and the extent to which the proportions of activities differ from "waterfall" processes. In the current study, we examine the variation in per formative routines in one large agile and traditional lifecycle project using an event sequenci... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • User-Centered Design and Agile Methods: A Systematic Review

    Publication Year: 2011, Page(s):77 - 86
    Cited by:  Papers (42)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (471 KB) | HTML iconHTML

    This paper presents the results of a systematic review of existing literature on the integration of agile software development with user-centered design approaches. It shows that a common process model underlies such approaches and discusses which artifacts are used to support the collaboration between designers and developers. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Collaborative Events and Shared Artefacts: Agile Interaction Designers and Developers Working Toward Common Aims

    Publication Year: 2011, Page(s):87 - 96
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (288 KB) | HTML iconHTML

    Agile processes emphasize collaboration. We were interested in studying collaboration in agile teams including interaction designers, since the integration of user interaction design processes and software development processes is still an open issue. This study focused on designer and developer collaborations in the early stages of project work at four workplaces. We found designer-developer coll... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Home Ground of Automated Acceptance Testing: Mature Use of FitNesse

    Publication Year: 2011, Page(s):97 - 106
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (245 KB) | HTML iconHTML

    This article describes a group of developers and how they successfully use Fitness. The study is based on interviews with 4 consultants, and shows that automated acceptance testing was used in two steps every iteration: a specification step where it helped communicate requirements, and a verification step where it helped developers in the process of producing and maintaining software. The study in... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Rule-Based Exploratory Testing of Graphical User Interfaces

    Publication Year: 2011, Page(s):107 - 116
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (334 KB) | HTML iconHTML

    This paper introduces rule-based exploratory testing, an approach to GUI testing that combines aspects of manual exploratory testing with rule-based test automation. This approach uses short, automated rules to increase the bug-detection capability of recorded exploratory test sessions. A preliminary evaluation found that this approach can be used to detect both general and application-specific bu... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Understanding Post-Adoptive Agile Usage -- An Exploratory Cross-Case Analysis

    Publication Year: 2011, Page(s):117 - 126
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (211 KB) | HTML iconHTML

    The widespread adoption of agile methodologies raises the question of their continued and effective usage in organizations. An agile usage model consisting of innovation, sociological, technological, team, and organizational factors is used to inform an analysis of post-adoptive usage of agile practices in two major organizations. Analysis of the two case studies found that a methodology champion ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Telling Stories about Software Evolution

    Publication Year: 2011, Page(s):127 - 130
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (240 KB) | HTML iconHTML

    Software systems evolve over time. The software development community is losing a great deal of information about the systems we create because of the way we currently record history. This paper argues that we need to capture more fine-grained historical information, like the kind that spreads in a pair programming session, and use it to tell stories about how software systems evolve over time. Th... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Path for Exploring the Agile Organizing Framework in Technology Education

    Publication Year: 2011, Page(s):131 - 134
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (165 KB) | HTML iconHTML

    When the Agile Organizing Framework (AOF) is examined through the lens of the social constructivist pedagogy, principles and practices that define an agile learning environment emerge. This paper presents a translation of the AOF to fit the context of instruction in higher education based on the social constructivist perspective, and is not limited to software engineering education. Additional res... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Confidence of Agile Assessment Methods in the Context of Software Process Improvement

    Publication Year: 2011, Page(s):135 - 138
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (144 KB) | HTML iconHTML

    With the advent of CMMI in the late 1990s, software companies tried to use a kind of score to rank themselves in the market. Being a CMMI level five company for a long time represented the epitome of highly qualified company. This phenomenon is also emerging in the agile software development with the emergence of methods such as Nokia or comparative test agility. This paper presents an analysis of... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using Acceptance Tests for Incremental Elicitation of Variability in Requirements: An Observational Study

    Publication Year: 2011, Page(s):139 - 142
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (274 KB) | HTML iconHTML

    Variability in software systems refers to the notion that the components constituting the software may vary due to a range of factors including diverse customer needs, technical constraints, and business strategies. Traditionally, variability has been treated proactively by investing in an upfront domain analysis phase. Such proactive treatment of requirements is not encouraged in agile environmen... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How to Build an Informative Workspace? An Experience Using Data Collection and Feedback

    Publication Year: 2011, Page(s):143 - 146
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (324 KB) | HTML iconHTML

    Several works on agile methods discuss the use of team's workspace for displaying relevant information. The management of an Informative Workspace (IW) is a challenging task as it can involve many different subjects such as team adaptability, continuous reflection, workspace layout, human cognition, usability, etc. Our paper explores the IW management and it is divided in two phases. The first pha... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.