Uncategorized

Introducing Adobe WorkflowLab

Having returned from this year’s monstrous MAX in Los Angeles (monstrous due to the vast amount of sessions and networking).
One of the major impressions is the focus all of Adobe seem to have had throughout the past year on working smarter – not harder. This has reflected itself into every product and every aspect of the “Adobe Lifestyle” effectively offering opportunities and challenges to all of us making a living and life off the Adobe ecosystem.

One very obvious results of this thinking and focus at Adobe is the ALPHA release of the Adobe WorkflowLab, created by Mr. Doug Winnie and his team of skilled designers and developers.

Adobe WorkflowLab Icon

The Workflow below is the workflow actually used to create WorkflowLab, its one of the many templates installed with the application itself… in all modesty a cool way of sharing this information with the community as well as a way of illustrating the willingness and ability to drink ones own cool-aid.

Adobe Workflow Behind WorkflowLab Screendumb

The screen below is the startup screen meeting the user after starting WorkflowLab, as you can see on the right side, it comes with a number of ready-made workflows which will allow people to get off on the right foot when starting a project type that they have not done before.

WorkflowLab Startup Screen

Adobe WorkflowLab is already available in a very early ALPHA release on Adobe Labs… Check it out…
http://labs.adobe.com/technologies/workflowlab/

Uncategorized

Mapping Design and Develop Disciplines… Team Competencies

In continuation of mapping my own competencies, I have taken the liberty of mapping a couple of my colleagues whom are obvious to compliment me…

Its an exercise intended to give it a shot at using the matrix as a team constellation practice. However, instead of using the circle diagram defined by Dough Winnie, I have used the Radarchart from the ILog Data Visualization package.

2009-07-06_2347

The data are easy to make, the results are easy to understand and since the results might be of some relevance I intend to continue mapping a couple of our existing teams and the hold them against a radar diagram representing the project characteristics, and then see if the project-team is wrongly configured…

If the configuration above had been taken from a real project, its likely we could have been able to state that all bases were covered, at least to some extend…

You can check the small applet out here… or by clicking on the picture above…
http://petermolgaard.com/projects/competencematrix/OurCompetencies.html

Tools

Adobe "Thermo"

Both before and after Adobe MAX Europe 2007 we have discussed which role Thermo is going to play in the integration between the graphics department and the development department.
To clarify a couple of things Narciso Jaramillo has posted some of his thoughts on his blog which are worth reading if interested in the emergence of Thermo.

Check it out:
http://www.rictus.com/muchado/2007/10/07/thoughts-on-thermo/

Note:
Narciso is part of the Adobe Flex Team.

Uncategorized

The Daily Motivator : 10 Ways for a Web Worker to Achieve Work-Life Balance

Som en af de der hyppigt ligger i toppen af den ugentlige inddaterings-summering i det firma jeg er tilknyttet tager jeg mig den frihed at dele denne artikel med jer.

Det er helt almindelig viden, men da det efterhånden er påvist udover nogen tvivl at produktiviteten (for slet ikke at nævne livskvaliteten) sænkes såfremt man glemmer at udøve fysisk udfoldelse samt at have et ikke-arbejdsrelateret liv gør det vel ikke noget at minde os selv og hinanden om det en gang imellem.

http://webworkerdaily.com/2007/09/14/10-ways-for-a-web-worker-to-achieve-work-life-balance/

Uncategorized

Indhold i en af vores standard RUP iterationer

Nedenstående er det overordnede format for iterationer vi arbejder med på et RUP projekt.

1. Assessment og eventuel tilpasning af processen.
2. Vurdering af use cases fra foregående iteration om de skal videreimplementeres i denne implementation.
3. Planlægning af iteration.
4. Implementation af eventuelle kritiske rester fra foregående iteration.
5. Implementation af use cases for iteration.
6. Etablering af baseline (executable, codebase og database ).
7. Review af iterationens resultater.
8. Opdatering af prioriteter samt krav baseret på resultatet af review.

Vi arbejder fortrinsvist med iterationer af 2 ugers varighed og vi oplever at ovenstående giver en god sammenhæng i en iteration og 2 ugers iterationerne giver en gunstig rytme på vores projekter.