IceScrum is an J2EE application for using Scrum while keeping the spirit of a collaborative workspace. It also offers virtual boards with post-its for sprint backlog, product backlog and others.
The tool offers everything that is in Scrum :
*
The role management: Product Owner, ScrumMaster, Team member and StakeHolder
*
The product backlog management with advanced features for prioritizing stories
*
Scrum lifecycle including a roadmap view
*
Release planning
*
Sprint backlog, as a task board facilitating the Scrum ceremonial
*
Management of impediments
*
Chart production such as burndown charts, velocity charts, cumulative flow diagram
Icescrum offers others agile practices like :
* Roadmap
* Vision
* Features
* User stories
* Acceptance tests associated to stories
* User roles
* Planning poker
Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems. Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner. As you see in Figure 1 AM is meant to be tailored into other, full-fledged development methodologies such as XP or RUP, enabling you to develop a software process which truly meets your needs. The techniques of AM, in particular Agile Model Driven Development (AMDD), the lifecycle for which is depicted in Figure 2, enable you to scale agile software development to very complex situations.
The concepts
The CodeCount toolset is a collection of tools designed to automate the collection of source code sizing information. The CodeCount toolset spans multiple programming languages and utilizes one of two possible Source Lines of Code (SLOC) definitions, physical or logical.
The CodeCount toolset is provided in source code only, and may be used as is, modified or further distributed subject to certain limitations.
The tools in the collection are supplied in C source code only. You are responsible for compiling and building executable versions.
The Product
The CodeCount toolset is copyright USC Center for Software Engineering but is made available with a Limited Public License which permits the distribution of the modifications you make provided you return a copy to us so we can further enhance the toolset for the benefit of all.
Crap4j is a Java implementation of the CRAP (Change Risk Analysis and Predictions) software metric – a mildly offensive metric name to help protect you from truly offensive code.
The CRAP metric combines cyclomatic complexity and code coverage from automated tests (e.g. JUnit tests) to help you identify code that might be particularly difficult to understand, test, or maintain – the kind of code that makes developers say: “This is crap!” or, if they are stuck maintaining it, “Oh, crap!”.
The best way to learn more about CRAP and Crap4j is to check the various articles, newsgroups and blogs about them.
Streber is a free wiki driven project management tool written in php5. Freelancers and small teams can easily setup projects and keep track of tasks, issues, bugs, efforts etc. Project-User-Rights can be adjusted e.g. to provide clients a limited view of the current project state.
It supports very easy Installation with FTP.
Build. Test. Release.
Maestro - the powerful, open source-based solution stack from Mergere, brings best practices to build automation, eliminating most tedious interaction at runtime.
Based on the Apache Software Foundation's Maven, the Mergere's build platform frees developers to focus on writing applications, instead of writing build scripts. Maestro gives development teams the tools to automate, track, audit and analyze their application life cycle, to ensure that builds run from start to finish without issues -- shortening release time-lines, enhancing code quality, and enabling organizations to capture, maintain and reuse project knowledge.
Studies (eg Standish, 1995 et al) show that poor requirements are a prime cause of project failure or insufficiency, yet commercial requirements tools are very expensive. There exists no full-featured Open Source Requirements Architecture tool. This project intends to fill that gap, integrating with other Open Source CASE tools to provide a complete Open Source CASE environment.
openArchitectureWare (oAW) is a modular MDA/MDD generator framework implemented in Java(TM). It supports parsing of arbitrary models, and a language family to check and transform models as well as generate code based on them. Supporting editors are based on the Eclipse platform. OAW has strong support for EMF (Eclipse Modelling Framework) based models but can work with other models, too (e.g. UML2, XML or simple JavaBeans) At the core there is a workflow engine allowing the definition of generator/transformation workflows. A number of prebuilt workflow components can be used for reading and instantiating models, checking them for constraint violations, transforming them into other models and then finally, for generating code.
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?
From the most interesting company in the IT area... "Continuous Integration, Source Control, a Wiki and a Bug-Tracker are all cornerstones of a functioning Agile development project. But if you've not configured them all before, it can be a bit tricky - a
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
This article finally pins down the elusive Maven 2 POM, version 4.0, the single largest configuration file you are likely ever to love. Readers will learn that the successful Maven 2 build system derives much of its power and portability from the POM, and
Joel on SW article, one argument is quite useful regarding the ongoing outsourcing discussion. Anyway, the most funny thing is, that Mozart did NOT write the whole Requiem, only Inroitus and Kyrie, the rest is Eybler and Süßmayr.
Very interesting article, seems to be an extract of the author's book on rapid sw development from 1996 (sic). Many points (especially #4 e.g.) look quite familiar to me.
M. Glinz. IWSSD '00: Proceedings of the 10th International Workshop on Software Specification and Design, page 11. Washington, DC, USA, IEEE Computer Society, (2000)