BibSonomy publications for /user/cschenk/developmentWed Jun 25 17:09:20 CEST 2008SCRUM Development Process 2006development paper process read:2008 scrum The stated, accepted philosophy for systems development is that the development process is a well understood approach that can be planned, estimated, and successfully completed. This has proven incorrect in practice. SCRUM assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression. SCRUM defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems. Since these activities are loose, controls to manage the process and inherent risk are used. SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle.Wed Jun 25 17:09:15 CEST 2008Harvard Business ReviewThe New New Product Development Game1986article business development game harvard hbr product read:2008 review scrum Wed Jun 25 14:56:03 CEST 2008SCRUM: An extension pattern language for hyperproductive software development2000development extension language paper pattern read:2008 scrum The patterns of the SCRUM development method are presented as an extension pattern language to the existing organizational pattern languages. In the last few years, the SCRUM development method has rapidly gained recognition as an effective tool to hyper-productive software development. However, when SCRUM patterns are combined with other existing organizational patterns, they lead to highly adaptive, yet well-structured software development organizations. Also, decomposing SCRUM into patterns can guide adoption of only those parts of SCRUM that are applicable to a specific situation.Wed Jun 25 10:57:21 CEST 2008Scrum in five minutes20065 article development five intro minutes overview process read:2008 scrum Wed Jun 25 10:50:53 CEST 2008OctoberAgile Development: Lessons Learned From The First Scrum2004agile article development first lessons read:2008 scrum Wed Jun 25 10:25:44 CEST 2008IEEE SoftwareJuly/AugustThe Scrum Software Development Process for Small Teams2000article development ieee process read:2008 scrum software teams In today’s software development environment, requirements often change during the product development life cycle to meet shifting business demands, creating endless headaches for development teams. We discuss our experience in implementing the Scrum software development process to address these concerns.Fri May 30 16:17:33 CEST 2008Software - Practice and ExperienceJuly7739-755Identifying Syntactic Differences between Two Programs211991algorithm code development diff matching paper read:2008 tree Programmers frequently face the need to identify the differences between two programs, usually two different versions of a program. Text-based tools such as the UNIX utility diff often produce unsatisfactory comparisons because they cannot accurately pinpoint the differences and because they sometimes produce irrelevant differences. Since programs have a rigid syntactic structure as described by the grammar of the programming language in which they are written, we develop a comparison algorithm that exploits knowledge of the grammar. The algorithm, which is based on a dynamic programming scheme, can point out the differences between two programs more accurately than previous text comparison tools. Finally, the two programs are pretty-printed ‘synchronously’ with the differences highlighted so that the differences are easily identified.Fri May 30 16:08:12 CEST 2008New York, NY, USAMSR '08: Proceedings of the 2008 international workshop on Mining software repositoriesMay31--34A Change-Aware Development Environment by Recording Editing Operations of Source Code2008code development diff eclipse paper plugin read:2008 recording source Understanding a program and its evolution is not satisfied only by looking at a current snapshot of its source code. Thus, a developer often examines a sequence of its snapshots stored in repositories of versioning systems, and identifies differences between two successive snapshots. Unfortunately, such differences do not represent individual changes of the source code. This paper proposes a mechanism for recording all editing operations a developer has applied to source code on an integrated development environment. The paper also shows a running implementation of the mechanism built as an Eclipse plug-in, which is called OperationRecorder. The experimental results with a small-scale program substantiate that it has a practical use from the viewpoint of its performance.Sat May 24 14:38:22 CEST 2008Int. Sym. Wikis177-183On-line Collaborative Software Development via Wiki2007collaborative development incremental paper programming read:2008 wiki Wiki is a collaborative authoring system for collective intelligence which is quickly gaining popularity in content publication. In software development communities, especially open source and global software development teams, wiki is already widely used for documentation and coordination purpose but not programming purpose. This paper presents a new programming approach based on wiki technology by which developers are able to experience “writing wiki page is wring source code”. Moreover, developers are able to compile, execute and debug programs in wiki pages too. A prototype of such on-line collaborative software development environment, Galaxy Wiki, is developed in this environment iteratively in order to prove the concept.Sat Jul 21 17:38:00 CEST 2007FebruarySeparation of Concerns1995aop aspect concerns development programming separation This paper identifies and analyzes the emergence of a new paradigm in software engineering, called separation of concerns, which tries to formally separate the basic algorithm from special purpose concerns such as synchronization, real-time constraints, and location control. This separation allows for the locality of different kinds of information in the programs, making them easier to write, understand, reuse, and modify. We identify the major concerns existing in today's software applications, and analyze recent proposals in the literature that address separation of single concerns. Furthermore, we study the commonalities of these proposals and discuss how they can be used to achieve separation of concerns in general. Finally, we address the problem of composition of several separated concerns.Fri Jul 06 17:20:44 CEST 2007MarchISBN-10: 3446223096 ISBN-13: 978-3446223097Der Pragmatische Programmierer2003book development pragmatisch programmierer rating:5 read:2005