{section}
{column}
h2. Introduction
{panel:title=Mission statement| borderStyle=solid| borderColor=#512B1B| titleBGColor=#cccccc| bgColor=#eeeeee}
The purpose of this wiki is to create processes, techniques and technology which, in combination, will provide cost efficient and easy-to-adopt bootstrapping environments. The starting point is agile methodology, but the focus is to solve the challenges in the enterprise under realistic conditions. By this we mean extending/strengthen the [agile manifesto|http://agilemanifesto.org/] with:
* evolve ability and *maintainability* over project heroes
* sustainability and total customer *value* over features and glass bowl project focus
* facts and *knowledge* over religion and preaching
{panel}
{panel:title=Where to begin| borderStyle=solid| borderColor=#512B1B| titleBGColor=#cccccc| bgColor=#eeeeee}
Even if your project do not fall into the sustainable or enterprise category, there should be *plenty of valuable advice* here which will prove useful. Our featured articles below provide some starting points, or you can search for topics.
{contentbylabel:featured|key=dev|showLabels=false|showSpace=false}
{livesearch:id=1|spaceKey=dev}
{panel}
{column}
{column}
{include:Navigation}
{column}
{section}
h2. Structure of this wiki-space
We are still debating an information architecture for the content of this site and value your feedback and suggestions.
{gliffy:name=Agile 2.0 structure|align=center|size=L}
{table-plus}
|| Name || Description || Completeness of documentation ||
| [Tactics] | The pieces of the puzzle, pure and simple | |
| [Evaluation of tactics according to organizational drivers] | A guide to which tactics are easy/difficult to implement to different organizations | |
| [architecture:Agile and Software Architecture] | Recommendations on how to ensure sound architecture and system design when doing "agile projects" | |
| [Agile Mindset and Methodology] | Most of the agile methodology aspects | |
| [Strategies] |How to combines tactics, methodology and architecture suited to solve a problem according to given drivers | |
{table-plus}
h4. Other challenges
The following are research areas that will generate results according to the above structure.
* [Test] - Advanced testing and continuous integration
* [Agile projects and contracts] - How contracts influence projects and how to be agile within specific standard contracts
* [Deployment and Configuration]
* [Collect and/or develop recommendations for common problems | Other]
** [Logging]
** [Error Handling And Exception Management]
{column}
h2. Introduction
{panel:title=Mission statement| borderStyle=solid| borderColor=#512B1B| titleBGColor=#cccccc| bgColor=#eeeeee}
The purpose of this wiki is to create processes, techniques and technology which, in combination, will provide cost efficient and easy-to-adopt bootstrapping environments. The starting point is agile methodology, but the focus is to solve the challenges in the enterprise under realistic conditions. By this we mean extending/strengthen the [agile manifesto|http://agilemanifesto.org/] with:
* evolve ability and *maintainability* over project heroes
* sustainability and total customer *value* over features and glass bowl project focus
* facts and *knowledge* over religion and preaching
{panel}
{panel:title=Where to begin| borderStyle=solid| borderColor=#512B1B| titleBGColor=#cccccc| bgColor=#eeeeee}
Even if your project do not fall into the sustainable or enterprise category, there should be *plenty of valuable advice* here which will prove useful. Our featured articles below provide some starting points, or you can search for topics.
{contentbylabel:featured|key=dev|showLabels=false|showSpace=false}
{livesearch:id=1|spaceKey=dev}
{panel}
{column}
{column}
{include:Navigation}
{column}
{section}
h2. Structure of this wiki-space
We are still debating an information architecture for the content of this site and value your feedback and suggestions.
{gliffy:name=Agile 2.0 structure|align=center|size=L}
{table-plus}
|| Name || Description || Completeness of documentation ||
| [Tactics] | The pieces of the puzzle, pure and simple | |
| [Evaluation of tactics according to organizational drivers] | A guide to which tactics are easy/difficult to implement to different organizations | |
| [architecture:Agile and Software Architecture] | Recommendations on how to ensure sound architecture and system design when doing "agile projects" | |
| [Agile Mindset and Methodology] | Most of the agile methodology aspects | |
| [Strategies] |How to combines tactics, methodology and architecture suited to solve a problem according to given drivers | |
{table-plus}
h4. Other challenges
The following are research areas that will generate results according to the above structure.
* [Test] - Advanced testing and continuous integration
* [Agile projects and contracts] - How contracts influence projects and how to be agile within specific standard contracts
* [Deployment and Configuration]
* [Collect and/or develop recommendations for common problems | Other]
** [Logging]
** [Error Handling And Exception Management]