|
|
Het Broodje van Blog:
Dit resultaat wijst erop dat de persoonlijke kenmerken van mensen een grens in het algemeen op het effect van methodologieën plaatsen. 3) Every project needs a slightly different methodology, based on those people characteristics, the project's specific priorities, and the technologies being used. This result indicates that a team's methodology should be personalized to the team during the project and may even change during the project. 4) A set of principles were found that can be used to shape an effective methodology to the above constraints. These principles deal with the amount of coordination and verification required in the project, the trade-off between rework and serialization of work, and the trade-off between tacit and externalized knowledge in use by the team. 5) A technique was found to create a situationally specific methodology during the project and in time to serve the project, and to evolve it as the project progresses. 6) All the above suggests a repeating cycle of behavior to use on projects. 1) The members establish conventions for their interactions — a base methodology — at the start of the project. This can be likened to them "programming" themselves. 2) They then perform their jobs in the normal scurry of project life, often getting too caught up to reflect on how they are doing. 3) They schedule regular periods of reflection in which they reconsider and adjust their working conventions. These results have been used successfully on several industrial projects having the usual time and cost pressures on the staff. Table of Contents: 1. The Research Topic 1.1 Clarification of Words 1.2 Background to Question 1 1.3 Background to Question 2 1.4 Background to Question 3 1.5 Placing This Work in Context 1.6 Personal Motivation and Direction 2. The Research Approach 2.1 The Research Practice 2.2 The Research Theory 3. Issues and Results Chronologically 3.1 The Impact of Object-Orientation on Application Development 3.2 Selecting a Project's Methodology 3.3 The Interaction of Social Issues and Software Architecture 3.4 Characterizing People as First-Order, Non-Linear Components in Software Development 3.5 Project Winifred Case Study 3.6 Just-in-Time Methodology Construction 3.7 Balancing Lightness with Sufficiency 4. Consolidation ed Results and Reflection 4.1 Answering the Questions 4.2 Consolidation and Reliability of Results 4.3 Relating to Mathiassen's Reflective Systems Development 4.4 Reflection: The Limits of People-Plus-Methodologies Technorati Tags: software development, software development methodology, application development methodology Popularity: 13% [?] No Comments »No comments yet. RSS feed for comments on this post. Leave a commentYou must be logged in to post a comment. Powered by WordPress |
 |
|
|
