Study Overview

This is the study overview page. Here you will find which goal and requisite contributions were reported by this study. If you are an author of this study, you can log in using your author username and password for this study and add or edit goal/requisite contributions.

Method fragments in this study

Here is a list of method fragment related to this study. Click on one to see its goal and requisite contributions as reported by this study.

Iteration Planning

Goal contributions

Major Goal Minor Goal Contribution Value Situation
Improved Project Planning More realistic prioritization of tasks + In General
Improved Project Planning Accurate project scheduling - customer and management were unaccustomed in negotiating schedule
Improved Communication Enhanced Communication with business people / project leader + In General
Improved Communication Better understanding of customer needs + In General
Improved Collaboration Closer collaboration of customer and development team + In General
Improved Project Management More Visibility of Project + In General
Improved Team Management Enhanced Self-Organizing (self-task/time management) + In General
Improved Effectiveness (performance) preventing teams from focusing on items with lower priority + In General

Requisite contributions

(S - Satisfied, PS - Partially Satisfied, U - Undefined, D - Denied, PD - Partly Denied)

Major Requisite Minor Requisite Requisite Satisfaction Value Situation

Story Board

Goal contributions

Major Goal Minor Goal Contribution Value Situation
Improved System Analysis Faster System Analysis ++ In general

Requisite contributions

(S - Satisfied, PS - Partially Satisfied, U - Undefined, D - Denied, PD - Partly Denied)

Major Requisite Minor Requisite Requisite Satisfaction Value Situation
Stories (requirements) be well-defined Story be business-oriented U N/A
Stories (requirements) be well-defined Story be estimatable U N/A
Stories (requirements) be well-defined Story be short and implementable during one iteration U N/A
Stories (requirements) be well-defined Story be testable U N/A

Study information

ID:
51

Name:
Beck1999

URL:
http://dx.doi.org/10.1109/2.796139

Study Type:
Empirical Study

Study Format:
Case Study

Description:
10 ~ 15 programmers

Organization:
NA

Year:
1999

Reference:
Beck; K. (1999). Embracing change with extreme programming. In Computer; 32(10); 70-77.

Title of Paper:
NA

Conference Name:
NA

Abstract:
NA