Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/21/d192906962/htdocs/agileux/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/21/d192906962/htdocs/agileux/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/21/d192906962/htdocs/agileux/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/21/d192906962/htdocs/agileux/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/21/d192906962/htdocs/agileux/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 339
workshops | Agile UX
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 339


Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-content/themes/bible-scholar/header.php on line 50
Monday, April 23, 2018

Subscribe to the RSS Feed


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

A Speed Boat or nothing…

Posted by jc-Qualitystreet on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55
2011/10/17


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 430

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 410

Deprecated: Function split() is deprecated in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 413

Speed ​​Boat is one of the “Innovation games“, one of those games that, like Product Vision Box , Remember the future or Buy a feature, is very useful during our Agile and UX workshops.

Speedboat is an interactive, collective and funny way to identify constraints, obstacles, problems with our product or our project, then to prioritize actions in order to remove them!

Speed boat, a boat with many facets…

The advantage of the Speed ​​Boat metaphor is that the game can be very useful in a lot of contexts. Indeed, our boat is appropriate to represent our development project (which does not advance for some reason…), our product, subject to criticisms and comments of its users or the team in charge to bring agility to the organization.

Result of our Speedboat WorkShop ...The goal is the Agile Enterprise

Result of our Speedboat WorkShop ...The goal is the Agile Enterprise

The rules of the game

  • Draw a speed boat on a whiteboard or poster
  • The boat is our system, our product, our project or our team, so name it (Here, the boat is our Agile transition team)
  • Of course, the objective of the Speed ​​boat (our product…) is to go fast (for best performance). So I first ask the participants to describe us precisely what characterizes the optimal performance, the desirable conditions (yellow notes attached to the port or on the island that the boat needs to reach)
  • The boat position represents today and the distance between the boat and the island can be seen as an indicator (not in our case)
  • The anchors represent the obstacles slowing the movement of our boat: impediments or things that our customers or users do not like about our product and affect its optimal functioning. The more they are low under the water, the more they are strong (well, up to you to follow this rule!)
  • The green arrows represent positive elements that push our boat

Facilitation

Several variations exist. Here is mine

  • Steps 1 & 2 After the opening and introduction of the game, I usually ask participants to work individually or in pairs (depending on group size) on the goal (desirable conditions) and the positive factors then to present their work to others.
  • Step 3: Then, individually or in small groups it is time to characterize the anchors (obstacles, constraints, things we don’t like)
  • Step 4: The work done, I ask the participants to post their anchors on the wall.
  • Step 5:  Collective consolidation and anchors prioritization
  • Step 6: I usually close the game with an action plan to set up to remove the major anchors!

In short, we generally have a good time playing that game: enjoyable, useful but also very effective!


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Paper Prototyping Workshop

Posted by jc-Qualitystreet on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55
2010/10/13


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

One more time… and in small groups please: more fun, more feedback and more information collected even if you need more preparation effort (related to realistic content, screenshots and elements cutting, materials provided).

Workshop de conception : Prototypage Papier avec sous groupes de travail

Design Workshop :Paper prototyping in small groups

At a time when others are still searching and waiting for the magic prototyping tool to make wireframe, Paper prototyping deliberately focuses on proximity, human interactions, feedback, collaboration, and simplicity… some core agile values.

According to me, even more in Agile contexts, the real strength of Wireframe format is on its ability:

  • To be done in a collaborative mode,
  • To generate feedback,
  • To share the Vision of  the User interface
  • To support business and development activities
  • To stay at a “just enough” level (documentation, process, effort…)

And this is exactly what paper prototyping offers…

Moreover, Paper prototyping technique is FAST, EASY and FLEXIBLE (in terms of protocols…).

This is what I have observed in some group sessions:

  • It is highly collaborative with a rich feedback generation (especially for group sessions)
  • It enables  multi disciplinary teams, various actors to get a common vision,
  • It reduces communication issues: we do it in groups, face to face, in the same room…
  • It fosters creativity by giving the impression that nothing is fixed and that we can change things easily
  • It’s interactive and fun with direct manipulation and collective activities (far from the passivity of some traditional meetings)
  • It is adaptive and scalable with various facilitation techniques adjusted to different contexts

To conclude, take a look at this huge session of paper prototyping:


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55

Involve me and I’ll understand

Posted by jc-Qualitystreet on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/21/d192906962/htdocs/agileux/wp-includes/functions.php on line 55
2009/01/08


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/21/d192906962/htdocs/agileux/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 440

Tell me and I’ll forget
Show me and I may remember
Involve me  and I’ll understand

A Chinese quote and a principle that we should apply everyday on our projects. So encourage good learning, seek maximum cooperation, stimulate interactions, raise the feedback… ENGAGE clients and stakeholders in order to make our intervention really valuable !