John Fisher's Process of Personal Transition Curve, and Personal Construct Psychology Theory explanation, plus more free online business training materials and tools for personal and organizational development.
Für erfolgreiches Change Management ist von entscheidender Bedeutung, dass der Kommunikationsfaden zwischen den Geschäftsleitung, Projektteams und dem "Rest der Menschheit" nicht abreißt - zumal dieser Rest in Großunternehmen aus einigen Zehntausend Mitarbeitern und Führungskräften bestehen kann.
Fokus Hochschulen, Themenschwerpunkt Personal- und Organisationsentwicklung
zwischen aktiver Positionierung und
systemischer Bescheidenheit
...aus 8 Perspektiven (u.a. Artikel "Entwicklung erfordert Flexibilität und Stabilität
Neue Steuerungs- und Lösungsmodelle"
Calm stands for…
Seascape Calm Weather
Seascape Calm Weather
…Calm Application Lifecycle Management, which stands for Calm Application Lifecycle Management Application Lifecycle Management … ehm just kidding ;)
Calm is an early implementation of main ALM use cases on an Open Source and collaborative framework based on Apache Maven.
What exactly is Maven Calm
Maven Calm is not just a Corporate POM. It’s a cross-corporate POM which provides lifecycle-oriented configuration for your Maven Plugins; the best way to start is having a look at the presentation! In short, your Project or Corporate POM should look like this to inherit all the ALM oriented behaviors.
iston eases your vendor branch management worries. A vendor branch is when you copy a vendor's code (plugins, gems, etc) inside your own repository / project.
What are the advantages of doing that?
* You don't depend on another repository to deploy to your staging or production machines;
* You are insulated from upstream changes, until you really want those changes and have a chance to test them;
* Piston allows you to apply local patches to your vendor code, until the upstream maintainers have applied them.
It is currently common to build a number of releases from a single code base. For example, a development release, a QA release, a production release and perhaps customer-specific releases. However, these releases seem to differ mostly in the contents of their XML configuration files, and then only very little. Maintaining all these slightly different configuration files is a real nuisance.
XConf was created to simplify this maintenance. Its fundamental premise is that a single development-release (or production-release) configuration file is created and maintained, and is processed by XConf at either build or deployment time into an appropriate release by applying one or more XML-based scripts. Each script contains only the differences required to create the appropriate release, thus removing the need for the mass duplication of configuration files.
This is not really a new solution, since XSLT has been used in the past to do this quite successfully, but XPath can get a little arcane, and maintaining transformation scripts using XSLT can become really complex very quickly. XConf uses a very simple and compact method of specifying elements that need to be processed, and provides some very useful constructs to make transformations painless.
Shotoku is designed to provide easy access to content repositories in which you can store data, bind metadata, revision content, and provide branching and merging strategies. This means Shotoku can interface with repositories such as the Java Content Repo
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