BibSonomy ::  user :: gresch ::

Open-source project management tool, intended to assist the collaborative aspect of work carried out by agile software development teams. Free / Open-source (MIT License) Full Development Life-cycle Comprehensive Adminstration Multiple projects within one instance Powerful Add-on Interface REST-API (Example) & RSS Support (Example)

Agilefant is an open source tool for managing agile software development activities, such as: projects, products, releases, iterations and backlogs. It brings together the perspectives of long-term product and release planning and project portfolio management.

AutoPatch was born from the needs of using an agile development process while working on systems that have persistent storage. Without AutoPatch, developers usually can't afford the maintenance headache of their own database, and DBAs are required just to apply changes to all of the various environments a serious development effort requires. The very application of database changes becomes an inefficient, error-prone, expensive process, all conspiring to discourage any refactoring that touches the model, or being a bottleneck when model changes are made. AutoPatch solves this problem, completely. With AutoPatch, an agile development process that requires a database change looks like this: * Developer alters the model, which requires a change to the database * Developer possibly consults a DBA, and develops a SQL patch against their personal database that implements the alteration * Developer commits the patch to source control at the same time as they commit their dependent code * Other developers' and environments' databases are automatically updated by AutoPatch the next time the new source is run This represents streamlined environment maintenance, allowing developers to cheaply have their own databases and all databases to stay in synch with massively lower costs and no environment skew. That's what AutoPatch does. Clusters with one database? Multiple schemas? Logical migrations, instead of just DDL changes? Need to do something special/custom? Need to distribute your changes commercially? All without paying anything? No problem.

Chariot Solutions is a software development and consulting firm focused on helping clients achieve greater success through the intelligent application of established and emerging technologies. Emphasizing the use of agile architectures based upon open standards, we deliver solutions that allow clients to react more quickly to competitive pressures and market opportunities.

Welcome to the AgileWiki Project How do you create Fluid Software Systems? For more than 35 years I have asked myself, what is the right way to program? I've learned about goto-less programming, top-down programming, object oriented programming, the Common Object Model, Java Beans, MBeans, Enterprise Java Beans, Plain Old Java Objects, and XML binding. But regardless of the approach, the software is always too rigid, the software stack is too deep, and the requirements always change in ways that require too much work. In 2002 I had the privilege of working for, and being mentored by, Norman Kashdan. By that time he had already spent 18 years developing a world view that he calls Rolonics. I believed then that there was something very right about Rolonics and have myself spent the last 5 years developing a software engineering practice around it. Finally I have come to understand [some of] its value: with a Rolonic approch to software engineering we can create highly configurable, fluid software systems that can change on-the-fly to meet ever changing requirements.

Agile Development is one of the big buzzwords of the software development industry. But what exactly is it? Agile Development is a different way of managing software development projects. The key principles, and how Agile Development fundamentally differs from a more traditional Waterfall approach to software development, are as follows:

There is, of course, no shortage of management tools for Agile software development. But none of them seem to be targeted at developers, small teams, or first-level managers. They seem to attempt to implement in software everything in any particular Agile methodology (for example Scrum and XP). They attempt to manage across the entire organization, especially highlighting managing above the project to the program and enterprise levels and in doing so become mostly an effort tracking system where developers become resources and are simply required to enter time spent on tasks. They also attempt to track all aspects of development by integrating testing (test tasks and test results) and defect tracking. By being all things to all people, the eventual interface become useless for a developer in their day-to-day development. By trying to provide a "complete" picture of a project's status, their interfaces become a mass of "percent complete" statistics where any particular stat one is looking for is not quickly identifiable.

jeanda stands for "Java Efficiency and Agility Analysis". It is a set of ant tasks and supporting Java code which are intended to be inserted into project builds. When inserted, it compares the .class files in the build fileset with previous builds, with the help of BCEL. It is intended to be fast, relatively space efficient, and non-intrusive - if successful in these respects, then it will not inhibit project builds. And, as long as it does not hinder project builds, then it has the capability to provide useful raw experimental data from a variety of Java development projects.

The project specification can be defined in word processor format as you would normally. By adding some special items, such as titled bulleted lists and highlighted text items, both a test suite and glossary can be written right into the spec. The Arbiter server will parse these documents and run the tests, reporting the results into the documents themselves. This allows the client to see project process.

Test driven development (TDD) is emerging as one of the most successful developer productivity enhancing techniques to be recently discovered. The three-step: write test, write code, refactor – is a dance many of us are enjoying. This site is dedicated to promoting techniques, tools, and general good will in the test-driven community.

Great ! - You're into Extreme Programming. You've written the tests ( JUnit of course). You've done the most simple thing that could possibly work. You've even shared your keyboard with a colleague. But have you done enough?

In this heady age of rapid technological change, we all struggle to maintain our bearings. The developments that unfold each day in communications and computing can be thrilling and disorienting. One understandable reaction is to wonder: Are these changes good or bad? Should we welcome or fear them?

EasyMock provides Mock Objects for interfaces in JUnit tests by generating them on the fly using Java's proxy mechanism. Due to EasyMock's unique style of recording expectations, most refactorings will not affect the Mock Objects. So EasyMock is a perfect

StoryTestIQ (a.k.a. 'STIQ') is a tool for creating "Executable Requirements" which have also been known as acceptance tests or functional tests. STIQ was developed based on two other open source acceptance testing tools, Selenium and FitNesse. This combin

Selenium is a test tool for web applications. Selenium tests run directly in a browser, just as real users do. And they run in Internet Explorer, Mozilla and Firefox on Windows, Linux, and Macintosh. No other test tool covers such a wide array of platform