Anmerkungen:
Diese Datenquelle enthält auch Bestandsnachweise, die nicht zu einem Volltext führen.
Beschreibung:
Embracing change is in these days the preferred mode of operating software development projects as to meet the pressure of time-to-market. In order to stick to deadline, agile project practices have become the means of first choice, because they implement a time-boxed software delivery process, which anticipates the emergence of requirements. The team is at the heart of each successful agile software project, equipped with all encompassing authority to decide on the scope of requirements to be done within the time available. When it comes to planning the delivery of working software on deadline, agile software development culture demands to Trust the team. Coincidentally or not, this agilist credo ignores the emergence of teams. It conceals the need for the team to know its speed in order to reach consensus on a sound work plan, one which satisfies the software product requirements in the time frame set for the project. Speed is team-unique, since it depends on the team members perception of the work volume they can accomplish within a given project timebox. Since different teams have different methods and experiences for justifying their work volume, speed is not comparable among them. This becomes a dilemma on projects with frequent membership turnover and projects at scale calling for a team of teams. The efficacious planning of time-boxed software projects depends on the team members way to share the knowledge of establishing consistent size estimates for a recognizable scope of software product requirements that they use as the basis for measuring speed. The principle idea followed in this dissertation is to make use of patterns as a common point of reference reusable by individuals and teams for adjusting their know-how and comparing their achievements. On these grounds, it introduces pre-defined units for reproducibly determining the scope and speed of software projects. It leverages the intertwining of patterns from problem analysis and solution design, for controlling project progress with respect to ...