Comparison of Process Quality Characteristics Based on Change Request Data
IWSM/Metrikon/Mensura '08 Proceedings of the International Conferences on Software Process and Product Measurement
Innovations for Requirement Analysis. From Stakeholders' Needs to Formal Designs
IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
Attracting the community's many eyes: an exploration of user involvement in issue tracking
Human Aspects of Software Engineering
Analysing requirements in a case study of pairing
Proceedings of the 1st Workshop on Agile Requirements Engineering
Evolution of features and their dependencies - an explorative study in OSS
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Always beta: cooperative design in the smart home
Proceedings of the 2013 ACM conference on Pervasive and ubiquitous computing adjunct publication
| Hi-index | 0.00 |
Eclipse is a widely recognized open source project dedicated to providing a platform for developing integrated tools. Throughout the history of Eclipse the development team was successful in hitting projected delivery dates with precision and quality. This isn't possible without a team strongly committed to ship quality software. How is this really done? How does Eclipse achieve quality and just-in-time delivery?This talk sheds light on the key practices of the Eclipse development process - from the development mantras "Always Beta", "Milestones First", "API First", and "Performance First" to practices such as ensuring quality through multiple feedback loops. Erich will reflect on proven practices for managing a large project performed by geographically dispersed teams and open source contributors in a highly competitive market. Most of these practices have evolved in the open source project, but they are equally applicable to closed source projects and will help to improve quality, timeliness and reduce development stress in both types of environments.